January 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] How to use %debug_package
by Matthias Bach 27 Jan '09

27 Jan '09

Hi! Trying to be prepare some packages for contrib I stumbeled upon the problem of stripping the package of its debug information. Now I learned that install- strip is not the way to go, as it will make it impossible to debug the application, and I should use %debug_packges, as that will create a "-debug" package with the stripped information. Having added a line "%debug_package" to the spec-file now gives me a strip package without using install-strip. It won't give me a "-debug"-package so, caused by the following problem printed by osc-out. Preparing packages for installation... vorbisgain-debuginfo-0.34-8 vorbisgain-debugsource-0.34-8 vorbisgain-0.34-8 ... running 01-check-debuginfo ... testing for empty debuginfo packages ! ! vorbisgain-debugsource-0.34-8.x86_64.rpm: no debug sources, deleting package ! vorbisgain-debuginfo-0.34-8.x86_64.rpm: WARNING: this probably means the debug information is invalid ! To me this looks that I am missing some information that I should have handed to the %debug_package macro. Sadly my googling (actually ixquick) skills could not provide me with any documentation on this macro. Did anybody master this macro and could give me a hint on what I am doing wrong, or which information is required to understand my problem? Regards, Matthias -- Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke

3 5

[opensuse-buildservice] Userland in ppc64
by Christof Hanke 26 Jan '09

26 Jan '09

Hi, I'd like to prepare some packages (openafs) for ppc64 in my home-project home:hauky Is it fully supported yet ? There are ppc64 hosts mentioned in the scheduler and I can add and enable a ppc64 repository, but it doesn't show up in "osc prjresults". Is it me or is it just not really implemented yet ? Anyway, what I'd wanted to know is if userland programs on ppc64 should be compiled as 32bits or 64bits. Does anyone know that ? Thanks, Christof -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

Re: [opensuse-buildservice] Resend: Ubuntu packaging problem
by Kevin James 26 Jan '09

26 Jan '09

On Fri, 2009-01-23 at 11:16 -0700, Andrew Ziem wrote: > On Fri, Jan 23, 2009 at 9:50 AM, Kevin James <kjames(a)novell.com> wrote: > > Hi all, > > > > I posted this on Tuesday, but didn't get any replies. I'm resending and > > hoping that someone who knows the answer missed the mail.... > > > > Got a Ubuntu packaging problem... I´ve specified debhelper as a > > build dependency in debian.control and <myprojectname>.dsc , but I still > > From memory, I think you also need to specify it in control.dsc. Check > project home:andrew_z and package bleachbit for an example. > > > Andrew Thanks Andrew I looked at your project, and I have the same debhelper entries as you do in <projectname>.dsc and debian.control. I noticed that your project isn't currently building for Ubuntu, due to an unrecognized file, otherwise I would have done a comparison of the build logs. My error occurs after the point where your build stops. Cheers, KEv. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] OBS on 11,1
by Dominique Leuenberger 26 Jan '09

26 Jan '09

In the weekend we (mainly ScriptRipper, }-Tux-{ and me) were busy making the 'first' install of an OBS-Server running on OSS 11.1. Signing works (created bnc #469229). Whereas we discovered some 'issues' that we could identify and solve, we believed by the end everything looks fine. It almost does: OBS is running and is correctly building packages. But now I ran into an issue: (again.. next one to come) - I can't check in new files anymore. As soon as I issue a osc ci -m "blabla" I get the following lines in production_slave.log (/srv/www/obs/frontend/log): --- start log --- Processing SourceController#index_package (for ::ffff:127.0.42.2 at 2009-01-26 08:53:37) [GET] Parameters: {"action"=>"index_package", "project"=>"VideoLAN", "package"=>"ffmpeg", "controller"=>"source"} SQL (0.000460) SET SQL_AUTO_IS_NULL=0 AUTH: Basic<And here would be my password... base64.. so OK> SQL (0.005579) SHOW TABLES User Columns (0.018492) SHOW FIELDS FROM `users` User Load (0.021333) SELECT * FROM `users` WHERE (login = '<UserName>') LIMIT 1 USER found: <UserName> User <UserName> initialised User's source backend <:> SQL (0.001270) SHOW TABLES DbPackage Columns (0.013361) SHOW FIELDS FROM `db_packages` DbPackage Load (0.001772) SELECT pack.* FROM db_packages pack LEFT OUTER JOIN db_projects pro ON pack.db_project_id = pro.id WHERE pro.name = BINARY 'VideoLAN' AND pack.name = BINARY 'ffmpeg' [backend] GET: /source/VideoLAN/ffmpeg? Sending data Completed in 0.23076 (4 reqs/sec) | Rendering: 0.00023 (0%) | DB: 0.06227 (26%) | 200 OK [http://127.0.42.2/source/VideoLAN/ffmpeg] Processing SourceController#file (for ::ffff:127.0.42.2 at 2009-01-26 08:53:38) [PUT] Parameters: {"rev"=>"upload", "action"=>"file", "project"=>"VideoLAN", "package"=>"ffmpeg", "controller"=>"source", "file"=>"ffmpeg-0.4.9.tar.bz2"} checking schema map for controller 'source', action 'file' schema_file: schema path not set, skipping validation AUTH: no authentication string was sent Rendering status errorcode 'unknown' - Authentication required Rendering status (401) Completed in 0.04921 (20 reqs/sec) | Rendering: 0.00220 (4%) | DB: 0.00000 (0%) | 401 Unauthorized [http://127.0.42.2/source/VideoLAN/ffmpeg/ffmpeg-0.4.9.tar.bz2?rev=upload] --- end log --- So action file seems actually not to work here! First I thought it might be because I patched out the check to run only on rails 2.0.2 (OSS is shipped with 2.1), so that check back in, replacing rails 2.1 with 2.0.2 (is provided in the openSUSE:Tools:Devel project, where I have the entire obs from). But the output above actually was created finally with rails 2.0.2, the check not patched out... so rails is not to blame here. What cought my eye is the line "schema path not set, skipping validation"... why is there no schema file if that's needed for auth? (but then: I really have no clue of the code, so this might just be a wrong info in the log file). osc gives the following output (just to make it complete here) --- start log osc --- Transmitting file data .Traceback (most recent call last): File "/usr/bin/osc", line 12, in <module> r = babysitter.run(osccli) File "/usr/lib64/python2.6/site-packages/osc/babysitter.py", line 40, in run return prg.main() File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 256, in main return self.cmd(args) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 279, in cmd retval = self.onecmd(argv) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 395, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 1070, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib64/python2.6/site-packages/osc/commandline.py", line 1350, in do_commit p.commit(msg) File "/usr/lib64/python2.6/site-packages/osc/core.py", line 751, in commit self.put_source_file(filename) File "/usr/lib64/python2.6/site-packages/osc/core.py", line 705, in put_source_file http_PUT(u, file = os.path.join(self.dir, n)) File "/usr/lib64/python2.6/site-packages/osc/core.py", line 1495, in http_PUT def http_PUT(*args, **kwargs): return http_request('PUT', *args, **kwargs) File "/usr/lib64/python2.6/site-packages/osc/core.py", line 1479, in http_request fd = urllib2.urlopen(req, data=data) File "/usr/lib64/python2.6/urllib2.py", line 124, in urlopen return _opener.open(url, data, timeout) File "/usr/lib64/python2.6/urllib2.py", line 395, in open response = meth(req, response) File "/usr/lib64/python2.6/urllib2.py", line 508, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib64/python2.6/urllib2.py", line 427, in error result = self._call_chain(*args) File "/usr/lib64/python2.6/urllib2.py", line 367, in _call_chain result = func(*args) File "/usr/lib64/python2.6/urllib2.py", line 847, in http_error_401 url, req, headers) File "/usr/lib64/python2.6/urllib2.py", line 825, in http_error_auth_reqed return self.retry_http_basic_auth(host, req, realm) File "/usr/lib64/python2.6/urllib2.py", line 835, in retry_http_basic_auth return self.parent.open(req) File "/usr/lib64/python2.6/urllib2.py", line 389, in open response = self._open(req, data) File "/usr/lib64/python2.6/urllib2.py", line 407, in _open '_open', req) File "/usr/lib64/python2.6/urllib2.py", line 367, in _call_chain result = func(*args) File "/usr/lib64/python2.6/urllib2.py", line 1139, in http_open return self.do_open(httplib.HTTPConnection, req) File "/usr/lib64/python2.6/urllib2.py", line 1112, in do_open r = h.getresponse() File "/usr/lib64/python2.6/httplib.py", line 970, in getresponse response.begin() File "/usr/lib64/python2.6/httplib.py", line 390, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.6/httplib.py", line 354, in _read_status raise BadStatusLine(line) httplib.BadStatusLine --- end log osc --- And now: thank you for reading such a loooong mail :) Now I'm looking forward for your tips on how to solve this one. I'm sure when we're all done and all issues are resolved, installation of OBS on 11.1 will be a breaze. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 8

[opensuse-buildservice] problem to rsync repo with ":" in DIR-names
by Christian 26 Jan '09

26 Jan '09

Hi, tried to rsync some repos to my internal system, but rsync seems to have a problem with ":" in DIR-names. (server:) obs:~/bin # rsync -rlpt rsync://ftp5.gwdg.de/pub/opensuse/repositories/server:/proxy /srv/ftp/pub/opensuse/repositories/server\:/ rsync: getaddrinfo: ftp5.gwdg.de/pub/opensuse/repositories/server 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(108) [receiver=2.6.8] I tried to replace ":" with "\:" or "%3A" but without success. Has anyone an Idea how to get this work ? Kind regards Chris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Debian/Ubuntu Repository structure
by Michael Schroeder 26 Jan '09

26 Jan '09

Hi build service folks, I'm trying to make the repositories the build service creates for debian and ubuntu more similar to what people expect. I need some advice to find the best solution. Here are some ideas to consider: doourl = download.opensuse.org/repositories/ 1) current layout: doourl/<project>/<repository>/<arch>/pkg.deb /Packages.gz apt-get entry: deb doourl/<project>/<repository> / issues: - non-standard layout, no pooling - Packages.gz not architecture dependent 2) packages pooled doourl/<project>/<repository>/pool/<pkg>/pkg.deb /Packages.gz apt-get entry: deb doourl/<project>/<repository> / questions: - shall we omit the "pool" directory? 3) multiple Packages.gz files for architectures no softlink solution: doourl/<project>/<repository>/pool/<pkg>/pkg.deb doourl/<project>/<repository>/dists/main/main/binary-<arch>/Packages.gz apt-get entry: deb doourl/<project>/<repository> main main issues: - the "main main" thing is confusing. 4) multiple Packages.gz files for architectures softlink solution: doourl/<project>/<repository>/pool/<pkg>/pkg.deb doourl/<project>/dists -> . (softlink) doourl/<project>/<repository>/main/binary-<arch>/Packages.gz apt-get entry: deb doourl/<project> <repository> main issues: - mirrors might have problems with dist symlink - dist symlink is at "repository" level, needs changes in mirror-push scripts the apt-get entry seems to be most debian like Note also that "real" debian has the pool at "project" level, i.e. doourl/<project>/pool/<pkg>/pkg.deb I don't think this can be done in the build service, as multiple repositories can create different packages with the same name. Any comments? Thanks, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

Re: [opensuse-buildservice] Error satisfying "BuildRequires" for non SuSE distro's
by Christof Hanke 25 Jan '09

25 Jan '09

Hi, try "%else" instead of "%elseif". Is the latter a valid tag ? Never seen it before. I just tried it within a normal spec-file and it seems to work like a normal "%else", for BuildRequires it fails however. My guess is that the parser for the BuildExpansion-stuff does not recognise "%elseif" HTH, Christof Am Sonntag, 25. Januar 2009 00:44:07 schrieb Joop Boonen: > |All, > > I get a build error for all non SuSE distro's on "BuildRequires". I've > checked the names in a test installation they are correct if I'm not > mistaken. > > This are the "BuildRequires" in the spec file: > > <quote> > %if 0%{?suse_version} > BuildRequires: libusb-devel, pkg-config, subversion >= 1.5.0 > %elseif > BuildRequires: libusb-devel, pkgconfig, subversion >= 1.5.0 > %endif > </quote> > > This is the build error I get: > > <quote> > I have the following modifications for dfu-util.spec: > 17c17 > < Release: 5.2 > --- > > > Release: 5.1 > > ----------------------------------------------------------------- > ----- building dfu-util.spec (user abuild) > ----------------------------------------------------------------- > ----------------------------------------------------------------- > + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define > 'disturl srcrep:1d4ecab9cbd0e3b0f54c29caf9af5778-dfu-util' > /home/abuild/rpmbuild/SOURCES/dfu-util.spec > error: Failed build dependencies: > libusb-devel is needed by dfu-util-0.1+svn4900-5.1.src > pkgconfig is needed by dfu-util-0.1+svn4900-5.1.src > subversion >= 1.5.0 is needed by dfu-util-0.1+svn4900-5.1.src > System halted. > </quote> > > Regards, > > Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Error satisfying "BuildRequires" for non SuSE distro's
by Joop Boonen 24 Jan '09

24 Jan '09

|All, I get a build error for all non SuSE distro's on "BuildRequires". I've checked the names in a test installation they are correct if I'm not mistaken. This are the "BuildRequires" in the spec file: <quote> %if 0%{?suse_version} BuildRequires: libusb-devel, pkg-config, subversion >= 1.5.0 %elseif BuildRequires: libusb-devel, pkgconfig, subversion >= 1.5.0 %endif </quote> This is the build error I get: <quote> I have the following modifications for dfu-util.spec: 17c17 < Release: 5.2 --- > Release: 5.1 ----------------------------------------------------------------- ----- building dfu-util.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl srcrep:1d4ecab9cbd0e3b0f54c29caf9af5778-dfu-util' /home/abuild/rpmbuild/SOURCES/dfu-util.spec error: Failed build dependencies: libusb-devel is needed by dfu-util-0.1+svn4900-5.1.src pkgconfig is needed by dfu-util-0.1+svn4900-5.1.src subversion >= 1.5.0 is needed by dfu-util-0.1+svn4900-5.1.src System halted. </quote> Regards, Joop. | -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Is it possible to edit a debian source package w/o using a debian system?
by Paul Elliott 24 Jan '09

24 Jan '09

Is it possible to do the following w/o using a debian system, that is on my opensuse development system: 1)Take an existing debian source package consisting of a)a pristine tarbal in .bz2 format b)a diff file c)a dsc file The above are known to build on debian development system. 2)Edit the source package with out a debian sytem, doing: a)slapping on a upgraded pristine tarbal, (new upstream source) b)edit the configure line in the rules file 3)Sending the resulting new debian source package to opensuse-buildservice to be built? Is this possible, or do I have to install a debian/ubuntu system to edit the debian source package? If it is possible, what are the steps of the procedure? Thank You. By the way, about a year and 1/2 ago I tried to build a ubuntu package using opensuse-buildservice, but it failed because the package had dependancies in the Universe, that opensuse-buildservice did not support the universe. Is this still a problem? Is there a workaround? Supporting the Universe sounds tiring . Even Atlas only tried to support the world. :-) -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

1 1

[opensuse-buildservice] Resend: Ubuntu packaging problem
by Kevin James 23 Jan '09

23 Jan '09

Hi all, I posted this on Tuesday, but didn't get any replies. I'm resending and hoping that someone who knows the answer missed the mail.... Got a Ubuntu packaging problem... I´ve specified debhelper as a build dependency in debian.control and <myprojectname>.dsc , but I still get dpkg-checkbuilddeps: Unmet build dependencies: debhelper The package is home:rincewind23/xmlcopyeditor. I tried following the instructions here: http://en.opensuse.org/Build_Service/Deb_builds But the first problem I've run into is this debhelper problem. If I remove the debhelper dependency, all the dh_* scripts aren't available, and it fails there. Cheers, KEv. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1