July 2015 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Introducing even more staging projects
by Stephan Kulow 20 Jul '15

20 Jul '15

Hi, For openSUSE Leap we faced the situation that packages submitted need to be test compiled against openSUSE:42 and most source projects don't have a built target for that (just think about openSUSE:Factory). To solve that problem, we now put *every* package in a staging project. So far we approved all factory submissions if they built in the devel project and did not affect rings. To also better control the Factory submissions, we put also factory submissions into staging projects. As it doesn't make sense to build an ISO and test it in openqa if the package is not even on the ISO, we create "staging projects light" that only check build success. Then name you will see for them is e.g openSUSE:Factory:Staging:adi:1 - we create and delete them as needed, reusing numbers. 'adi' is what sticked from the naming discussion and is a rather unusual abbrevation of ad interim. Please let me know if you notice something unusual with this process. We just deployed it, so it's pretty young. Thanks, Stephan -- 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] empty apache_suse_maintenance_mmn
by Olaf Hering 16 Jul '15

16 Jul '15

What is supposed to fill the %apache_suse_maintenance_mmn macro? Its empty for everything but Factory, breaking the build of apache-rpm-macros. --- Factory/home/abuild/rpmbuild/BUILD/macros.apache +++ SLE_12/home/abuild/rpmbuild/BUILD/macros.apache @@ -1,13 +1,13 @@ %apache_major 2 %apache_branch 2.4 %apache_pname apache2 -%apache_apxs /usr/bin/apxs -%apache_cflags -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fPIC -Wall -DLDAP_DEPRECATED +%apache_apxs /usr/bin/apxs2 +%apache_cflags -fmessage-length=0 -grecord-gcc-switches -fstack-protector -O2 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -g -fPIC -Wall -DLDAP_DEPRECATED %apache_includedir /usr/include/apache2 %apache_libexecdir /usr/lib64/apache2 %apache_localstatedir /var/lib/apache2 %apache_mmn apache_mmn_20120211 -%apache_suse_maintenance_mmn suse_maintenance_mmn = 0 +%apache_suse_maintenance_mmn %apache_serverroot /srv/www %apache_sysconfdir /etc/apache2 %apache_datadir /srv/www Olaf -- 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] rpmbuild %lang() handling for new locales
by Olaf Hering 15 Jul '15

15 Jul '15

How does rpmbuild decide if LANG in such line generated by /usr/lib/rpm/find-lang.sh is valid? %lang($LANG) /usr/share/locale/$LANG/LC_MESSAGES/$PKG.mo I suggest to enhance /usr/lib/rpm/find-lang.sh to wipe all files in $LANG if its unknown by rpmbuild because at least the SLE11 version just ignores the line. As a result the build fails due to unpackaged files. Olaf -- 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] Introduce golang-packaging
by Marguerite Su 13 Jul '15

13 Jul '15

Hi, friends, Last month I saw some posts in this list complaining that our devel:languages:go is not packager friendly, eg, we don't have "golang(google.golang.org/cloud/compute/metadata)" style BuildRequires, and package names are not intuitive (not following golang's importpath so when an error about importpath occurs, packager don't know which package provides it) So I coded. https://github.com/marguerite/golang-packaging devel:languages:go/golang-packaging This is inspired by the logic behind the nodejs-packaging packge in devel:languages:nodejs. nodejs-packaging is developed by Fedora/RedHat package maintainers, using the brand-new system RPM 4.9 provides: http://www.rpm.org/wiki/PackagerDocs/DependencyGenerator Basically it has two parts: * matching rule * scripts to generate Provides/Requires When a RPM is being built, if file will install to the dir that mentioned by the regex matching rule, the self-maintained scripts will be called and the generated Provides/Requires will be attached along with the regular Provides/Requires. So I wrote two scripts: 1. golang.prov will extract importpath from specfile: "%define importpath xxx" > "%goprep xxx" > URL: xxx and all the sub-directories in /home/abuild/rpmbuild/BUILD/gocloud-%{version}(this is detected by "Source" tag), that is because both "google.golang.org/cloud" and "google.golang.org/cloud/compute/metadata" are valid importpaths in golang. 2. golang.req will extract such lines from all *.go files (except for those .go files inside examples/test directory and *_test.go files, because examples/tests are useless in production environment, with the imports inside them): * import "xxx" * import { xxx "xxx" } * import xx "xxx" these lines can actually be treated as golang's "include" or build/runtime Requires. and generate such golang() Requires. So if you're a golang packager, now you can just "BuildRequires: golang-packaging" and let my scripts to handle Provides/Requires for you automatically. with this, you can also "BuildRequires: golang(xxx)" for packages built with golang-packaging. Additional information: 1. If there're unneeded importpath in examples/tests, just leave them there, my package will skip them. If such importpath resides in main .go source codes, "%go_strip_builddep xx" in %prep step can help you strip them manually. 2. there's one shortcoming, the same as the one for nodejs-packaging: The build "success" status for a package doesn't mean the package can be installed without any problem. Because there might be non-fulfilled Requires for the package, remember to check it again using page like this: https://build.opensuse.org/package/binary/devel:languages:go/golang-org-x-t… As to package renames: I just follow the Fedora style: golang + importpath like string, eg: golang-github-golang-glog refers to github.com/golang/glog. basically importpath with ".org/.net/.com" will be okay with my package. You can refer to the golang-* packages I recently send to devel:languages:go as examples. Welcome to help golang package renaming and contribute to my package :-) Marguerite -- 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] Some trouble with language files
by Axel Braun 13 Jul '15

13 Jul '15

Hi all, I have a package with a couple of language files. The .mo files get compild from the .po - just one as an example [ 21s] + /usr/bin/python setup.py compile_catalog [ 21s] running compile_catalog [ 21s] compiling catalog 'share/locale/es_ES/LC_MESSAGES/tryton.po' to 'share/locale/es_ES/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/es_AR/LC_MESSAGES/tryton.po' to 'share/locale/es_AR/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/es_EC/LC_MESSAGES/tryton.po' to 'share/locale/es_EC/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/es_CO/LC_MESSAGES/tryton.po' to 'share/locale/es_CO/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/bg_BG/LC_MESSAGES/tryton.po' to 'share/locale/bg_BG/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/de_DE/LC_MESSAGES/tryton.po' to 'share/locale/de_DE/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/sl_SI/LC_MESSAGES/tryton.po' to 'share/locale/sl_SI/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/lt_LT/LC_MESSAGES/tryton.po' to 'share/locale/lt_LT/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/ca_ES/LC_MESSAGES/tryton.po' to 'share/locale/ca_ES/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/fr_FR/LC_MESSAGES/tryton.po' to 'share/locale/fr_FR/LC_MESSAGES/tryton.mo' [ 21s] compiling catalog 'share/locale/nl_NL/LC_MESSAGES/tryton.po' to 'share/locale/nl_NL/LC_MESSAGES/tryton.mo' [ 22s] compiling catalog 'share/locale/ja_JP/LC_MESSAGES/tryton.po' to 'share/locale/ja_JP/LC_MESSAGES/tryton.mo' [ 22s] compiling catalog 'share/locale/cs_CZ/LC_MESSAGES/tryton.po' to 'share/locale/cs_CZ/LC_MESSAGES/tryton.mo' [ 22s] compiling catalog 'share/locale/ru_RU/LC_MESSAGES/tryton.po' to 'share/locale/ru_RU/LC_MESSAGES/tryton.mo' Afterwards they are copied: [ 23s] creating /home/abuild/rpmbuild/BUILDROOT/tryton-3.6.1-0.i386/usr/share/locale/nl_NL/LC_MESSAGES [ 23s] copying share/locale/nl_NL/LC_MESSAGES/tryton.mo -> /home/abuild/rpmbuild/BUILDROOT/tryton-3.6.1-0.i386/usr/share/locale/nl_NL/LC_MESSAGES [ 23s] copying share/locale/nl_NL/LC_MESSAGES/tryton.po -> /home/abuild/rpmbuild/BUILDROOT/tryton-3.6.1-0.i386/usr/share/locale/nl_NL/LC_MESSAGES the %find_lang macro then kicks some out again: [ 23s] + /usr/lib/rpm/suse_update_desktop_file.sh tryton [ 23s] + /usr/lib/rpm/find-lang.sh /home/abuild/rpmbuild/BUILDROOT/tryton-3.6.1-0.i386 tryton --without-C [ 24s] removing translation /usr/share/locale/bg_BG/LC_MESSAGES/tryton.mo: 377 translated messages. [ 24s] removing translation /usr/share/locale/lt_LT/LC_MESSAGES/tryton.mo: 386 translated messages. [ 24s] removing translation /usr/share/locale/ca_ES/LC_MESSAGES/tryton.mo: 402 translated messages. [ 24s] removing translation /usr/share/locale/nl_NL/LC_MESSAGES/tryton.mo: 338 translated messages. [ 24s] removing translation /usr/share/locale/ja_JP/LC_MESSAGES/tryton.mo: <stdin>:81: 'msgid' and 'msgstr' entries do not both end with '\n' [ 24s] <stdin>:383: 'msgid' and 'msgstr' entries do not both end with '\n' [ 24s] <stdin>:709: 'msgid' and 'msgstr' entries do not both end with '\n' [ 24s] <stdin>:877: 'msgid' and 'msgstr' entries do not both end with '\n' [ 24s] msgfmt: found 4 fatal errors [ 24s] 337 translated messages. Three questions... - Why are the .mo files compiled without error (of course, this should be the standard case...)? - Why does find_lang issue the error (despite proper compilation) - and is it treated critical? Thanks Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 16

[opensuse-packaging] force obsolete old library
by Olaf Hering 09 Jul '15

09 Jul '15

The shared library from x.rpm was moved to a subpackage libx0.rpm. Since x.rpm contained just that lib the new libx0.rpm now has: Obsoletes: x < %version Provides: x = %version But since x.rpm and libx0.rpm have the very same version number the %version is actually %version-%release for both tags. Unfortunately the %release of x.rpm is larger than the one from libx0.rpm. As a result x.rpm will not be removed, and zypper reports fileconflicts. Is there a way for the packager or OBS admin to adjust the release, other than creating 20 dummy SR for Factory? The offending package is libquvi-0.9.4-23.1.rpm, built Dec 2014 in PMBS. Now the package is in TW, there is no need to have it in PMBS anymore. Olaf -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 7

[opensuse-packaging] Problem building otrverwaltung
by Axel Braun 09 Jul '15

09 Jul '15

Hello, I'm currently trying to build otrverwaltung, a python tool to decode and cut files downloaded from OTR (this is legal even in Germany...). It has some components that run under wine, which cause problems. During build, a couple of files are copied: [ 85s] copying data/tools/intern-VirtualDub/wine/drive_c/Program Files/ffdshow/ff_wmv9.dll -> /home/abuild/rpmbuild/BUILDROOT/otr-verwaltung-0.96-2.1.i386/usr/share/otrverwaltung/tools/intern-VirtualDub/wine/drive_c/Program Files/ffdshow [ 85s] copying data/tools/intern-VirtualDub/wine/drive_c/windows/system32/tapi32.dll -> /home/abuild/rpmbuild/BUILDROOT/otr-verwaltung-0.96-2.1.i386/usr/share/otrverwaltung/tools/intern-VirtualDub/wine/drive_c/windows/system32 When checking later on, it comes to an error on these files: [ 89s] calling /usr/lib/rpm/brp-suse.d/brp-72-extract-appdata [ 90s] Processing files: otr-verwaltung-0.96-2.1.noarch [ 90s] error: File must begin with "/": Files/ffdshow/ff_wmv9.dll [ 90s] error: File must begin with "/": Files/ffdshow/languages/ffdshow.1046.br [ 90s] error: File must begin with "/": Files/ffdshow/custom [ 90s] error: File must begin with "/": matrices/eqm_v3uhr_rev2.xcm [ 90s] error: File must begin with "/": Files/ffdshow/languages/ffdshow.1034.es Any idea how to solve or work around this? Thanks Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 8

[opensuse-packaging] ERROR: RPATH
by Michael Ströder 09 Jul '15

09 Jul '15

HI! I wanted to update FreeRADIUS packages: https://build.opensuse.org/package/show/home:stroeder:branches:network/free… This build fails now although I don't see a difference related to my last update of this package: [ 281s] calling /usr/lib/rpm/brp-suse.d/brp-35-rpath [ 282s] ERROR: RPATH "/usr/local/unixodbc/lib" on /home/abuild/rpmbuild/BUILDROOT/freeradius-server-3.0.9-91.1.x86_64/usr/lib64/freeradius/rlm_sql_unixodbc.so is not allowed See full build log here: https://build.opensuse.org/build/home:stroeder:branches:network/openSUSE_Tu… Any clue? Is this RPATH check new? Ciao, Michael.

2 2

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

08 Jul '15

7 14

[opensuse-packaging] zypper problem with Ncurses
by Rusmir Duško 07 Jul '15

07 Jul '15

Hello I have problem with all packages since long time which use Ncurses, not only Games also now tmux [ 13s] [76/118] cumulate ncurses-devel-5.9-67.18 [ 38s] checking curses.h usability... yes [ 38s] checking curses.h presence... yes [ 38s] checking for curses.h... yes .. [ 24s] checking for library containing setupterm... -lncurses /var/tmp/build-root/openSUSE_Factory-x86_64/.build.packages/RPMS/x86_64/ > zypper in -f tmux-2.0-0.x86_64.rpm Loading repository data... Reading installed packages... Forcing installation of 'tmux-2.0-0.x86_64' from repository 'Plain RPM files cache'. Resolving package dependencies... Problem: nothing provides libtinfo.so.5(NCURSES_TINFO_5.0.19991023)(64bit) needed by tmux-2.0-0.x86_64 Solution 1: do not install tmux-2.0-0.x86_64 Solution 2: break tmux-2.0-0.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): When download mine RPM from my OBS page then works with zypper Have installed Ncurses zypper se ncurses Loading repository data... Reading installed packages... S | Name | Summary | Type --+--------------------------+-----------------------------------------------------------+----------- | gambas3-gb-ncurses | The ncurses component | package i | libncurses5 | The New curses Libraries | package i | libncurses5-32bit | The New curses Libraries | package i | libncurses6 | The New curses Libraries | package i | libncurses6-32bit | The New curses Libraries | package | libyui-ncurses-devel | Libyui-ncurses header files | package | libyui-ncurses-doc | Libyui-ncurses documentation | package | libyui-ncurses-pkg | Libyui - yast2 package selector widget for the ncurses UI | srcpackage | libyui-ncurses-pkg-devel | Libyui-ncurses-pkg header files | package | libyui-ncurses-pkg-doc | Libyui-ncurses-pkg documentation | package | libyui-ncurses-pkg-doc | Libyui-ncurses-pkg documentation | srcpackage i | libyui-ncurses-pkg6 | Libyui - yast2 package selector widget for the ncurses UI | package i | libyui-ncurses6 | Libyui - Character Based User Interface | package i | ncurses-devel | Include Files and Libraries mandatory for Development | package | ncurses-devel-32bit | Include Files and Libraries mandatory for Development | package i | ncurses-utils | Tools using the new curses libraries | package I have all reinstalled Ncurses packages with zypper in -f libncurses5 libncurses5-32bit libncurses6 libncurses6-32bit libyui-ncurses-pkg6 libyui-ncurses6 ncurses-devel ncurses-utils -- nemysis / Rusmir Dusko <nemysis(a)gmx.ch> -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 7