January 2013 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] cleanup for 12.3: not packaging files / directories in /var/run, /var/lock (and /run)
by Frederic Crozat 28 Jan '13

28 Jan '13

Hi all, as some of you might have noticed with recent systemd, you can see a warning at startup stating : var-lock.mount: Directory /var/lock to mount over is not empty, mounting anyway. (To see the over-mounted files, please manually mount the underlying file system to a secondary location.) var-run.mount: Directory /var/run to mount over is not empty, mounting anyway. (To see the over-mounted files, please manually mount the underlying file system to a secondary location.) This warning is caused by some packages installing either files or directories in /var/run (or /var/lock) which are later bind-mount to /run (/run/lock) which is a tmpfs, hiding files beneath. Robert Milasan has fixed some packages like dbus, avahi and unscd (moving them also from /var/run to /run) but feel free to help, making sure packages never create files nor directories in /var/run (and at the same time, migrate them to use /run instead) nor /var/lock. If a directory or a file needs to be created with specific permissions, package a tmpfiles.d file instead (see manpage). And if you want a file / directory to be "owned" by a package but at the same time, it will be stored on a tmpfs mount point (/var/run , /var/lock, /run), use %ghost so rpm will not write the file on disk. Thanks for your help. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- 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] Bugzilla outage
by Robert Schweikert 25 Jan '13

25 Jan '13

Hi All, Sorry for the cross-post, but due to the short time frame there's not much time to let the message percolate. Anyway, Bugzilla will be down starting at 5:00 P.M. MST. The planned outage is 1.5 hours. Bugzilla is being shutdown to upgrade the disk storage, we are running out of space. Sorry for the short notice, I am just the messenger ;) Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- 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 Status (2012/12/28)
by Cristian Morales Vega 23 Jan '13

23 Jan '13

This time I didn't report the new problems. Simply we are in Christmas and people is less active. But just in case somebody feels like fixing something, here is the list. In any case the list is too long, We have six build failures because sblim-sfcb removed its /etc/init.d/sfcb file to use only Systemd and those packages restart the service in the scriplets. Then there are also a few C# failures. And the classic failures from the kernel update. Name Devel Project Bug report Status - selinux-policy security:SELinux bnc#789160 Fails for 136 days: error(s) encountered while parsing configuration (Request 145734 to openSUSE:Factory) - hawk network:ha-clustering:Factory bnc#789165 Fails for 95 days: cannot load such file -- gettext/tools/rgettext (rails 2 vs rails 3?) (Request 146273 to openSUSE:Factory) - psi network bnc#789178 Fails for 85 days: error: 'OtrlMessageAppOps' has no member named 'notify' (Different changes in devel project (since 15 days)) - gnome-do-plugins GNOME:Apps bnc#789193 Fails for 85 days: Type `FlickrNet.FoundUser' does not contain a definition for `Username' - qutim KDE:Distro:Factory bnc#789195 Fails for 85 days: libotr update - f-spot GNOME:Apps bnc#789196 Fails for 85 days: The type or namespace name `Licenses' could not be found - pcsc-asedriveiiie-usb security:chipcard bnc#793542 Fails for 52 days: /usr/lib/udev/rules.d/*.rules not found - ksymoops Base:System bnc#793544 Fails for 47 days: #error config.h must be included before this header - excalibur Java:packages bnc#793551 Fails for 47 days: error: method checkPackage in class Component cannot be applied - postgresql server:database:postgresql bnc#793553 Fails for 45 days: timezone package needed for timezone (Different changes in devel project (since 3 months)) - libzypp-bindings zypp:Head bnc#793554 Fails for 45 days: test suite fails - webyast-base YaST:Web bnc#793558 Fails for 40 days: No such file or directory - /var/lib/polkit-1/ (Request 146369 to openSUSE:Factory) - libimobiledevice mobile:synchronization:FACTORY bnc#796133 Fails for 25 days: Overriding final methods is not allowed - compiz X11:Compiz bnc#789161 Fails for 19 days: kwin 4.10 - mono-tools Mono:Factory Fails for 18 days: error CS1061: Type `Mono.Cecil.Cil.ExceptionHandler' does not contain a definition for `FilterEnd' (Different sources in devel project (since about 1 month)) - nant Mono:Factory Fails for 18 days: missing framework mono - gnome-do GNOME:Apps Fails for 18 days: error CS0012: The type `Do.Platform.Linux.IConfigurable' is defined in an assembly - gbrainy GNOME:Apps Fails for 18 days: error CS1729: The type `Mono.CSharp.Report' does not contain a constructor - docky GNOME:Apps Fails for 18 days: Assuming assembly reference `Mono.Cairo - libvirt-cim Virtualization Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-ssh_service_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-power_supply_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-fan_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-ethport_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-boot_control_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - smuxi GNOME:Apps Fails for 18 days: error CS0305: Using the generic type `System.Action<T>' requires `1' type argument(s) (New upstream version 0.8.10.12100 available) - perl-Sys-Virt Virtualization Fails for 17 days: libvirt >= 1.0.0 is required - atspiuiasource Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - uiadbus Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - uiaatkbridge Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - uiautomationwinforms Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - xerces-j2-bootstrap openSUSE:Factory Fails for 13 days: the typical java one - python-nose devel:languages:python Fails for 10 days: assert 'test_timeout' in log - haveged security Fails for 10 days: failing test suite (Request 146266 to openSUSE:Factory) - ImageMagick graphics Fails for 10 days: failing test suite - calibre Documentation:Tools Fails for 9 days: /etc/bash_completion.d/calibre not found (Different changes in devel project (since 3 days)) - bundle-lang-gnome-extras openSUSE:Factory Fails for 9 days: dia graphs are missing - libwebkit3 openSUSE:Factory Fails for 9 days: Installed (but unpackaged) file(s) found: - _product:openSUSE-ftp-livetree-gnome-i586 Fails for 9 days: outdated lists - _product:openSUSE-ftp-livetree-gnome-x86_64 Fails for 9 days: outdated lists - kernel-vanilla openSUSE:Factory Fails for 8 days: worker ran out of disc space (Request 146394 to openSUSE:Factory) - gstreamer-0_10-plugins-bad multimedia:libs Fails for 8 days: error: expected ')' before '__attribute__' - iscsitarget hardware Fails for 8 days: Kernel 3.7 - hdjmod hardware Fails for 8 days: Kernel 3.7 (Request 146314 to openSUSE:Factory) - ndiswrapper hardware Fails for 8 days: Kernel 3.7 - virtualbox Virtualization Fails for 8 days: Kernel 3.7 - xtables-addons security:netfilter Fails for 8 days: Kernel 3.7 (Request 146265 to openSUSE:Factory) - coreutils-testsuite openSUSE:Factory Fails for 8 days: broken spec - cogl GNOME:Factory Fails for 8 days: compiling docu fails (libxml?) - ibus M17N Fails for 8 days: compiling docu fails (libxml?) - installation-images system:install:head Fails for 7 days: no such package: libnl-* - libdlm network:ha-clustering:Factory Fails for 7 days: Unknown build failure - gdome2 GNOME:Apps Fails for 7 days: Unknown build failure - yast2-installation YaST:Head Fails for 7 days: Unknown build failure -- 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] Common LIsp packaging
by Alex Naumov 22 Jan '13

22 Jan '13

Hello everyone, as you know, we're recently formed a team that will take care of the packaging guidelines and introduced a small process to change them: http://en.opensuse.org/openSUSE:Packaging_guidelines_change_process I would like to start discussion about Common Lisp and create Lisp packaging related rules. The first version of it you can find there: http://en.opensuse.org/openSUSE:Packaging_Lisp (please discuss here before edit something in wiki) I don't know how many Lisp developers we have, but I invite everybody to find and create most interesting, correct and optimal packaging rules for openSUSE distribution. Alex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 9

[opensuse-packaging] A better handling of several BLAS and LAPACK implementations
by Sebastien Corot 21 Jan '13

21 Jan '13

Hi, I just want to have your comments and feedback regarding the changes I made on the lapack, libatlas3 and openblas packages in order to provide the to the end users the ability to switch between the several BLAS implementations available on OBS. These changes have been inspired from debian (http://wiki.debian.org/DebianScience/LinearAlgebraLibraries) which uses update-alternatives. My work is available in https://build.opensuse.org/project/show?project=home%3Ascorot%3Abranches%3A… Sebastien -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5

[opensuse-packaging] OBS runs %post during the build process (?)
by Alex Naumov 21 Jan '13

21 Jan '13

Hi, can somebody remind me how to add some piece of code to spec that will *NOT* run during the build process (I need it at installation only). As I remember, it was %post... but OBS run %post during the build. Thank you, Alex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

11 19

[opensuse-packaging] RFC: Guidelines change: Erlang
by Matwey V. Kornilov 21 Jan '13

21 Jan '13

Hi, I am a maintainer at devel:languages:erlang, and current problem is that we do not have guidelines for Erlang libraries (packages). I would like to discuss this situation. The guidelines are subject to decide and to agree. I list some issues and possible options for each. Next, I would like to put in discussion some additional ideas to further development. 1. Names. I suggest erlang-* convention naming (like python-, ruby-, etc...). Some existing packages have to be renamed (pure technical moment). 2. Group. As for me, It is clear: "Development/Languages/Other" 3. +debug_info. Should we build beam-code with +debug_info, or without? I suggest to build everything with +debug_info, this makes dumps more informative not only for development but for runtime production also. 4. /src subtree. My suggestion is not to pack sources at all, or pack it as separate package. (Compare with erlang and erlang-src) 5. Versions (A). Some libraries at github don't have any tags or releases, this is for us to decide how to enumerate packages. My suggestion is 1) to ask upstream maintainer to apply tags and releases 2) to use _service:tar_scm and _service:set_version to enumerate git master by UNIX timestamps (This is the most automatic and simple way). 6. Versions (B1). Every erlang library (application) have to have .app file with 'vsn' field where its version is indicated. The library location must be in agreement with this version and application name. I.e, if we have {application, myapp, [{description, "myapp My Erlang Application"}, {vsn, "1.2.3"}, then correct place is "/usr/lib/erlang/lib/myapp-1.2.3/". We have to provide some lint-checks and rpm-macros to check this and to simplify packaging. 7. Versions (B2). 'vsn' and appname often don't coincide with upstream git reponame and tag/release. My suggestion is 1) to ask upstream maintainer to sort the things out 2) to use upstream name and upstream version as name and version of RPM package, and to generate location from .app-file. (some rpm- macros have to be written to simplify). 8. noarch. BEAM bytecode is platform independent, AFAIK. Should we build packages as noarch? Further ideas: I. An analogous to py2pack to generate spec-templates from .app files or rebar settings of project. II. Automatic Requires/Provides checking for erlang. Some BEAM-code inspection is needed to produce the lists of exported and required symbols/modules. Remember, erlang has common namespace. Functions from different modules and packages may interfere with each other. p.s. So, gentlemen, please give me the feedback. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 6

[opensuse-packaging] removal help -line: %suse_update_config.
by doiggl＠velocitynet.com.au 21 Jan '13

21 Jan '13

Hello How is the following error fixed: Thanks Glenn Part of log shown below. Full Log see [1] Here is the spec file[2] Question: What can replace this section ? %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" \ ./configure \ --prefix=%{_prefix} \ --libdir=%{_libdir} \ --bindir=%{_bindir} \ --includedir=%{_includedir} \ --sysconfdir=%{_sysconfdir} \ --mandir=%{_mandir} make %{?jobs:-j%jobs} CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" entire log see [1] https://build.opensuse.org/package/live_build_log?arch=x86_64&package=reise… . . [ 58s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/home:doiggl/openSUSE_12.2/cdaef9d019b97ec53d83b9f7…' /home/abuild/rpmbuild/SOURCES/reiser4progs.spec [ 58s] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.XZ0ADg [ 58s] + umask 022 [ 58s] + cd /home/abuild/rpmbuild/BUILD [ 58s] + cd /home/abuild/rpmbuild/BUILD [ 58s] + rm -rf reiser4progs-1.0.7 [ 58s] + /usr/bin/bzip2 -dc /home/abuild/rpmbuild/SOURCES/reiser4progs-1.0.7.tar.bz2 [ 58s] + /bin/tar -xf - [ 59s] + STATUS=0 [ 59s] + '[' 0 -ne 0 ']' [ 59s] + cd reiser4progs-1.0.7 [ 59s] + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . [ 59s] + echo 'Patch #1 (fsck-dont-allocate-unalloc-extents.patch):' [ 59s] Patch #1 (fsck-dont-allocate-unalloc-extents.patch): [ 59s] + /usr/bin/cat /home/abuild/rpmbuild/SOURCES/fsck-dont-allocate-unalloc-extents.patch [ 59s] + /usr/bin/patch -s -p1 --fuzz=0 [ 59s] + echo 'Patch #2 (reiser4progs-fsck-handle-unprepped-cluster.patch):' [ 59s] Patch #2 (reiser4progs-fsck-handle-unprepped-cluster.patch): [ 59s] + /usr/bin/patch -s -p1 --fuzz=0 [ 59s] + /usr/bin/cat /home/abuild/rpmbuild/SOURCES/reiser4progs-fsck-handle-unprepped-cluster.patch [ 59s] + exit 0 [ 59s] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.9M0EQf [ 59s] + umask 022 [ 59s] + cd /home/abuild/rpmbuild/BUILD [ 59s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-5.1.x86_64 [ 59s] ++ dirname /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-5.1.x86_64 [ 59s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT [ 59s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-5.1.x86_64 [ 59s] + cd reiser4progs-1.0.7 [ 59s] + echo 'WARNING: REMOVE %suse_update_config. If your sources are really' [ 59s] WARNING: REMOVE %suse_update_config. If your sources are really [ 59s] + echo 'too old to cover current architectures, prefer autoreconf --force --install' [ 59s] too old to cover current architectures, prefer autoreconf --force --install [ 59s] + autoreconf --force --install [ 59s] /var/tmp/rpm-tmp.9M0EQf: line 33: autoreconf: command not found [ 59s] error: Bad exit status from /var/tmp/rpm-tmp.9M0EQf (%build) [ 59s] [ 59s] [ 59s] RPM build errors: [ 59s] Bad exit status from /var/tmp/rpm-tmp.9M0EQf (%build) [ 61s] /.build/build: line 313: 239 Killed background_monitor_process / &>/dev/null [ 63s] [ 49.794059] SysRq : Power Off [ 63s] [ 49.819442] Power down. [2]https://build.opensuse.org/package/view_file?expand=1&file=reiser4progs.s… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 9

[opensuse-packaging] help needed: scala compile error - missing artifact super-pom / aqute
by Denny Beyer 21 Jan '13

21 Jan '13

Dear all, I'm trying to build the latest scala packages, but don't get it to compile due to missing artifacts, which seemed to be introduced in scala version 2.10 . There are some maven dependencies missing, I can't find on obs. As well as a aqute package. If someone has got some experience compiling scala 2.10 or with those libs/jars, please help. packages are under https://build.opensuse.org/project/show?project=devel%3Alanguages%3Ascala Compile output: [ 5s] [artifact:dependencies] Unable to resolve artifact: Missing: [ 5s] [artifact:dependencies] ---------- [ 5s] [artifact:dependencies] 1) biz.aQute:bnd:jar:1.50.0 [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] Try downloading the file manually from the project website. [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] Then, install it using the command: [ 5s] [artifact:dependencies] mvn install:install-file - DgroupId=biz.aQute -DartifactId=bnd -Dversion=1.50.0 -Dpackaging=jar - Dfile=/path/to/file [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] Alternatively, if you host your own repository you can deploy the file there: [ 5s] [artifact:dependencies] mvn deploy:deploy-file - DgroupId=biz.aQute -DartifactId=bnd -Dversion=1.50.0 -Dpackaging=jar - Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] Path to dependency: [ 5s] [artifact:dependencies] 1) org.apache.maven:super-pom:jar:2.0 [ 5s] [artifact:dependencies] 2) biz.aQute:bnd:jar:1.50.0 [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] ---------- [ 5s] [artifact:dependencies] 1 required artifact is missing. [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] for artifact: [ 5s] [artifact:dependencies] org.apache.maven:super-pom:jar:2.0 [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] from the specified remote repositories: [ 5s] [artifact:dependencies] central (http://repo1.maven.org/maven2) [ 5s] [artifact:dependencies] [ 5s] [artifact:dependencies] [ 5s] [ 5s] BUILD FAILED [ 5s] /home/abuild/rpmbuild/BUILD/scala-2.10.0-sources/build.xml:46: The following error occurred while executing this line: [ 5s] /home/abuild/rpmbuild/BUILD/scala-2.10.0-sources/build.xml:284: Unable to resolve artifact: Missing: [ 5s] ---------- [ 5s] 1) biz.aQute:bnd:jar:1.50.0 [ 5s] [ 5s] Try downloading the file manually from the project website. [ 5s] [ 5s] Then, install it using the command: [ 5s] mvn install:install-file -DgroupId=biz.aQute -DartifactId=bnd - Dversion=1.50.0 -Dpackaging=jar -Dfile=/path/to/file [ 5s] [ 5s] Alternatively, if you host your own repository you can deploy the file there: [ 5s] mvn deploy:deploy-file -DgroupId=biz.aQute -DartifactId=bnd - Dversion=1.50.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] - DrepositoryId=[id] [ 5s] [ 5s] Path to dependency: [ 5s] 1) org.apache.maven:super-pom:jar:2.0 [ 5s] 2) biz.aQute:bnd:jar:1.50.0 [ 5s] [ 5s] ---------- [ 5s] 1 required artifact is missing. [ 5s] [ 5s] for artifact: [ 5s] org.apache.maven:super-pom:jar:2.0 [ 5s] [ 5s] from the specified remote repositories: [ 5s] central (http://repo1.maven.org/maven2) -- 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] 64bit compatibility issue with python 3 package
by todd rme 20 Jan '13

20 Jan '13

On openSUSE 12.1 and 12.2 (but not Factory), I am getting a build error for python3-simplejson in devel:languages:python E: python3-simplejson 64bit-portability-issue simplejson/_speedups.c:357, 514, 521, 622, 773, 1098, 1133, 1251, 1546, 1775, 1984, 2054, 2201 (this happens on both 32bit and 64bit systems) All of these lines are related to unicode. The most common is: void *str = PyUnicode_DATA(pystr); where pystr is as PyObject *pystr I can't find any information online about what might be causing this problem. Anybody have any ideas? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2