June 2015 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] release-notes-openSUSE requires google-opensans-fonts
by Felix Miata 23 Apr '17

23 Apr '17

TW $SUBJECT can't be right, but trying to zypper rm opensans wants to remove releasenotes. :-( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] Python 2 and 3 in single specfile
by Jan Matějek 22 Jul '15

22 Jul '15

Fellow packagers, after some discussions in our team, we figured that it would be neat if we could build python modules for Python 2 and 3 from a single spec file. Now that a great deal of python modules work with both pythons, this makes a lot of sense. A good deal of work can be done by RPM macros. Then we could even seamlessly start building modules for PyPy, Jython and other pythons. A sample specfile, and the corresponding set of RPM macros, is attached. As you can see, the appropriate subpackage is generated automatically by %python_subpackages, build and install steps are handled through %python_build and %python_install respectively. There is some more magic involved, as well as possibilities for customization. There is a minor problem with BuildRequires. As long as you only need python-devel, it's not too bad to just list $flavor-devel requirements by hand. It's worse when you require more subpackages, because then you need all of them in both python2 and python3 versions. It would be nice to be able to specify %{python_require Mako} and expand that to all the necessary BuildRequires, but OBS blocks us here, because the limited environment will not expand such macros. mls, ro, or anyone from the OBS team, would it be possible to solve this? Still, it basically doesn't matter if you list all the BuildRequires twice in one spec or in two specs, so there. Another thing I'm still unclear on are the filelists. It's certainly possible to make a generic filelist, something along the lines of: %package -n %flavor-%modname # python3-Mako %defattr(-, root, root) %{%flavor_sitelib}/* %{%flavor_sitearch}/* but this doesn't solve docs and possible other files. Again, obviously, we can write the filelists by hand. But if you have good suggestions for some smart macros here, I'd love to see them. What do you folks think? Comments, questions? m.

3 5

[opensuse-packaging] undefined symbol pdns / libboost
by Michael Ströder 08 Jul '15

08 Jul '15

7 14

[opensuse-packaging] osc build openSUSE_13.2 not works for some RPMs
by Rusmir Duško 29 Jun '15

29 Jun '15

Hello I try to build more RPMs for openSUSE 13.2 with osc build openSUSE_13.2 and get unclean /var/tmp/build-root/openSUSE_13.2-x86_64 [ 50s] kernel-obs-build-3.16.6-2.1 ######################################## [ 51s] hicolor-icon-theme-0.13-2.1.2 ######################################## [ 51s] exit ... The buildroot was: /var/tmp/build-root/openSUSE_13.2-x86_64 Or similar for other RPMs. Have get file /var/tmp/build-root/openSUSE_13.2-x86_64/not-read When wish to build again with osc build openSUSE_13.2 get [ 0s] It seems that there was an incomplete setup of /var/tmp/build-root/openSUSE_13.2-x86_64. [ 0s] To be sure, we will build it again completely... [ 0s] Your build system is broken!! Shall I execute [ 0s] [ 0s] rm -rf -- /var/tmp/build-root/openSUSE_13.2-x86_64/* [ 0s] [ 0s] y - yes, cleanup the build root [ 0s] N - No, abort build (default on enter) [ 0s] c - Continue anyway with this build root When use Y (yes) get for other RPM [ 140s] build-mkbaselibs-20140424-2.1.3 ######################################## [ 142s] kernel-obs-build-3.16.6-2.1 ######################################## [ 142s] exit ... The buildroot was: /var/tmp/build-root/openSUSE_13.2-x86_64 and again is build broken :( When try to build with osc build openSUSE_13.2 i586 works all good. I use openSUSE 13.2 Release. What is wrong with build for openSUSE 13.2 x86_64? For some RPM this build works, for some fewer not. -- Rusmir Dusko openSUSE Games maintainer https://build.opensuse.org/project/users/games -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 15

[opensuse-packaging] gnome and kde updates
by doiggl＠velocitynet.com.au 26 Jun '15

26 Jun '15

Hello, 2 questions: - Can Gnome be updated to the latest release ? https://download.gnome.org/core/3.17/3.17.3/ https://download.gnome.org/apps/3.17/3.17.3/ - Can Kde updated to the latest release ? http://download.kde.org/stable/applications/15.04.2/src/ Thank you --Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 5

[opensuse-packaging] is bash 'set -xv' possible for scriptlets during build?
by Johannes Meixner 25 Jun '15

25 Jun '15

Hello, I would like to suggest to run RPM scriptlets during build (and only during build) with bash 'set -xv' if possible. Reasoning: At the end of a package build, the binary RPMs get installed and thereby RPM scriptlets are executed. When a RPM scriptlet fails, the build fails but there is nothing in the build log that shows the scriptlet code. Because often in the spec file scriptlets are specified by RPM macros, the actual scriptlet code is also not in the spec file. In the end when a RPM scriptlet fails during build one has to do cumbersome reverse engineering to find out the actual scriptlet code for the particular repository and architecture where it had failed. Even with the actual scriptlet code it is not obvious what exactly had failed without knowing the exact command that had actually failed. If scriptlets would be run with bash 'set -xv' during build the build log would show the actual scriptlet code plus the commands and their arguments as they are executed. This should help a lot to find out the root cause why a scriptlet failed for a particular repository/architecture. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] Packaging go
by Matwey V. Kornilov 25 Jun '15

25 Jun '15

Hi, I've been working on RPM for new release of InfluxDB and found that we have to consider following Fedora Provides/Requires model for Go. The build time error looks like the following: [ 23s] ../go/src/github.com/prometheus/client_golang/prometheus/desc.go:12:2: cannot find package "github.com/golang/protobuf/proto" in any of: [ 23s] /usr/lib64/go/src/github.com/golang/protobuf/proto (from $GOROOT) [ 23s] /home/abuild/rpmbuild/BUILD/go/src/github.com/golang/protobuf/proto (from $GOPATH) [ 23s] /usr/lib64/go/contrib/src/github.com/golang/protobuf/proto And I would like just add BuildRequires: golang(github.com/golang/protobuf) to my spec file. Nowadays, I have to find go-protobuf package in OBS and then check where did it come from. There are two implementations of protobuf golang/protobuf (which is go-protobuf) and gogo/protobuf (which is go-gogo-protobuf package in my branch). [1] http://fedoraproject.org/wiki/PackagingDrafts/Go -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] Solving FHS policy, rpmlint error arch-dependent-file-in-usr-share
by Roman Evstifeev 24 Jun '15

24 Jun '15

Hi. I am trying to build a package "Carla" I got rpmlint error "arch-dependent-file-in-usr-share": [ 489s] Carla.x86_64: E: arch-dependent-file-in-usr-share (Badness: 590) /usr/share/carla/resources/zynaddsubfx-ui [ 489s] This package installs an ELF binary in the /usr/share hierarchy, which is [ 489s] reserved for architecture-independent files. I have couple of questions: 1) Is it possible or allowed to fix this by creating a symlink (to binary) under /usr/share hierarchy? 2) Is such a violation of FHS acceptable in official openSUSE repositories? -- 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] gh2pack announce
by Matwey V. Kornilov 19 Jun '15

19 Jun '15

Hi, I've started to develop gh2pack python3 script to simplify creation of new rpm packages from repos located at GitHub service. It is in early draft state and based on py2pack ideas: gh2pack fetches meta information from GitHub API and fills it into Jinja2 templates. GitHub is used to store sources for modules written in different languages such as Erlang, Go, etc. Everybody is welcome to participate writing code or new templates for different languages, your impact will be appreciated. [1] https://github.com/matwey/gh2pack -- 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] Apache 2.2 to 2.4 Migration
by Sankar P 18 Jun '15

18 Jun '15

Hi I have been trying to migrate an old apache module written for Apache 2.2 to Apache 2.4 To be honest, I do not have any experience with writing or packaging apache modules before. So I am trying to find out if there are any patches for any modules that went through this phase, especially the ones which have used the ap_requires API. The release notes page http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html says: ===== ap_requires() The core server now provides better infrastructure for handling Require configuration. Register an auth provider function for each supported entity using ap_register_auth_provider(). The function will be called as necessary during Require processing. (Consult bundled modules for detailed examples.) ===== However, I am not able to find the bundled modules that does this. Also, based on my google search results, I could find only abandoned modules which never migrated to 2.4 because of the ap_requires API usage. So, can any of you point me to a patch/module, where the migration from 2.2 to 2.4 went through fine, even with the use of this API ? Thanks. -- Sankar -- 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] Berkeley-DB issue in Factory
by Michael Ströder 18 Jun '15

18 Jun '15

HI! This builds for openSUSE 13.2 and SLES12 but not for Factory/Tumbleweed. https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap… Anything changed with libdb recently? Strange enough OpenLDAP builds just fine on my local Tumbleweed system (not a OSC build though). Ciao, Michael.

4 3

[opensuse-packaging] systemd presets vs. package install order
by Christian Boltz 17 Jun '15

17 Jun '15

Hello, AppArmor has a preset "enable by default" (in the separate systemd- presets-branding-openSUSE), but unfortunately the AppArmor package gets installed before systemd-presets-branding-openSUSE gets installed. The result is: AppArmor doesn't get enabled :-( (see also https://bugzilla.opensuse.org/show_bug.cgi?id=931792 ) Can someone recommend a solution for this, or do I need to add a "systemctl enable apparmor.service" in %post? Regards, Christian Boltz -- Please note that unstable software can harm your computer, your cat and even your dog. [Ismail Dönmez in opensuse-factory] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

9 23

[opensuse-packaging] builds blocked: have choice for libitm1...
by Michael Ströder 17 Jun '15

17 Jun '15

HI! I want to urgently build the following for Tumbleweed: https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap… But it's blocked saying: "have choice for libitm1 >= 4.8.3+r218481-2.3 needed by gcc48: libitm1-gcc48 libitm1-gcc5, have choice for libtsan0 >= 4.8.3+r218481-2.3 needed by gcc48: libtsan0-gcc48 libtsan0-gcc5" Any clue what's going on? Ciao, Michael.

5 4

[opensuse-packaging] problem with python package
by Klaas Freitag 16 Jun '15

16 Jun '15

Hi, I am trying to update devel:languages:python python-netlib to the new version. It's a dependency of mitmproxy that I also wanna update. The new version has some C code embedded with cffi which I haven't seen before. My local build results in http://paste.opensuse.org/25035334 after I added a couple of dependencies. It builds, but has the install errors. Can anybody explain what the problem is? How can that be fixed? How do I handle the debug files? Where should the compiled shared library go? Thanks, Klaas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] Sricplet in spec
by Eric Schirra 13 Jun '15

13 Jun '15

Hello, i hope someone can help me. I wan't to add scriptlet in spec. It should run only at upgrade a package not run by new install. So i insert something like: %post if [ "$1" = 2 ]; then %{_bindir}/php %{my_path}/%{name}/console param fi I have try [ "$1" -gt 1 ] too without right result. Obs will run this at build. And so an error is rising up. Can i prevent this from running at build? It should run only at package-install or upgrade. Or is something wrong at my code? Or is something missing in Requires? Best regards Eric -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] suse_version handling troubles/solutions
by Tomáš Chvátal 12 Jun '15

12 Jun '15

Hello, As discussed a bit on the 42 thread and I don't wanna get it lost in some crazy deep thread on Factory. %suse_version is not really well set-up for our mix of sle/opensuse so we need to devise something to solve the trouble. There are multiple solutions: 1) Introduce extra macro, ie %opensuse_version YYYYMMDD which would be based on the snapshots and always bumped, so we can seriously finegrain what to enable. This has problem if we backport back the features back to SLE so suddenly they are supposed to be covered just by %suse_version thing. Or we would need to mesh in that anything %suse_version 12 %opensuse_version ANYTHING is older than %suse_version 12.1... 2) Redo how we think about optional features and why we use the suse_version. Instead of %if suse_version > 1140 BuildRequires: bla %endif We could devise in rpm like TryBuildRequires which would pull in packages if they are around and otherwise provide some packagename = 0 for further depending conditions. For defines we could instead of version requirement check for the define and if not found, define it with expected value/behaviour (like in python packages), and so on. As coolo already pointed out on factory ml it is not all uses for the suse_version. But most common usage in spec files is the above and it would reduce the "prone to error" path quite bit I suppose. Would it be worth all the work? Tom

9 15

[opensuse-packaging] python package has a strange egg-info path in one instance?
by Greg Freemyer 11 Jun '15

11 Jun '15

All, I'm test packaging the RC1+ release of plaso. For openSUSE 13.1 and 13.2 I get egg-info files in something like: /usr/lib/python2.7/site-packages/plaso-1.3.0_20150609-py2.7.egg-info That is what I expect. With factory/Tumbleweed I find those files in: /usr/lib/python2.7/site-packages/plaso-1.3.0.post20150609-py2.7.egg-info Note that '1.3.0_' is replaced with '1.3.0.post' in the factory version. That strikes me as wrong because I've never noted '.post' in that folder name before, but I'm not sure. I asked upstream and they don't know why. Thought it might be the version of setuptools in factory. Does anyone know if this is expected with factory/tumbleweed, or is there a bug? For now I'm using a filespec of plaso-*-py2.7.egg-info so my RPM build is working. Thanks Greg -- Greg Freemyer www.IntelligentAvatar.net -- 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] Re: How exactly rpm is packaged?
by Andreas Schwab 11 Jun '15

11 Jun '15

Stanislav Baiduzhyi <baiduzhyi.devel(a)gmail.com> writes: > Ah, the stripping... Could you tell me more about that? Maybe some exact > commands performed during the stripping so I could try it locally? See /usr/lib/rpm/brp-suse.d/brp-15-strip-debug (package brp-check-suse). Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- 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] How exactly rpm is packaged?
by Stanislav Baiduzhyi 11 Jun '15

11 Jun '15

Could anyone please point me at some exact steps what is performed after the %install macro is finished and when rpm package is written? I've noticed really strange thing, in one of the packages there are 2 libraries with the same name but in different subfolders, probably a legacy of old and complicated build system. After the build their md5sums are different, but after unpacking the rpm - they are identical. Which means that cpio or something before the cpio merges them together or uses bad duplicate finder. If someone knows some magic spec file trick to avoid that de-duplication, please tell me or give me the link. -- Regards, Stas -- 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] %{reconfigure_fonts_scriptlets}
by Marcus Rueckert 11 Jun '15

11 Jun '15

Hi, That macro is less than ideal. I think it should be split up in macros per section like e.g. the desktop db macros [1]. If that macro is used you cant not call other per section macros anymore. Thoughts? darix [1] https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#.25deskto… -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 7

[opensuse-packaging] Re: [opensuse-factory] a common project for packages built for SLE12
by Ludwig Nussel 08 Jun '15

08 Jun '15

Paul Gonin wrote: > Thanks ! > Could it be considered somehow similar to EPEL ? Somehow. I'm not familiar with EPEL. From reading it's documentation a difference seems to be that EPEL wants frozen versions where we would like to follow Tumbleweed if possible, ie allow stable version updates. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- 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] a common project for packages built for SLE12
by Ludwig Nussel 08 Jun '15

08 Jun '15

Hi, Those of you running SUSE Linux Enterprise somewhere may know the problem. openSUSE contains some package that you want on SLE but since there is no SUSE support for that particular package you won't find it in any of the official repos either. openSUSE on the other hand contains that package and maybe the package maintainer(you!?) even builds it in the Factory devel project for SLE. Devel projects however may contain lots of other experimental stuff that you may not want on your SLE installation. So it would be really nice to have a central project to collect known good community packages built for SUSE Linux Enterprise server. That project is here now: openSUSE:Backports:SLE-12! Getting a package in there is quite easy. Just file a submit request to openSUSE:Backports:SLE-12. There are basically two rules for packages in that project: - packages must not conflict with packages already contained in SLE - package sources must be accepted also in Factory More details are explained in the wiki: https://en.opensuse.org/Portal:Backports The whole thing is still a bit experimental to find out what works and what not. Nevertheless testers, contributors and feedback in general welcome! cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] What package is needed to resolve error 'Missing vcl resource' ?
by doiggl＠velocitynet.com.au 08 Jun '15

08 Jun '15

Hello, What package is needed to resolve error 'Missing vcl resource' ? --Glenn # strace -e open /usr/bin/libreoffice . . Missing vcl resource. This indicates that files vital to localization are missing. You might have a corrupt installation. +++ exited with 77 +++ # rpm -qa |grep -i libreoffice |sort libreoffice-4.4.3.2-3.1.x86_64 libreoffice-branding-openSUSE-4.0-1.4.noarch libreoffice-calc-4.4.3.2-3.1.x86_64 libreoffice-draw-4.4.3.2-3.1.x86_64 libreoffice-filters-optional-4.4.3.2-3.1.x86_64 libreoffice-icon-theme-crystal-4.1.6.2-37.1.noarch libreoffice-icon-theme-galaxy-4.4.3.2-3.1.noarch libreoffice-icon-theme-hicontrast-4.4.3.2-3.1.noarch libreoffice-icon-theme-oxygen-4.4.3.2-3.1.noarch libreoffice-icon-theme-sifr-4.4.3.2-3.1.noarch libreoffice-impress-4.4.3.2-3.1.x86_64 libreoffice-kde4-4.4.3.2-3.1.x86_64 libreoffice-l10n-en-4.4.3.2-3.1.noarch libreoffice-math-4.4.3.2-3.1.x86_64 libreoffice-share-linker-1-1.1.noarch libreoffice-templates-en-3.3-14.1.noarch libreoffice-templates-labels-a4-1.0.1-12.1.noarch libreoffice-templates-labels-letter-1.0.1-12.1.noarch libreoffice-templates-presentation-layouts-3.3-13.1.noarch libreoffice-writer-4.4.3.2-3.1.x86_64 # # strace -e open /usr/bin/libreoffice open("/lib64/bash/4.2/tls/x86_64/libreadline.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib64/bash/4.2/tls/libreadline.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib64/bash/4.2/x86_64/libreadline.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib64/bash/4.2/libreadline.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 open("/lib64/libreadline.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/lib64/libtinfo.so.5", O_RDONLY|O_CLOEXEC) = 3 open("/lib64/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3 open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/dev/tty", O_RDWR|O_NONBLOCK) = 3 open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib/locale/en_US.UTF-8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/locale/en_US.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3 open("/proc/meminfo", O_RDONLY|O_CLOEXEC) = 3 open("/usr/bin/libreoffice", O_RDONLY) = 3 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5683, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5684, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5685, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5686, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5689, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5690, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5691, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=5693, si_status=0, si_utime=0, si_stime=0} --- open("/usr/lib64/libreoffice/program/tls/x86_64/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/tls/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/x86_64/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/tls/x86_64/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/tls/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/x86_64/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libXinerama.so.1", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/libX11.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/libX11.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libX11.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/libpng16.so.16", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/libpng16.so.16", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libpng16.so.16", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/libuno_sal.so.3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/libuno_sal.so.3", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libXext.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libxcb.so.1", O_RDONLY|O_CLOEXEC) = 3 open("/lib64/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3 open("/lib64/libz.so.1", O_RDONLY|O_CLOEXEC) = 3 open("/lib64/libm.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/../ure-link/lib/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib64/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/../ure-link/lib/librt.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib64/librt.so.1", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/../ure-link/lib/libstdc++.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/libstdc++.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libreoffice/program/../ure-link/lib/libgcc_s.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib64/libgcc_s.so.1", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/libXau.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib/locale/en_US.UTF-8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/locale/en_US.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3 open("/usr/lib64/libreoffice/program/bootstraprc", O_RDONLY|O_EXCL) = 3 open("/usr/lib64/libreoffice/program/intro-en_US.png", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/intro.png", O_RDONLY) = 3 open("/usr/lib64/libreoffice/program/sofficerc", O_RDONLY|O_EXCL) = 3 open("/root/.xauthsHr3pl", O_RDONLY) = 4 open("@/usr/lib64/libreoffice/program/pagein-common", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/pagein-common", O_RDONLY) = 4 open("/usr/lib64/libreoffice/program/libmergedlo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/libi18nlangtag.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/libfwllo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/libvclplug_genlo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/libvclplug_gtklo.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/../ure-link/lib/libstocserviceslo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/lib/libbootstraplo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/lib/libreglo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/lib/libstorelo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/lib/libreflectionlo.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/lib/libuno_cppu.so.3", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/lib/libuno_sal.so.3", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/libucbhelper.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/libcomphelper.so", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/../ure-link/share/misc/types.rdb", O_RDONLY) = 5 open("/usr/lib64/libreoffice/program/services.rdb", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/oovbaapi.rdb", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib64/libreoffice/program/libgconfbe1lo.so", O_RDONLY) = -1 ENOENT (No such file or directory) Missing vcl resource. This indicates that files vital to localization are missing. You might have a corrupt installation. +++ exited with 77 +++

1 0

[opensuse-packaging] Editing rpm changelogs
by Stanislav Baiduzhyi 01 Jun '15

01 Jun '15

I see that lots of packages include changelog entries up to seconds. I wounder, are people writing time with seconds (while rpm allows it to be date only) or is there some special tool to do that properly that I'm not aware of? -- Regards, Stas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3