April 2016 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Rename a file in OBS
by Roger Oberholtzer 22 Apr '16

22 Apr '16

I have a number of spec files in obs. I usually work via the web interface. In porting some packages from MinGW32 to MinGW64, I see that there is an RPM test for the name of the spec file. All my spec files are named mingw32-PKG.spec. It seems they need to be called mingw64-PKG.spec in the 64-bit build. Can I rename these files via the obs command line? I can do other things from that. But I don't see how to rename a file. Or, can I disable this specific check? I would prefer to rename the files. -- Roger Oberholtzer -- 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] continuous build with OBS: advocacy (background and rationale)
by Martin A. Brown 21 Apr '16

21 Apr '16

Hello there, I'm certain that I am not the only person to ever have written up an encomium of the OBS, highlighting features, benefits and, of course, rationale. I feel that I have often had to explain the problem(s) that OBS solves (or allows solving). With that in mind, I share the following, in the event that it is useful for others who need to explain to the uninitiated what OBS is. http://linux-ip.net/continuous-build-with-the-open-build-service.html Hopefully, I have not mischaracterized anything. -Martin P.S. If I have made substantive or even typographical errors, I'd gladly take corrections and, always suggestions. -- Martin A. Brown http://linux-ip.net/ -- 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] Ubuntu 14.04 build setup Fails due to init script issues
by Matthew Drobnak 21 Apr '16

21 Apr '16

I have an a local issue...that has been reproduced in the public OBS: https://build.opensuse.org/package/live_build_log/home:mdrobnak/libvirt/xUb… Because scripts like /etc/init.d/<stuff> don't seem to work correctly, the VM build fails for anything that triggers running of these scripts, such as: libpam-systemd nfs-common Which are being called by attempting to build libvirt. I think this likely affects any Debian package which is even remotely 'system'-like. Please let me know what the fix is, as I need to do it locally as well. Thanks. -Matthew Drobnak

1 0

[opensuse-buildservice] sha256 for current OBS ISO image
by Alex Naumov 21 Apr '16

21 Apr '16

Hello, does anybody know where is the sha256 for the current OBS ISO image? http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/iso/obs-s… Cheers, Alex -- 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 On-site install - standby / staging box
by Matthew Drobnak 21 Apr '16

21 Apr '16

Hi everyone. I am trying to set up a clone of my production OBS 2.5 system. This is in preparation for updating our local installation of OBS 2.5 to 2.6, and to serve as cold-standby. I have an issue where 'ghost' jobs show up on the standby cluster. Does anyone have a list of all the directories that should be sync'd over, or a list of directories that need to be cleaned out or modified after syncing? The ideal scenario is a sync of the tree and DB restore should bring the cold standby system up into an idle state, and I should be able to submit a job and have it build normally. Currently that does not work. Any help in getting this set up would be greatly appreciated. -Matt

1 1

[opensuse-buildservice] Preserving ~/rpmbuild/BUILDROOT/* contents after osc build
by Markos Chandras 20 Apr '16

20 Apr '16

Hi, Does anyone know how to preserve the contents of ~/rpmbuild/BUILDROOT/* after a successful osc build? It looks like osc build cleans up that directory once it has built the rpm files. However, I would like to examine the ~/rpmbuild/BUILDROOT/ directory to address some rpmlint warnings. Alternatively, does anyone know if it is possible to use 'osc' to run only specific parts of the build process? for example, I would like to run configure->build->install and stop there. Any ideas? I believe that's a useful feature(s) to have so if there is currently no way to achieve that I will open a bug report. -- Markos Chandras SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg -- 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] s390 support
by Peter Czanik 19 Apr '16

19 Apr '16

Hi, Is s390 support available in the OBS? Someone asked me, if I could provide him with up to date syslog-ng packages for SLES 11 SP4 on s390. It has syslog-ng 2.0.9 and the latest stable version is 3.7... I tried to enable building syslog-ng for this platform, but it seems to me, that even basic dependencies are missing: https://build.opensuse.org/project/monitor/home:czanik:syslog-ng37?arch_s39… Is it possible at all? If yes, how? Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] RFC: slow ftp product builds
by Dinar Valeev 19 Apr '16

19 Apr '16

Hi, I'm looking for a solution to fix a slow ftp tree build, it takes about 5 hours to build it. It is fine to wait, but in Tumbleweed days where many snapshots released during the week this is rather slow. We build medias and ftp on special "local" arch, which have special workers for it. x86 got fancy machines, while "Ports" have to share a single machine. Here are the numbers to compare: 2016-04-18 17:11:19 _product:openSUSE-ftp-ftp-ppc64_ppc64le meta change succeeded 4h 51m 41s build36:1 2016-04-17 20:59:09 _product:openSUSE-ftp-ftp-i586_x86_64 source change succeeded 39m 47s typhoon1:1 Building on local have other disadvantages, like we depend on x86 to get kiwi build env since local is x86 [1]. And while we were waiting for x86 kiwi to finish build, x86 product is passed to openQA already, since this moment a new source checking round might happen, which brings me to the beginning of the loop (build packages, wait for kiwi, start building product). Having multiple machines for local will not help IMO, we can't predict where build will be scheduled, on a host with cache or not. There is an other option, to build ftp on native arch, basically bring your own product builder. But then tooling around Tumbleweed assumes products to work with are in 'local' architecture. Given Ports family is growing (zSystems and possible Leap i586), all ports architectures will benefit from it. [1] https://github.com/openSUSE/open-build-service/blob/master/src/backend/BSCo… Dinar, -- 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] What is this: Recognition of file ... failed: mode 100755 (null)
by Dr. Werner Fink 19 Apr '16

19 Apr '16

Hi, this morning I see a lot of failed packages with this message and this also happens at local builds. Why do this messages hapen and how to avoid them? Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

1 1

[opensuse-buildservice] Re: [opensuse-factory] Transitioning to GCC 6
by Normand 19 Apr '16

19 Apr '16

On 15/04/2016 13:25, Richard Biener wrote: > > You may have noticed that GCC 6 packages appeared in Factory (but gcc > used for building packages still points to GCC 5). Somewhen in > January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used > to build packages. The status of that is that it depends on the > glibc update pending in Staging:B and it still requires fixing a few > packages, mostly -Werror related. There was a point in time where > openQA was green for x86_64 (and Minimal-X). > > Once Staging:B has been accepted I'll formally submit an update > to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6. > That staging can nevertheless be used to look at the current FAILs > which are > > build failed > cluster-glue failed > elfutils failed > espeak failed > gdb failed > jack failed > libyui failed > llvm failed > mozilla-nss failed > pesign failed > python3-base failed > xen failed > > and can also be caused by the glibc update which I pulled into > Staging:Gcc6. > > Any help is appreciated. > > Richard. > Dinar, I do not know anything about required bootstrap for Staging setup but I am impressed by the number of unresolvable for ppc64le archi (1) (439 entries at time of this email) Are there missing copy somewhere ? (1) https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:Gcc6?ar… -- Michel Normand -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4