[opensuse-factory] What the heck is buildservice "lamb64 failed"?
New build service error on package that built fine 5 days ago: [ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img [ 42s] [ 42s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:18 UTC 2017. [ 42s] [ 42s] ### VM INTERACTION START ### [ 45s] [ 36.694037] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:21 UTC 2017. [ 45s] What is lamb67? (it should be fed to the wolves...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08/16/2017 01:30 AM, David C. Rankin wrote:
New build service error on package that built fine 5 days ago:
[ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img [ 42s] [ 42s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:18 UTC 2017. [ 42s] [ 42s] ### VM INTERACTION START ### [ 45s] [ 36.694037] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:21 UTC 2017. [ 45s]
What is lamb67? (it should be fed to the wolves...)
Sorry for the Title Typo, it's lamb67, what is that? Package builds just fine locally, and built fine before the /usr/share/gtkwrite/img directory was added. What is 'directories not owned by a package:' (the directory is owned by whoever git-hub (at git-hub) sets the directory ownership to, I have no control over that...) Is there something else I need to do in the spec other than: %install # %makeinstall install -m 755 -d $RPM_BUILD_ROOT/%{_bindir} install -m 755 bin/%{name} $RPM_BUILD_ROOT/%{_bindir} install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite_light.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.png $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.ico $RPM_BUILD_ROOT/usr/share/gtkwrite/img << last dir and two files above are new >> %clean rm -rf %{buildroot} %files %defattr(-,root,root) /usr/bin/gtkwrite /usr/share/gtksourceview-2.0/styles/gtkwrite.xml /usr/share/gtksourceview-2.0/styles/gtkwrite_light.xml /usr/share/gtkwrite/img/gtkwrite.png /usr/share/gtkwrite/img/gtkwrite.ico %doc README.md gpl-2.0.txt -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Aug 16, 2017 at 01:40:41AM -0500, David C. Rankin wrote:
On 08/16/2017 01:30 AM, David C. Rankin wrote:
New build service error on package that built fine 5 days ago:
[ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img [ 42s] [ 42s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:18 UTC 2017. [ 42s] [ 42s] ### VM INTERACTION START ### [ 45s] [ 36.694037] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:21 UTC 2017. [ 45s]
What is lamb67? (it should be fed to the wolves...)
Sorry for the Title Typo, it's lamb67, what is that? Package builds just fine locally, and built fine before the /usr/share/gtkwrite/img directory was added. What is 'directories not owned by a package:'
(the directory is owned by whoever git-hub (at git-hub) sets the directory ownership to, I have no control over that...)
Is there something else I need to do in the spec other than:
%install # %makeinstall install -m 755 -d $RPM_BUILD_ROOT/%{_bindir} install -m 755 bin/%{name} $RPM_BUILD_ROOT/%{_bindir} install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite_light.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.png $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.ico $RPM_BUILD_ROOT/usr/share/gtkwrite/img
<< last dir and two files above are new >>
%clean rm -rf %{buildroot}
%files %defattr(-,root,root) /usr/bin/gtkwrite /usr/share/gtksourceview-2.0/styles/gtkwrite.xml /usr/share/gtksourceview-2.0/styles/gtkwrite_light.xml /usr/share/gtkwrite/img/gtkwrite.png /usr/share/gtkwrite/img/gtkwrite.ico %doc README.md gpl-2.0.txt
lamb* are some of the hostnames of our buildcluster. You need to add: %dir /usr/share/gtkwrite %dir /usr/share/gtkwrite/img in the filelist. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi On 16/08/17 16:10, David C. Rankin wrote:
On 08/16/2017 01:30 AM, David C. Rankin wrote:
New build service error on package that built fine 5 days ago:
[ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img [ 42s] [ 42s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:18 UTC 2017. [ 42s] [ 42s] ### VM INTERACTION START ### [ 45s] [ 36.694037] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:21 UTC 2017. [ 45s]
What is lamb67? (it should be fed to the wolves...)
lamb67 is the name of the machine used to build your package the actual error is slightly above [ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img
Sorry for the Title Typo, it's lamb67, what is that? Package builds just fine locally, and built fine before the /usr/share/gtkwrite/img directory was added. What is 'directories not owned by a package:'
(the directory is owned by whoever git-hub (at git-hub) sets the directory ownership to, I have no control over that...)
Is there something else I need to do in the spec other than:
%install # %makeinstall install -m 755 -d $RPM_BUILD_ROOT/%{_bindir} install -m 755 bin/%{name} $RPM_BUILD_ROOT/%{_bindir} install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite_light.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.png $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.ico $RPM_BUILD_ROOT/usr/share/gtkwrite/img
<< last dir and two files above are new >>
%clean rm -rf %{buildroot}
%files %defattr(-,root,root) /usr/bin/gtkwrite /usr/share/gtksourceview-2.0/styles/gtkwrite.xml /usr/share/gtksourceview-2.0/styles/gtkwrite_light.xml /usr/share/gtkwrite/img/gtkwrite.png /usr/share/gtkwrite/img/gtkwrite.ico %doc README.md gpl-2.0.txt
Unless /usr/share/gtkwrite/ is written to by other packages as well you should just list that directory rather then all the files in it but best practice would be to use the "%{_datadir}" macro instead so you would end up with something like: %files %defattr(-,root,root) %doc README.md gpl-2.0.txt %{_bindir}/gtkwrite %{_datadir}/gtksourceview-2.0/ %{_datadir}/gtkwrite/ Unless %{_datadir}/gtksourceview-2.0/ can be written too by multiple packages. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Den 2017-08-16 kl. 08:40, skrev David C. Rankin:
On 08/16/2017 01:30 AM, David C. Rankin wrote:
New build service error on package that built fine 5 days ago:
[ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img [ 42s] [ 42s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:18 UTC 2017. [ 42s] [ 42s] ### VM INTERACTION START ### [ 45s] [ 36.694037] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:21 UTC 2017. [ 45s]
What is lamb67? (it should be fed to the wolves...)
It's one of the workers (VM) for the open build service. The status can be seen here https://build.opensuse.org/monitor Cause of the power down you need to check with the open build service infrastructure team. Quickest way would be to reach out on IRC. irc://irc.freenode.net/openSUSE-buildservice ref. http://openbuildservice.org/support/ PS. I've got no insight in open build service infrastructure I just did some fault isolation a while back myself. DS. -- /bengan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Aug 16 2017, "David C. Rankin"
What is lamb67? (it should be fed to the wolves...)
It's the name of the build worker. https://build.opensuse.org/monitor Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08/16/2017 01:40 AM, David C. Rankin wrote:
On 08/16/2017 01:30 AM, David C. Rankin wrote:
New build service error on package that built fine 5 days ago:
[ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img [ 42s] [ 42s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:18 UTC 2017. [ 42s] [ 42s] ### VM INTERACTION START ### [ 45s] [ 36.694037] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:21 UTC 2017. [ 45s]
What is lamb67? (it should be fed to the wolves...)
Sorry for the Title Typo, it's lamb67, what is that? Package builds just fine locally, and built fine before the /usr/share/gtkwrite/img directory was added. What is 'directories not owned by a package:'
(the directory is owned by whoever git-hub (at git-hub) sets the directory ownership to, I have no control over that...)
Is there something else I need to do in the spec other than:
%install # %makeinstall install -m 755 -d $RPM_BUILD_ROOT/%{_bindir} install -m 755 bin/%{name} $RPM_BUILD_ROOT/%{_bindir} install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite_light.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.png $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.ico $RPM_BUILD_ROOT/usr/share/gtkwrite/img
<< last dir and two files above are new >>
%clean rm -rf %{buildroot}
%files %defattr(-,root,root) /usr/bin/gtkwrite /usr/share/gtksourceview-2.0/styles/gtkwrite.xml /usr/share/gtksourceview-2.0/styles/gtkwrite_light.xml /usr/share/gtkwrite/img/gtkwrite.png /usr/share/gtkwrite/img/gtkwrite.ico %doc README.md gpl-2.0.txt
Now the error has changed to cloud126, e.g. [ 62s] ... checking for files with abuild user/group [ 62s] ... running 00-check-install-rpms [ 62s] ... installing all built rpms [ 62s] Preparing packages... [ 62s] gtkwrite-0.1.6-7.1.x86_64 [ 62s] ... running 01-check-debuginfo [ 62s] ... testing for empty debuginfo packages [ 62s] ... running 02-check-gcc-output [ 62s] ... testing for serious compiler warnings [ 62s] (using /usr/lib/build/checks-data/check_gcc_output) [ 62s] (using //.build.log) [ 62s] [ 62s] I: File is compiled without RPM_OPT_FLAGS [ 62s] W: gtkwrite no-rpm-opt-flags <cmdline>:gtk_toolbar.c, gtk_settings.c, gtk_findreplace.c, gtk_sourceview.c, gtk_print.c, gtk_goto.c, gtkwrite.c, gtk_common_dlg.c, gtk_menu.c, gtk_statusbar.c, gtk_filebuf.c, gtk_windef.c, gtk_appdata.c, gtk_filemon.c [ 62s] ... running 03-check-binary-kernel-log [ 62s] ... running 04-check-filelist [ 62s] ... checking filelist [ 62s] gtkwrite-0.1.6-7.1.x86_64.rpm: directories not owned by a package: [ 62s] - /usr/share/gtkwrite [ 62s] - /usr/share/gtkwrite/img [ 62s] [ 62s] cloud126 failed "build gtkwrite.spec" at Wed Aug 16 06:54:12 UTC 2017. [ 62s] [ 62s] ### VM INTERACTION START ### [ 65s] [ 49.219174] reboot: Power down [ 72s] ### VM INTERACTION END ### [ 72s] [ 72s] cloud126 failed "build gtkwrite.spec" at Wed Aug 16 06:54:22 UTC 201 Back to square one... What to try? Any links to the error messages? Where to look? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-08-16 09:05, David C. Rankin wrote:
On 08/16/2017 01:40 AM, David C. Rankin wrote:
On 08/16/2017 01:30 AM, David C. Rankin wrote:
New build service error on package that built fine 5 days ago:
[ 42s] gtkwrite-0.1.6-5.1.x86_64.rpm: directories not owned by a package: [ 42s] - /usr/share/gtkwrite [ 42s] - /usr/share/gtkwrite/img [ 42s] [ 42s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:18 UTC 2017. [ 42s] [ 42s] ### VM INTERACTION START ### [ 45s] [ 36.694037] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb67 failed "build gtkwrite.spec" at Wed Aug 16 05:09:21 UTC 2017. [ 45s]
What is lamb67? (it should be fed to the wolves...)
Sorry for the Title Typo, it's lamb67, what is that? Package builds just fine locally, and built fine before the /usr/share/gtkwrite/img directory was added. What is 'directories not owned by a package:'
(the directory is owned by whoever git-hub (at git-hub) sets the directory ownership to, I have no control over that...)
Is there something else I need to do in the spec other than:
%install # %makeinstall install -m 755 -d $RPM_BUILD_ROOT/%{_bindir} install -m 755 bin/%{name} $RPM_BUILD_ROOT/%{_bindir} install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 644 styles/gtkwrite_light.xml $RPM_BUILD_ROOT/usr/share/gtksourceview-2.0/styles install -m 755 -d $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.png $RPM_BUILD_ROOT/usr/share/gtkwrite/img install -m 644 img/gtkwrite.ico $RPM_BUILD_ROOT/usr/share/gtkwrite/img
<< last dir and two files above are new >>
%clean rm -rf %{buildroot}
%files %defattr(-,root,root) /usr/bin/gtkwrite /usr/share/gtksourceview-2.0/styles/gtkwrite.xml /usr/share/gtksourceview-2.0/styles/gtkwrite_light.xml /usr/share/gtkwrite/img/gtkwrite.png /usr/share/gtkwrite/img/gtkwrite.ico %doc README.md gpl-2.0.txt
Now the error has changed to cloud126, e.g.
[ 62s] ... checking for files with abuild user/group [ 62s] ... running 00-check-install-rpms [ 62s] ... installing all built rpms [ 62s] Preparing packages... [ 62s] gtkwrite-0.1.6-7.1.x86_64 [ 62s] ... running 01-check-debuginfo [ 62s] ... testing for empty debuginfo packages [ 62s] ... running 02-check-gcc-output [ 62s] ... testing for serious compiler warnings [ 62s] (using /usr/lib/build/checks-data/check_gcc_output) [ 62s] (using //.build.log) [ 62s] [ 62s] I: File is compiled without RPM_OPT_FLAGS [ 62s] W: gtkwrite no-rpm-opt-flags <cmdline>:gtk_toolbar.c, gtk_settings.c, gtk_findreplace.c, gtk_sourceview.c, gtk_print.c, gtk_goto.c, gtkwrite.c, gtk_common_dlg.c, gtk_menu.c, gtk_statusbar.c, gtk_filebuf.c, gtk_windef.c, gtk_appdata.c, gtk_filemon.c [ 62s] ... running 03-check-binary-kernel-log [ 62s] ... running 04-check-filelist [ 62s] ... checking filelist [ 62s] gtkwrite-0.1.6-7.1.x86_64.rpm: directories not owned by a package: [ 62s] - /usr/share/gtkwrite [ 62s] - /usr/share/gtkwrite/img
The three lines above are your error, see the instructions you received earlier and add the directories to your spec file. cloud126 is the host building.
[ 62s] [ 62s] cloud126 failed "build gtkwrite.spec" at Wed Aug 16 06:54:12 UTC 2017. [ 62s] [ 62s] ### VM INTERACTION START ### [ 65s] [ 49.219174] reboot: Power down [ 72s] ### VM INTERACTION END ### [ 72s] [ 72s] cloud126 failed "build gtkwrite.spec" at Wed Aug 16 06:54:22 UTC 201
Back to square one... What to try? Any links to the error messages? Where to look?
-- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Now the error has changed to cloud126, e.g.
You're focusing on the wrong part of the error log.
[ 62s] ... checking for files with abuild user/group [ 62s] ... running 00-check-install-rpms [ 62s] ... installing all built rpms [ 62s] Preparing packages... [ 62s] gtkwrite-0.1.6-7.1.x86_64 [ 62s] ... running 01-check-debuginfo [ 62s] ... testing for empty debuginfo packages [ 62s] ... running 02-check-gcc-output [ 62s] ... testing for serious compiler warnings [ 62s] (using /usr/lib/build/checks-data/check_gcc_output) [ 62s] (using //.build.log) [ 62s] [ 62s] I: File is compiled without RPM_OPT_FLAGS [ 62s] W: gtkwrite no-rpm-opt-flags <cmdline>:gtk_toolbar.c, gtk_settings.c, gtk_findreplace.c, gtk_sourceview.c, gtk_print.c, gtk_goto.c, gtkwrite.c, gtk_common_dlg.c, gtk_menu.c, gtk_statusbar.c, gtk_filebuf.c, gtk_windef.c, gtk_appdata.c, gtk_filemon.c [ 62s] ... running 03-check-binary-kernel-log [ 62s] ... running 04-check-filelist [ 62s] ... checking filelist [ 62s] gtkwrite-0.1.6-7.1.x86_64.rpm: directories not owned by a package: [ 62s] - /usr/share/gtkwrite [ 62s] - /usr/share/gtkwrite/img
This is where the error happens, at this point the rpmbuild has exited with an error code. This error is telling you that those two files have been installed into %{buildroot} but aren't owned by any package defined in the spec file. As Marcus told you earlier, a simple fix is to add: %dir /usr/share/gtkwrite %dir /usr/share/gtkwrite/img To your %files section.
[ 62s] [ 62s] cloud126 failed "build gtkwrite.spec" at Wed Aug 16 06:54:12 UTC 2017. [ 62s] [ 62s] ### VM INTERACTION START ### [ 65s] [ 49.219174] reboot: Power down [ 72s] ### VM INTERACTION END ### [ 72s] [ 72s] cloud126 failed "build gtkwrite.spec" at Wed Aug 16 06:54:22 UTC 201
And this section is just noting that the build on that particular VM host has failed. Builds are scheduled to random VM hosts, so it's not surprising at all that the "error text" changed, because that "error text" is just telling you what VM host the build failed on. I'm very surprised that the build works on your local machine, because directories unowned by a particular package -- Aleksa Sarai Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-08-16 11:03, Aleksa Sarai wrote:
I'm very surprised that the build works on your local machine, because directories unowned by a particular package
Rather trivial: .oscrc can have a line "extra-pkgs" which can satisfy the directory ownership. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 16-08-2017 a las 3:30, David C. Rankin escribió:
What is lamb67? (it should be fed to the wolves...)
Heh..the ambiguities in the logs.. it should say something like "build gtkwrite.spec" failed on build host: $(hostname) at $(date -u --iso-8601=seconds) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2017-08-17 22:32, Cristian Rodríguez wrote:
El 16-08-2017 a las 3:30, David C. Rankin escribió:
What is lamb67? (it should be fed to the wolves...)
Heh..the ambiguities in the logs.. it should say something like
"build gtkwrite.spec" failed on build host: $(hostname) at $(date -u --iso-8601=seconds)
Why ambiguous? The log starts exactly with a line like that. [ 1s] obs-power8-04 started "build kopano.spec" at Thu Aug 10 09:40:22 UTC 2017. So if you see it again at the end… -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 18-08-2017 a las 4:33, Jan Engelhardt escribió:
Why ambiguous? The log starts exactly with a line like that.
It isn't ambigous for you and me, since both of us are familiar with the tools and may have even coded some of it However if one isn't used to reading the logs or the source code of the build script it may become ambiguous ..what if the hostname is "cc1" or "gcc", "ld" or "icecream" ? :-D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2017-08-18 16:42, Cristian Rodríguez wrote:
Why ambiguous? The log starts exactly with a line like that.
However if one isn't used to reading the logs or the source code of the build script it may become ambiguous ..what if the hostname is "cc1" or "gcc", "ld" or "icecream" ? :-D
Then the same would still apply. Log begins with "gcc started build command `xyz`" and ends with "gcc failed xyz". The takeaway is that reading the log - and afterwards, the complete log - is usually the solution... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-08-18 20:38, Jan Engelhardt wrote:
On Friday 2017-08-18 16:42, Cristian Rodríguez wrote:
Why ambiguous? The log starts exactly with a line like that.
However if one isn't used to reading the logs or the source code of the build script it may become ambiguous ..what if the hostname is "cc1" or "gcc", "ld" or "icecream" ? :-D
Then the same would still apply. Log begins with "gcc started build command `xyz`" and ends with "gcc failed xyz".
It would be clearer to write "host 'gcc' started build command 'xyz'" or something like that. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Friday 2017-08-18 21:35, Carlos E. R. wrote:
Then the same would still apply. Log begins with "gcc started build command `xyz`" and ends with "gcc failed xyz".
It would be clearer to write "host 'gcc' started build command 'xyz'" or something like that.
I guess "patches/pull requests welcome" is an acceptable answer these days :-D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (10)
-
Aleksa Sarai -
Andreas Jaeger -
Andreas Schwab -
Bengt Gördén -
Carlos E. R. -
Cristian Rodríguez -
David C. Rankin -
Jan Engelhardt -
Marcus Meissner -
Simon Lees