Hello, I tried to compile the fox1.4 package for ubuntu and wanted to add the sources directly from the debian server http://packages.debian.org/etch/libfox1.4 Unfortunately when adding the files by URL to my obs package (like http://ftp.de.debian.org/debian/pool/main/f/fox1.4/fox1.4_1.4.34.orig.tar.gz) something went wrong, because the build process fails:
dpkg-source: error: file fox1.4_1.4.34.orig.tar.gz has md5sum 724e66b89b5451d5032165e03ff5228d instead of expected 3424b9d3f9b71e1f53e9c3822de3b76c
I checked this by downloading the file once from the debian site and once from the obs and they have different checksums indeed. The sizes are the same thus it is probably not a matter of automatic gz extraction. The diff.gz of the same package has the same problem, that's why I think there might be something wrong with the remote upload. Has anyone else encountered this problem? Is there a known workaround besides down-/uploading?
Regards, Michael
Hi Michael
On Sa 25 Okt 2008 23:44:17 CEST Michael Behrisch behrisch@informatik.hu-berlin.de wrote:
I tried to compile the fox1.4 package for ubuntu
Beside the described problems: what about working together in the X11:FOX project? I added you as maintainer already - feel free to add the missing repositories :-)
With kind regards, Lars
Am Montag, 27. Oktober 2008 20:55 schrieb Lars Vogdt:
Beside the described problems: what about working together in the X11:FOX project?
Yes, I think I could contribute my changes concerning RHEL and CentOS.
I added you as maintainer already - feel free to add the missing repositories :-)
Actually, with respect to debian/ubuntu, I think this would be duplicating efforts, since there are already debian and ubuntu packages on the debian and ubuntu servers. I just needed to rebuild them because they are in the ubuntu universe repository. Because others may have the problem as well, I would favor the idea of setting up an ubuntu universe project on obs where we just duplicate the ubuntu packages needed in their precise ubuntu config. This was already proposed earlier on this list but I didn't find anything about the status of the proposal.
Regards, Michael
Am Dienstag, 28. Oktober 2008 23:23 schrieb Michael Behrisch:
Am Montag, 27. Oktober 2008 20:55 schrieb Lars Vogdt:
Beside the described problems: what about working together in the X11:FOX project?
Yes, I think I could contribute my changes concerning RHEL and CentOS.
I tried, but somehow obs is ignoring my patch against configure.in. I added the patch-file to the package and to the spec but it is not even mentioned in the build log. Do I miss something?
Regards, Michael
On Wed, 29 Oct 2008 00:41:16 +0100, you wrote:
I tried, but somehow obs is ignoring my patch against configure.in. I added the patch-file to the package and to the spec but it is not even mentioned in the build log. Do I miss something?
You forgot to apply your patch, i.e. a
%patch2
is missing in the %prep section of fox14.spec. Without that, the patch is simply ignored.
cheers Philipp
Philipp Thomas escribió:
You forgot to apply your patch, i.e. a
%patch2
is missing in the %prep section of fox14.spec. Without that, the patch is simply ignored.
yeah, and remember to run autoreconf if you modified configure.in.. ;-)
Am Donnerstag, 30. Oktober 2008 00:55 schrieb Philipp Thomas:
On Wed, 29 Oct 2008 00:41:16 +0100, you wrote:
I tried, but somehow obs is ignoring my patch against configure.in. I added the patch-file to the package and to the spec but it is not even mentioned in the build log. Do I miss something?
You forgot to apply your patch, i.e. a
%patch2
is missing in the %prep section of fox14.spec. Without that, the patch is simply ignored.
Thank You, that solved the problem indeed.
Regards, Michael
Am Samstag, 25. Oktober 2008 23:44 schrieb Michael Behrisch:
Hello, I tried to compile the fox1.4 package for ubuntu and wanted to add the sources directly from the debian server http://packages.debian.org/etch/libfox1.4 Unfortunately when adding the files by URL to my obs package (like http://ftp.de.debian.org/debian/pool/main/f/fox1.4/fox1.4_1.4.34.orig.tar.g z) something went wrong, because the build process fails:
dpkg-source: error: file fox1.4_1.4.34.orig.tar.gz has md5sum 724e66b89b5451d5032165e03ff5228d instead of expected 3424b9d3f9b71e1f53e9c3822de3b76c
Just in case the original topic of this thread got lost ;-) Is this problem trivial or is just nobody out there using this functionality except for me?
Regards, Michael
Am Montag, 3. November 2008 21:13 schrieb Michael Behrisch:
Am Samstag, 25. Oktober 2008 23:44 schrieb Michael Behrisch:
Hello, I tried to compile the fox1.4 package for ubuntu and wanted to add the sources directly from the debian server http://packages.debian.org/etch/libfox1.4 Unfortunately when adding the files by URL to my obs package (like http://ftp.de.debian.org/debian/pool/main/f/fox1.4/fox1.4_1.4.34.orig.tar .g z) something went wrong, because the build process fails:
dpkg-source: error: file fox1.4_1.4.34.orig.tar.gz has md5sum 724e66b89b5451d5032165e03ff5228d instead of expected 3424b9d3f9b71e1f53e9c3822de3b76c
Does anyone know whether this problem still persists, because something similar happened to me again today?
Thanks for your help, Michael
On Tue, Mar 17, 2009 at 02:05:57AM +0100, Michael Behrisch wrote:
Am Montag, 3. November 2008 21:13 schrieb Michael Behrisch:
Am Samstag, 25. Oktober 2008 23:44 schrieb Michael Behrisch:
Hello, I tried to compile the fox1.4 package for ubuntu and wanted to add the sources directly from the debian server http://packages.debian.org/etch/libfox1.4 Unfortunately when adding the files by URL to my obs package (like http://ftp.de.debian.org/debian/pool/main/f/fox1.4/fox1.4_1.4.34.orig.tar .g z) something went wrong, because the build process fails:
dpkg-source: error: file fox1.4_1.4.34.orig.tar.gz has md5sum 724e66b89b5451d5032165e03ff5228d instead of expected 3424b9d3f9b71e1f53e9c3822de3b76c
Does anyone know whether this problem still persists, because something similar happened to me again today?
Debian's dsc file contains a checksum, so you need to adapt the dsc content if you change a file.
Cheers, Michael.
Am Dienstag, 17. März 2009 10:21:05 schrieb Michael Schroeder:
On Tue, Mar 17, 2009 at 02:05:57AM +0100, Michael Behrisch wrote:
Am Montag, 3. November 2008 21:13 schrieb Michael Behrisch:
Am Samstag, 25. Oktober 2008 23:44 schrieb Michael Behrisch:
Hello, I tried to compile the fox1.4 package for ubuntu and wanted to add the sources directly from the debian server http://packages.debian.org/etch/libfox1.4 Unfortunately when adding the files by URL to my obs package (like http://ftp.de.debian.org/debian/pool/main/f/fox1.4/fox1.4_1.4.34.orig .tar .g z) something went wrong, because the build process fails:
dpkg-source: error: file fox1.4_1.4.34.orig.tar.gz has md5sum 724e66b89b5451d5032165e03ff5228d instead of expected 3424b9d3f9b71e1f53e9c3822de3b76c
Does anyone know whether this problem still persists, because something similar happened to me again today?
Debian's dsc file contains a checksum, so you need to adapt the dsc content if you change a file.
I know that. The problem is, that I did not change any of the files. I just let obs download the files directly from the debian servers and they seem to be corrupted afterwards. I checked, that the checksums are correct if I download the files to my computer. I also checked that if I download the files from the obs after they have been transferred by he method mentioned above, they are corrupt (not even valid tar.gz's anymore). Am I missing something?
Regards, Michael
On Wed, Mar 18, 2009 at 05:37:26PM +0100, Michael Behrisch wrote:
I know that. The problem is, that I did not change any of the files. I just let obs download the files directly from the debian servers and they seem to be corrupted afterwards.
That can't work. The build clients are sandboxed with XEN and have no network interface.
Cheers, Michael.
Am Mittwoch, 18. März 2009 17:42 schrieben Sie:
On Wed, Mar 18, 2009 at 05:37:26PM +0100, Michael Behrisch wrote:
I know that. The problem is, that I did not change any of the files. I just let obs download the files directly from the debian servers and they seem to be corrupted afterwards.
That can't work. The build clients are sandboxed with XEN and have no network interface.
I am sorry if I did not make my point clear but the problem occurs if I use the "Remote File URI" in the "Add File" dialog of the web frontend of obs. I do not download any files during build.
Regards, Michael
Hello folks,
I just added openSUSE:Tools, openSUSE_11.1 as my repo on SLED 11, and install obs-server, obs-worker and obs-api, and I followed the wiki[0] to setup my server. visit http://127.0.42.1/
the login page showed up, but when i loged in, there is the error message[1].
what's the problem? big thanks! Ray
[0] http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/ope...
[1] Error Details: Errorcode: unknown Message: <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>500 - Internal Server Error</title> </head> <body> <h1>500 - Internal Server Error</h1> </body> </html>
Exception from Webclient: ActiveXML::Transport::Error: <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>500 - Internal Server Error</title> </head> <body> <h1>500 - Internal Server Error</h1> </body> </html> Stack Trace:
/srv/www/obs/common/lib/activexml/transport.rb:549:in `handle_response' /srv/www/obs/common/lib/activexml/transport.rb:534:in `http_do' /srv/www/obs/common/lib/activexml/transport.rb:346:in `find' /srv/www/obs/common/lib/activexml/base.rb:69:in `find' /srv/www/obs/webclient/app/controllers/application.rb:116:in `basic_auth' /srv/www/obs/webclient/app/controllers/application.rb:74:in `authorize' /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.2/lib/active_support/callbacks.rb:173:in `send' /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.2/lib/active_support/callbacks.rb:173:in `evaluate_method' /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.2/lib/active_support/callbacks.rb:161:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:191:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:591:in `run_before_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:577:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/rescue.rb:201:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:568:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/session_management.rb:130:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:389:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:149:in `handle_request' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:107:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `synchronize' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:35:in `dispatch' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:103:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:153:in `with_signal_handler' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:101:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:78:in `process_each_request' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:77:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `catch' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:50:in `process!' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:24:in `process!' /srv/www/obs/webclient/public/dispatch.fcgi:24
This is the key line. It usually happens when OBS can't talk to whatever you're using for authentication.
On Fri, 2009-03-20 at 01:20 -0600, Ray Wang wrote:
/srv/www/obs/webclient/app/controllers/application.rb:74:in `authorize'
Ray Wang schrieb:
Hello folks,
I just added openSUSE:Tools, openSUSE_11.1 as my repo on SLED 11, and install obs-server, obs-worker and obs-api, and I followed the wiki[0] to setup my server. visit http://127.0.42.1/
the login page showed up, but when i loged in, there is the error message[1].
what's the problem? big thanks!
Your api has some serious problems (it sends HTML when it should send XML).
Please look at /var/log/lighttpd/error.log and /srv/www/obs/frontend/log/production_slave.log and try again. Post anything suspicious showing up like stacktraces or lines containing the word WARNING.
Andreas
Thank you Andreas,
Your api has some serious problems (it sends HTML when it should send XML).
:( I don't know why.
Please look at /var/log/lighttpd/error.log and /srv/www/obs/frontend/log/production_slave.log and try again. Post anything suspicious showing up like stacktraces or lines containing the word WARNING.
I follow the wiki[0]'s instructions to copy all the rpms from SLED 11 DVD1 and SDK to /srv/obs/build/SLED11/standard/i586/:full/, and add a package, but it still report it could not find autoconf, gcc, blah, blah packages, so where is the path which builder search the rpms at?
[0] http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/ope... is this link the only one which is for latest distribution?, I use SLED11 and openSUSE 11.1
--- Ray Wang (王磊) Software Engineer rawang@novell.com +86 10 6533 9220
Novell Software (Beijing) Ltd Making IT Work As One www.novell.com
Hi folks,
I just find the page[0] from wiki, and that's the only one which teach you how to establish a local build service, and the latest update is for opensuse 11.0
I would like to know more about configuration. For example. 1) where could i configure what repository I could provide, and default are openSUSE11.1, openSUSE11.0, Fedora, RHEL, Mandriva, Debian, Ubuntu etc, but actually I will not provide those repository, I want to configure it, add SLES11, SLED11 instead, where could i configure the repository list?
2) according to the page[0], I could use apiurl 127.0.42.2 as my local api server by using osc but what about if i use osc on any other machine? you know, I could not use 127.0.42.2 as my apiurl on other pc...., and also, how to make the webpage ip address as my api server ip address?
So I ask a well-documented document here. does anyone help me out with that? thanks a lot!
Ray
[0] http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/ope
Hi Ray,
please let me know what's missing in /usr/share/doc/packages/obs-api/README.SETUP
In there you also find how to give the api a different virtual hostname, so you can connect to it from another machine with osc.
hth?
S.
buildservice@lists.opensuse.org
-
Andreas Bauer -
Cristian Rodríguez -
Lars Vogdt -
Luke Imhoff -
Michael Behrisch -
Michael Schroeder -
Philipp Thomas -
Ray Wang -
Susanne Oberhauser