January 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Expired OBS Keys?
by King Thorin 02 Jul '13

02 Jul '13

It seems the OBS Security key (keyid 79EAFD54) on keys.gnupg.net has expired (2011-Apr-2). Would it be possible for someone to update it? I know an updated key has been generated (which expires 2013) as it can be found here: http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/xUb… Further details can be found via: http://lists.wald.intevation.org/pipermail/openvas-distro/2011-April/thread… Basically the issue came to light when following instructions: http://www.openvas.org/install-packages.html#openvas4_ubuntu_obs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] Use solid state disks [ssd] to improve obs build times.
by doiggl＠velocitynet.com.au 30 Jul '12

30 Jul '12

Hello With the opensuse build service [obs] getting more usage every day I wonder if this would make a diffence :- 1. Use solid state disks [ssd] to improve build times of package rpms on, perhaps point the BuildRoot or _tmppath to the ssd's Reason for asking. Improve the packaging times during busy times on obs. Cheers Glenn. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 17

[opensuse-buildservice] Fedora repo fails when installing portaudio
by Ruediger Meier 07 Jun '12

07 Jun '12

Hi, On Fedora (15/16) BuildRequires: portaudio-devel gives me this: [...] installing portaudio-19-12.fc15 warning: .init_b_cache/portaudio.rpm: Header V3 RSA/SHA256 Signature, key ID 069c8460: NOKEY error: unpacking of archive failed on file /usr/lib64/libportaudio.so.2.0.0;4f24be4b: cpio: read failed - Bad file descriptor error: portaudio-19-12.fc15.x86_64: install failed [...] Local build works. This is the package where is happens https://build.opensuse.org/package/show?package=FreeMat&project=home%3Arudi… but I'll work around it so the logs may be gone. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] MonoOSC?
by Roger Luedecke 03 Jun '12

03 Jun '12

ANy plans to get this working again? I'm at a loss as to how to get it going though I had branched the project etc. Frankly, I'm figuring out the build service, and think monoosc would go a long way to fostering a quicker understanding. -- Roger Luedecke openSUSE Ambassador Ind. Repairs and Consulting **Looking for a C++ etc. mentor*** -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 25

[opensuse-buildservice] OBS 2.3 corrections
by Joop Boonen 14 Apr '12

14 Apr '12

Hi all, I found some errors in de configurations of the OBS 2.3 server. I've attached the corrected files and the patches. It's related to: Documentation: /usr/share/doc/packages/obs-api/README.SETUP Apache vhosts configuration: /etc/apache2/vhosts.d/obs.conf I've added the api port 81 connection as a quick fix and as the internal doesn't really need to be encrypted. Should I create a bug report for this? Regards, Joop.

3 3

[opensuse-buildservice] Add Mageia to OBS
by Stephan Kleine 21 Mar '12

21 Mar '12

Hi, could Mageia please get added to OBS? thanks a lot in advance, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 6

[opensuse-buildservice] openSUSE 10.3 runs out of maintenance
by Adrian Schröter 21 Feb '12

21 Feb '12

Hello, is usual, openeSUSE 10.3 runs out of maintenance and I will remove all repos building against it in OBS. openSUSE:10.3 project has been moved to DISCONTINUED: namespace as announced a while ago. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] openSUSE:Tools dropped 11.3 repo already?
by Archie Cobbs 16 Feb '12

16 Feb '12

I noticed that openSUSE:Tools has dropped its 11.3 repo already. I understand 11.3 is EOL'd, but it seems like Tools repo should be special, as it contains zypper -- the tool that lets you upgrade. I understand that EOL means no longer "community supported" - that's fine.. but it seems to me that "community supported" is a completely different concept than "exists as a repo in a project". After all, openSUSE:Tools has RHEL 4 and all these other non-SUSE repos... are those distributions "community supported" by the openSUSE project?? So I don't understand the rush to remove the repo. Needless to say, I still have stable 11.3 systems around that I'm not ready to upgrade just yet... Thanks, -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

17 98

[opensuse-buildservice] version-release numbering for DEB packages
by Steve Rae 08 Feb '12

08 Feb '12

I understand the release tag numbering in spec files (for ‘rpm’ packages): Release: <CI_CNT>.<B_CNT> However, I am unable to determine how to perform the same “release” numbering in ‘deb’ packages. A simple test in home:srae:tools (build.opensuse.org) shows: - the ‘rpm’ <CI_CNT> incrementing, but - the ‘deb’ stays the same -- actually, it seems to use the <version>-<release> as specified on the first line of the ‘debian/changelog’ file (in debian.tar.gz) Thanks in advance! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Question for unsupported packages: Octave, Scilab, Warsow
by Кириллов Александр 06 Feb '12

06 Feb '12

1. Why is the octave in http://download.opensuse.org/repositories/science/openSUSE_12.1/ ? (At the same time qtoctave in Pacman Repository) Why not both packages are in OSS? 2.Scilab is: -- in the factory, but it does not work (http://download.opensuse.org/repositories/Education/openSUSE_Factory/) --http://download.opensuse.org/repositories/Education/openSUSE_11.4/ Why it is not for openSUSE 12.1 ? 3.Why not package Warsow, although previously was? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 14

[opensuse-buildservice] [PATCH] show full package name and its arch with title tag
by Dinar Valeev 01 Feb '12

01 Feb '12

Hi, Some times package name doesn't fit to monitor build progress and doesn't show at all whether it is 32bit or 64bit build. Following patch adds that information. (to see full package name and its arch, you should hover mouse over the build job). Have fun, Dinar

2 3

[opensuse-buildservice] test of obs-server.x86_64-2.2.116-Build1.2.raw in a update from version 2.1
by Karsten Keil 01 Feb '12

01 Feb '12

Hi, I want share my expirence during a update of a test install from image obs-server.x86_64-2.1.16-Build1.6.raw.bz2 to obs-server.x86_64-2.2.116-Build1.2.raw.bz2. It was a more or less standard setup following the howto on a x86_64 physical host, booted from USB stick and have a LVM setup for the storage: pingi8:/usr/lib/obs/server # ll /dev/OBS/ total 0 drwxr-xr-x 2 root root 240 Jan 30 10:13 . drwxr-xr-x 22 root root 4560 Jan 30 10:13 .. lrwxrwxrwx 1 root root 7 Jan 30 10:13 cache -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 30 10:13 server -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 30 10:13 worker_root_1 -> ../dm-3 lrwxrwxrwx 1 root root 7 Jan 30 10:13 worker_root_2 -> ../dm-4 lrwxrwxrwx 1 root root 7 Jan 30 10:13 worker_root_3 -> ../dm-5 lrwxrwxrwx 1 root root 7 Jan 30 10:13 worker_root_4 -> ../dm-6 lrwxrwxrwx 1 root root 7 Jan 30 10:13 worker_swap_1 -> ../dm-7 lrwxrwxrwx 1 root root 7 Jan 30 10:13 worker_swap_2 -> ../dm-8 lrwxrwxrwx 1 root root 7 Jan 30 10:13 worker_swap_3 -> ../dm-9 lrwxrwxrwx 1 root root 8 Jan 30 10:13 worker_swap_4 -> ../dm-10 Under 2.1 a small local project was copied from OBS and setuped for local build, for 11.4 and 12.1 (32 and 64 bit) and OBS remote link (to opensuse.org) 2.1 was running fine, every package did build. Then I replaced the 2.1.16 USB Stick whith the 2.2.116 version. I did this after a full backup and a clean shutdown. First boot die crash the MySQL database completely during the MySQL update process. The database did not longer work and could not be repaired (BUG 743697 was submitted). Later I restored the database backup on an other 12.1 machine and did the update manually - without any error. So it looks like that if the update is running on boot time something goes wrong (I did repeat it 3 times). Then I copied the updated data base to the target machine again and did the database migration manually - also without any error. After reboot MySQL was not running, because it did start before the /obs directory was mounted - fixed with Required-Start: $network $remote_fs obsstoragesetup in the mysql startscript and insserv. obsstoragesetup did not mount /dev/OBS/cache, moved the mount in the startscript before the worker setups. Then apache did start before MYSQL was started, because it was in systemd defined as service. Deleted apache2.service file, now apache2 starts as expected after the required services are running. Still wrong rights on many files under /obs (because of changed UID/GID values, repaired with chown -R obsrun:obsrun /obs/* chown -R mysql:mysql /obs/MySQL No access to http://server:82 Error 403 - link not allowed, because root dir is /srv/obs/repos which is symlinked to /obs/repos. I tried option FollowSymLinks in the *82 vhost config in /etc/apache2/vhosts.d/obs.conf and did a restart - still not working. Then I changed the root dir to /obs/repos in /etc/apache2/vhosts.d/obs.conf - works, now I have access to the repos again and also zypper works with the test project. Main webinterface https://server also works, but builds did not. Also montitor shows, that the schedulers are not running, after rcobsscheduler start the processes seems to start and ps ax show them for 3-5 sec, then they die. Logfile looks like: http://pastie.org/3282456, last lines are: fetching remote project data for openSUSE.org:openSUSE:12.1 fetching remote project data for openSUSE.org:SUSE:SLE-11 sorting projects and repositories... setting up watcher for https://api.opensuse.org/public exiting (with complete info)... bye. Even reboot or several restarts of rcobsscheduler did not start it. For further debugging I started it with cd /usr/lib/obs/server strace ./bs_sched x86_64 and it run normally, also the web monitor changed from red to green, and builds are running now. I stopped the strace and did run rcobsserver start again - now also this works for x86_64 as it should !??? - i586 still not runing (did die after few secs). Repeated the same procedure for i586 without strace. cd /usr/lib/obs/server ./bs_sched i586 also this does work now and the i586 builds also succeeded. Now the 2.2.116 apliance seems to run just fine :-) Maybe this helps to find the remaining problems, if you want some logfiles request it. Best Karsten -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 6

[opensuse-buildservice] Bug with "osc service localrun download_files"?
by Greg Freemyer 01 Feb '12

01 Feb '12

All, I got an automatic rejection on a package I submitted yesterday. It says the *.tgz file in may package is different from what's online. I just re-pulled the *.tgz file and it has the same md5 hash as the file in the project. Is there something wrong with the source checker? The below is cut and pasted straight from a real terminal session and the commands are in order. I'm confused. === > cd security/ # move into my local security repo project > osc co log2timeline # check out a fresh copy of the package in question > cd log2timeline > osc service localrun download_files log2timeline_0.61.tgz /home/gaf/obs/security/log2timeline/log2timeline_0.61.tgz differ: byte 5, line 1 /home/gaf/obs/security/log2timeline # note that it fails with a virgin copy of the package from OBS > mv log2timeline_0.61.tgz log2timeline_0.61-old.tgz > wget http://log2timeline.net/files/log2timeline_0.61.tgz > md5sum *.tgz e89eaca27324aa7b0de52c09d35ec592 log2timeline_0.61-old.tgz e89eaca27324aa7b0de52c09d35ec592 log2timeline_0.61.tgz # I should now have a identical copy, but freshly downloaded from the original source > osc service localrun download_files /home/gaf/obs/security/log2timeline # But now it works???????? # I did NOT change the specfile between the failure and the success. I only downloaded a fresh copy of the tarball. It has the same md5 hash, so the original version wasn't corrupt. === Thanks for suggestions, Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Packages missing from Fedora 16
by Shih-Yuan Lee (FourDollars) 31 Jan '12

31 Jan '12

Hi, I encounter unresolvable issue: "have choice for desktop-notification-daemon needed by libnotify: kdebase-runtime notification-daemon xfce4-notifyd" on Fedora_16. And I can not find any package from http://software.opensuse.org/ on Fedora 16 by keyword 'notification-daemon'. But I can find 'notification-daemon' on https://admin.fedoraproject.org/pkgdb. My package is at https://build.opensuse.org/package/show?package=pcmanx-gtk2&project=home%3A… . Could you help me to solve this problem? Cheers, $4 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 6

[opensuse-buildservice] Cannot install texlive-latex-base
by Claudio Freire 31 Jan '12

31 Jan '12

Hi guys. I'm building a totally unrelated package that's a dependency for a project of mine, from a debian .dsc. I'm getting a weird error even before the VM starts, while installing all the buildrequires I imagine: https://build.opensuse.org/package/live_build_log?arch=i586&package=quilt&p… """ Building format(s) --all --cnffile /etc/texmf/fmt.d/10texlive-latex-base.cnf. This may take some time... fmtutil-sys failed. Output has been stored in /tmp/fmtutil.OHjyFZQu Please include this file if you report a bug. dpkg: error processing texlive-latex-base (--install): subprocess post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: texlive-latex-base exit ... """ I tried to trigger a rebuild a few times, it always breaks the same way. Any ideas? -- 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] distro independant rpms and debs for distro independant data?
by Paul Elliott 31 Jan '12

31 Jan '12

This question concerns both the OBS and packaging so I am sending to both lists. I am currently working on packaging the Swiss Ephemeris http://www.astro.com/swisseph/ I am currently at the planning scheming and experimentation stage. First I will do the library. But then there is the data. The data is about 60 files not all of which will be wanted by all people. There may be ways of grouping but I am not sure. Perhaps one rpm per file. The Web page says: > For this extended timespan the ephemeris requires 32 Mbytes of ephemeris > files. It would be a shame if this had to repeat for each distro. There may be other projects with even more data. This data is distro and architecture independent. I understand that there should be different rpm per distro because different distros link libraries differently and do other details differently. There could be rpm version dependencies. Perhaps one distro can not understand rpms from another distro as raw data. My question is this is there a lowest common denominator rpm format that can represent pure data (and a few text licensing files) and be understood by all distros? How would you get the build service to produce such rpms? After you produced them how would you get the build service to serve them for all rpm based distros? Same question for debs and the debian based distros? Unrelated question: a while back OBS debian binary repositories were debian compatible but the source repositories were not. Is this still true? -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

7 8

[opensuse-buildservice] $bconf->{'debuginfo'} ?
by Robert Schiele 30 Jan '12

30 Jan '12

Hi, In src/backend/bs_sched the line my $debuginfo = $bconf->{'debuginfo'}; refers to a variable $bconf->{'debuginfo'}. According to my understanding this value is to be read from the build config but I found no code that would ever write something in there that would make this variable to become 1. Could someone just tell me how I could reproduce a situation that this value would evaluate to 1? Or is this just some legacy code that could just be read as: my $debuginfo = 0; ? Robert -- 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 armv7l postfix cant resolve rpm-build
by Joop Boonen 29 Jan '12

29 Jan '12

Hi all, Currently postfix and some other packages for armv7l cant be (re)build cause rpm-build cant be resolved. https://build.opensuse.org/package/show?package=rpm&project=openSUSE%3AFact… https://build.opensuse.org/package/show?package=postfix&project=openSUSE%3A… Regards, Joop. -- 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] SSL cert update for opensuse.org hosts in Nuremberg
by Marcus Rueckert 27 Jan '12

27 Jan '12

hi Thursday 2012-02-02 we will update the certificates for all openSUSE hosts located Nuremberg (see detailed list below). The fingerprint of the new certificate is: [[[ Signed with security(a)suse.de key: pub 2048R/3D25D3D9 1999-03-06 uid SuSE -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SHA1 Fingerprint=F0:76:9C:42:D3:F1:C0:ED:C6:F6:15:C0:F8:D5:C7:29:60:EB:53:46 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iQEVAwUBTyAnZXey5gA9JdPZAQI7yQf/d4OqlBnV4WT80cqI3DVGGcEacTSES8Ux dK0z9aW/UQWFTHGoQmDk8xcgHED/mHVAlywIPgccbleWNi3NND3+1EAvsxnR5M1m mdVsNYOEsGDrk/3qvPVzyTjkBgINOnetH/0Hd77NhxaDVkU0f1Tl0wbO5NdhKy6m 0dmGwJgUESi3IQjubaibmGZHCZPfEEO0ReW00tRDjFpV4MnU923/BZWT30WuvfMo ClSedk0r6PBt3FGr5yqIFyjM1i3CX/dioW1nJ3qOP1GKMDGLSL20YEY6ZE/F8nL4 bycPLfTjDxKodWXeAmeBlXNTNVYxjphowtjYMQqFe7hXyUkSHBCLLQ== =UhMT -----END PGP SIGNATURE----- ]]] The following hosts will be affected: * static.opensuse.org * api.opensuse.org * build.opensuse.org * connect.opensuse.org * features.opensuse.org * hermes.opensuse.org * login.opensuse.org * notify.opensuse.org * svn.opensuse.org * ci.opensuse.org We do not expect any service interruptions, but some users run with strict certificate checks. With kind regard Your openSUSE admin team -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.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

[opensuse-buildservice] OBS ARM resolving issue (rpm cant be build).
by Joop Boonen 26 Jan '12

26 Jan '12

Hi all, I see that rpm cant be build because of "nothing provides lua51-devel". https://build.opensuse.org/package/show?package=rpm&project=openSUSE%3AFact… The lua51-devel package has been build. https://build.opensuse.org/package/show?package=lua51&project=openSUSE%3AFa… Regards, Joop. -- 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] enabling obs-service-* packages for Debian builds
by Robert Schiele 25 Jan '12

25 Jan '12

Hi, We were just thinking about enabling obs-service-* packages for Debian builds to have them available for osc installations on Debian systems. Problem currently is that those packages have the source service script and the corresponding XML file flat in the directory, while Debian builds expect everything in a tar.gz. There are several solutions for that now how we could solve that and we would like to hear your opinion on which way we should go. The options we could think of are: 1. Change packages in a way that the files are contained in a tar.gz. 2. Implement a source service that would package flat files into a tar.gz automatically. 3. Enhance debtransform to automatically package flat files into a tar.gz for Debian builds. Any opinions? Robert -- 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] Request #99848
by Joop Boonen 24 Jan '12

24 Jan '12

Dear all, Can someone, who is authorized as security user, accept request 99848. https://build.opensuse.org/request/show/99848 I want to move my Contrib packages to devel projects. Can I please also be the maintainer in this devel project? Regards, Joop. -- 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] [RFC] transparent cross compiliation support for OBS
by Daniel Gollub 24 Jan '12

24 Jan '12

Hi, we currently plan to enable OBS with an additional cross-compilation feature. Which is referred in the "Build Service Concept CrossDevelopment" [1] as Type 3: "[...] the build system is modified so original source and binary packages can be build and used in a repository ". So instead of using QEMU to emulate a different architecture completely, we want to make use of cross-compilation using the host toolchain. Later: for executing tests or other "target"-binaries during the %build/%install/%check there will be still the need to use QEMU - which would be then a mix of Type 3 and Type 4. We have not started yet any coding, just have done some rough concepts and wanted to make our planned effort public to involve the community in the design, to make sure everyone is happy with that effort and useful not only for us. Goal: transparent cross compilation ==================================== The idea of "transparent cross compilation" to get the same spec file working for one architecture also building for an architecture which needs to get cross-compiled, but without using QEMU for compilation. To get this working the idea is to use common packaging macros like %configure to apply the right parameters if the build is a "transparent cross-compile" build. One alternative would be to make heavy use of rpm conditionals on your own if you are not happy with using pre-defined macros like %configure. inside obs-build ================ We briefly checked some cross-compile helper tools/frameworks and efforts like scratchbox or this project [2]: Several tools available to "fake" a native build environment through emulation and replace core components (like the compiler) through native binaries to speed up the build. The idea in [2] instead tries to inject relevant modifications into rpmbuild to cause rpm to do a "traditional" real cross build. Later one comes quite close to what we could thing have could be done inside obs-build to perform the transparent cross-compilation: - perform a regular host (e.g. x86) build environment including preinstall/install - including the required toolchain to perform cross-compilation (and later for type 3-4 mix: qemu and binfmt register scripts) - setup a separated target root ("sysroot") - e.g. /opt/cross/%_target_platform/sysroot * create new separated RPM database for target platform * use the sysroot as rpm root - install buildrequires of the target repo inside the sysroot * packages like gcc, gcc-c++, ... needs to be substitued so those get installed in the host environment (not in the target environment) - define/redefine additionally requird rpm macros for the cross-compile build - run rpmbuild with buildroot, root, target, ... parameter inside the sysroot * inside: lots of details which need to be defined later * host toolchain get used where possible - move build results from the target sysroot to the "right" location so they can be picked up extractbuild (if VM worker) obs-build would have to be changed to handle additional to the host repository (to setup the changeroot/VM worker) an additional repository for the target buildrequires. Is this approach inside obs-build reasonable for transparent cross- compilation support? Looking forward to your feedback. [1] http://en.opensuse.org/openSUSE:Build_Service_Concept_CrossDevelopment#Type… [2] http://wiki.qt-project.org/QtonPi/Contribute#Cross-build_tools Best Regards, Daniel -- Daniel Gollub Linux Consultant & Developer Tel.: +49-160 47 73 970 Mail: gollub(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

3 3

[opensuse-buildservice] Short downtime in ~ 10-12 hours
by Adrian Schröter 21 Jan '12

21 Jan '12

Hi, I will try to move the last part from the faulty raid (our source server) either on saturday or sunday morning. So please expect 1hour downtime in 10-12 hours. (typically a time with low load). JFYI adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] Help with file list please
by Robert Schweikert 20 Jan '12

20 Jan '12

Hi, I am running into an issue with the file list of a package Virtualization:Cloud:Eucalyptus/axis2c The spec file currently has the following entry: ...... %define axis2c_home %{_libdir}/%{name} ......... %files %defattr(-,root,root) %config /etc/ld.so.conf.d/* %doc AUTHORS ChangeLog COPYING CREDITS LICENSE NEWS NOTICE README %{axis2c_home}/bin %{axis2c_home}/lib %{axis2c_home}/modules %{axis2c_home}/modules/*/module.xml %{axis2c_home}/axis2.xml %{_bindir}/axis2* # .so links need to be in the regular package as they will be used by dlopen %{_libdir}/*.so* #%dir %{axis2c_home} #%dir %{axis2c_home}/lib #%dir %{axis2c_home}/modules #%dir %{axis2c_home}/modules/addressing #%dir %{axis2c_home}/modules/logging #%dir %{axis2c_home}/services %files doc %defattr(-,root,root) %doc %{_defaultdocdir}/%{name} #%dir %{_defaultdocdir}/%{name} %files devel %defattr(-,root,root) %doc INSTALL %{_includedir}/* %{_libdir}/pkgconfig/%{name}.pc This results in the message: ... checking filelist axis2c-1.6.0-1.x86_64.rpm: directories not owned by a package: - /usr/lib64/axis2c This should be cured by uncommenting the %dir derective(s). However, as soon as I comment out the %dir directive(s) I end up with tons of messages claiming that files in /usr/share/doc/packages/axis2c are packaged twice in axis2c and axis2c-doc. These messages are prefixed with ERROR. This problem occur when building for Factory. Help is much appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 7

[opensuse-buildservice] historic errors showing up again in linkedbuild projects
by Robert Schiele 20 Jan '12

20 Jan '12

Hi, It's me again. It seems I am running into all bugs related to linkedbuild projects in combination with source services. Probably I am the only user of this feature set combination. ;) Now, here it is: With current versions, including up to this version: commit ad4cc3d11b9b6daed710f7d7bad80d7b9440c2e6 Author: Michael Schroeder <mls(a)suse.de> Date: Fri Dec 16 16:02:38 2011 +0100 [backend] use url as fallback for title in patchinfo references I can see the following behavior: 1. I have a project (referring to as the main project in the following) including some packages using source services that pull their sources from an external server. 2. I have other projects that have a subset of packages from the previous projects and pull in the rest of the packages with the linkedbuild feature. 3. One day the external source server referred to in the source services was temporarily down, thus leading to source service errors in the main project and thus some broken packages. 4. After the external source server came back up again I retriggered all source service runs that previously failed and got successful results, such that all packages in the project were fine again. 5. Some packages (but interestingly not all of them) in the linkedbuild projects kept the error. It is not possible to retrigger the runs there since those packages are only linked ones and no real ones. 6. Making an explicit copy of an affected package into the linkedbuild project fixes the problem, since the package is now a materialized copy and thus causes a separate source service run. As soon as this copy is removed again though and the project falls back to the linked project the error reappears. 7. Creating a new linkedbuild project has the same broken packages, even though the packages had been fixed in the main project already long time before the new linkedbuild project was created. So, to sum this up: What I observed in 5-7 seems to be a bug that the source service results are not always copied correctly, picking an outdated result for copying instead of the most recent one. Especially the fact that the problem even persists for newly created projects makes me a bit nervous about the reliability here. Anyone with an idea, what could be causing that, which places in the sources I should focus on for searching for the cause? Alternatively does someone have a good idea for a suitable workaround that is smarter than my current approach to just explicitly copy in all packages that suffer from this behavior? Robert -- 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] are builds stopped or stuck on the build service ? , many are showing red
by doiggl＠velocitynet.com.au 20 Jan '12

20 Jan '12

Hello Some info - are builds stopped or stuck on the build service ? [1], many are showing red. [1] https://build.opensuse.org/monitor Cheers Glenn -- 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] Scheduling x86_64 packages
by Johannes Weberhofer 19 Jan '12

19 Jan '12

Fyi: No x86_65 packages are currently scheduled. -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 5

[opensuse-buildservice] Different archives are made by the same _service file (with bzr) in my local computer and in OBS
by Dmitriy Perlow 17 Jan '12

17 Jan '12

Hello. I wrote the _service file to get the freshest sources from bazaar. In my local computer I run osc build --ccache openSUSE_12.1 x86_64 or osc service run and I get _service:recompress:tar_scm:python-itmages-service-0.38.tar.bz2 and it is OK. But when I commit it into OBS service made archive with filename _service:recompress:tar_scm:python-itmages-service-38.tar.bz2 (without "0.") and it is wrong. _service — https://build.opensuse.org/package/view_file?file=_service&package=itmages-… log from OBS — https://build.opensuse.org/package/live_build_log?arch=i586&package=itmages… my local log — http://paste.kde.org/183764/ Could anybody help my please? -- Best regards, Dmitriy DarkneSS Perlow / Linux x64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] build.opensuse.org OBS binary backend is down
by Adrian Schröter 17 Jan '12

17 Jan '12

The SAN array of the backend server server seems to have lost 3 hard disk at once now :/ That means the array is broken atm. We can not fix this before monday. Since not all binary parts of the projects are in backup it means that we will need to rebuild some of them afterwards. Sources and project configurations shall not be affected by this. It is sunshine out there, have fun :) sorry adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Dependency resolution prefers package names rather than "provides"?
by Cristian Morales Vega 16 Jan '12

16 Jan '12

With the OBS down I can't give any example now. But if there is packageA-devel in openSUSE:12.1 and in the devel project it is renamed to stillpackageA-devel, the other packages in that devel project that require "packageA-devel" seem to prefer packageA-devel to stillpackageA-devel. stillpackageA-devel provides "packageA-devel = <new_version>" and obsoletes "packageA-devel < <new_version>". Is this expected? Usually what happens is that the devel project requires the exact version of "packageA" and the OBS gives an "unresolvable" state because it can't find "packageA = <old_version>", "packageA = <new_version>" hides it. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] OBS down ?
by Christian 15 Jan '12

15 Jan '12

Hi, since yesterday eening OBS seem to be down. Anyone aware of this problem ? -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de ---------------------------------------------------- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 16

Re: [opensuse-buildservice] Re: OBS down ?
by Bryen M Yunashko 15 Jan '12

15 Jan '12

On Sat, 2012-01-14 at 19:47 -0600, Archie Cobbs wrote: > > While some outages have been frustratingly low on information, I think > > this time we saw good spread of information and the bases were pretty > > well covered. However, let's at least be fair and give some benefit of > > the doubt by recognizing that in life there's always room for > > improvement. Where else do you feel it should have been posted? > > Hmmm... how about this: set up a blog page for OBS general news and info. Then we can all subscribe to the RSS feed in our google reader. > > -Archie 1. Please reply to list, I don't need to be CC'ed on a mailing list that we're already on. :-) 2. Isn't that already done? The information was posted on news.opensuse.org promptly and n.o.o is definitely "RSS-able." Bryen -- 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] libreoffice on onerirc takes an extremely long time to build
by Paul Elliott 13 Jan '12

13 Jan '12

Because it was not in BS, I attempted to build libreoffice for oneriric. It takes an extremely long time to build. The i586 version is still building. x86_64 version terminated with this error: > Job seems to be stuck here, killed. > qemu: terminating on signal 15 from pid 14358 > No buildstatus set, either the packager broke the base system > (glibc/bash/perl) or the build host has a kernel or hardware problem, OBS > server will retry... https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libre… dependancies&repository=xUbuntu_11.10 https://build.opensuse.org/package/show?package=libre-office-java-common&pr… Did it stop because of a limit on total build time for a single source package? If so, that limit needs to be increased. Because it takes so long, I hesitate to trigger a rebuild without somekind of solution to this prpblem. Please suggest what I should do. Thank You. -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

3 7

[opensuse-buildservice] are builds stopped or stuck on the build service ? , many are showing red
by doiggl＠velocitynet.com.au 13 Jan '12

13 Jan '12

Hello Some info - are builds stopped or stuck on the build service ? [1], many are showing red. [1] https://build.opensuse.org/monitor Cheers Glenn -- 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] special hack for handing off remote source requests to ajax server
by Robert Schiele 11 Jan '12

11 Jan '12

Hi, I identified a problem when accessing a remote OBS instance through a squid proxy. The change commit 5ed45e0096ff5051827c251c8fd384dd70debcbb Author: Michael Schroeder <mls(a)suse.de> Date: Wed May 26 11:26:55 2010 +0200 - handoff remote source requests to ajax server - make request data available diff --git a/src/backend/BSServer.pm b/src/backend/BSServer.pm index 154b965..afead0f 100644 --- a/src/backend/BSServer.pm +++ b/src/backend/BSServer.pm @@ -44,6 +44,7 @@ use BSHTTP; use strict; # FIXME: store in request and make request available +our $request; our $peer; our $peerport; our $slot; @@ -824,6 +825,7 @@ sub compile_dispatches { sub dispatch { my ($conf, $req) = @_; + $BSServer::request = $req; my $disps = $conf->{'dispatches'}; my $stdreply = $conf->{'stdreply'}; die("500 no dispatches configured\n") unless $disps; diff --git a/src/backend/bs_srcserver b/src/backend/bs_srcserver index 3364355..daf6662 100755 --- a/src/backend/bs_srcserver +++ b/src/backend/bs_srcserver @@ -2814,9 +2814,17 @@ sub getfile { die("404 $filename: no such file\n") unless $files->{$filename}; my @s = repstat($rev, $filename, $files->{$filename}); die("$projid/$packid/$files->{$filename}-$filename: $!\n") unless @s; - local *F; - repopen($rev, $filename, $files->{$filename}, \*F) || die("$projid/$packid/$files->{$filename}-$filename: $!\n"); - BSServer::reply_file(\*F); + if (!$BSStdServer::isajax && $rev->{'srcmd5'} && $rev->{'srcmd5'} ne 'upload' && $rev->{'srcmd5'} ne 'pattern' && $rev->{'srcmd5'} ne 'empty') { + # hack: we identify remote source downloads by looking at the user agent + my $useragent = $BSServer::request->{'headers'}->{'user-agent'} || ''; + if ($useragent =~ /BSRPC/) { + BSHandoff::handoff($ajaxsocket, "/source/$projid/$packid/$filename", undef, "rev=$rev->{'srcmd5'}"); + exit(0); + } + } + my $fd = gensym; + repopen($rev, $filename, $files->{$filename}, $fd) || die("$projid/$packid/$files->{$filename}-$filename: $!\n"); + BSWatcher::reply_file($fd); return undef; } @@ -4980,6 +4988,7 @@ my $dispatches_ajax = [ '/getbinaries $project $repository $arch binaries: nometa:bool? raw:bool?' => \&worker_getbinaries, '/lastevents $filter:* start:num? obsname:?' => \&worker_lastevents, '/source/$project/$package rev' => \&getfilelist_ajax, + '/source/$project/$package:package_pattern/$filename rev?' => \&getfile, ]; #################################################################### causes special handling if the user-agent string indicates that the other system is an OBS system as well, resulting in using chunked transfer encoding instead of having the content length. When this passes through the squid proxy the chunked transfer encoding is replaces by "normal" encoding but still the content-length not added. The receiving OBS cannot deal with that situation. Thus my question is, why was this special handling introduced and what would be the consequences if I disabled that? Is this just a performance downgrade or would that also have an impact on functionality. Robert -- 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 Team meeting
by Adrian Schröter 10 Jan '12

10 Jan '12

present: mls, saschpe, adrian Open features until OBS 2.3 =========================== * Support issue tracking (mirror bug entries and owners) and assign it to packages. => Show open patchinfos to the packager based on bugzilla data. DONE, except update mechanism. AI: adrian * support osc search for published binaries with limiters: - version/release - base project AI: mls * webui patchinfo editor - add button: update _patchinfo file based on the mentioned (bugzilla and cve) issues from sources. AI: benjamin * enable publishing and useforbuild only for patchinfos on release project AI: adrian * maintenance request accept will create patchinfo on accept if none is provided. AI: adrian * enhance createrepo for delta downloads AI: sascha * Show required and existing fixes on incidents. required bug ids are defined in _patchinfo, existing are parsed from source diff. AI: sascha * Show incident status - build status - patchinfo bugnummer diffs: => take bug nummer => show package diff => link to bugzilla bug AI: sascha * A number of bugs have been opened by maintenance team to be verified/fixed. * Open question how to help the user to find sources in open incidents. (automatic devel package definition change in :Update project?) Implemented requests ==================== * Handle declined requests in UI (webui and osc): All requests (not just maintenance) will require a handling of submitter after getting the request declined (by reviewer or target). This is because declined request notifications can be easily overlooked, the current state should always be available. Therefore the declined request will stay visible for the creator until the submitter decides to: - revoke : Accepting the decline - superseed : Submitting an improvement - reopen : disagreement with the reason and ask back again. (DONE) * Support linking to not yet existing packages for release number handling * set bugowner on incident creation (DONE) * export severity to updateinfo.xml (DONE) * faster product build thanks to enhanced obs-worker (DONE) * Resign packages on release. Incident projects must never contain final signed packages, since they are not complete reviewed yet. (DONE) * Support aggregate of updateinfo.xml (DONE) * Cached issue parsing from source diffs in backend (DONE) * switch to security patchinfo category when found CVE (DONE) * Solution for bugzgilla groups (eg. kde-maintainers). Who should see open issues in bugzilla because of this ? DONE. bugzilla groups are created as users in OBS. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Job seems to be stuck here, killed.No buildstatus set, either the packager broke the base system (glibc/bash/perl) or the build host has a kernel or hardware problem
by doiggl＠velocitynet.com.au 10 Jan '12

10 Jan '12

Hello Saw a odd message in a build job [1] odd , something broken ? Glenn [1] Source: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libre… Job seems to be stuck here, killed. qemu: terminating on signal 15 from pid 14358 No buildstatus set, either the packager broke the base system (glibc/bash/perl) or the build host has a kernel or hardware problem, OBS server will retry... -- 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] "dead lock" between autoyast2 and yast2-schema
by Joop Boonen 09 Jan '12

09 Jan '12

All, Currently there is a "dead lock" between package autoyast2 and yast2-schema (for the openSUSE:Factory:ARM build). The thing is that autoyast2 Requires yast2-schema. Because of this yast2-schema is blocked. I got around this by removing the autoyast2 requirement. Until yast2-schema has been build. When this package was build I added the Requirement again. I wonder if there is a better "mechanism" in OBS that solves such "lock issue" automatically? Otherwise someone has to handle this by hand. Regards, Joop. -- 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] about latest openssl update for SLE_11_SP1
by Christian 09 Jan '12

09 Jan '12

Hi, latest updates for SLE_11 SP1 brought 0.9.8j --snip-- v | SDK-SP1_upd | libopenssl-devel | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 v | SP1_upd | libopenssl0_9_8 | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 v | SP1_upd | libopenssl0_9_8-32bit | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 v | SP1_upd | nscd | 2.11.1-0.32.1 | 2.11.1-0.34.1 | x86_64 v | SP1_upd | openssl | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 --snip-- shouldn't a SLES be "binary compatible" ? building proftpd and starting will show following: proftpd[4078]: mod_tls/2.4.3: compiled using OpenSSL version 'OpenSSL 0.9.8h 28 May 2008' headers, but linked to OpenSSL version 'OpenSSL 0.9.8j-fips 07 Jan 2009' library so should we have the new openssl in "SUSE:SLE-11 <https://build.opensuse.org/project/show?project=SUSE%3ASLE-11>:Update <https://build.opensuse.org/project/show?project=SUSE%3ASLE-11%3AUpdate>" ? -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de ---------------------------------------------------- -- 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] packages missing from oneiric
by Paul Elliott 08 Jan '12

08 Jan '12

ubuntu package search http://packages.ubuntu.com/ shows the packages libreoffice-writer and libreoffice-java-common in main in oneiric, but the buildservice thinks they are unresolveable. See: https://build.opensuse.org/package/show?package=debian&project=home%3Apelli… What is happening here? -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

2 1

[opensuse-buildservice] subversion seems to be missing in Factory and devel project
by Joop Boonen 07 Jan '12

07 Jan '12

Hi all, I was looking for subversion, I 'm not able to find it anymore in Factory and and development project. I would expect it in Base:build as CVS also resides here. Regards, Joop. -- 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] are builds stopped or stuck on build27 (x86_64) ? , all are showing red
by doiggl＠velocitynet.com.au 07 Jan '12

07 Jan '12

Hello Some info - are builds stopped or stuck on build27 (x86_64) ? [1], all are showing red. [1] https://build.opensuse.org/monitor Cheers Glenn are builds stopped or stuck on build26 (x86_64) ? , all are showing red. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] Missing OBS server and rubygem-rmagick in openSUSE:Tools
by Mikhail Zabaluev 06 Jan '12

06 Jan '12

Hi, I am trying to install OBS from openSUSE:Tools:Unstable on openSUSE 12.1. There is an unresolved dependency on rubygem-rmagick. I can see the package in openSUSE:Tools, and the binary packages are listed as successfully built on build.opensuse.org, but the download repository for openSUSE 12.1 misses them. Interestingly, the obs server packages are also missing from the openSUSE:Tools stable repository. Is it some temporary glitch? Mikhail -- 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 ARM build discussion I would like to start
by Joop Boonen 03 Jan '12

03 Jan '12

Hi all, Currently we have the following problem. Due to security issues we only have native ARM workers for the internal openSUSE buildservice. For the external build service we only use qemu. Because qemu is much slower them native ARM builds the external build is way behind. So for people outside of suse.com it's not really possible to fix packages as you don't know if the current status is still valid. I would like to know how the people in charge of OBS think about this? Can the current situation be changed or is this due to a security policy? Can we help to solve this issue? If so what are the problems we are facing and which security should be met? Did I leave something out or is something now correct? Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 8

[opensuse-buildservice] Set devel-package dependency to automake on Factory? (for directory /usr/share/aclocal)
by Nico Kruber 02 Jan '12

02 Jan '12

Recently rpmlint checks for Factory are complaining about no package owning /usr/share/aclocal for aqbanking and gwenhywfar. Both their devel packages install their *.m4 files into this folder. I see that this directory is owned by automake but which of the following solutions is the best way to solve this? 1) Should I set a hard dependency to automake into the devel package. AFAIK, it is not necessarily needed for the devel package and developers using aqbanking or gwenhywfar. 2) Should I include the directory in the devel packages (probably not). 3) Should I split off a sub-package (but an extra package for a single file is probably not worth it). Regards Nico Kruber -- 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] unable to do a local build of ubuntu packages
by Sebastian Held 02 Jan '12

02 Jan '12

Hello, I'm trying to build an Ubuntu package locally to fix some bugs. osc build is not able to download the prerequisites. Here is the log: $ /home/sebastian/OpenSuSE-BuildService/osc/osc-wrapper.py -vv -t -d build xUbuntu_11.04 i586 CSXCAD.dsc makeurl: https://api.opensuse.org ['source', 'home:sibbi77', '_meta'] [] GET https://api.opensuse.org/source/home:sibbi77/_meta makeurl: https://api.opensuse.org ['source', 'home:sibbi77', 'libCSXCAD'] cmd=getprojectservices POST https://api.opensuse.org/source/home:sibbi77/libCSXCAD?cmd=getprojectservic… Building CSXCAD.dsc for xUbuntu_11.04/i586 Getting buildinfo from server and store to /home/sebastian/OpenSuSE-BuildService/home:sibbi77/libCSXCAD/.osc/_buildinfo-xUbuntu_11.04-i586.xml makeurl: https://api.opensuse.org ['build', 'home:sibbi77', 'xUbuntu_11.04', 'i586', 'libCSXCAD', '_buildinfo'] [] POST https://api.opensuse.org/build/home:sibbi77/xUbuntu_11.04/i586/libCSXCAD/_b… Getting buildconfig from server and store to /home/sebastian/OpenSuSE-BuildService/home:sibbi77/libCSXCAD/.osc/_buildconfig-xUbuntu_11.04-i586 makeurl: https://api.opensuse.org ['build', 'home:sibbi77', 'xUbuntu_11.04', '_buildconfig'] [] GET https://api.opensuse.org/build/home:sibbi77/xUbuntu_11.04/_buildconfig Updating cache of required packages 98.3% cache miss. 6/357 dependencies cached. GET http://download.opensuse.org/repositories/Ubuntu:/11.04/standard/i386/bash_… Trying openSUSE Build Service server for bash (Ubuntu:11.04), not found at download.opensuse.org. If I try to build a rpm package, it works: $ /home/sebastian/OpenSuSE-BuildService/osc/osc-wrapper.py build openSUSE_11.4 i586 CSXCAD.spec How can I specify the download url such that osc build downloads from the ubuntu archive server? Why does it work on the official OBS, but not locally? Thanks, Sebastian -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] Mandriva 2011 Tweak needed
by Peter Linnell 02 Jan '12

02 Jan '12

nothing provides libpulseaudio0 needed by lib64pulseaudio0, nothing provides libalsa-plugins-pulseaudio needed by lib64alsa-plugins-pulseaudio Thanks, Peter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0