June 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] download repository -built rpms not listed.
by doiggl＠velocitynet.com.au 22 Jun '12

22 Jun '12

Hello, I have a package which builds ok and produces built rpms[1], but when I go to download repository[2] the files are not listed. Question: How can it be fixed so the download repository shows the built rpms ? Thanks Glenn... [1]Built rpm list. https://build.opensuse.org/package/binaries?package=kernel-vanilla&project=… kernel-vanilla-3.0.35-10.1.x86_64.rpm kernel-vanilla-base-3.0.35-10.1.x86_64.rpm kernel-vanilla-base-debuginfo-3.0.35-10.1.x86_64.rpm kernel-vanilla-debuginfo-3.0.35-10.1.x86_64.rpm kernel-vanilla-debugsource-3.0.35-10.1.x86_64.rpm kernel-vanilla-devel-3.0.35-10.1.x86_64.rpm kernel-vanilla-devel-debuginfo-3.0.35-10.1.x86_64.rpm kernel-vanilla-hmac-3.0.35-10.1.x86_64.rpm kernel-vanilla-3.0.35-10.1.nosrc.rpm [2] download repository -built rpms not listed. http://download.opensuse.org/repositories/home:/doiggl/openSUSE_12.1/x86_64/ -- 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] qemu Cross Compilation Instructions
by Troy Telford 21 Jun '12

21 Jun '12

I'd really like to RTFM, but in this case I can't find it: I'm looking for documentation - How do I configure my OBS 2.3 instance so that I can use qemu to compile packages for the ARM architecture? I've seen a few posts which mention installing qemu as a build dependency, such as: Preinstall: qemu-linux-user ExportFilter: ^qemu-linux-user.*\.x86_64.rpm$ . armv7l armv5el However, this doesn't seem to be all that is required. So far, I've been able to create a repo for the ARM architecture, and get the ARM scheduler running - however, builds are never attempted; they are stuck at "scheduled". So what else am I missing? Also - has qemu cross-compilation been attempted for a distribution other than openSUSE? Thanks. -- Troy Telford -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 11

[opensuse-buildservice] Improving debtransform
by Martin Koegler 19 Jun '12

19 Jun '12

OBS offers source services to build packages out of a VCS. But for dpkg-based distribution, the version number handling is not working. The version number of the binary packages is derived from debian/changelog file - updating this file in the source package is currently not possible. Therefore I tried to improve debtransform: https://github.com/e9925248/obs-build The changes make sure, that the first entry of any added changelog file matches the version number of the dsc file - otherwise it adds a dummy entry with the correct version number. This way, binary and source version number stay in sync. Other improvements: * support for replacing file content in the debian directory * fix empty file behaviour Regards, Martin -- 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] [gsoc] osc2 client - summary of week 3 and 4
by Marcus Hüwe 19 Jun '12

19 Jun '12

Hi, here's a small summary of the 3rd and 4th (coding) week . First of all I wasn't able to do lots of work in week 3 and 4 so I'm still working on the new build module for the osc2 library. The initial plan was to copy/reuse some of the existing modules from the (old) "osc" like the cpio [1] and packagequery modules. But I decided to refactor/rewrite cpio module for the following reasons: - "save" disc space: In our scenario we retrieve a cpio archive from the api (which contains binary packages for example). The old cpio module expects a filename in order to "unpack" the archive - that is the file has to be stored on disc first. Consequently approximately 2 * <archive size> of free disc space is needed. The new idea is that we pass a file-like object (in our case an object which inherits from "AbstractHTTPResponse") to the cpio module and unpack the archive "on the fly" (without storing the http response on disc first). - have testcases: The old cpio module has no testcases (because some time ago I didn't follow the TDD approach;) ). For nearly all modules in osc2 there exist testcases (white-box tests) thus it would be nice if we have some testcases for the cpio module, too (theoretically we could add some black-box tests (the current methods aren't really testable thus white-box tests aren't possible)). - have a nice pythonic interface: The new interface will look like this: from cpio import cpio_open # let "f" be a file-like object (for instance a http response) with cpio_open(fobj=f) as cpio_archive: for a_file in cpio_archive: # store file (with correct permissions etc.) in os.curdir a_file.write(os.curdir) # alternatively it's also possible to read some data (instead of # writing it to disc) via a_file.read(len) We will also support a plain filename in cpio_open. Currently the cpio module will only support the "new ascii" (ascii SVR4 no CRC) format and regular files (that's sufficient for our needs). But it will be possible to simply pass in a class for a different format (that is no code has to be altered in order to support a new format). Finally this will be finished by the end of this week. If you have any questions or suggestions please tell me:) Marcus [1] https://github.com/openSUSE/osc/blob/master/osc/util/cpio.py -- 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] OBS 1.3 Privately signed certificate and osc
by Dominig ar Foll (Intel OTC) 19 Jun '12

19 Jun '12

Hello, having just updated to OBS 1.3, my API is now running under https (not a bad idea). I have created a PRIVATE certificate following the README. --------------- mkdir /srv/obs/certs openssl genrsa -out /srv/obs/certs/server.key 1024 openssl req -new -key /srv/obs/certs/server.key \ -out /srv/obs/certs/server.csr openssl x509 -req -days 365 -in /srv/obs/certs/server.csr \ -signkey /srv/obs/certs/server.key -out /srv/obs/certs/server.crt cat /srv/obs/certs/server.key /srv/obs/certs/server.crt \ > /srv/obs/certs/server.pem ---------------------- I see that with osc (version 0.134.1) if the privately signed certificate is create with a Common Name (CN) which is not the server name, osc refuses to chat with the API. That is bit strick as : - CN name is normally free of use - In that mode access via IP address is not possible any more - auto recovery system with shadow server configuration cannot be done. That is very strange as it seems that when the certificate with an official root, the common name is not critical. Any clue how to overcome that issue ? Regards -- Dominig -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 7

[opensuse-buildservice] "W: non-executable-script" for files which are executable in the sources
by Florian Höch 19 Jun '12

19 Jun '12

I get the above warning for some files in the following package: https://build.opensuse.org/package/show?package=dispcalGUI&project=home%3Af… rpmlint log for Factory i586: dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxDisplayAdjustmentFrame.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/ccmx.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/main.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/report.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxwindows.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxLUTViewer.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/colormath.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/encodedstdio.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/jspacker.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/util_str.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxMeasureFrame.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/safe_print.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/xrandr.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/argyll_RGB2XYZ.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxTestchartEditor.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxProfileInfo.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/colord.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/util_win.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/setup.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/postinstall.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/dispcalGUI.py 0644L /usr/bin/env When I look into the source archive, the respective files have the executable bit set, so I'm not really understanding where the warning comes from. I've even hacked the spec file to make sure the files have the executable bit set (ie. I call chmod +x on the files in %prep), but it seems almost as if something removes it later? -- 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

3 4

[opensuse-buildservice] Authorative list of allowed RPM groups?
by Florian Höch 18 Jun '12

18 Jun '12

Basically I'd like something which isn't prone to change often, as I originally got the RPM group (Applications/Multimedia) I used for a package that I'm trying to submit to Factory from http://en.opensuse.org/openSUSE:Package_group_guidelines, but it seems the group was since removed. Are there any "safe bets" from the general graphics category which are less likely to change? (rpmlint returns a different list of possible RPM group names, are those more reliable)? -- 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 6

[opensuse-buildservice] Bogus warning "W: python-naming-policy-not-applied /usr/lib/pythonX.X/site-packages/X/lib/Y.py"
by Florian Höch 18 Jun '12

18 Jun '12

If you have a python package named X, which happens to contain a subpackage lib/Y, OBS complains that "This package doesn't respect the naming policy for python packages. Its name should match the regular expression ^python(-|$).", which is nonsensical because you can't import from a package "python-Y" as hyphens are not possible in package names, and a subpackage just named "python" doesn't make sense either. The warning in the subject should thus be removed. -- 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

1 0

[opensuse-buildservice] Creating anaconda style respin with OBS
by He Zhenxing 18 Jun '12

18 Jun '12

Hi, OBS has a great feature that it can define release media with production definition and uses kiwi to build the media, but I'm wondering if it also supports creating anaconda (RedHat/Fedora) style installation media or not. and if yes, where can I find the instructions? Thank you in advance! -- 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] Is Git backend for OBS available?
by He Zhenxing 18 Jun '12

18 Jun '12

Hi, What's the status of using git as the backend of OBS? Is this available in OBS 2.3? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1