October 2013 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Prjconf Prefer
by Darin Perusich 17 Oct '13

17 Oct '13

Hello All, I'm trying to work around an issue in devel:lang:perl for SLE_SP3 where perl provides an old version of perl(version) which is causing numerous build failures. The prjconf documentation says you can use Prefer to choose a different package for a dependency, but I've set the below Prefer value but I'm still getting "provider perl-version is obsoleted by installed perl". Can someone provide some guidance on this? %if 0%{?suse_version} <= 1110 Prefer: perl:perl-version %endif http://en.opensuse.org/openSUSE:Build_Service_prjconf#Prefer -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] optimization of OBS experience
by Boris Manojlovic 15 Oct '13

15 Oct '13

Dear all, after looking into results of simple load of page on main OBS (request view but all pages suffer from this) i have come to conclusion that simplest things are not implemented to lower bandwidth usage nor load speed of pages. I understand that most of the time people wait for api.o.o response but really do we need to wait for 70% more time because as can be seen here http://paste.opensuse.org/29484148 Most of "issues" i would list here as: - No javascript "minification", - No css "minification", - No gzip/deflate encoding/content type at all and as such high bandwidth usage, - Etag support is non existent Not everyone have 40/MBs :) Boris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] obs build changing devpts mount opts
by Darin Perusich 15 Oct '13

15 Oct '13

Hello All, I was building some packages locally afterward/during I started having this problem where when I'd open a new konsole it would just be blank and it seemed like the only way to get my system back in order was to reboot. After some digging I've determined that after running "obs build openSUSE_12.3" the mount opts of devpts are changing to "rw,relatime,mode=600,ptmxmode=000" from "rw,relatime,gid=5,mode=620,ptmxmode=000" This appears to be related to a glibc update released the other day and how "osc build" does it's chroot, "mount -n -tdevpts none $BUILD_ROOT/dev/pts". A quick work around is to "mount -oremount /dev/pts" should anyone else get hit by this. I haven't filed a bug yet but it's coming. http://sourceware.org/ml/libc-alpha/2013-08/msg00454.html http://lists.opensuse.org/opensuse-updates/2013-09/msg00072.html -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Branching fails for devel:ide:tools/codeblocks
by Andreas Vetter 15 Oct '13

15 Oct '13

Hi, I just branched devel:ide:tools/codeblocks. Then i added and deleted some Repos in my branch https://build.opensuse.org/package/show/home:asvetter:branches:devel:tools:… But the branch is broken somehow for package codeblocks. The error in the WebUI is: Files could not be expanded: service recompress failed: Running /usr/lib/obs/service/recompress --file *.tar --compression bz2 --outdir /lxc.tmp.19206/out Compressed _service:tar_scm:codeblocks-unstable-12.11.9399.tar to tar_scm:codeblocks-unstable-12.11.9399.tar.bz2 Any hints? TIA -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] ubuntu build hangs in dh_installdocs
by Andreas Baumann 14 Oct '13

14 Oct '13

Hi, I installed a local OBS-Server 2.4 (as appliance image). Added a project, added a repository with Ubuntu 13.04. Running a build on the one local worker. I'm building a boost 1.49 package.. The build starts and then hangs forever in: /usr/bin/perl -w /usr/bin/dh_installdocs --all debian/README.Debian debian/NEWS.Debian 0 S 399 759 753 0 98 18 - 5968 wait 14:59 ? 00:00:00 /usr/bin/perl -w /usr/bin/dh_installdocs --all debian/README.Debian debian/NEWS.Debian stracing PID 399, I get: wait4(762, This process with PID 762 is a: chown -R 0:0 debian/libboost1.49-doc/usr/share/doc the strace of it shows it waits in: read(3, An lsof of it shows: chown 762 399 3u IPv4 516089 0t0 TCP localhost:39812->localhost:55332 (ESTABLISHED) So the read hangs getting an answer from the 'faked': tcp 0 0 0.0.0.0:55332 0.0.0.0:* LISTEN 813/faked-tcp I just wondered, if somebody else has experienced this problem before. I saw a rather old message of somebody who might have had the same problem: http://lists.opensuse.org/opensuse-buildservice/2008-11/msg00231.html Greetings Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: abaumann(a)yahoo.com Homepage: www.andreasbaumann.cc -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] obs build triggers
by Michal Šebeň 14 Oct '13

14 Oct '13

Hi all, looks like obs doesn't rebuild packages when their required dependency packages are disabled, for easier understanding I created 2 dummy packages in my home : https://build.opensuse.org/project/show/home:mseben:dependency_issue Check the package with name dummy (with BuildRequires vim) it's in "unresolvable" state : nothings provides noneexistent-dependency needed by vim problem is that I already disabled build/publish/useforbuild for this testing vim package with dependency on "nonexistent-dependency", however this disable action doesn't trigger rebuilding of package called dummy similar real world example is package devel:languages:ruby:extensions/post-build-checks and its deps on aaa_base-malloccheck - this deps isn't fulfilled on older distros (which leads to chain of failing builds for them) and I want to just disable building of this package only for these older distros in order to fix builds for them -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] what about these auto delete requests
by Ruediger Meier 14 Oct '13

14 Oct '13

Hi, a few weeks ago while I was on vacation I've got dozens of delete requests like this one https://build.opensuse.org/request/show/188119 They all were auto accepted only a few days later when I was still on vacation. Moreover I got no emails about these requests. No chance for me to take any action. Just noticed them randomly. Also I don't understand why (almost) nothing seems to be deleted at all allthough these requests are in state accepted. So this request history seems to be useless. How can I find out what actually happened to my projects for real. Or is it still possible that my repos will be removed somewhen in future? BTW I also got repeated delete requests which I declined already some months ago. This is really annoying. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 6

[opensuse-buildservice] Upgrade from OBS 2.3.0 on SLES11 SP2 to the last OBS server
by Fadi Kelajian 14 Oct '13

14 Oct '13

Hello, First of all, sorry for my english. Currently, we have an OBS 2.3.0 on SLES11 SP2 x64 with many RPM compiled. Now, we want to install OBS Server (http://openbuildservice.org/download/) but before, i have an important question : Is it possible to get back our old RPMs from OBS 2.3.0 on SLES11 SP2 to the new OBS server ? Do you have any recommendations to upgrade without lose our RPMs ? Thanks. Best regards -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Faster Kiwi ISO product builds in OBS
by Ladislav Slezak 14 Oct '13

14 Oct '13

Hi, Some time ago I set up my own OBS instance for building YaST installation images. I noticed that building Kiwi ISO image takes too much time. It turned out that OBS was downloading all packages inlucluding source packages (src.rpm) and debuginfo/debug source packages which are not used in the final ISO image at all. In our case the extra packages are over 7GB in size, which is a lot (and this just for a small installation DVD, I have selected just "minimal X" packages). So I decided to look at it during HackWeek. I wanted to get rid of the extra download which just wastes space and download bandwidth and make ISO builds faster. And I was successfull, see more details at https://hackweek.suse.com/projects/143 So please, comment on this pull request: https://github.com/openSUSE/open-build-service/pull/426 I think this will be usefull also for other people building ISO images in OBS and it could speed up ISO builds also in the public OBS instance as well. Thank you! Ladislav -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Can we fix the Tumbleweed builds
by James Bottomley 09 Oct '13

09 Oct '13

Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update? Thanks, James -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

12 23

[opensuse-buildservice] provider perl-version is obsoleted by installed perl
by Darin Perusich 09 Oct '13

09 Oct '13

I'm trying to update a number of perl packages in d:l:p so they'll build in SLE_SP3 and after enabling perl-version for SLE_SP3 I'm getting unresolvable "provider perl-version is obsoleted by installed perl". The packages in question are perl-CPAN-Meta and perl-CPAN-Meta-Requirements, but I'm sure there are more. This was brought up on this list last year, different package, but not real solution was provided from what I can tell. Can someone provide some insight on what needs to be done to move past this. http://lists.opensuse.org/opensuse-buildservice/2012-11/msg00123.html Thanks! -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

Re: [opensuse-buildservice] source server broken
by Dmitriy Perlow 08 Oct '13

08 Oct '13

Hello. It's a known issue of several services types. ______________ Perlow Dmitriy A. via SE Elm ---- Original message ---- From: Michael Schroeder <mls(a)suse.de> Sent: ‎08-Oct‎-2013 11:58 To: Stephan Kulow <coolo(a)suse.de> Cc: opensuse-buildservice mailing list <opensuse-buildservice(a)opensuse.org> Subject: Re: [opensuse-buildservice] source server broken On Tue, Oct 08, 2013 at 08:18:04AM +0200, Stephan Kulow wrote: > This doesn't look like a problem in my perl package: > > Running /usr/lib/obs/service/source_validator --outdir /lxc.tmp.25388/out > /usr/lib/obs/service/source_validators/20-files-present-and-referenced: > line 42: /dev/fd/62: No such file or directory > grep: write error: Broken pipe > (W) Attention, .old is not mentioned in spec files as source or patch. > !! .old is a directory !! > ###ASK -r /lxc.tmp.25388/src/.old > (W) Attention, .tmp is not mentioned in spec files as source or patch. > !! .tmp is a directory !! > ###ASK -r /lxc.tmp.25388/src/.tmp > /usr/lib/obs/service/source_validators/60-spec-filelist: line 12: > /dev/fd/62: No such file or directory > /usr/lib/obs/service/source_validators/60-spec-filelist: line 12: echo: > write error: Broken pipe > rm: cannot remove `/var/lib/lxc/obs.service.jail.25388': Is a directory It also does not look like a bug with the source server. Maybe the "service server"? M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Re: [opensuse-factory] Factory _constraints for 32bit architectures
by Sascha Peilicke 08 Oct '13

08 Oct '13

On 10/07/2013 03:14 PM, Wolfgang Rosenauer wrote: > Am 07.10.2013 15:07, schrieb Dirk Müller: >> Hi, >> >> increasingly recently I'm seeing constraints added to Factory packages >> in this form: >> >> <constraints> >> <hardware> >> <physicalmemory> >> <size unit="M">2048</size> >> </physicalmemory> >> ... >> >> This tells OBS to not schedule the job on hosts that can not provide >> at least 2048 Megabyte (2048 * 1024 * 1024 bytes). With other words, >> this rules out all 32bit workers without LPAE extension. >> >> Unfortunately due to unsolved upstream bugs, the current Guest kernel >> we use for KVM builds does not have LPAE enabled, which means we can >> boot VMs with 2000 MB memory maximum (actually a bit lower than that). >> >> As a temporary measurement, I've hacked the workers to report 64GB of >> memory to the scheduler so that those constraints are not effective, >> but it would be nice to fix this at the source. >> >> Please do not add a constraint that rules out any chance of 32bit ARM >> builds unless you really really really need it (so far I have not seen >> any package in Factory that cannot be made building with less than 2GB >> of RAM though). For devel:languages:python:Factory/pypy I have the following set: <constraints> <hardware> <cpu> <flag>sse2</flag> </cpu> <physicalmemory>  <size unit="M">5120</size> </physicalmemory> </hardware> </constraints> As you can read from my comment, I can probably live with half the mem on 32bit hardware but _constraints currently can't be limited to architectures. That's a feature I already talked to Adrian about and I think he's got it on his radar (CC'ing opensuse-buildservice@ therefore). > Just for clarification. This addresses especially <physicalmemory> and not <memory>? > I have no idea for ARM but for Firefox & Co. I need usually around 4GB of > "memory" which can involve swap I guess which is more than suboptimal for speed > but otherwise I guess we have only very few machines to have real physical 4GB? According to [1] (and Adrian), <memory> includes swap, whereas <physicalmemory> does not. I am inclined to always use the latter since pypy builds still take about 3-5 hours to complete. I don't dare to imagine how long it would take when using swap :-) [1] http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_… -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)

1 0

[opensuse-buildservice] source server broken
by Stephan Kulow 08 Oct '13

08 Oct '13

This doesn't look like a problem in my perl package: Running /usr/lib/obs/service/source_validator --outdir /lxc.tmp.25388/out /usr/lib/obs/service/source_validators/20-files-present-and-referenced: line 42: /dev/fd/62: No such file or directory grep: write error: Broken pipe (W) Attention, .old is not mentioned in spec files as source or patch. !! .old is a directory !! ###ASK -r /lxc.tmp.25388/src/.old (W) Attention, .tmp is not mentioned in spec files as source or patch. !! .tmp is a directory !! ###ASK -r /lxc.tmp.25388/src/.tmp /usr/lib/obs/service/source_validators/60-spec-filelist: line 12: /dev/fd/62: No such file or directory /usr/lib/obs/service/source_validators/60-spec-filelist: line 12: echo: write error: Broken pipe rm: cannot remove `/var/lib/lxc/obs.service.jail.25388': Is a directory Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] local osc build in VM
by Wolfgang Rosenauer 08 Oct '13

08 Oct '13

Hi, since building Mozilla Clients does not work with osc build locally since ages and nobody is looking at the reported bug about it I'm looking for a complete description how I can build locally using a VM (kvm?) build machine instead of a chroot build. I only know some settings from .oscrc but I understood I need more than just flip a few switches in .oscrc? Can someone please point me to the full documentation how to set this up? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] Need information about failing _constraint
by Dirk Müller 07 Oct '13

07 Oct '13

Hi, is there any way to figure out why a constraint is non-fulfillable? for this one: https://build.opensuse.org/package/show/openSUSE:13.1/llvm it seems the constraint is never fulfilled for the qemu workers (aarch64, armv6l), while it works fine for native workers (armv7l). Strangely enough, a similar constraint in glibc-testsuite (that also checks for hypervisor==kvm) seems to work fine. Any idea why it is not fulfilled? There are certainly workers available (idle even) that would fulfill the constraint. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] macros (e.g. %{buildroot} are expanded to NULL ("")...
by David Haller 05 Oct '13

05 Oct '13

Hello, basically, the subject says it all... E.g. %config(noreplace) %{_sysconfdir}/%{name}/vche.conf results in [ 50s] error: Installed (but unpackaged) file(s) found: [ 50s] /vche/vche.conf [ 50s] RPM build errors: [ 50s] File not found: /home/abuild/rpmbuild/BUILDROOT/vche-1.7.2-210.1.i386/etc/vche/vche.conf [ 50s] Installed (but unpackaged) file(s) found: [ 50s] /vche/vche.conf There's several other weird errors along that line (%buildroot not being expanded in %install, and whatnot ..) -dnh -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] Programa de desarrollo de competencias gerenciales
by Universidad Matias Delgado 04 Oct '13

04 Oct '13

PROGRAMA DE DESARROLLO DE COMPETENCIAS GERENCIALES 2013 ¿Quieres ser un mejor Jefe en tus areas de trabajo? Informate sobre nuestros Programa de desarrollo de competencias Gerenciales. puedes escribirnos a:maestriasmatias@ujmd.edu.sv ¡Porque somos #1 en formacion profesional!

1 0

[opensuse-buildservice] Question about the new comment feature
by Greg Freemyer 03 Oct '13

03 Oct '13

In a devel project I maintain I got a SR that I wasn't sure about. I added a comment to it with my question. Does that comment automatically get emailed to the originator of the SR? Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] tomcat7 update missing on the mirrors
by Darin Perusich 02 Oct '13

02 Oct '13

I've just ran across this and I'm not really sure what's going on or how to proceed. An update for tomcat 7 on OpenSUSE 12.3 was release back on 7 August 2013 which brought it up to version tomcat-7.0.35-2.9.1. Earlier I went to install the tomcat-admin-webapps package and it failed because due to a version requirement, version 7.0.35-2.2.1 is what it was trying to install. I do run a local mirror and thought maybe it was out of sync but then I checked http://download.opensuse.org/update/12.3 there are no tomcat update packages available. Something tells me packages should just disappear like this. Should I file a bug for this, is this a maintenance or OBS issue? I have about a dozen+ tomcat servers which could be effected by this so I'd like to get to the bottom of it asap. http://lists.opensuse.org/opensuse-updates/2013-08/msg00013.html -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] OBS build against Fedora Updates?
by Tim Serong 02 Oct '13

02 Oct '13

Hi All, I hit a problem late last week doing a Hawk build in network:ha-clustering:Stable against Fedora 19, namely that OBS builds against Fedora 19 GA, but if I install Hawk on a Fedora 19 test VM with all updates applied, Hawk doesn't run because it was built against libcib.so.2, whereas Pacemaker in Fedora updates supplies libcib.so.3. I hacked around this in Hawk by having it try to dlopen() both of libcib.so.2 and libcib.so.3, as I'm only calling a couple of functions and their signatures apparently didn't change, but it's a bit nasty. Then, the other day, I was trying to get sbd builds in network:ha-clustering:Stable (as cluster-glue requires sbd, and we want to be able to provide builds of all this stuff for Fedora as well as openSUSE, largely to facilitate uptake of crmsh and hawk), and I hit the same problem again. Building sbd against Fedora GA links to libcrmcluster.so.2 and libcib.so.2, but Fedora Updates has libcrmcluster.so.4 and libcib.so.3. Someone already opened a bug requesting OBS build against Fedora Updates (although that was Fedora 18, it was a while ago): https://bugzilla.novell.com/show_bug.cgi?id=804202 Can anyone suggest a solution to this? Is it possible to get OBS to build against Fedora Updates somehow? Because without this ability I'm having a hard time seeing using OBS for viable Fedora builds of HA clustering packages, unless we build the whole stack ourselves, which I'd rather not do (yet more maintenance work for no real benefit, given a viable Pacemaker and Corosync already ship in the base Fedora distro). Thanks, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] I suspect that my chromium package build is going wrong
by James Bond 01 Oct '13

01 Oct '13

This is the package I'm trying to build https://build.opensuse.org/package/show/home:evantonsuse/chromium Build process worked for almost 10 hours, the last message I saw in the build log was the one related to the linking of the chromium binary I think (that's when I've got out of memory error when trying to build locally, so that's the reason why I've tried to build using the build service). After that the timestamps in the build log suddenly started over and judging by the content of the log, the build process started from the beginning again. I've got no package. The build is shown as still going. Could somebody have a look and tell me what's going on, please? Thanks. PS: I am trying to rebuild chromium because of a few reasons: - the official 32bit chromedriver binary for linux doesn't work on debian wheezy because it's compiled against a newer version of glibc - there's a chromium debian package, but there's no package for chromedriver - source code of chromedriver is part of chromium source code tree At this moment it looks like the build process is running for the third time already. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

Fwd: [opensuse-buildservice] I suspect that my chromium package build is going wrong
by James Bond 01 Oct '13

01 Oct '13

---------- Forwarded message ---------- From: James Bond <evanton(a)tut.by> Date: 2013/10/1 Subject: Re: [opensuse-buildservice] I suspect that my chromium package build is going wrong To: Raymond Wooninck <tittiatcoke(a)gmail.com> >Currently network:chromium builds indeed the chromium package for openSUSE distro's, but it doesn't any SUSE specific patches, etc to the source tarball. I see chromium 31 there, chromium in debian repository is an older version. chromedriver is tricky since it has requirements about the version of chromium. A version (or a few versions) mismatch between chromedriver and chromium can lead to chromedriver not working at all with that version of chromium. I know this for a fact since I've bumped into this problem while trying to get them to work in another linux distribution. That's why I have thought it is a good idea to attempt building chromedriver from the same version of source code that was used to build the chromium package for the debian repository. >If I understood you correctly, then the only thing you want is to build the chromedriver? Correct. As stated above, there's no chromedriver package in the debian repository (and I don't know why, it would be so much easier if chromedriver would be just one apt-get install command away!). >If that is correct, then why do you build the full chromium build? I have looked for hints here: http://packages.ubuntu.com/raring/chromium-chromedriver . This is the chromedriver package for ubuntu, yet chrome is specified as build target in rules file. I am just trying to guide myself using reasons that look like common sense to me, I have zero prior experience building debian packages. To me, just adding chromedriver as additional target looked like the minimum change I have to make manually to the build scripts. 2013/10/1 Raymond Wooninck <tittiatcoke(a)gmail.com>: > On Tuesday 01 October 2013 15:16:51 James Bond wrote: >> correct me if I'm making a wrong assumption) that openSUSE:Factory is >> a project that builds packages for OpenSUSE and network:chromium is a >> project for building Linux binaries that are distribution agnostic. My > > Currently network:chromium builds indeed the chromium package for openSUSE > distro's, but it doesn't any SUSE specific patches, etc to the source tarball. > >> project is making use of the vanilla source code chromium tarball + >> Debian patches and is trying to build a package for the 32bit Debian >> Wheezy - same version of chromium as the one in the repository, the >> only difference between it and the chromium package from the Debian >> repository being that I'm trying to also compile chromedriver and >> bundle it into the package. > > If I understood you correctly, then the only thing you want is to build the > chromedriver ? If that is correct, then why do you build the full chromium > build ? Building chromium will not give you the chromedriver as that this need > to be explicitly indicated and build separately. The outcome of the > chromedriver build is a single executable which could be packaged separately > (same as happens on openSUSE). You can then decide whether or not to install > that particular package. > > Regards > > Raymond > -- > To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1