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