Mailinglist Archive: opensuse-buildservice (253 mails)

< Previous Next >
[opensuse-buildservice] Is there a server problem (Error: can't get ............)
  • From: Richard Bos <radoeka@xxxxxxxxx>
  • Date: Wed, 22 Nov 2006 20:34:21 +0100
  • Message-id: <200611222034.22329.radoeka@xxxxxxxxx>
I get this output, after starting the build for wireshark:
Putting files in AC_CONFIG_AUX_DIR, `..'.
Error: can't
get 'https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log?nostream=1&start=15004'
HTTP Error 500: Internal Server Error

Debugging output follows.
url:
https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log?nostream=1&start=15004
response:
[left out the debug output]

And this for 10.1

Requires: wireshark = 0.99.4
Obsoletes: ethereal-devel
Checking for unpackaged
file(s): /usr/lib/rpm/check-files /var/tmp/wireshark-0.99.4-build
warning: Could not canonicalize hostname: build08
Wrote: /usr/src/packages/SRPMS/wireshark-0.99.4-7.1.src.rpm
Wrote: /usr/src/packages/RPMS/x86_64/wireshark-0.99.4-7.1.x86_64.rpm
Error: can't
get 'https://api.opensuse.org/result/home:rbos/SL-10.1_x86_64/wireshark/x86_64/log?nostream=1&start=2831017'
HTTP Error 500: Internal Server Error
[left out the debug output]

# osc results
wireshark> osc results
SL-10.0_i586 i586 failed:
https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log
SL-10.0_x86_64 x86_64 failed:
https://api.opensuse.org/result/home:rbos/SL-10.0_x86_64/wireshark/x86_64/log
SL-10.1_i586 i586 succeeded
SL-10.1_x86_64 x86_64 building
SL-9.3_i586 i586 disabled
SL-9.3_x86_64 x86_64 disabled
SLES_9 x86_64 disabled
SLES_9 i586 disabled
SLE_10 x86_64 expansion error: nothing provides libadns-devel
SLE_10 i586 expansion error: nothing provides libadns-devel


Server problem?

--
Richard Bos
Without a home the journey is endless
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups