November 2014 - openSUSE Build Service

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