November 2014 - openSUSE Build Service

[opensuse-buildservice] enabling networking for workers
by Darin Perusich 19 Dec '17

19 Dec '17

Hello All, I'm running a private instance and I'd like to enable networking on my workers so they can build some java apps, via maven, which need to download pom's/war's from the net. I ask google but he wasn't much help so I'm hoping someone here can help;-) How can I go about doing this? -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 10

[opensuse-buildservice] Ghost package
by trcs＠gmx.com 14 Dec '15

14 Dec '15

Hi. There is a ghost package in my OBS home project. I'm using the web interface, not the command line one. If you go to https://build.opensuse.org/project/show/home:jcsl:LXDE you can see the real 10 packages in the Packages box on left side, but if you look in the Build Results box, on the right side, you see 11 next to the "succeeded" text. If you then click the succeeded link you find the pcmanfm-1.2.0-beta1 package, and if you click on its link you get a Package "pcmanfm-1.2.0-beta1" not found in project "home:jcsl:LXDE", as expected. It even appears in the scheduled and building states when something I'm building triggers its build (I don't know how can this be). Any hints? Greetings. -- 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] Stalled submit requests
by Matwey V. Kornilov 18 Feb '15

18 Feb '15

Hm... You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right. 2012/10/18 Jos Poortvliet <jos(a)opensuse.org>: > On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote: > >> Hi, > >> > >> Is there a page to see full list of submit requests, ordered by date? This > >> statistics is of quite interest. > >> > >> For instance, there is no reaction for two month: (It is not ok for devel: > >> project, I think) > >> > >> >> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam > >> qp > >> > >> I think, having such a page, such statistics, one would be able to > >> redistribute his power. > > > > Not a bad idea at all - it'd nice to show which projects need some help, > which are doing very well etcetera. Maybe a top-ten of fastest SR/MR > solvers, too ;-) > > > > Crazy idea: Adrian responded to you that it is possible to request this info > from the API. If you got the skillzz to do that, it'd be nice to publish > those statistics somewhere - and that part I could help with. Something like > a weekly overview of the health of the OBS projects and stuff like that. > > > > Up for it? > > > > /Jos -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 9

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released
by Adrian Schröter 17 Feb '15

17 Feb '15

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- 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

4 4

[opensuse-buildservice] local check for if the "Requires" statements are correct?
by Gregor Mi 09 Feb '15

09 Feb '15

Hello, when I am doing an osc build locally all packages that are specified in the "BuildRequires" tags are installed in a isolated environment. Is the same possible for packages (including their versions) needed at runtime, i.e. specified by the "Requires" tags? My goal is to run some unit tests of packaged software to ensure the Requires dependencies are specified correctly without having to test it on a separate test machine. Best regards Gregor -- 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] SUSE:SLE-12:GA project is there
by Adrian Schröter 14 Jan '15

14 Jan '15

Good news everyone .... more work for OBS and all of us :) SLE 12 got imported. Right now only the x86_64 architecture is usable. ppc64le will come when we have the hardware in place. SLE 12 got added to the simple default target list in webui or when you want to add it manually use SUSE:SLE-12:GA / standard repository. Please note that the former existing SUSE:SLE-12 project got removed. -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] new package based on the existing one
by Gour 10 Dec '14

10 Dec '14

Hello, after many years I'm back to Suse and would like to create new package which is based on some existing one, iow. take existing one, rename it and modify. What is the best way to accomplish it? I was reading 'tutorial' but not sure whether 'branch' command is the way to go? Sincerely, Gour -- From wherever the mind wanders due to its flickering and unsteady nature, one must certainly withdraw it and bring it back under the control of the self. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 21

[opensuse-buildservice] no download for subproject's RPM
by Gour 30 Nov '14

30 Nov '14

Hello! I did some work on hiawatha-9.8 web server - applied patch which fixes problem when using wwwrun:www uid:gid for ServerId in Hiawatha's config file. The package did build successfully both locally and, afaict, it's fine in the cloud as well: https://build.opensuse.org/package/show/home:gour:branches:server:http/hiaw… but I wonder why is it not available for download via web like the other package I did today (https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite)? I'm still new to SUSE and OBS, but I assume that I do not have need to run Factory/Tumbleweed and can stay with stable (e.g. 13.2) and still submit packages for Factory and subscribe via URL to the repo containing my OBS home projects for the packages I fix or want newer versions? Sincerely, Gour -- The senses, the mind and the intelligence are the sitting places of this lust. Through them lust covers the real knowledge of the living entity and bewilders him. -- 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] arm workers
by Matwey V. Kornilov 29 Nov '14

29 Nov '14

Hi, Most of ARM workers seem to be dead. -- 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] May open build service be used to build Whonix (debian derivative) VM images?
by Patrick Schleizer 29 Nov '14

29 Nov '14

Hi! Whonix [1] is a derivative of Debian. Its VM build script needs: - mount (device-mapper), but I guess that would not be a problem, since open build service is based on KVM? - sudo (not just fakeroot) - is it available? - quite some load (hdd load, traffic load [downloading packages from debian repositories], build time [takes some time to create a whole vm image] - would that be a problem? Your servers are accustomed to building SUSE vm images, but as far I understand its architecture is a bit different and you might be using packaging caches and such. Using open build service as a CI service that is capable of building VM images would be very helpful to Whonix! What do you think? Would Whonix VM builds be welcome on open build service servers? Cheers, Patrick [1] https://www.whonix.org -- 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] Build C++ Files for different distributions
by Tobias Lauterbach 26 Nov '14

26 Nov '14

Okay, so what I achieved/understood so far is this: What Open Build Service does is extract my helloWorld-1.tar.gz After that we have a folder helloWorld-1 in our working directory. After which we change into that directory. Afterwards my build command "g++ -o helloWorldBin helloWorld.cpp" is executed, so I have a binary called "helloWorldBin" in my helloWorld-1 folder. As you said I now need to copy this binary into the" $RPM_BUILDROOT%{_bindir}" -Folder in the install section and add this file to the files section. Did I miss anything? If not, why can´t I just add the binary to the files Section? Because I just have one .cpp file and no make file I can´t execute any make commands like all of the examples I found., I tried to do the following: --- Name: helloWorld Version: 1 Release: 0 License: GPL-2.0+ Summary: helloWorld Url: http://www.qosmotec.com Group: Other Source: helloWorld-1.tar.gz BuildRequires: gcc-c++ cmake BuildRoot: %{_tmppath}/helloWorld %description %prep %setup -q %build g++ -o helloWorldBin helloWorld.cpp %install cp helloWorldBin $RPM_BUILDROOT%{_bindir}/hello_world_1 %post %postun %files %defattr(-,root,root) $RPM_BUILDROOT%{_bindir}/hello_world_1 ------ I get the following error: cp: cannot create regular file `/usr/bin/hello_world_1': Permission denied Somehow the spec guideline isn´t helping me much (https://en.opensuse.org/openSUSE:Specfile_guidelines) Excuse me for asking again and thank you very much for your help! Tobias N��r��y隊Z)z{.��Wlz��qﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǜ�)]��Ǿ� ޮ�^�ˬz��

4 3

[opensuse-buildservice] sles: xsltproc
by Matwey V. Kornilov 26 Nov '14

26 Nov '14

Hi, I need /usr/bin/xsltproc at build time. It is provided by libxslt package in SLES or libxslt-tools in openSUSE. Is there a way not to use %if version inside my spec? I mean, maybe substitute something. -- 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] Archiving Project - No openSUSE 13.2 build target.
by Malcolm 26 Nov '14

26 Nov '14

Hi Would some kind soul with the power needed, enable openSUSE 13.2 as a build target in this project? -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default up 3 days 13:02, 5 users, load average: 1.38, 0.61, 0.34 CPU Intel® B840(a)1.9GHz | GPU Intel® Sandybridge Mobile -- 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] Build C++ Files for different distributions
by Tobias Lauterbach 25 Nov '14

25 Nov '14

Hello, I´m quite new to building packages on Linux, so I have some very basic, probably stupid questions, but after hours of luckless research this is the last way I see to understand this. I have the task to find out how to avoid the need of 3 build servers for supplying three different distributions. All I read is the open build service would be able to build binary packages from sources for a wide range of operating systems and hardware architectures. But I don't understand what those sources are. Would I be able to compile binaries for different distributions from C++ code with this? And then based on those binaries build the packages? If yes, how can I do it? If not, what is the benefit from just building packages if I need to build the binaries on different distributions? Thank you very much, tol -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] Building 32bit-x86_64 bit libraries/packages for SLES12
by Jens Viebig 25 Nov '14

25 Nov '14

Hi List, we have just setup a local instance of OBS to build some third party packages and libraries not contained in SLES12. We have the need to build 32bit compatibility packages for x86_64 because some third party tool requires 32bit variants of some libraries, but we cannot figure out how to do it for SLES12 because there is no i586 toolchain. I had a look at sqlite2 that is also availabe as 32bit variant in SLES12. If we import it to our OBS instance and build it against SLES12 it only generates the 64bit variant and no 32bit_x86_64. If we build against openSUSE Factory, it builds both variants because i586 and x86_64 toolchains and dependencies are available If we enable i586 for the SLES12 repository target, it is unresolvable because of missing dependencies: nothing provides libtool, nothing provides readline-devel, nothing provides tcl-devel, nothing provides update-desktop-files, nothing provides rpm-build How were these packages like sqlite2 built for SLES12 and what is the official way to create 32bit variants of libraries for SLES12 ? Regards Jens -- 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] 用短信做宣传，怎么这么有效
by 小潘 23 Nov '14

23 Nov '14

想要最有效果的宣传，发发短信足矣。加q q ⑴⑼-⑶⑼-⑻⑼-⑺⑵⑸，支持测试。直在找你，可惜找不到，我猜想你应该是第一高中的学生，因此过来找你，想不到还真的遇见了你！” 夏小洛笑道：“嘿……雕虫小技！” 他的神态甚是亲昵，和刚刚对嘲笑，他嘴巴撇了一个足够表示他鄙视之情的弧度。曹浩暄拿起电话亲热地叫道：“小洛，你终于来电话了！” “开学挺忙的。”夏小洛简单的寒暄一句，直接切入正题。“浩暄，国学谈到俄语。他这才发现，田盛文还是文革前的大学生呢，俄语说得很溜，可是他结婚后，就真正的在这田家庄生了根，再也没有挪过窝。这种脊梁一般的知识分子，在商品经济洛，都以崇敬的目光看着夏小洛，产生了跟随之心。刚刚被流氓打倒的两个少年，走到已经奄奄一息的几个小流氓边上，不停地踢啊踢啊踢啊……怒道：“操恁娘，告诉你打人不打脸啊是情场浪子，但是那棵心脏早已经冷却，很难动心。在二十一世纪的大都市里，人们脚步匆忙，如同一台高速运转的发动机上的一枚微不足道的零件，在这种情况下，各种快餐式爱情发一个月工资就几十块钱，这手术费花了我二百多呢，可是，人命关天啊。” 夏小洛道：“放心吧，妈，儿子这个暑假一定帮你挣回这么多钱来。” 许小曼道：“得得，一边去，老妈

1 0

[opensuse-buildservice] custom kiwi build
by Matwey V. Kornilov 23 Nov '14

23 Nov '14

Hi, I would like to build kiwi image, using my custom kiwi patched package. I put the package into the project, and referenced it from both kiwi-config and project config, but OBS still uses kiwi version from 13.2. What did I do wrong? https://build.opensuse.org/project/show/home:matwey:pcm051:13.2 -- 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] multiple repos are repeatedly/frequently reporting "signed with an unknown key". what's misconfigured/broken, or ... ?
by grantksupport＠operamail.com 21 Nov '14

21 Nov '14

We've upgraded all our opensuse instances to 13.2; currently several hundred across multiple sites. As we're doing post-upgrade cleanups, etc, on `zypper *` we're seeing LOTS of 'unknown key' messages for/from repositories, for example, @ refresh, zypper -v ref Verbosity: 1 Initializing Target Specified repositories: Checking whether to refresh metadata for Backup Retrieving: repomd.xml ................................................................................................................................................................................................................[done] Repository 'Backup' is up to date. Checking whether to refresh metadata for BaseSystem Retrieving: repomd.xml ................................................................................................................................................................................................................[done] Retrieving: repomd.xml ................................................................................................................................................................................................................[done] Retrieving: repomd.xml.asc ............................................................................................................................................................................................................[done] Retrieving: repomd.xml.key ............................................................................................................................................................................................................[done] Retrieving: repomd.xml ................................................................................................................................................................................................................[done] File 'repomd.xml' from repository 'BaseSystem' is signed with an unknown key '88EB5D66E2C0098C'. Continue? [yes/no] (no): That ^^^ is just ONE example; most, if not yet all, enabled repos have returned this error at least once recently -- typically more often. This is NEW/CHANGED behavior. We're not alone -- we're hearing about this from multiple clients, and are bumping into similar issues/comments/questions online, in IRC, etc. This is happening for a broad variety of repos -- home: repos, 'semi-official' repos, *AND* official release/distribution repos. In any one run, there can be none-to-many repos that return the "signed with an unknown key" And, it's happening repeatedly & frequently. If I force clean up zypper clean --all rpm -qa | grep gpg-pubkey | xargs rpm -e zypper -vvv --gpg-auto-import-keys --no-gpg-checks ref --force then, an IMMEDIATELY subsequent `ref` or `dup`, of course, has no issues with unknown keys -- until "some time later". After a seemingly random amount of time -- just minutes to hours -- re-exec of the zypper cmd gets another mix of "unknown key" reports. For the example above, cat /etc/zypp/repos.d/BaseSystem.repo [BaseSystem] name=BaseSystem enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/repositories/Base:/System/openSUSE_13.2 gpgcheck=1 keeppackages=0 priority=30 type=rpm-md Checking @ http://download.opensuse.org/repositories/Base:/System/openSUSE_13.2/repoda… Index of /repositories/Base:/System/openSUSE_13.2/repodata Icon Name Last modified Size [DIR] Parent Directory - [ ] 0ebcac183295ce4d1fde2c8f614bbe0fc481804c7948418a9ac0613ad16a5efe-primary.xml.gz 20-Nov-2014 14:48 23K Details [ ] 488fb3091c6e475a247d1b10a6035dafb05519f9fbd6ddaa5265c2826517b5d0-other.xml.gz 20-Nov-2014 14:48 25K Details [ ] d5fc3d48a3aa46cf156ac47421ec3d979ba0d7849fc503437701384455726e4b-filelists.xml.gz 20-Nov-2014 14:48 47K Details [TXT] repomd.xml 20-Nov-2014 14:48 1.6K Details [ ] repomd.xml.asc 20-Nov-2014 14:48 481 Details [ ] repomd.xml.key 20-Nov-2014 14:48 1.1K Details Apache/2.2.12 (Linux/SUSE) Server at download.opensuse.org Port 80 MirrorBrain powered by Apache it's clear there's a recent "Last Modified" change to the repodata ... I do not yet know if there ae ACTUAL changes, or only timestamps are changing. At first glance, it appears that with each change to the repo's content -- specifically the filelists -- the ENTIRE file content of the /repodata dir is being re-timestamped. Including the repomd.xml.key ... which would be ONE cause of the "unkonwn key" issue. It's *possible* that multiple repos have been compromised, and that blackhats are changing keys at will -- but I *seriously* doubt it; pls correct me if I'm wrong. (1) Why are multiple repos' keys changing so frequently -- even for the same repo, sometimes multiple times within a day or so? (2) There appears to be no mechanism/source for VALIDATING the new/updated keys from within a zypper command -- That's a potential security issue. How are keys to be validated? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 2

[opensuse-buildservice] Enable "Go to download repository" link
by Jens Viebig 20 Nov '14

20 Nov '14

Another beginners question. In our private OBS instance the "Go to download repository"-Link is not available on the "State of Repository for..." page. I would love to have it the same way like it is on build.opensuse.org Where can this be configured/enabled ? As an Idea for the future, this could be set to http://custom.ip:82/home:/user/blahbla and enabled by default in a the default setup/iso for convenience on new installs ? Regards Jens -- 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] service tar_scm not automatically updating on build ?
by Jens Viebig 20 Nov '14

20 Nov '14

We have setup a local OBS instance (2.5) and are trying to build a package from svn via _service and tar_scm. It works fine but it seems when a rebuild is triggered via "trigger rebuild" on the repository web page it does not check against the svn if a new revision is available and does not update the tarball. I have to touch/re-save the _service file to trigger a tarball update. Is this a bug or intended behaviour ? How to make the build server to re-check against svn without changing _service file every time ? Here is my _service file: <services> <service name="tar_scm"> <param name="scm">svn</param> <param name="url">http://some.ip/repos/somerepo/trunk</param> <param name="filename">somename</param> </service> <service name="recompress"> <param name="compression">gz</param> <param name="file">*.tar</param> </service> <service name="set_version"/> </services> Sorry for asking so many questions just after registering Regards Jens -- 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] obs-service-$whatever tooling, packaging
by Roman Neuhauser 20 Nov '14

20 Nov '14

hello, TL;DR: i'd like all obs-service-* tools to have a Makefile, and i'd prefer if we could colocate all of them in a single git repository. i want to package obs-service-* for ArchLinux. most of these tools have no Makefile, and the build/install procedures are spelled out in their specfiles in b.o.o. i set out to move the build scripts into Makefiles since a) i don't fancy reproducing them in the prospective PKGBUILD files and b) it would do zilch for the future Debian packager. the various obs-service-* have quite simple and similar needs. if i went with a simple Makefile per service we'd end up with the common bits interspersed with the tool-specific ones, which i sense as fertile ground for divergence. instead, i went for a common obs-service.mk file which is identical among the different tools, and a GNUmakefile file to provide that with tool-specific bits. this arrangement makes it a bit easier to keep the common bits identical in the various tools, even though it obviously does nothing to remove the duplication itself; i'm not sure what/if i can do with that. simple: https://github.com/roman-neuhauser/obs-service-python_sdist/compare/wip-mak… local extras: https://github.com/roman-neuhauser/obs-service-download_files/compare/wip-m… https://github.com/roman-neuhauser/obs-service-format_spec_file/compare/wip… https://github.com/roman-neuhauser/obs-service-source_validator/compare/wip… obs-service-download_files inspired the $(cachedirs)/install-cache code which, on a closer look, should be local to that tool, AFAICT there's no other consumer of that feature. --- while the above solves the issues of packaging the various services for different packaging formats and removes *some* of the pain of keeping the machinery in sync, it does not solve the latter completely. even with the syncing procedure as simple as copying a file around, i fully expect the various copies of obs-service.mk to diverge over time. my suggestion here would be to mvoe all the obs-service-* tools into a single repository to bring the number of obs-service.mk copies down to one. is there another way? -- roman -- 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] Fwd: MonoDevelop crashes because of a library version mismatch
by Jacek Rużyczka 18 Nov '14

18 Nov '14

Hi folks, I have already posted this matter in the gtk-sharp mailing list, but the guys there suspect my issue to be related to the MonoDevelop RPM I am using: I am using gtk-sharp2 incl. glib-sharp2-2.12.10-85.13.x86_64 for my Mono project and for MonoDevelop (5.0.1-110.14) itself. The issue is that after the recent update, MD crashes a few seconds after opening whatever project. I get the following error message: monodevelop: symbol lookup error: /usr/lib64/libglibsharpglue-2.so: undefined symbol: g_type_check_instance_is_fundamentally_a The version of glib-sharp2 is the most recent I can get for my openSuSE 12.3 machine. For MD and the Mono files incl. gtk-sharp2 I am using Mono/Factory as a repo. One of the gtk-sharp guys told me the instance checking routine in libglibsharpglue had been added in May 2014: https://mail.gnome.org/archives/commits-list/2014-May/msg08836.html What shall I do? Thank you for any useful hints. Kind regards Jacek Rużyczka -- 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-compare forces republish for new commit and new rpm
by Olaf Hering 18 Nov '14

18 Nov '14

I wonder why its important to republish a package which just had a new commit. If the resulting binary package is identical there is no need to republish, just because the rpm %RELEASE string happens to differ. Similar for a new rpm version in the build tree. Why would that require a republish of the entire tree? I mean the install stack has to cope with old rpm packages anyway, no matter which version of rpm was used to create these packages. Thats the (untested) change I propose to handle both cases and leave the previous package on the mirror: Index: functions.sh =================================================================== --- functions.sh (revision 222a61b1a991885b87a3e16ef27c22bb) +++ functions.sh (working copy) @@ -59,7 +59,7 @@ QF="$QF %{VENDOR} %{DISTRIBUTION} %{DISTURL}" QF="$QF %{LICENSE} %{LICENSE}\\n" QF="$QF %{GROUP} %{URL} %{EXCLUDEARCH} %{EXCLUDEOS} %{EXCLUSIVEARCH}\\n" - QF="$QF %{EXCLUSIVEOS} %{RPMVERSION} %{PLATFORM}\\n" + QF="$QF %{EXCLUSIVEOS} %{PLATFORM}\\n" QF="$QF %{PAYLOADFORMAT} %{PAYLOADCOMPRESSOR} %{PAYLOADFLAGS}\\n" @@ -91,13 +91,6 @@ # Remember to quote the . which is in release release1=`$RPM --qf "%{RELEASE}" "$oldrpm"|sed -e 's/\./\\\./g'` release2=`$RPM --qf "%{RELEASE}" "$newrpm"|sed -e 's/\./\\\./g'` - # This might happen with a forced rebuild of factory - if [ "${release1%.*}" != "${release2%.*}" ] ; then - echo "release prefix mismatch" - if test -z "$check_all"; then - return 1 - fi - fi check_provides $oldrpm $release1 > $file1 check_provides $newrpm $release2 > $file2 Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 15

[opensuse-buildservice] build fails with "missing packages: build-compare@<chksum>"
by Olaf Hering 18 Nov '14

18 Nov '14

I have tweaked build-compare enough to handle kernel-binary packages. For some reason the part of the build which does "rpmbuild kernel-binary.spec" fails at the very end with: missing packages: build-compare@4fb40b45ede614509b721c69adb46441 This does not happen with other packages like xen or whatever. Looking through my changes its not obvious why the kernel packages behave different. Any idea what is going on, and how to debug the remote build? Olaf -- 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] OBS 2.5 appliance behind company proxy - problems
by Miroslav Sabljic 17 Nov '14

17 Nov '14

Hello guys! I need some help with setting up my local OBS installation to work behind our company proxy (squid). I was searching trough documentation and tried whatever I found about proxy but so far nothing was successful. So here is the story. OBS is installed and proxy is configured on the system with yast. Zypper, curl, and other work without a problem. Proxy uses port 8080 and authentication. I've defined http_proxy and no_proxy variables to options.yml because without this it couldn't download list of available platform repositories from remote OBS instance. After all this I still cannot build a package, it is always staying in scheduled state and nothing happens. Can you please point me to some documentation about proxy or tell me is there maybe some older version of OBS that officially supports proxy? Thanks! -- Best regards, Miroslav -- 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 2.5.x + clockwork = ActiveRecord::ConnectionTimeoutError
by Srinidhi B 17 Nov '14

17 Nov '14

Hi, A couple of months back, we updated our local OBS server to OBS 2.5.4. Ever since this update, we've had a lot of issues with clockwork and delayed_job. As soon as we updated OBS, /srv/www/obs/api/tmp/clockworkd.clock.output said: I, [2014-09-12T20:30:55.163170 #29041] INFO -- : Triggering 'fetch notifications' E, [2014-09-12T20:31:00.163931 #29041] ERROR -- : could not obtain a database connection within 5.000 seconds (waited 5.000 seconds) (ActiveRecord::ConnectionTimeoutError) /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:190:in `block in wait_poll' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:181:in `loop' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:181:in `wait_poll' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:136:in `block in poll' /usr/lib64/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:146:in `synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:134:in `poll' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:423:in `acquire_connection' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:356:in `block in checkout' /usr/lib64/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:355:in `checkout' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection' /usr/lib64/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection' /srv/www/obs/api/config/clock.rb:39:in `block in <module:Clockwork>' /usr/lib64/ruby/gems/2.0.0/gems/clockwork-0.7.0/lib/clockwork/event.rb:51:in `call' /usr/lib64/ruby/gems/2.0.0/gems/clockwork-0.7.0/lib/clockwork/event.rb:51:in `execute' /usr/lib64/ruby/gems/2.0.0/gems/clockwork-0.7.0/lib/clockwork/event.rb:41:in `block in run' This continued for a few days until I realized we weren't receiving any build failure notifications. Since I couldn't debug the issue - and I wasn't aware of the fact that clockwork log file was in "tmp" directory instead of "log" - I simply restarted /etc/init.d/obsapidelayed service. Immediately, our users were bombarded with a build failure mails! Running "mysqladmin processlist", showed that there were more than 34-36 database connections open - almost each and every one of them had "Sleep" mentioned in the "Command" column. The same story repeated a couple of weeks back which triggered me to make the following changes in database.yml: production: .. - pool: 30 + pool: 50 + checkout_timeout: 15 After this change, I managed to keep delayed_job happy for almost 2 weeks. Last week, things once again went to bad state: I, [2014-11-12T16:09:31.940219 #6089] INFO -- : Triggering 'status.refresh' E, [2014-11-12T16:09:36.938688 #6089] ERROR -- : could not obtain a database connection within 15.000 seconds (waited 15.000 seconds) (ActiveRecord::ConnectionTimeoutError) /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:190:in `block in wait_poll' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:181:in `loop' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:181:in `wait_poll' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:136:in `block in poll' /usr/lib64/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:146:in `synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:134:in `poll' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:423:in `acquire_connection' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:356:in `block in checkout' /usr/lib64/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:355:in `checkout' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection' /usr/lib64/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection' /usr/lib64/ruby/gems/2.0.0/gems/activerecord-4.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection' /srv/www/obs/api/config/clock.rb:39:in `block in <module:Clockwork>' /usr/lib64/ruby/gems/2.0.0/gems/clockwork-0.7.0/lib/clockwork/event.rb:51:in `call' /usr/lib64/ruby/gems/2.0.0/gems/clockwork-0.7.0/lib/clockwork/event.rb:51:in `execute' /usr/lib64/ruby/gems/2.0.0/gems/clockwork-0.7.0/lib/clockwork/event.rb:41:in `block in run' As of now, I've 57 connections to the database: # mysqladmin processlist | grep frontend | wc -l 57 (Ignore the "grep", I'm just being lazy for skipping the table borders and the table header. There is just one database served by the MySQL server) Regarding mysql's max connections: # mysqladmin -p variables | grep max_conn Enter password: | max_connect_errors | 10 | | max_connections | 151 | Apparently, we keep filling up ActiveRecord's connection pool without freeing any of the connections. Not sure if the issue occurs because we have set "fetch_notifications" job to be run in a different thread: every(27.seconds, 'fetch notifications', thread: true) do ActiveRecord::Base.connection_pool.with_connection do |sql| # this will return if there is already a thread running UpdateNotificationEvents.new.perform end end (Yes, I changed the duration from 17 to 27 seconds after I increased the timeout in database.yml from 5 to 15) Has someone else found this issue? I can't find any solution other than setting a daily cron job to restart obsapidelayed :-/ Regards, Srinidhi. -- 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] Factory vs Tumbleweed repos (again)
by Greg Freemyer 17 Nov '14

17 Nov '14

In my home project I just removed the Factory repo and added the Tumbleweed repo. I understood that to be the recommendation. Now when I run "osc build" the default repo is RedHat. Not exactly my preference. I'm re-adding factory until that is resolved. 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 2

[opensuse-buildservice] Freeing buildserver resources: remove driver:
by Johannes Weberhofer 17 Nov '14

17 Nov '14

Dear all! In September there was a discussion about maintainers of the driver: section here: http://lists.opensuse.org/opensuse-factory/2014-09/msg00163.html I think it's time to delete the complete "driver:" project. Any objections against? Can someone do that? Best regards, Johannes -- 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

1 0

[opensuse-buildservice] "Link has errors: conflict in file debian.control"
by Florian Höch 15 Nov '14

15 Nov '14

Hi, if you look at the following URL: https://build.opensuse.org/package/show/multimedia:color_management/dispcal… You'll see the error "Link has errors: conflict in file debian.control". I have no clue what that is supposed to mean, pointers welcome. -- 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 1

[opensuse-buildservice] solving conflicts
by Olaf Hering 14 Nov '14

14 Nov '14

How do I solve this conflict? Just copying the prjconf part from openSUSE:Factory does not work. The package has a PreReq: udev. [ 11s] now installing cumulated packages [ 14s] Preparing... ######################################## [ 14s] file /usr/lib64/libudev.so.1.4.0 conflicts between attempted installs of libudev-mini1-210-25.5.4.x86_64 and libudev1-210-25.5.4.x86_64 [ 14s] file /usr/bin/udevadm conflicts between attempted installs of udev-mini-210-25.5.4.x86_64 and udev-210-25.5.4.x86_64 [ 14s] file /usr/lib/systemd/systemd-udevd conflicts between attempted installs of udev-mini-210-25.5.4.x86_64 and udev-210-25.5.4.x86_64 [ 14s] file /usr/lib/udev/accelerometer conflicts between attempted installs of udev-mini-210-25.5.4.x86_64 and udev-210-25.5.4.x86_64 [ 14s] file /usr/lib/udev/ata_id conflicts between attempted installs of udev-mini-210-25.5.4.x86_64 and udev-210-25.5.4.x86_64 [ 14s] file /usr/lib/udev/cdrom_id conflicts between attempted installs of udev-mini-210-25.5.4.x86_64 and udev-210-25.5.4.x86_64 [ 14s] file /usr/lib/udev/collect conflicts between attempted installs of udev-mini-210-25.5.4.x86_64 and udev-210-25.5.4.x86_64 [ 14s] file /usr/lib/udev/scsi_id conflicts between attempted installs of udev-mini-210-25.5.4.x86_64 and udev-210-25.5.4.x86_64 [ 14s] exit ... %if 0%{?suse_version} >= 1310 # prefer the small systemd for building Conflict: libudev1:udev-mini Prefer: libudev-mini-devel libudev-mini1 udev-debuginfo libudev1-debuginfo Prefer: systemd-mini systemd-mini-devel Prefer: systemd-mini-devel:systemd-mini Prefer: udev-mini libcom_err2-mini libext2fs2-mini Prefer: libudev1:udev %endif Olaf -- 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] How to suppress rpmlint error for non-standard interpretor
by Rashmi Ranjan Mohanty 14 Nov '14

14 Nov '14

Hi, I am getting these rpmlint errors. How do I suppress it ? ==================================== [ 885s] (none): E: badness 3831 exceeds threshold 1000, aborting. [ 885s] novell-zenworks-rubygem-rake.noarch: E: wrong-script-interpreter (Badness: 533) /opt/novell/zenworks/bin/rake /opt/novell/zenworks/bin/ruby [ 885s] novell-zenworks-ruby.x86_64: E: wrong-script-interpreter (Badness: 533) /opt/novell/zenworks/bin/irb /opt/novell/zenworks/bin/ruby [ 885s] novell-zenworks-ruby.x86_64: E: wrong-script-interpreter (Badness: 533) /opt/novell/zenworks/bin/testrb /opt/novell/zenworks/bin/ruby [ 885s] novell-zenworks-ruby.x86_64: E: wrong-script-interpreter (Badness: 533) /opt/novell/zenworks/bin/erb /opt/novell/zenworks/bin/ruby [ 885s] novell-zenworks-ruby.x86_64: E: wrong-script-interpreter (Badness: 533) /opt/novell/zenworks/bin/rdoc /opt/novell/zenworks/bin/ruby [ 885s] novell-zenworks-ruby.x86_64: E: wrong-script-interpreter (Badness: 533) /opt/novell/zenworks/bin/ri /opt/novell/zenworks/bin/ruby [ 885s] novell-zenworks-ruby.x86_64: E: wrong-script-interpreter (Badness: 533) /opt/novell/zenworks/bin/gem /opt/novell/zenworks/bin/ruby [ 885s] This script uses an incorrect interpreter. Correct interpreters should be an [ 885s] absolute path to a file in in /(s)bin or /usr/(s)bin. Alternatively, if the [ 885s] file isn't supposed to be executed, then don't mark it as executable. ======================================== Also is there a way to completely skip the tests that are run after building the packages ? I think these tests run only for SUSE distros. Regards Rashmi -- 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] Package publication to few repository servers
by Konstantin Rudenkov 14 Nov '14

14 Nov '14

Is it possible to setup parallel package publication to few repository servers? If yes, where shall i look for? Do you have examples? ________________________________________ best regards Konstantin Rudenkov -- 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] Package fails in OBS, local osc build works
by Dimstar / Dominique Leuenberger 13 Nov '14

13 Nov '14

Hi all, I'm posting to -buildservice as I think from a packaging PoV, the .spec should be fine. The package Virtualization:VMware/open-vm-tools fails to build for openSUSE_13.2 and openSUSE_Factory repositories. If I check this package out and do locally osc build, then the build works just fine, either in a chroot env (default for me) or in a kvm sessioon using --vm-type=kvm. Both cases give successful builds. Which special trick did I miss to get the same result in OBS as I get locally? Cheers, Dominique -- Dimstar / Dominique Leuenberger <dimstar(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

3 6

[opensuse-buildservice] External kernel modules SLES 12
by Christof Hanke 12 Nov '14

12 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I have a strange problem with loading a kernel-module (openafs) built on OBS (package filesystems/openafs16). The module builds fine and is apparently signed : dummy0:~ # modinfo /lib/modules/3.12.28-4-default/updates/libafs.ko filename: /lib/modules/3.12.28-4-default/updates/libafs.ko license: http://www.openafs.org/dl/license10.html srcversion: 40263E5014D985AEA7C9C32 depends: vermagic: 3.12.28-4-default SMP mod_unload modversions signer: SUSE Linux Enterprise Secure Boot Signkey sig_key: 3F:B0:77:B6:CE:BC:6F:F2:52:2E:1C:14:8C:57:C7:77:C7:88:E3:E7 sig_hashalgo: sha256 insmod however fails with ERANGE : dummy0:~ # insmod /lib/modules/3.12.28-4-default/updates/libafs.ko insmod: ERROR: could not insert module /lib/modules/3.12.28-4-default/updates/libafs.ko: Numerical result out of range Unfortunately, ERANGE is not mentioned as a possible errno in the man-page, neither can I find something useful on google. However, I provide also the kernel-module source as an rpm for people to build the module against custom kernels. This one also builds fine, but it is unsigned : dummy0:~ # modinfo /usr/src/kernel-modules/openafs/libafs_tree/src/libafs/MODLOAD-3.12.28-4-default-MP/libafs.ko filename: /usr/src/kernel-modules/openafs/libafs_tree/src/libafs/MODLOAD-3.12.28-4-default-MP/libafs.ko license: http://www.openafs.org/dl/license10.html srcversion: 40263E5014D985AEA7C9C32 depends: vermagic: 3.12.28-4-default SMP mod_unload modversions and insmod works : dummy0:~ # insmod /usr/src/kernel-modules/openafs/libafs_tree/src/libafs/MODLOAD-3.12.28-4-default-MP/libafs.ko dummy0:~ # lsmod | grep afs libafs 844736 0 (Actually, the whole openafs-client works). The only difference I see is the signature of the module. Is this a bug in OBS or in SLES 12 ? Whom should I contact about this ? Many thanks, Christof -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJUYjk6AAoJEHOAkeR8FKk+w9IH/i1aNOAlSvd/IQ4DxLmfegth ndZn7L8xpZpCSlOVI2IBaRgbC4tOHAh02R68RM2WjAWiqfsWeGp29O1UeH4uLpDG H6s5BPYSbmZWwa/1KMPWxndakMWR2WCdtUq8RpvWganYOAtttyBo1vw9U2+DBESK 7L7FvaA49j6SKy4Wfpm8eiH682Pey4cP0zb8cuDZ5IhAFKJZM6b6kTv1ygeiOqgo RhhppG9BiX6Xm6ImZUch+Bae9BcibXpzK2/hO6mQOaGop4BJ6JXYF1t23RvznEXG 645ws04OWltN8U/Wpgzj+x6jobILjcg5TWL4LkXdD29tC4r+S30gX59m+G3pP3I= =qK2a -----END PGP SIGNATURE-----

2 2

[opensuse-buildservice] obs and proxy authentication
by Markus Hartmann 12 Nov '14

12 Nov '14

Hi all, I'am trying to set up an internal instance of obs version 2.5.5. I followed the guides and all works fine, except the proxy authentication. User who are already registert at the build service have no problem to login, but users who was not registered before get an internal server error. The authentication at the proxy works fine (apache + kerberos) for them. Completed 200 OK in 68ms (Views: 9.6ms | ActiveRecord: 0.4ms | Backend: 0.0ms | XML: 0.0 ms) [8ac1975a-8cd7-4afd-b9c2-67ff1fca5217] [6116:624.76] Started GET "/" for ::1 at 2014-11-12 10:30:07 +0100 [8ac1975a-8cd7-4afd-b9c2-67ff1fca5217] [6116:624.77] Processing by Webui::MainController#index as HTML [312c941a-850a-42ef-ae03-23981e8a6c8e] [6027:706.40] Started GET "/person/p0543101" for ::1 at 2014-11-12 10:30:07 +0100 [312c941a-850a-42ef-ae03-23981e8a6c8e] [6027:706.40] Processing by PersonController#get_userinfo as XML [312c941a-850a-42ef-ae03-23981e8a6c8e] [6027:706.40] Parameters: {"login"=>"p0543101"} [312c941a-850a-42ef-ae03-23981e8a6c8e] [6027:706.40] iChain user extracted from header: p0543101 [312c941a-850a-42ef-ae03-23981e8a6c8e] [6027:706.41] Rendered status.xml.builder (0.8ms) [312c941a-850a-42ef-ae03-23981e8a6c8e] [6027:706.41] Completed 404 Not Found in 8ms (Views: 3.1ms | ActiveRecord: 0.7ms | Backend: 0.0ms | X ML: 0.0ms) [8ac1975a-8cd7-4afd-b9c2-67ff1fca5217] [6116:624.83] Completed 500 Internal Server Error in 62ms [8ac1975a-8cd7-4afd-b9c2-67ff1fca5217] [6116:624.84] ActiveXML::Transport::NotFoundError (<status code="not_found"> <summary>Couldn't find User with login = p0543101</summary> </status> ): lib/activexml/transport.rb:447:in `handle_response' lib/activexml/transport.rb:394:in `http_do' lib/activexml/transport.rb:231:in `direct_http' app/controllers/webui/webui_controller.rb:139:in `authenticate_proxy' app/controllers/webui/webui_controller.rb:113:in `authenticate' activesupport (4.0.3) lib/active_support/callbacks.rb:427:in `_run__4557803593320860530__process_action__callbacks' activesupport (4.0.3) lib/active_support/callbacks.rb:80:in `run_callbacks' actionpack (4.0.3) lib/abstract_controller/callbacks.rb:17:in `process_action' actionpack (4.0.3) lib/action_controller/metal/rescue.rb:29:in `process_action' actionpack (4.0.3) lib/action_controller/metal/instrumentation.rb:31:in `block in process_action' activesupport (4.0.3) lib/active_support/notifications.rb:159:in `block in instrument' activesupport (4.0.3) lib/active_support/notifications/instrumenter.rb:20:in `instrument' activesupport (4.0.3) lib/active_support/notifications.rb:159:in `instrument' actionpack (4.0.3) lib/action_controller/metal/instrumentation.rb:30:in `process_action' actionpack (4.0.3) lib/action_controller/metal/params_wrapper.rb:245:in `process_action' activerecord (4.0.3) lib/active_record/railties/controller_runtime.rb:18:in `process_action' actionpack (4.0.3) lib/abstract_controller/base.rb:136:in `process' actionpack (4.0.3) lib/abstract_controller/rendering.rb:44:in `process' actionpack (4.0.3) lib/action_controller/metal.rb:195:in `dispatch' actionpack (4.0.3) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch' actionpack (4.0.3) lib/action_controller/metal.rb:231:in `block in action' actionpack (4.0.3) lib/action_dispatch/routing/route_set.rb:80:in `call' actionpack (4.0.3) lib/action_dispatch/routing/route_set.rb:80:in `dispatch' actionpack (4.0.3) lib/action_dispatch/routing/route_set.rb:48:in `call' actionpack (4.0.3) lib/action_dispatch/routing/mapper.rb:44:in `call' actionpack (4.0.3) lib/action_dispatch/journey/router.rb:71:in `block in call' actionpack (4.0.3) lib/action_dispatch/journey/router.rb:59:in `each' actionpack (4.0.3) lib/action_dispatch/journey/router.rb:59:in `call' actionpack (4.0.3) lib/action_dispatch/routing/route_set.rb:680:in `call' config/initializers/wrap_parameters.rb:41:in `call' hoptoad_notifier (2.4.11) lib/hoptoad_notifier/rack.rb:27:in `call' rack (1.5.2) lib/rack/deflater.rb:25:in `call' I tought the obs would create an internal account for everey "trusted" user who come from the proxy. Also a creation by my self does not work, because sign up is disabled in proxy mode. Any suggestions? Tanks in advance Markus -- 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 do I go about packaging Bitwig Studio?
by Roger Luedecke 11 Nov '14

11 Nov '14

I've never really tried packaging anything before, but I'd really like to make Bitwig Studio available. I've successfully converted Bitwig Studio from .deb using alien. I also found a Fedora guy who has been building RPM for it, and I'll attach his spec file. If I understand his .spec, it'd require the inclusion of the .deb which if I remember we aren't allowed to put proprietary software in OBS. This is a very impressive piece of software, so I'd like some guidance. -- Roger Luedecke openSUSE Project Member and Advocate since 2011 http://www.opensuseadventures@blogspot.com

3 7

[opensuse-buildservice] Is the Tumbleweed Repo stable yet?
by Greg Freemyer 11 Nov '14

11 Nov '14

I just happened to notice I have several packages that build fine for 13.2 and factory, but fail for tumbleweed. Do I need to delete Tumbleweed as a repo and re-add it? -- As an example this one should build fine for Tumbleweed: https://build.opensuse.org/package/show/security:forensics/libbde I just triggered a rebuild and the rebuild failed stating I can't meet all the dependencies. The dependencies are all in 13.2 as well as factory, so Tumbleweed should have them under both the old and new definition. 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

1 0

[opensuse-buildservice] Question: SourceService _service
by Carsten Ziepke 10 Nov '14

10 Nov '14

Hello, a question about the SourceService _service, where i couldn't find an answer: Is it possible to keep the via _service downloaded source files? When I used _service to download the source files, it reruns the service after every small changes (e.g. small fixes to spec or adding an entry in changes). Thank you, Carsten

2 1

[opensuse-buildservice] "Delete built binaries" not working?
by Urs Beyerle 09 Nov '14

09 Nov '14

Hi, How can I delete binaries from a repo? What I have tried so far: 1. Using the webgui, I disabled all flags (including build and publish flag) 2. Using the webgui, I clicked under "State of Repository" on "Delete built binaries" 3. Waiting 3 days Unfortunately the binaries are still remaining in the repo. My repo: https://build.opensuse.org/project/show/home:beyerle:IAC In case of openSUSE_13.2 I have disabled 36 packages and I have deleted all corresponding binaries - which didn't work has far as I see. For example "nethogs" https://build.opensuse.org/package/show/home:beyerle:IAC/nethogs https://build.opensuse.org/package/binaries/home:beyerle:IAC/nethogs?reposi… shows "No built binaries" But the files are still in the repo: http://download.opensuse.org/repositories/home:/beyerle:/IAC/openSUSE_13.2/… http://download.opensuse.org/repositories/home:/beyerle:/IAC/openSUSE_13.2/… Any help is very welcome! Urs -- 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] Open Build Service 2.5.5 released
by Adrian Schröter 07 Nov '14

07 Nov '14

This is most likely our last OBS 2.5 maintenance release. It contains some fixes which were provided by you guys. Thanks a lot again for this. Refreshed packages and appliances can be found at the usual place, the OBS:Server:2.5 project Details from the ReleaseNotes: ============================== Feature backports: ================== * none Changes: ======== * none Bugfixes: ========= * api: Fixes for LDAP authentification * api: Do not enable enforce_project_keys by default for new installations * api: Use be_not_nobody! in Package model check_source_access * api: use own delayed job queue for bugzilla monitoring * backend: do not depend ith initrd creation on LVM * backend: Add armv7hl again for compatibility on setup using it to build soft/hardfloat side-by-side * backend: LVM setup: take size of OBS server partition into account -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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 2.6 Beta 1
by Adrian Schröter 05 Nov '14

05 Nov '14

Good news admins.... ... you have new work :) The best way that we hear and solve your update problem is to update to OBS 2.6 Beta 1 right now (you may use a test system). OBS 2.6 Beta is available as version 2.5.90 inside of OBS:Server:2.6 project. You can find appliances and package repositories here: http://download.opensuse.org/repositories/OBS:/Server:/2.6/ SLE_12 needs one more fix to be available. You can find the temporary release and update notes here: https://github.com/openSUSE/open-build-service/blob/2.6/ReleaseNotes-2.6 We will improved it a bit more before the release. -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] MemoryCrash with rpmlint (32bit)
by Raymond Wooninck 05 Nov '14

05 Nov '14

Hi, At this moment I am receiving a memorycrash for rpmlint when building chromium. The buildlog shows: [ 9524s] + rpmlint_logfile=/home/abuild/rpmbuild/OTHER/rpmlint.log [ 9524s] + rm -f //home/abuild/rpmbuild/OTHER/rpmlint.log [ 9524s] + ret=0 [ 9524s] + mount -n -tproc none //proc [ 9524s] + su -s /opt/testing/bin/rpmlint abuild -- --info //home/abuild/rpmbuild/RPMS/i586/chromium-beta- ffmpegsumo-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium- beta-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium-beta- desktop-gnome-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromedriver-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium-beta-desktop- kde-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/SRPMS/chromium- beta-39.0.2171.42-1.3.src.rpm [ 9745s] Traceback (most recent call last): [ 9745s] File "rpmlint.py", line 384, in <module> [ 9745s] File "rpmlint.py", line 169, in main [ 9745s] File "rpmlint.py", line 231, in runChecks [ 9745s] File "BinariesCheck.py", line 382, in check [ 9745s] File "BinariesCheck.py", line 179, in __init__ [ 9745s] File "Pkg.py", line 93, in getstatusoutput [ 9745s] MemoryError [ 9745s] + ret=1 [ 9745s] + cat //home/abuild/rpmbuild/OTHER/rpmlint.log [ 9745s] 1 packages and 0 specfiles checked; 0 errors, 2 warnings. This is however only for the i586 buildhosts and I would like to know how I can resolve this ? I already have a _constraints file that is requesting 4Gb of memory, but I can't imagine that rpmlint requires more. The 64bit builds goes fine. Thanks Regards Raymond ----------------------------------------- -- 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] Need an RSA key for openssl signing, please create a new key
by Jörg Lorenzen 05 Nov '14

05 Nov '14

Hi, I have a problem with building KMP-packages for openSUSE 13.2 and higher (Factory). When I branch e.g. package virtualbox from project Virtualization, the build process ends successfully for repositories < 13.2, but fails for openSUSE 13.2 with following message: "Need an RSA key for openssl signing, please create a new key" Non-KMP-packages are build successfully for all repositories, it only fails for packages that provide kernel object files. Is there anything I forgot as I added repository for 13.2 or is this an error in OBS? Greetings Jörg Lorenzen -- 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] Project-Meta Information to build for/against tumbleweed and factory
by Johannes Kastl 04 Nov '14

04 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, as Tumbleweed and Factory merged, what to change in a home project's meta settings, to build for/against the new tumbleweed and the new factory? I have not seen (or may have missed) information on this. Are these still valid entries, or are they merging, getting new names or whatever? <repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Tumbleweed" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_Factory"> <path project="openSUSE:Factory" repository="snapshot"/> <arch>i586</arch> <arch>x86_64</arch> </repository> Regards, Johannes - -- It is dangerous to be right when the government is wrong. (Voltaire) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlRZJiEACgkQzi3gQ/xETbKO7ACggodcP/EtCX0VZA2bbtOnsVd0 hMcAn27g3uSFVrQefzupy3vSG/TOrmKB =21BN -----END PGP SIGNATURE----- -- 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] inject _pubkey to imported SUSE:SLE-12:GA (own instance)
by Christian Schneemann 04 Nov '14

04 Nov '14

Hi, at the moment I have to do local builds with osc build SUSE:SLE-12:GA x86_64 --no-verify, because there is no pubkey for this repository. Is it possible to inject the pub key somehow? I have imported the RPMs from the ISO files. Regards, Christian -- Christian Schneemann System Management & Monitoring Architect Tel.: +49-175-7250665 Mail: schneemann(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 -- 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] Issue with sqlite and libxml2 packages in SLE12 ?
by Rashmi Ranjan Mohanty 03 Nov '14

03 Nov '14

Hi, Is there any issue with the sqlite and libxml2 packages in SLE12 OBS repository ? One package I was building failed while linking to these libraries. When I tried to compile the package on an installed SLE12 system, it worked just fine. Only in OBS its failing. Project : home:mrashmiranjan:zmd-backend Package : solv-backend Can someone please help what is the problem ? Thanks and Regards Rashmi -- 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] [Fwd: Re: [Openvpn-users] RE 2.3.5 - systemd] fail on the OBS 2/2
by Hans Witvliet 01 Nov '14

01 Nov '14

Please have a look at the comment of one of the developpers of openvpn.. How can i provide: libsystemd.pc or libsystemd-daemon.pc files ? Hans -------- Forwarded Message -------- > From: David Sommerseth <openvpn.list(a)topphemmelig.net> > Reply-to: openvpn-users(a)lists.sourceforge.net > To: Gert Doering <gert(a)greenie.muc.de>, J.Witvliet(a)mindef.nl > Cc: hwit(a)a-domani.nl, openvpn-users(a)lists.sourceforge.net > Subject: Re: [Openvpn-users] RE 2.3.5 - systemd > Date: Fri, 31 Oct 2014 21:51:22 +0100 > > On 30/10/14 19:28, Gert Doering wrote: > > Hi, > > > > On Thu, Oct 30, 2014 at 11:39:22AM +0100, J.Witvliet(a)mindef.nl > > wrote: > >> My first assumption was that on this particular build-node, > >> system was not found, But that makes no sense, as 2.3.4 builds > >> OK, with or without system on OS12.2, OS12.3, OS13.1, OS13.2, > >> OSFactory, SLES11SP3 and SLES12 > >> > >> Have to dive a bit deeper, I guess. > >> > > > > 2.3.4 doesn't link to systemd, just call the binary - 2.3.5 > > contains the additional check "is systemd running?" via libsystemd. > > So, on a system that does not actually have systemd installed, > > 2.3.4 would compile just fine, and possibly just not use the > > systemd ask-password at run-time, while 2.3.5 will not build. > > > > If there *is* systemd on that node, it should compile, though... > > > > David, this is yours to diagnose further and patch :-) > > Yes, 2.3.4 and earlier did not carry any libsystemd or > libsystemd-daemon if compiled with --enable-systemd. However, the > check if the system was booted with systemd or not was not optimal > earlier on either. That has improved now. > > The dependency of libsystemd or libsystemd-daemon (depends on which > version of systemd is installed) is caused by us now calling > sd_booted() now instead of checking if the cgroups file tree with > systemd traces is present or not. By calling sd_booted(), systemd > provides us a sane way to do this check, even if they decide to change > the check mechanism under the hood. > > When OpenVPN is built for a system using systemd, it doesn't matter if > it has this dependency or not, systemd will always be available. And > if not, the OpenVPN package should pull in the needed systemd package > when being installed. For RPM based distributions, the complete > distro is built either with or without systemd, there is no "maybe > systemd is here" scenario. > > The problem in this particular case is solely that the RPM .spec file > openSuSE uses is not updated with the dependency on the systemd-devel > package (that's what it's called in Fedora at least). That package > carries the needed pkg-config files telling how to include the needed > systemd library when linking the openvpn binary. This [1] is what the > Fedora packager did when building 2.3.5 for Fedora. > > [1] > <http://pkgs.fedoraproject.org/cgit/openvpn.git/commit/?id=ef86d1da9850e23a6…> > > So, Hans, please ensure that the package providing the proper > libsystemd.pc or libsystemd-daemon.pc files are installed. OpenVPN > now needs a BuildRequirement for that particular package, as well as > Requires on the systemd-libs package (which should carry libsystemd.so > and/or libsystemd-daemon.so). If the systemd packages have similar > names as Fedora, then you can look what's done in the Fedora .spec file. > > > -- > kind regards, > > David Sommerseth -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] systemd detection 1/2
by Hans Witvliet 01 Nov '14

01 Nov '14

Hi all, It seems that I hit a snag, that as a noob I am not able to solve. Let me first explain that, until now, I only used the web-interface. I cloned one of the existing packages with succes: https://build.opensuse.org/package/show/home:testhans:network:network:vpn/o… As you can see, they all build successfully, even 13.2 and sles12 So i dared to try to build the latest release (not to be found anywhere else on the obs) https://build.opensuse.org/package/show/home:testhans:network:network:vpn/o… After some tweaking the spec-file, some build succeeded But those using systemd failed. Initially, i assumed PEBKAC, but next I checked upstream, and they said if i used ./configure with --enable-systemd all should be fine Next the dev's wrote because it used to work, and still works for non-systemd, the original author of previous patch should correct it. However, that author blames the build-environment, the obs. I'll forward his conclusion next to the list... ========================================================================================== From: Witvliet, J, DMO/OPS/I&S/HIN Sent: woensdag 29 oktober 2014 17:41 To: 'openvpn-users(a)lists.sourceforge.net' Subject: RE [Openvpn-users] 2.3.5 - systemd Indeed, as David said: No package 'libsystemd-daemon' found OTOH, it should be enabled… (excerpt from the spec:) … %configure \ --enable-iproute2 \ --enable-x509-alt-username \ --enable-password-save \ %if %{with_systemd} --enable-systemd \ %endif --enable-plugins \ --enable-plugin-down-root \ --enable-plugin-auth-pam \ --with-lzo-headers=%_includedir/lzo \ CFLAGS="$CFLAGS $(getconf LFS_CFLAGS) -fPIE $PLUGIN_DEFS" \ And it seems to be “turned-on”, in the log: [ 46s] systemd-210-44.1 But some lines further: [ 71s] checking for libsystemd... no [ 71s] checking for libsystemd... no [ 71s] configure: error: Package requirements (libsystemd-daemon) were not met: [ 71s] [ 71s] No package 'libsystemd-daemon' found My first assumption was that on this particular build-node, system was not found, But that makes no sense, as 2.3.4 builds OK, with or without system on OS12.2, OS12.3, OS13.1, OS13.2, OSFactory, SLES11SP3 and SLES12 Have to dive a bit deeper, I guess. Hans °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° -----Original Message----- Hi, On Wed, Oct 29, 2014 at 03:41:53PM +0100, J.Witvliet(a)mindef.nl wrote: > Does that imply any required-change during building? > I tried to build on a remote build-farm, and much to my surprise only the targets (SLES12, openSUSE_13.2, openSUSE_13.1) with systemd fails, while others like sles11sp3 and openSUSE_12.2 succeed. Well, if you use --enable-systemd, it should better be there (as it will now try to link to it). If you do not use that, it MUST NOT fail building, whether or not systemd is there. So - how are you calling configure, what is the error message? gert =================================================================== -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2