October 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Selecting GCC version
by Matthias Fehring 03 Apr '18

03 Apr '18

Hello, is there a simple way to force the GCC version used to build a package? openSUSE Leap 42.2 for example uses GCC 4.8 as default compiler, but also provides packages for GCC 5.3. Simply using BuildRequires gcc5 pulls gcc5 in but still uses gcc48 to build the package (especially in Build Service). So is there maybe some Buid Service or spec file switch (bcond) to select the used GCC version? Best greetings Matthias Fehring P.S. Not sure if it is a problem with my browser settings, but when I try to search lists.opensuse.org, it is not possible for me to limit the results to a specific list. Even if I set one, I get results from all lists, what makes searching almost impossible, because most results are commit messages. -- Das Gesetz hat zum Schneckengang verdorben, was Adlerflug geworden wäre. (Friedrich Schiller - Die Räuber) www.buschmann23.de GPG-Key: 0x614C3258 GPG Fingerprint: D786 DDF8 4CA9 00BC CDE0 9A5F CCC5 125D 6E87 D4FC

6 13

[opensuse-packaging] .changes madness with upstream updates
by Michael Ströder 13 Nov '17

13 Nov '17

HI! Sometimes a submission of me gets declined because of changelog being too short or too long referring to this policy: https://en.opensuse.org/openSUSE:Creating_a_changes_file_%28RPM%29#What_goe… While the guide-lines were surely outlined with good aims I have to question the current policy of package changelogs (*.changes) regarding upstream updates. The rules are too blurry and boil down to "Do the right thing". I don't like to provide an extract of an upstream changelog because I'm convinced that no packager is capable of extracting a really meaningful essence from an upstream changelog. Furthermore I assume that upstream developers are also lazy writing docs and the changelog would have been already shorter if still meaningful. So IMO the right way is to.. 1. just mention upstream release and packaging changes xor 2. add the complete changelog. Ciao, Michael.

14 18

[opensuse-packaging] Java-build on TW fails suddenly: [javac] error: Source option 1.5 is no longer supported. Use 1.6 or later.
by Axel Braun 12 Nov '17

12 Nov '17

Hi, maybe we have a Java-Expert around that can support: projectlibre [1] suddenly fails to build on TW, with the error message: [ 31s] [ 31s] init: [ 31s] [mkdir] Created dir: /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/build [ 31s] [mkdir] Created dir: /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/tmp [ 31s] [ 31s] build: [ 31s] [javac] /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/build.xml:30: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [ 31s] [javac] Compiling 10 source files to /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/build [ 31s] [javac] error: Source option 1.5 is no longer supported. Use 1.6 or later. [ 31s] [javac] error: Target option 1.5 is no longer supported. Use 1.6 or later. [ 31s] [ 31s] BUILD FAILED As the version setting is not explicit mentioned in the spec file I guess it is some implicit definition. Anyone an idea where to look forß Thanks Axel [1] https://build.opensuse.org/package/show/Office/projectlibre -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 8

[opensuse-packaging] RFC: changing RPM's default scriptlet locale
by jan matejek 06 Nov '17

06 Nov '17

Fellow mortals, more and more packages need their locale to be set to something more sensible than C. This hit me while switching packages over to Python 3. Python gets its encoding from locale, so by default, it won't decode UTF-8 unless the appropriate encoding is set. Right now, when gtk-doc is switched to use Python 3, it won't build UTF-8 documentation. This could be changed in gtk-doc itself (although that is impractical), but perhaps a better way is to change the default locale for spec scriptlets. Right now the macros set it to C. We could switch that to "C.UTF-8", "en_US.UTF-8", or export a special RPM variable that could be overriden in your spec file. Still, the default should be something with UTF-8 in it. I'm now trying to build a Ring 1 staging project with this change. So far I have seen one failure related to it: with en_US.UTF-8, bash ranges (like [a-z]) are case-insensitive and match more than intended. That could be solved by changing the expression, or by setting locale to C.UTF-8. Thoughts, comments? regards m.

7 16

[opensuse-packaging] RFC: best practices for referencing bugs/features in commit messages and %changelog
by Adam Spiers 25 Oct '17

25 Oct '17

Hi all, openSUSE has a documented policy for how to reference external bugs / features from within package %changelogs: https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM)#Bug_fix.2C_f… This works fairly well, but is not perfect, especially in the case where entries in a foo.changes file are automatically generated from upstream SCM repositories, e.g. via the tar_scm source service. Some recent discussion amongst my team got me thinking about whether we could improve this slightly. So I just wrote up my thoughts, which include two possible ways forward: https://github.com/openSUSE/obs-service-tar_scm/issues/207 Feedback on this would be very welcome. Thanks! Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] /mounts/work_src_done/SLE15-STAGING/jeos-firstboot not checked in
by ro 25 Oct '17

25 Oct '17

Script 'mail_helper' called by ro Hi gmoro(a)suse.com, /mounts/work_src_done/SLE15-STAGING/jeos-firstboot was not checked in by ro for the following reasons: (submitrequest 144700 on https://build.suse.de) request on hold, please create a matching submitrequest to the devel project on OBS (devel:openSUSE:Factory) your dist/autobuild team. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Kiwi - different behaviour on OBS and locally
by Axel Braun 19 Oct '17

19 Oct '17

Hi, I'm working on a Kiwi-build (export from Studio) and always run into the error: [ 2461s] Installation of glibc-locale-2.22-8.4.x86_64 failed: [ 2461s] Error: Subprocess failed. Error: RPM failed: warning: /var/cache/kiwi/packages/usr_src_packages_SOURCES_repos_openSUSE:Leap:42.3_standard/glibc-locale.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY [ 2461s] installing package glibc-locale-2.22-8.4.x86_64 needs 340MB on the / filesystem I have added a constraint for a larger disk space during build, I'm now at 10G but the error does not change. So I tried to build locally: Kiwi adds sources: Oct-19 15:19:50 <1> : Setting up source channel: Oct-19 15:19:50 <1> : --> http://download.opensuse.org/update/leap/42.3/oss/ Oct-19 15:19:50 <1> : Setting up source channel: Oct-19 15:19:50 <1> : --> http://download.opensuse.org/distribution/leap/42.3/repo/oss/ Oct-19 15:19:50 <1> : Removing old root directory '/home/docb/isobuild/result/root' Oct-19 15:19:50 <1> : Set root log: /home/docb/isobuild/result/root.3082.screenrc.log... done Oct-19 15:19:50 <1> : Setting target architecture to: x86_64 and later it fails: + SPID=3259 + wait 3259 + /usr/bin/zypper --non-interactive --pkg-cache-dir /var/cache/kiwi/packages --reposd-dir /home/docb/isobuild/result/root//var/cache/kiwi/zypper/repos --solv-cache-dir /home/docb/isobuild/result/root//var/cache/kiwi/zypper/solv --cache-dir /home/docb/isobuild/result/root//var/cache/kiwi/zypper --config /var/cache/kiwi/zypper/zypper.conf.3082 --no-gpg-checks --root /home/docb/isobuild/result/root install --auto-agree-with-licenses --no-recommends filesystem glibc-locale module-init-tools gfxboot-devel shim zypper File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/distribution/leap/42.3/repo/oss/' File './noarch/kbd-legacy-2.0.3-3.14.noarch.rpm' not found on medium 'http://download.opensuse.org/distribution/leap/42.3/repo/oss/' Problem occurred during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. Repository types are rpm-md. Is this an issue on download.opensuse.org? Thanks for hints! Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Why does the build for succeed[i586] and fail[x86_64] on platforms ?
by doiggl＠velocitynet.com.au 18 Oct '17

18 Oct '17

Hello, Questions: Why does the build for succeed[i586] and fail[x86_64] on platforms ? Why does x86_64 fail ,how is spec fixed so build completes. ? Thanks --Glenn [urls] https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla1 https://build.opensuse.org/public/build/home:doiggl/openSUSE_Factory/i586/k… https://build.opensuse.org/public/build/home:doiggl/openSUSE_Factory/x86_64… from logs: https://build.opensuse.org/package/live_build_log/home:doiggl/kernel-vanill… [ 58s] CC arch/x86/purgatory/sha256.o [ 59s] AS arch/x86/purgatory/entry64.o [ 59s] CC arch/x86/purgatory/string.o [ 59s] LD arch/x86/purgatory/purgatory.ro [ 59s] BIN2C arch/x86/purgatory/kexec-purgatory.c [ 59s] CC kernel/bounds.s [ 59s] cc1: error: code model kernel does not support PIC mode [ 59s] make[2]: *** [kernel/bounds.s] Error 1 [ 59s] make[1]: *** [prepare0] Error 2 [ 59s] make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.2.1/linux-4.2/linux-obj' [ 59s] make: *** [sub-make] Error 2 [ 59s] make: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.2.1/linux-4.2' [ 59s] error: Bad exit status from /var/tmp/rpm-tmp.bXHOnk (%prep) [ 59s] [ 59s] [ 59s] RPM build errors: [ 59s] Bad exit status from /var/tmp/rpm-tmp.bXHOnk (%prep) [ 59s] [ 59s] lamb27 failed "build kernel-vanilla.spec" at Sun Oct 8 13:36:55 UTC 2017. [ 59s] or ## https://build.opensuse.org/public/build/home:doiggl/openSUSE_Factory/i586/k… [ 1967s] ... saving statistics [ 1967s] ... saving built packages [ 1967s] RPMS/i686/kernel-vanilla-devel-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1967s] RPMS/i686/kernel-vanilla-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1967s] SRPMS/kernel-vanilla-4.2.1-2.1.gd2bbe7f.nosrc.rpm [ 1967s] OTHER/_statistics [ 1967s] OTHER/rpmlint.log [ 1967s] [ 1967s] lamb70 finished "build kernel-vanilla.spec" at Sun Oct 8 14:08:44 UTC 2017. [ 1967s] [ 1967s] ### VM INTERACTION START ### [ 1970s] [ 1962.791243] sysrq: SysRq : Power Off [ 1970s] [ 1962.798089] reboot: Power down [ 1970s] ### VM INTERACTION END ### [ 1970s] build: extracting built packages... [ 1970s] RPMS/i686/kernel-vanilla-devel-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1970s] RPMS/i686/kernel-vanilla-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1970s] SRPMS/kernel-vanilla-4.2.1-2.1.gd2bbe7f.nosrc.rpm [ 1970s] OTHER/_statistics [ 1970s] OTHER/rpmlint.log

2 5

[opensuse-packaging] Python scripts and rpmlint
by Todd Rme 18 Oct '17

18 Oct '17

The current version of rpmlint in devel:languages:python [1] contains a patch relative to the one in openSUSE:Factory. This patch adds additional warnings and errors regarding shebangs in scripts. Specifically, executable scripts with "/usr/bin/env" cause an error and "/usr/bin/python" cause a warning. However, the submission to openSUSE:Factory [2] was rejected 4 months ago over doubts regarding whether there should be an error and whether the checks are really necessary. Since then, devel:languages:python has had this different rpmlint behavior than openSUSE:Factory. I hope we can get this issue resolved so we can bring the two versions back into agreement. 1: https://build.opensuse.org/package/show/devel:languages:python/rpmlint 2: https://build.opensuse.org/request/show/508168 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 5

[opensuse-packaging] Building python-urllib for SLES12 GA and SP1 hangs and hangs and hangs...
by Johannes Kastl 17 Oct '17

17 Oct '17

Dear python experts, I tried to build python-urllib for SLES12 GA and SP1, but it is hanging in the tests. Previously it failed, because it timed out after 28000s. > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Redfish_S… For SP2 and SP3 it builds in a reasonable time and does not fail or time out. Anything I need to change? Any package or setting that is missing on SP1 and GA? Thanks in advance. Johannes

1 0

[opensuse-packaging] 10 hours package signing?
by Bjoern Voigt 16 Oct '17

16 Oct '17

Some of my build service packages currently take a very long time. E.g. https://build.opensuse.org/package/live_build_log/home:bjoernv:branches:net… The build process itself is fast (118 seconds). But since 10 hours the status is "signing". Some other packages of the same repository are ready now. Is there an build service problem or is it my fault? Where can I report such problems in future? Greetings, Björn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] python-redfish singlespec conversion: update-alternatives, subpackage common
by Johannes Kastl 14 Oct '17

14 Oct '17

Dear python-experts, I wanted to play around with python-redfish, so I started to package it. mnhauke already had a package, which I took as a starting point and tried to convert to singlespec. home:ojkastl_buildservice:Redfish_openSUSE 2 questions: ### I copied the update-alternative stuff from another spec (I think python-chardet), and it seems to build, but this is in the logs. Am I missing something in the spec? Error in the mv commands (mv /usr/bin/redfish-client /usr/bin/redfish-client-2.7 etc.)? Conditional missing? > [ 71s] (order: reverse python-redfish-common python2-redfish python3-redfish) > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-client-2.7 doesn't exist > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-check-cartridge-2.7 doesn't exist > [ 71s] warning: %postun(python2-redfish-0.4.1-3.1.noarch) scriptlet failed, exit status 2 > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-client-3.6 doesn't exist > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-check-cartridge-3.6 doesn't exist > [ 71s] warning: %postun(python3-redfish-0.4.1-3.1.noarch) scriptlet failed, exit status 2 ### I created a subpackage python-redfish-common and required it in the preamble, as there are some files, that seem to exist or be needed in both the python2 and python3 package. %files -n %{name}-common %config(noreplace) %{_sysconfdir}/redfish-client.conf %{_datadir}/redfish-client %{_mandir}/man1/python-redfish.1%{ext_man} I have not tested, whether both versions can use the same config file (I guess so). There are some templates in %{_datadir}/redfish-client that seem to be needed by both versions. Is this a valid approach? Or should I solve this differently? I found nothing (or missed it) in the singlespec page. ### Thanks in advance for any hints, tips, tricks and comments! Johannes

3 3

[opensuse-packaging] Be very careful with Requires(pre)!
by Michael Schroeder 13 Oct '17

13 Oct '17

Hi Packagers, some days I stumbled over an oddity in the wicked package. Rpm allowed the deinstallation of the "wicked" and "libwicked-0-6" packages even if wicked-service was still installed. It turned out that the issue was with Requires(pre). What many packagers seem to not know is that this means two things: - the package is needed in the prein scriptlet - the package is no longer needed after the installation (!) This is also cleary stated in the rpm's documentation: http://rpm.org/user_doc/more_dependencies.html#scriptlet-dependencies Note that this was not a problem for PreReq, as it is identical to Requires(pre,preun) and thus the package needs to be kept installed. But it's dangerous to simply change PreReq to Requires(pre), as seemed to be done for a large amount of packages. So I'd like to ask all of you to check your packages if you have a Requires(pre) that's also needed at runtime. The most correct way of fixing this is to simply add another line without the (pre): Requires(pre): libwicked-0-6 = %{version} Requires: libwicked-0-6 = %{version} Thank you, 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);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Building python-chardet for Leap 42.2 fails, if python-coverage is not added to the project
by Johannes Kastl 13 Oct '17

13 Oct '17

Hi all, I get build failures for python-chardet in my Redfish_openSUSE project, but only for Leap 42.2. home:ojkastl_buildservice:Redfish_openSUSE/python-chardet [ 33s] File "/usr/lib/python2.7/site-packages/hypothesis/core.py", line 32, in <module> [ 33s] from coverage.files import canonical_filename [ 33s] ImportError: cannot import name canonical_filename It seems to build fine for 42.2 in d:l:p. devel:languages:python/python-chardet My first guess would be that it needs python-coverage as BuildRequires. Which might be available on other versions of Leap and Tumbleweed and in d:l:p. I tried linkpac'ing python-coverage to my project (for 42.2. only), and yes, suddenly python-chardet builds fine for 42.2. 2 questions: My naive guess would be that python-coverage (or %{python_module coverage}) is missing from the BuildRequires of python-chardet. But why does it get pulled in, once there is a version of python-coverage available, even without being added to the spec? Or is it pulled in by one of the dependencies of python-chardet, so that package's spec needs to be adapted? Or both spec files? Or is there a version available, but not in the right version? Leap 42.2 has python-coverage, it seems: | python-coverage | Paket | 3.7.1-6.3 | x86_64 | openSUSE-Leap-42.2-Oss | python3-coverage | Paket | 3.7.1-4.4 | x86_64 | openSUSE-Leap-42.2-Oss Thanks in advance! Confused. Johannes

2 3

[opensuse-packaging] [Fwd: [opensuse-factory] Deprecation of devel:languages:python3]
by Tomas Chvatal 13 Oct '17

13 Oct '17

Hi, as I was poked that there might be people interested in this even here please read up and discuss on opensuse-factory mailinglist to avoid cluttering. (Also there already is some discussion thus if not subscribed check up the lists.opensuse.org archives) Tom

1 0

[opensuse-packaging] Re: [opensuse-factory] rpmlint 1.10 about to enter openSUSE Factory
by Richard Biener 11 Oct '17

11 Oct '17

On Mon, 9 Oct 2017, Dirk Müller wrote: > Hi, ... > - env-script-interpreter: This is a new check that has a Badness of 9. > The value is so low because it triggers tremendously often right now. > Basically, for shell scripts installed with chmod +x in the typical > binary directories like /usr/bin and the like, it is alerting when the > script shebang starts with "#!.*env ". The intention here is to avoid > the rpm-dependency logic add a file-depends on /usr/bin/env (which is > useless) and have the *actual* interpreter added as dependency > instead. So to silence the warning, something like > > sed -i -e "1 s,#! */usr/bin/env python,#!/usr/bin/python2," > %{buildroot}/%{_bindir}/*.py > > is needed. This lets the rpm-dependency magic add a proper > file-depends on /usr/bin/python2, pulling in python-base if it isn't > installed already. Huh, why not fix RPM instead? Richard. -- Richard Biener <rguenther(a)suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

4 3

[opensuse-packaging] Aw: Re: [opensuse-factory] Re: SUSE Studio Express questions
by Axel Braun 10 Oct '17

10 Oct '17

> Gesendet: Montag, 09. Oktober 2017 um 18:12 Uhr > Von: "Roger Oberholtzer" <roger.oberholtzer(a)gmail.com> > An: "Andreas Jaeger" <aj(a)suse.com> > Cc: "Jim Henderson" <hendersj(a)gmail.com>, opensuse-factory <opensuse-factory(a)opensuse.org> > Betreff: Re: [opensuse-factory] Re: SUSE Studio Express questions > > On Mon, Oct 9, 2017 at 9:32 AM, Andreas Jaeger <aj(a)suse.com> wrote: > > On 2017-10-09 09:07, Roger Oberholtzer wrote: > >> On Fri, Oct 6, 2017 at 2:09 PM, Andreas Jaeger <aj(a)suse.com> wrote: > >>> On 2017-09-26 12:34, Roger Oberholtzer wrote: > >>>> On Mon, Sep 25, 2017 at 8:33 PM, Jim Henderson <hendersj(a)gmail.com> wrote: > >>>> > >>>> It would be great if one could import a kiwi project that one > >>>> currently runs on a local computer. Not just one set up in Studio. > >>> > >>> You should be able to add kiwi files that you have locally, there's > >>> nothing magic here. What is not working for you? > >> > >> I have not figured out the general work flow. I can choose some > >> pre-defined things to build. So I am guessing one chooses one of > >> those, and then changes files as needed? > >> > >> I guess I need to play with it a bit to see what I can do. An "Import > >> local KIWI spec" would make sense. Of course, I only have a handful of > >> these. So if I get the steps sorted out I can do things by hand. I'm > >> okay with that. As long as I know what makes sense to change. > >> > > > > See also > > http://openbuildservice.org/2017/09/27/suse-studio-express/ > > I've added my kiwi files, but I get a error that nothing defines any > of the packages I want. I know that if I specify the repository wrong > I get an error. But I don't get that kind of error. > > https://build.opensuse.org/package/show/home:rogeroberholtzer/rsl-oem-42.3 > > This pretty much works as a native build on my Leap 42.3. I expect it > would get further along. I'm sure I'm just blind. There are some error messages regarding 'have choice of...' - fix them by adding the respective package to your build, then try again I cc opensuse-packaging, we should follow-up there. Cheers Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Re: [opensuse-kernel] What reiser4 parameters do I to append to .config to enable the reiser4-for-4.13.0.patch in kernel build process.
by Takashi Iwai 09 Oct '17

09 Oct '17

On Mon, 09 Oct 2017 11:50:59 +0200, Matthias Brugger wrote: > > > > On 10/07/2017 03:54 PM, doiggl(a)velocitynet.com.au wrote: > > Hello. > > > > What reiser4 parameters do I to append to .config to enable the > > reiser4-for-4.13.0.patch in kernel build process. > > > > The reiser4-for-4.13.0.patch applies to kernel ok. > > > > Build Log shows: > > + patch -s -F0 -E -p1 --no-backup-if-mismatch -i > > ../patches.rpmify/reiser4-for-4.13.0.patch > > > > I put 'reiser4' parameters in zreiser4parameters.txt and it gets appended > > that to .config > > I just trigger rebuild process. > > > > I think the best way would be to change the needed config parameters > in the configs you care from config.tar.bz2 Yes, either that or putting the new stuff into patches.addon.tar.bz2 and config.addon.tar.bz2. Takashi > > Regards, > Matthias > > > Thanks for your expertise. > > --Glenn > > > > # > > > > project info, patch and log urls: > > > > :project > > # https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla > > > > spec: > > # > > https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ker… > > > > :apply reiser4 patch > > # > > https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ser… > > > > :reiser4 parameters used added to: zreiser4parameters.txt > > CONFIG_DEBUG_INFO_REDUCED=n > > CONFIG_DEBUG_INFO_SPLIT=n > > CONFIG_FRAME_POINTER_UNWINDER=n > > CONFIG_GDB_SCRIPTS=n > > CONFIG_REISER4_DEBUG=n > > CONFIG_REISER4_FS=m > > CONFIG_SUSE_KERNEL_SUPPORTED=y > > > > > > #add reiser4 parameters to .config line , from spec file: > > /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i > > zreiser4parameters.txt` >> .config > > > > > > :build log > > # > > https://build.opensuse.org/public/build/home:doiggl/openSUSE_Leap_42.3/x86_… > > > > # > > Steps done in specfile: > > ---------------------- > > > > KERN_DIRS="-C .. O=$PWD" > > if test -e %_sourcedir/TOLERATE-UNKNOWN-NEW-CONFIG-OPTIONS; then > > yes '' | make oldconfig $MAKE_ARGS $KERN_DIRS > > else > > cp -v .config .config.orig > > > > ###########add reiser4 params to config > > /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i > > zreiser4parameters.txt` >> .config > > #########add repser4 params to config > > #cat zreiser4parameters.txt > > #CONFIG_REISER4_DEBUG=n > > #CONFIG_REISER4_FS=m > > ######### > > > > > > # > > From last build log: > > [ 43s] '.config' -> '.config.orig' > > [ 43s] ++ /usr/bin/find /home/abuild/rpmbuild/BUILD/. > > [ 43s] ++ grep -i zreiser4parameters.txt > > [ 43s] + /bin/cat > > [ 43s] + make silentoldconfig -j6 -C .. > > O=/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj > > [ 43s] make: Entering directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' > > [ 43s] make[1]: Entering directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' > > [ 43s] GEN ./Makefile > > [ 43s] HOSTCC scripts/basic/fixdep > > [ 44s] HOSTCC scripts/kconfig/conf.o > > [ 44s] SHIPPED scripts/kconfig/zconf.tab.c > > [ 44s] SHIPPED scripts/kconfig/zconf.lex.c > > [ 44s] SHIPPED scripts/kconfig/zconf.hash.c > > [ 44s] HOSTCC scripts/kconfig/zconf.tab.o > > [ 47s] HOSTLD scripts/kconfig/conf > > [ 47s] scripts/kconfig/conf --silentoldconfig Kconfig > > [ 47s] * > > [ 47s] * Restart config... > > [ 47s] * > > [ 47s] * > > [ 47s] * File systems > > [ 47s] * > > [ 47s] Second extended fs support (EXT2_FS) [N/m/y/?] n > > [ 47s] The Extended 3 (ext3) filesystem (EXT3_FS) [N/m/y/?] n > > [ 47s] The Extended 4 (ext4) filesystem (EXT4_FS) [Y/n/m/?] y > > [ 47s] Use ext4 for ext2 file systems (EXT4_USE_FOR_EXT2) [Y/n/?] y > > [ 47s] Ext4 POSIX Access Control Lists (EXT4_FS_POSIX_ACL) [Y/n/?] y > > [ 47s] Ext4 Security Labels (EXT4_FS_SECURITY) [Y/n/?] y > > [ 47s] Ext4 Encryption (EXT4_ENCRYPTION) [Y/n/?] y > > [ 47s] EXT4 debugging support (EXT4_DEBUG) [N/y/?] n > > [ 47s] JBD2 (ext4) debugging support (JBD2_DEBUG) [N/y/?] n > > [ 47s] Reiser4 (EXPERIMENTAL) (REISER4_FS) [N/m/y/?] (NEW) aborted! > > [ 47s] > > [ 47s] Console input/output is redirected. Run 'make oldconfig' to > > update configuration. > > [ 47s] > > [ 47s] make[2]: *** [silentoldconfig] Error 1 > > [ 47s] make[1]: *** [silentoldconfig] Error 2 > > [ 47s] make[1]: Leaving directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' > > [ 47s] make: *** [sub-make] Error 2 > > [ 47s] make: Leaving directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' > > [ 47s] error: Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) > > [ 47s] > > [ 47s] > > [ 47s] RPM build errors: > > [ 47s] Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) > > [ 47s] > > [ 47s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:40 > > UTC 2017. > > [ 47s] > > [ 47s] ### VM INTERACTION START ### > > [ 52s] [ 45.550906] reboot: Power down > > [ 52s] ### VM INTERACTION END ### > > [ 52s] > > [ 52s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:45 > > UTC 2017. > > > -- > To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] What reiser4 parameters do I to append to .config to enable the reiser4-for-4.13.0.patch in kernel build process.
by doiggl＠velocitynet.com.au 07 Oct '17

07 Oct '17

Hello. What reiser4 parameters do I to append to .config to enable the reiser4-for-4.13.0.patch in kernel build process. The reiser4-for-4.13.0.patch applies to kernel ok. Build Log shows: + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/reiser4-for-4.13.0.patch I put 'reiser4' parameters in zreiser4parameters.txt and it gets appended that to .config I just trigger rebuild process. Thanks for your expertise. --Glenn # project info, patch and log urls: :project # https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla spec: # https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ker… :apply reiser4 patch # https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ser… :reiser4 parameters used added to: zreiser4parameters.txt CONFIG_DEBUG_INFO_REDUCED=n CONFIG_DEBUG_INFO_SPLIT=n CONFIG_FRAME_POINTER_UNWINDER=n CONFIG_GDB_SCRIPTS=n CONFIG_REISER4_DEBUG=n CONFIG_REISER4_FS=m CONFIG_SUSE_KERNEL_SUPPORTED=y #add reiser4 parameters to .config line , from spec file: /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i zreiser4parameters.txt` >> .config :build log # https://build.opensuse.org/public/build/home:doiggl/openSUSE_Leap_42.3/x86_… # Steps done in specfile: ---------------------- KERN_DIRS="-C .. O=$PWD" if test -e %_sourcedir/TOLERATE-UNKNOWN-NEW-CONFIG-OPTIONS; then yes '' | make oldconfig $MAKE_ARGS $KERN_DIRS else cp -v .config .config.orig ###########add reiser4 params to config /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i zreiser4parameters.txt` >> .config #########add repser4 params to config #cat zreiser4parameters.txt #CONFIG_REISER4_DEBUG=n #CONFIG_REISER4_FS=m ######### # >From last build log: [ 43s] '.config' -> '.config.orig' [ 43s] ++ /usr/bin/find /home/abuild/rpmbuild/BUILD/. [ 43s] ++ grep -i zreiser4parameters.txt [ 43s] + /bin/cat [ 43s] + make silentoldconfig -j6 -C .. O=/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj [ 43s] make: Entering directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' [ 43s] make[1]: Entering directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' [ 43s] GEN ./Makefile [ 43s] HOSTCC scripts/basic/fixdep [ 44s] HOSTCC scripts/kconfig/conf.o [ 44s] SHIPPED scripts/kconfig/zconf.tab.c [ 44s] SHIPPED scripts/kconfig/zconf.lex.c [ 44s] SHIPPED scripts/kconfig/zconf.hash.c [ 44s] HOSTCC scripts/kconfig/zconf.tab.o [ 47s] HOSTLD scripts/kconfig/conf [ 47s] scripts/kconfig/conf --silentoldconfig Kconfig [ 47s] * [ 47s] * Restart config... [ 47s] * [ 47s] * [ 47s] * File systems [ 47s] * [ 47s] Second extended fs support (EXT2_FS) [N/m/y/?] n [ 47s] The Extended 3 (ext3) filesystem (EXT3_FS) [N/m/y/?] n [ 47s] The Extended 4 (ext4) filesystem (EXT4_FS) [Y/n/m/?] y [ 47s] Use ext4 for ext2 file systems (EXT4_USE_FOR_EXT2) [Y/n/?] y [ 47s] Ext4 POSIX Access Control Lists (EXT4_FS_POSIX_ACL) [Y/n/?] y [ 47s] Ext4 Security Labels (EXT4_FS_SECURITY) [Y/n/?] y [ 47s] Ext4 Encryption (EXT4_ENCRYPTION) [Y/n/?] y [ 47s] EXT4 debugging support (EXT4_DEBUG) [N/y/?] n [ 47s] JBD2 (ext4) debugging support (JBD2_DEBUG) [N/y/?] n [ 47s] Reiser4 (EXPERIMENTAL) (REISER4_FS) [N/m/y/?] (NEW) aborted! [ 47s] [ 47s] Console input/output is redirected. Run 'make oldconfig' to update configuration. [ 47s] [ 47s] make[2]: *** [silentoldconfig] Error 1 [ 47s] make[1]: *** [silentoldconfig] Error 2 [ 47s] make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' [ 47s] make: *** [sub-make] Error 2 [ 47s] make: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' [ 47s] error: Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) [ 47s] [ 47s] [ 47s] RPM build errors: [ 47s] Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) [ 47s] [ 47s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:40 UTC 2017. [ 47s] [ 47s] ### VM INTERACTION START ### [ 52s] [ 45.550906] reboot: Power down [ 52s] ### VM INTERACTION END ### [ 52s] [ 52s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:45 UTC 2017. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] factory-auto declines deletion request of linked package
by Michal Srb 06 Oct '17

06 Oct '17

Hi, I am trying to request deletion of openSUSE:Factory/lldb4 which is a link to openSUSE:Factory/llvm4. It was there because llvm4 was multispec package with llvm4.spec and lldb4.spec files in it, but since sr#532127 it won't be anymore. The original packages from lldb4.spec will be subpackages in llvm4.spec. The request is automatically declined with following message: "This is an incorrect request, it's a linked package to openSUSE:Factory/ llvm4" Why is that a reason to decline the request? Is there some other way to delete linked packages? Thanks, Michal Srb -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Fwd: Build failure of openSUSE:Tools/osc-plugin-install in Fedora_Rawhide/armv7l
by Oliver Kurz 06 Oct '17

06 Oct '17

Any Idea what that means "unknown host 'back-other-opensuse'" ? ---------- Forwarded Message ---------- Subject: Build failure of openSUSE:Tools/osc-plugin-install in Fedora_Rawhide/ armv7l Date: Wednesday, 27 September 2017, 18:22:35 CEST From: OBS Notification <admin(a)opensuse.org> To: okurz(a)suse.de Visit https://build.opensuse.org/package/live_build_log/openSUSE:Tools/osc-plugin… Package openSUSE:Tools/osc-plugin-install failed to build in Fedora_Rawhide/ armv7l Check out the package for editing: osc checkout openSUSE:Tools osc-plugin-install Last lines of build log: unknown host 'back-other-opensuse' -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/) ----------------------------------------- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] A python singlespec question
by Greg Freemyer 05 Oct '17

05 Oct '17

All, What's the right syntax for: %{python_sitelib}/dfvfs-%{timestamp}-py2.7.egg-info in a spec file %files section. Obviously "py2.7" is wrong. My testing package for python singlespec is at: https://build.opensuse.org/package/show/home:gregfreemyer:Tools-for-forensi… Thanks Greg -- Greg Freemyer Advances are made by answering questions. Discoveries are made by questioning answers. — Bernard Haisch -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 5

[opensuse-packaging] need advice to fix "zypper up" conflicts
by Konstantin Voinov 05 Oct '17

05 Oct '17

Greetings. I'm "maintainer" of papirus-icon-theme in OBS https://build.opensuse.org/package/show/home%3Akill_it/papirus-icon-theme Some times ago upstream did made changes in directory structure, they changed some symlinks to dirs, and some symlinks to files. Now I have conflict warning with zypper up during "checking for conflicts" stage, but rpm -Uhv says nothing. >> File /usr/share/icons/Papirus/24x24/actions/zoom-previous.svg >> from install of >> papirus-icon-theme-20171005-1.noarch (Plain RPM files cache) >> conflicts with file >> /usr/share/icons/Papirus-Light/24x24/actions/zoom-previous.svg >> from install of >> papirus-icon-theme-20171005-1.noarch (Plain RPM files cache) >> >> File conflicts happen when two packages attempt to install files with >> the same name but different contents. If you continue, conflicting >> files will be replaced losing the previous content. >> Continue? [yes/no] (no): Strange to me, names of conflicting packages are same. I've tried fix this by adding %pretrans section with checking for such symlinks presence and remove them if so. But I guess zypper doesn't care about %pretrans, just simple compare list of files in packages (hope i'm wrong). >> if [ -h %{_datadir}/icons/Papirus-Light/16x16 ]; then >> rm -f %{_datadir}/icons/Papirus-Light/16x16 >> fi Would appreciate if someone tell me where to dig. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Removing unnecessary packages from devel:languages:go
by Thomas Hipp 04 Oct '17

04 Oct '17

Hello, a few weeks ago, some of us maintainers of the devel:languages:go[0] project decided to get rid of some source-only packages that are strictly not needed, since they are no dependency of any binary package. Instead of having to maintain these packages on OBS, we now recommend using `go get`. The maintainers of the packages have been contacted. Should they want to keep their packages, they can respond until 1st November 2017, and will then be solely responsible for the package(s). Should there be any questions or issues regarding this, please don't hesitate. Cheers, Thomas [0] https://build.opensuse.org/project/show/devel:languages:go -- Thomas Hipp Software Developer — k8s core SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49 (0) 911 74053 0 — Fax: +49 (0) 911 7417755 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) PGP fingerprint: 48D6 A5F4 2D60 57BF 9A37 8004 5DE8 949A 899C 8D99

2 1

[opensuse-packaging] What can be changed so the x86_64 builds pass and not fail. Where is the 'Unescaped left brace ' as x86_64 build fails see log
by doiggl＠velocitynet.com.au 04 Oct '17

04 Oct '17

Hello, What can be changed so the x86_64 builds pass and not fail. Where is the 'Unescaped left brace ' as listed in x86_64 .spec , build log ? The i586 i686 build passed. spec and logs. :spec https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ker… [1] :fail x86_64 https://build.opensuse.org/build/home:doiggl/openSUSE_13.1/x86_64/kernel-va… :pass i586 https://build.opensuse.org/build/home:doiggl/openSUSE_13.1/i586/kernel-vani… result of x86_64 failed build. [ 96s] + popd [ 96s] ~/rpmbuild/BUILD/pesign-repackage-1.0 [ 96s] + /usr/lib/rpm/pesign/pesign-gen-repackage-spec --directory=/home/abuild/rpmbuild/BUILDROOT/pesign-repackage-1.0-1.1.x86_64 /home/abuild/rpmbuild/SOURCES/kernel-vanilla-4.13.4-1.1.x86_64.rpm /home/abuild/rpmbuild/SOURCES/kernel-vanilla-base-4.13.4-1.1.x86_64.rpm /home/abuild/rpmbuild/SOURCES/kernel-vanilla-devel-4.13.4-1.1.x86_64.rpm [ 96s] Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\%{ <-- HERE -n\*}/ at /usr/lib/rpm/pesign/pesign-gen-repackage-spec line 477. [ 96s] error: Bad exit status from /var/tmp/rpm-tmp.fQJlMG (%install) [ 96s] [ 96s] [ 96s] RPM build errors: [ 96s] Bad exit status from /var/tmp/rpm-tmp.fQJlMG (%install) [ 96s] [ 96s] build36 failed "build pesign-repackage.spec" at Tue Oct 3 03:53:35 UTC 2017. [ 96s] [ 96s] ### VM INTERACTION START ### [ 100s] [ 71.649678] reboot: Power down [ 124s] ### VM INTERACTION END ### [ 124s] [ 124s] build36 failed "build pesign-repackage.spec" at Tue Oct 3 03:54:04 UTC 2017. [ 124s] # [ 96s] ++ pesign -n /home/abuild/rpmbuild/BUILD/pesign-repackage-1.0/rsasigned/nss-db -h -i /home/abuild/rpmbuild/BUILDROOT/pesign-repackage-1.0-1.1.x86_64/./boot/vmlinuz-4.13.4-1-vanilla [ 96s] + nhash='hash: 102835091a8faeb6465df1d1110e2c7186a421eb239ffe812bf37dc09f74bf8b' [ 96s] + test 'hash: 102835091a8faeb6465df1d1110e2c7186a421eb239ffe812bf37dc09f74bf8b' '!=' 'hash: 102835091a8faeb6465df1d1110e2c7186a421eb239ffe812bf37dc09f74bf8b' [ 96s] + popd [ 96s] ~/rpmbuild/BUILD/pesign-repackage-1.0 [ 96s] + /usr/lib/rpm/pesign/pesign-gen-repackage-spec --directory=/home/abuild/rpmbuild/BUILDROOT/pesign-repackage-1.0-1.1.x86_64 /home/abuild/rpmbuild/SOURCES/kernel-vanilla-4.13.4-1.1.x86_64.rpm /home/abuild/rpmbuild/SOURCES/kernel-vanilla-base-4.13.4-1.1.x86_64.rpm /home/abuild/rpmbuild/SOURCES/kernel-vanilla-devel-4.13.4-1.1.x86_64.rpm [ 96s] Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\%{ <-- HERE -n\*}/ at /usr/lib/rpm/pesign/pesign-gen-repackage-spec line 477. [ 96s] error: Bad exit status from /var/tmp/rpm-tmp.fQJlMG (%install) [ 96s] [ 96s] [ 96s] RPM build errors: [ 96s] Bad exit status from /var/tmp/rpm-tmp.fQJlMG (%install) [ 96s] [ 96s] build36 failed "build pesign-repackage.spec" at Tue Oct 3 03:53:35 UTC 2017. [ 96s] [ 96s] ### VM INTERACTION START ### [ 100s] [ 71.649678] reboot: Power down [ 124s] ### VM INTERACTION END ### [ 124s] [ 124s] build36 failed "build pesign-repackage.spec" at Tue Oct 3 03:54:04 UTC 2017. # rpms-built: https://download.opensuse.org/repositories/home:/doiggl/openSUSE_13.1/i686/ :other info # osc copypac Kernel:stable kernel-vanilla home:doiggl Sending meta data... Copying files... <revision rev="1" vrev="1"> <srcmd5>c49e0dd2f8390371fc18b506a82f7994</srcmd5> <version>unknown</version> <time>1506993883</time> <user>doiggl</user> <comment>osc copypac from project:Kernel:stable package:kernel-vanilla revision:1951</comment> <requestid/> </revision> Thanks --Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1