December 2017 - openSUSE Build Service

Re: [opensuse-buildservice] Archlinux builds with cmake miss rhash
by Andreas Baumann 15 Dec '17

15 Dec '17

dependency Reply-To: Andreas Baumann <mail(a)andreasbaumann.cc> In-Reply-To: <20171215151231.GB12779(a)suse.de> On Fri, Dec 15, 2017 at 04:12:31PM +0100, Michael Schroeder wrote: > On Fri, Dec 15, 2017 at 03:12:17PM +0100, Andreas Baumann wrote: > > Hi, > > Building a package on Archlinux, 64-bit with cmake results in > > > > "nothing provides rhash needed by cmake" > > rhash seems to be in the Community repo. I wonder why a Extra package > has a hard dependency on a Community package, is that an oversight or > done on purpose? Hi, This seems to be a bug. I'll report it upstream. Cheers Andreas > > Cheers, > Michael. > > -- > Michael Schroeder mls(a)suse.de > SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg > main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: mail(a)andreasbaumann.cc Homepage: www.andreasbaumann.cc -- 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] Archlinux32
by Andreas Baumann 15 Dec '17

15 Dec '17

Hi, May I do a shameless plug for https://www.archlinux32.org? After November 2017 upstream Archlinux dropped support for 32-bit, but we keep it alive in a separate project. :-) The ISO and the packages are logically the same as before and we sync and rebuild from upstream Archlinux 64-bit. Is it possible for you to create the 32-bit Arch_Extra/Arch_Core slaves from the 32-bit ISO and packages? What can I do to help? Cheers, Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: mail(a)andreasbaumann.cc Homepage: www.andreasbaumann.cc

1 0

[opensuse-buildservice] OBS frontend deployment
by ammartinez 14 Dec '17

14 Dec '17

Hi, we are going to deploy OBS in 15 minutes. You might experience a minimal downtime. I'll let you know as soon as we are done. Cheers, Ana -- Ana María Martínez Gómez - ammartinez(a)suse.de | ammartinez(a)suse.com BuildService Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- 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] Substitute is only partially applied
by Olaf Hering 13 Dec '17

13 Dec '17

Substitute: in prjconf is applied to BuildRequires, and the changes appear in the pkg.spec file. But it is only partly applied to Requires(pre|post). The "solver" uses the replaced strings, but they are not applied to the pkg.spec. As a result the binary package can not be installed because it still requires the string that was supposed to be replaced by Substitute. Is that done intentional, or is it a bug? Olaf

3 4

[opensuse-buildservice] Deploy openSUSE-Leap-42.3-JeOS-for-VMware to ESXi
by Matwey V. Kornilov 10 Dec '17

10 Dec '17

Hello, I am trying to use https://build.opensuse.org/package/show/openSUSE:Templates:Images:42.3/open… with ESXi, but it seems that ESXi still wants flat vmdk. I can upload the file to ESXi and attach the image to VM, but VM can't start after it. How could I convert the image to use with ESXi? -- 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 ARM repositories
by Marco Poletti 10 Dec '17

10 Dec '17

Hi, OBS allows to build ARM (armv7l and aarch64) packages for Debian and Fedora, however the xUbuntu repositories in OBS only have i586 and x86_64 as enabled architectures. Example: https://build.opensuse.org/project/show/Ubuntu:17.10 Would it be possible to enable armv7l and aarch64 for these repos too, so that we can use OBS to build/publish Ubuntu ARM packages? Or, is there a good reason to keep these disabled? (e.g., «we've tried, it doesn't work», or «you can use repo X instead to build for Ubuntu ARM») I found this other forum thread with someone asking for this: https://forums.opensuse.org/showthread.php/525112-Cross-compile-for-Ubuntu-… However there was no answer there (besides «ask in the mailing-list»). Thanks in advance. -- 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] Please process SAPCAL changes
by Robert Schweikert 09 Dec '17

09 Dec '17

Hi, Could you please process the following requests: created request id 148815 created request id 148816 created request id 148817 SAP has requested the addition of packages to the image. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Team Lead Public Cloud rjschwei(a)suse.com IRC: robjo

1 1

[opensuse-buildservice] Building for SLE-15
by wengel＠suse.de 07 Dec '17

07 Dec '17

Hi, I'm trying to build a package for SLE-15 but currently it fails with the following error: package build was not possible: no compliant workers (constraints mismatch hint: hostlabel) Please adapt your constraints. I'm not aware of any constraints I have to adjust there... This is the package: https://build.opensuse.org/package/show/home:bigironman:Backports:SLE-15/tm… Should building for SLE-15 currently work in general in OBS ? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 8

[opensuse-buildservice] Debian packages build, but are not published
by Rainer Gerhards 07 Dec '17

07 Dec '17

Hi there, I have problems with building debian packages. I am new to OBS and packaging in general, so I may be overlooking something very obvious. I have begun to build packages for multiple distros, for example in this small project: https://build.opensuse.org/package/show/home:rgerhards/libestr As you can see, it builds for both RPM and DEB based systems. Unfortunately, the download page only shows the RPM-based distros: https://software.opensuse.org//download.html?project=home%3Argerhards&packa… However, the .deb's are also built: https://download.opensuse.org/repositories/home:/rgerhards/xUbuntu_16.10/ Some additional info may be found here (not sure if it is useful): https://twitter.com/obshq/status/937073469782597632 I have disabled all DEB based distributions, waited several hours (> 4), re-enabled them and then waited for about a day without any improvement. Is this a problem with OBS or am I doing something wrong? Any advise would be deeply appreciated! Many thanks, Rainer Gerhards -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 5

[opensuse-buildservice] Re: [opensuse-factory] OBS: nothing provides this-is-only-for-build-envs
by Linux Kamarada 05 Dec '17

05 Dec '17

Em Dom, 2017-12-03 às 10:54 -0200, Linux Kamarada escreveu: > Em Dom, 2017-12-03 às 08:12 +0100, Stephan Kulow escreveu: > > > > Am 03.12.2017 um 03:58 schrieb Linux Kamarada: > > > > > > > > > Hi, everyone! Again, I'm talking about OBS... > > > > > > I am moving to the next generation KIWI (https://suse.github.io/kiwi/) but when > > > I try to build, I get unresolvable: > > > > > > nothing provides this-is-only-for-build-envs needed by libsystemd0-mini, nothing > > > provides this-is-only-for-build-envs needed by systemd-mini > > > > > > Googling, I found this message: > > > > > > https://lists.opensuse.org/opensuse-buildservice/2016-03/msg00003.html > > > > > > > > > > > > > > > Add these lines to your prjconf: > > > > > > > > Ignore: systemd-mini:this-is-only-for-build-envs > > > > Ignore: libsystemd0-mini:this-is-only-for-build-envs > > > > Ignore: udev-mini:this-is-only-for-build-envs > > > > Ignore: libudev-mini1:this-is-only-for-build-envs > > > > > This is to ignore it for normal package builds - for product builds this > > is harmful. > > > > What you need to do is adding systemd to your kiwi config, so that > > systemd-mini isn't even pulled in. > > > > Greetings, Stephan > > > > -- > > Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die > > ganze Welt an Arsch offen hat, oder grad deswegn. > > Thank you, Stephan Kulow. I deleted those lines from my prjconf and added systemd to config.kiwi. It worked. > > But now, I get a different error: > > [ 81s] [ INFO ]: Processing: [ ] 0%[ DEBUG ]: 12:41:27 | system: Loading repository data... > [ 81s] [ DEBUG ]: 12:41:27 | system: Reading installed packages... > [ 81s] [ DEBUG ]: 12:41:27 | system: 'systemd' is already installed. > [ 81s] [ DEBUG ]: 12:41:27 | system: No update candidate for 'systemd-228-38.1.x86_64'. The highest available version is already installed. > [ 81s] [ INFO ]: Processing: [########################################] 100% > [ 81s] [ ERROR ]: 12:41:27 | KiwiInstallPhaseFailed: System package installation failed: Package 'dracut-kiwi-live' not found. > [ 81s] Package 'yast2-live-installer' not found. > > I don't understand, because here is my config.kiwi: > > https://build.opensuse.org/package/view_file/home:livesuse:dev/LiveSUSE-Lea… > > My repository configuration: > > <repository alias="kiwi-next-generation" priority="1" type="rpm-md"> > <source path="obs://Virtualization:Appliances:Builder/openSUSE_Leap_42.3"/> > </repository> > <repository alias="repo-update" imageinclude="true" priority="2" type="rpm-md"> > <source path="obs://openSUSE:Leap:42.3:Update/standard"/> > </repository> > <repository alias="repo-oss" imageinclude="true" priority="3" type="rpm-md"> > <source path="obs://openSUSE:Leap:42.3/standard"/> > </repository> > > dracut-kiwi-live is available on the kiwi-next-generation repo. > > yast2-live-installer is available on the repo-oss repo. > > Why are those packages not found? Do you have any ideas? > > I'm using the following images as examples to move mine to the next generation KIWI: > > https://github.com/SUSE/kiwi-descriptions/tree/master/suse/x86_64/suse-leap… > > https://build.opensuse.org/package/view_file/Virtualization:Appliances:Imag… > > https://build.opensuse.org/package/view_file/home:probono:branches:KDE:Medi… > > > Antonio > The Linux Kamarada Project > https://kamarada.github.io/ Curiously, I changed: <packages type="image" patternType="plusRecommended"> ... </packages> <packages type="iso"> <package name="dracut-kiwi-live"/> <package name="yast2-live-installer" /> </packages> To: <packages type="image" patternType="plusRecommended"> ... <package name="dracut-kiwi-live"/> <package name="yast2-live-installer" /> </packages>  And the package installation has proceeded. Actually, all the prepare step went well, but the create step failed with "No space left on device": [ 1869s] [ INFO ]: 01:20:09 | --> Creating squashfs container for root image [ 1869s] [ DEBUG ]: 01:20:09 | EXEC: [mkdir -p /usr/src/packages/KIWI-iso/live-container.c77ev8ou/LiveOS] [ 2118s] [ ERROR ]: 01:24:18 | Unexpected error: [ 2118s] /.build/build-vm: line 417: echo: write error: No space left on device [ 2118s] Traceback (most recent call last): [ 2118s] File "/usr/bin/kiwi", line 9, in <module> [ 2118s] load_entry_point('kiwi==9.11.24', 'console_scripts', 'kiwi-ng-3')() [ 2118s] File "/usr/lib/python3.4/site-packages/kiwi/kiwi.py", line 54, in main [ 2118s] App() [ 2118s] File "/usr/lib/python3.4/site-packages/kiwi/app.py", line 35, in __init__ [ 2118s] task_class().process() [ 2118s] File "/usr/lib/python3.4/site-packages/kiwi/tasks/system_build.py", line 256, in process [ 2118s] result = image_builder.create() [ 2118s] File "/usr/lib/python3.4/site-packages/kiwi/builder/live.py", line 178, in create [ 2118s] root_image.name, self.live_container_dir + '/LiveOS/rootfs.img' [ 2118s] File "/usr/lib64/python3.4/shutil.py", line 229, in copy [ 2118s] copyfile(src, dst, follow_symlinks=follow_symlinks) [ 2118s] File "/usr/lib64/python3.4/shutil.py", line 110, in copyfile [ 2118s] copyfileobj(fsrc, fdst) [ 2118s] File "/usr/lib64/python3.4/shutil.py", line 70, in copyfileobj [ 2118s] fdst.write(buf) [ 2118s] OSError: [Errno 28] No space left on device How much space can we use at OBS? SUSE Studio used to offer 15GB for free. I am also moving this thread to the opensuse-buildservice mailing list because maybe it is more appropriate. Thank you! Antonio The Linux Kamarada Project https://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2