October 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Fwd: [Meego-distribution-tools] obslight automatic patch creation for OBS
by Dominig ar Foll (Intel OTC) 28 Oct '11

28 Oct '11

Hi, as I know that most of you do not watch the distribution-tool mailing list, I push you for your information that info which could be of interested. Please note that discussion on that will take place on the distribution-tools mailing list. http://lists.meego.com/listinfo/meego-distribution-tools Regards -- Dominig -------- Message original -------- Sujet: [Meego-distribution-tools] obslight Date : Thu, 27 Oct 2011 13:44:20 +0200 De : Ronan Le Martret (Intel OTC) <ronan(a)fridu.net> Pour : meego-distribution-tools(a)lists.meego.com Hi , We are glad to announce a major delivery of the OBS Light project which concerns the ease of creation of a chroot and automation of a package patching. You will find more information at : * http://wiki.meego.com/OBS_Light For now the core of system as command line is ready. * You can cross compile. * Have local and remote references. * Automatic creation of patch for a package. You can find obslight here. * http://wiki.meego.com/ObsLightDeliverable If you want to use obslight a FAQ will guide you. * http://wiki.meego.com/OBS_Light_FAQ Your feedback is welcome. -- Ronan Le Martret Intel Open Source Technology Center _______________________________________________ MeeGo-distribution-tools mailing list MeeGo-distribution-tools(a)lists.meego.com http://lists.meego.com/listinfo/meego-distribution-tools -- 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] "bad config" in a "preloaded" repository
by Pascal Bleser 27 Oct '11

27 Oct '11

I'm having a long standing issue with the OBS instance at Packman (OBS 2.1.3). We have an "Oracle" project where we build a few packages that require the Oracle InstantClient RPMs (well, the Oracle database shlibs and headers) in order to build. We obviously don't publish the Oracle InstantClient RPMs themselves, but need them to be present as dependencies -- people need to get the InstantClient RPMs from Oracle directly. To do so, I have created a project "Oracle:InstantClient/11.2" (in the same fashion as e.g. "openSUSE:12.1/standard"), and copied the RPMs from Oracle into /srv/obs/build/Oracle:InstantClient/11.2/x86_64/:full/ (and the same for i586) ("11.2" because it's the version of the InstantClient RPMs) Now, we have another project named "Oracle", which has, as repos, paths to both the relevant distribution repositories as well as to that Oracle:InstantClient/11.2 -- the project meta looks like this: ---[prj meta for "Oracle"]------------------------------------ ... <repository name="Evergreen_11.1"> <path repository="standard" project="openSUSE.org:openSUSE:Evergreen:11.1"/> <path repository="11.2" project="Oracle:InstantClient"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_11.4"> <path repository="standard" project="openSUSE.org:openSUSE:11.4:Update"/> <path repository="11.2" project="Oracle:InstantClient"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_12.1"> <path repository="standard" project="openSUSE.org:openSUSE:12.1:Update"/> <path repository="11.2" project="Oracle:InstantClient"/> <arch>i586</arch> <arch>x86_64</arch> </repository> ... --->8--------------------------------------------------------- ("openSUSE.org:" being the prefix for the remote instance at build.o.o) Here's the meta for the project "Oracle:InstantClient": ---[prj meta for "Oracle:InstantClient"]---------------------- ... <useforbuild> <enable/> </useforbuild> <debuginfo> <disable/> </debuginfo> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="11.2"> <arch>x86_64</arch> <arch>i586</arch> </repository> ... --->8--------------------------------------------------------- Now, the weird thing is that it actually works perfectly fine for openSUSE_11.3, openSUSE_11.4 and SLE_11, but fails for other targets (factory, 12.1, evergreens, tumbleweed, SLE_10), and the only thing I can see in the logs is "bad config" for Oracle:InstantClient:11.2 I tried several obs_admin commands (check project, deep check project, etc...), but to no avail. Any idea what could cause this weird behaviour ? Or did I set up the whole thing completely wrong ? :) cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf

1 0

[opensuse-buildservice] Packaging dpkg as .deb
by Nasa 25 Oct '11

25 Oct '11

Hi, I have been trying to create a .deb package of the most recent version of dpkg. It isn't going so well. I noted the following errors from the log that maybe relevent... ----- preinstalling bash... ar: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory tar: control.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors tar: data.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors preinstalling perl... ar: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory tar: control.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors tar: data.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors preinstalling perl-base... ar: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory tar: control.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors tar: data.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors ..... dpkg: libc6: dependency problems, but configuring anyway as you requested: libc6 depends on libc-bin (= 2.11.1-0ubuntu7); however: Package libc-bin is not installed. libc6 depends on debconf (>= 0.5) | debconf-2.0; however: Package debconf is not installed. Package debconf-2.0 is not installed. libc6 depends on libgcc1; however: Package libgcc1 is not installed. libc6 depends on tzdata; however: Package tzdata is not installed. libc6 depends on findutils (>= 4.4.0-2ubuntu2); however: Package findutils is not installed. .... dpkg: plymouth: dependency problems, but configuring anyway as you requested: plymouth depends on mountall (>= 2.0); however: Package mountall is not installed. update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... installing mountall Processing triggers for man-db ... configure all installed packages... removing nis flags from //etc/nsswitch.conf... now finalizing build dir... dpkg-source: warning: could not verify signature on /usr/src/packages/SOURCES/dpkg_1.16.1ubuntu1.dsc since gpg isn't installed dpkg-source: info: extracting dpkg in /usr/src/packages/BUILD dpkg-source: info: unpacking dpkg_1.16.1ubuntu1.tar.bz2 ----------------------------------------------------------------- ----- building dpkg_1.16.1ubuntu1.dsc (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- dpkg-buildpackage: set CFLAGS to default value: -g -O2 dpkg-buildpackage: set CPPFLAGS to default value: dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions dpkg-buildpackage: set FFLAGS to default value: -g -O2 dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 dpkg-buildpackage: source package dpkg dpkg-buildpackage: source version 1.16.1ubuntu1 dpkg-buildpackage: source changed by Colin Watson <cjwatson(a)ubuntu.com> dpkg-buildpackage: host architecture i386 dpkg-checkbuilddeps: Unmet build dependencies: libselinux1-dev (>= 1.28-4) dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting. dpkg-buildpackage: warning: (Use -d flag to override.) [ 655.856369] Power down. Does anyone know what I can do to correct this? Thanks in advance, Nasa -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 16

[opensuse-buildservice] Build for Mandriva 2011: Dependencies unresolvable
by Florian Höch 25 Oct '11

25 Oct '11

Hi, is building for Mandriva 2011 supposed to work yet? I've a lot of (auto-)dependencies listed as unresolvable, ie. common stuff like glibc and automake. -- Florian Höch -- 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] Public availability of ci.opensuse.org
by Sascha Peilicke 24 Oct '11

24 Oct '11

The development process of the Open Build Service (OBS) code base as well as it's accompanying tools is largely test-driven. Major parts of the OBS source code are covered by a comprehensive test-suite. Traditionally, after each new code submission, these tests have been run by a custom shell-script on a local machine that wasn't publically available for several reasons. Even though this setup served us well for a long time, but we needed more. We want to provide a more transparent solution that allows the community to participate and maybe take over some responsibilities. Thus, your hard-working OBS-team hereby kindly introduces http://ci.opensuse.org, our new public interface for continuous integration (CI) testing! Currently, we run the testsuites of the OBS, osc and osc2 code-bases and publish their results to a newly created mailinglist, obs-tests(a)opensuse.org. Additionally, reports about the code coverage and quality (amounts of TODOS, FIXMEs, etc.) are generated. Behind the scenes, we are using Jenkins, probably the most prominet open source CI tool available. Currently, the OBS and osc/osc2 code bases are tested, but we would like to see more openSUSE projects utilize ci.opensuse.org. In the future, we also want to test the RPMs (and appliances) for new OBS releases. And of course, we want to invite the community to have a close look at those test results and provide us with valuable input (or even patches). In case you want to work on the currently available test runners, they are part of the OBS code base and found under $OBS_ROOT/dist/ci (http://github.com/openSUSE/open- build-service/tree/master/dist/ci). -- Mit freundlichen Grüßen, Sascha Peilicke

7 9

[opensuse-buildservice] rebuild="local" issues
by Wolfgang Rosenauer 24 Oct '11

24 Oct '11

Hi, I've recently updated openssl in openSUSE:Evergreen:11.1 and now I got quite some updated packages (which apparently were triggered by the openssl update) which were published w/o any code changes. Anyone an idea what is going on? Wolfgang -- 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] How to send email to all project maintainers?
by Roman Evstifeev 24 Oct '11

24 Oct '11

Hi. Is there a way to send a email to all project maintainers? ---- 1) Is it possible to do this via osc or OBS web interface? 2) Or is there a way to get a list of all email addresses of project maintainers? 2) Or maybe there is a mail-list of the project, i can send email to? ---- (i'm looking for "multimedia:apps" project, but those questions are interesting for all projects in general) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] expired GPG keys ?
by Martin Koller 24 Oct '11

24 Oct '11

Hi, I'd like to learn how the keyhandling in OBS is done, because when trying to install some software today, which refreshes the repos in yast, it complains about more or less every repo having an expired key (yast wants to import all the keys again). Now I check my own repo http://download.opensuse.org/repositories/home:/martinkoller/openSUSE_11.3/… and find repomd.xml.key which contains a key which has expired more than a year ago: expired: 2010-04-01 How can this be ? -- Best regards/Schöne Grüße Martin A: Because it breaks the logical sequence of discussion Q: Why is top posting bad? () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at

2 2

[opensuse-buildservice] Program returns random data in a function
by Damian Ivanov 23 Oct '11

23 Oct '11

Hi, I try to package dockmanager: https://launchpad.net/dockmanager The build fails at the end with: I: Program returns random data in a function E: dockmanager no-return-in-nonvoid-function dockmanager-daemon.c:1642 I am not a developer so I even have no clue what no-return-in-nonvoid-function is :) Can I disable somehow these tests? -- 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] Changing main sponsor from Novell to SUSE
by Kim Leyendecker 22 Oct '11

22 Oct '11

Hello all, There´s still shown Novell as "main sponsor" on build.o.o, shouldn´t this changed to SUSE? thanks, --kdl -- -o) Kim Leyendecker /\\ openSUSE Ambassador, openSUSE Wiki Team DE _\_v http://www.opensuse.org - Linux for open minds -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0