February 2017 - openSUSE Packaging - openSUSE Mailing Lists

Re: [opensuse-packaging] wx Blues (again)
by Jan Engelhardt 14 Feb '17

14 Feb '17

On Tuesday 2017-02-14 06:42, Dave Plater wrote: > >https://build.opensuse.org/package/view_file/openSUSE:Factory/wxWidgets-3_0/ >relax-abi.diff?rev=15 > >I've removed the patch in home:plater and after everything has rebuilt and published I'll get the bug >reporter to test. >Jan, what's the purpose of this patch? The patch makes it such that programs being compiled treat ABIs 1002..1010 the same. Of course that requires applications to be rebuilt to get the notice.. so the patch does not fix the issue -- but it does not break it either. -- 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] wx Blues (again)
by Bruno Friedmann 14 Feb '17

14 Feb '17

In an effort to clean up Application:Geo we (maintainers there) have cleanup all different kind of *wx* build there to use what oss/update propose. Now I've an error on trying to fix grass build for TW if [ "/home/abuild/rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/ scripts/d.rast.edit" != "" ] ; then GISRC=/home/abuild/rpmbuild/BUILD/ grass-7.2.0/dist.x86_64-pc-linux-gnu/demolocation/.grassrc72 GISBASE=/home/ abuild/rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu PATH="/home/abuild/ rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/bin:/home/abuild/rpmbuild/ BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/bin:/home/abuild/rpmbuild/BUILD/ grass-7.2.0/dist.x86_64-pc-linux-gnu/scripts:$PATH" PYTHONPATH="/home/abuild/ rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/etc/python:/home/abuild/ rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/gui/wxpython:$PYTHONPATH" LD_LIBRARY_PATH="/home/abuild/rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux- gnu/bin:/home/abuild/rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/bin:/ home/abuild/rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/scripts:/home/ abuild/rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/lib:/home/abuild/ rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/lib:" LC_ALL=C /home/ abuild/rpmbuild/BUILD/grass-7.2.0/dist.x86_64-pc-linux-gnu/scripts/d.rast.edit --html-description < /dev/null | grep -v '</body>\|</html>' > d.rast.edit.tmp.html ; fi Fatal Error: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1002,STL containers,compatible with 2.8), and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1010,STL containers,compatible with 2.8). make: *** [../../include/Make/Html.make:14: d.rast.edit.tmp.html] Error 1 rm d.rast.edit.tmp.html Anyone has an idea how this can be fixed, or do we have more deeper problems with *wx*/python-wx ? Packages installed with wx in libwx_baseu_xml-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_adv-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_propgrid-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_media-suse1-3.0.2-9.1.x86_64 wxWidgets-3_0-devel-3.0.2-9.1.x86_64 libwx_baseu-suse1-3.0.2-9.1.x86_64 libwx_baseu_net-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_core-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_html-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_xrc-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_stc-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_gl-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_ribbon-suse1-3.0.2-9.1.x86_64 python-wxWidgets-3_0-3.0.2.0-2.11.x86_64 python-wxWidgets-3_0-devel-3.0.2.0-2.11.x86_64 libwx_gtk2u_richtext-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_aui-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_qa-suse1-3.0.2-9.1.x86_64 libwx_gtk2u_webview-suse1-3.0.2-9.1.x86_64 Extract of the wip spec # Post Leap 42 / TW %if 0%{?suse_version} > 1325 BuildRequires: python-wxWidgets-3_0-devel BuildRequires: wxWidgets-3_0-devel %else BuildRequires: python-wxWidgets >= 2.8 BuildRequires: wxWidgets-devel >= 2.8 %define _use_internal_dependency_generator 0 %define __find_requires %wx_requires %endif Thanks for any thoughts about this situation. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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] Question for license
by Eric Schirra 13 Feb '17

13 Feb '17

Hello, I have an request for package lazarus. And in this request is an exclude for aggpas/gpc on the grounds that license is proplematic. In decription of license is called "not for commercial product" but free for non-commercial-use. Here is the page: http://crossgl.com/aggpas/aggpas-licence.htm http://www.cs.man.ac.uk/aig/staff/alan/software/ And text from copying.txt: Copyright: (C) 1997-1999, Advanced Interfaces Group, University of Manchester. This software is free for non-commercial use. It may be copied, modified, and redistributed provided that this copyright notice is preserved on all copies. The intellectual property rights of the algorithms used reside with the University of Manchester Advanced Interfaces Group. You may not use this software, in whole or in part, in support of any commercial product without the express consent of the author. There is no warranty or other guarantee of fitness of this software for any purpose. It is provided solely "as is". Can this now deliver in package or must it exclude? Can someone from suse help me? -- Gruß eRiC -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 6

[opensuse-packaging] [lsyncd, official repo] Wrong path to conf-file
by Mikhail Kasimov 13 Feb '17

13 Feb '17

Hello! [1] https://software.opensuse.org/package/lsyncd (2.1.5 in TW and 42.(1|2) official repo) when installed 'systemctl start lsyncd.service' cannot be run, because wrong path to conf-file is defined: /etc/lsyncd.conf instead of /etc/lsyncd/lsyncd.conf This error is also present in /etc/sysconfig/lsyncd file: ===================================================== k_mikhail@linux-mk500:~> cat /etc/sysconfig/lsyncd # Keep the space there for systemd. Don't nest variables without # changing the systemd service file to use: /usr/bin/sh -c 'eval XXXX' # #LSYNCD_OPTIONS="-pidfile /run/lsyncd.pid /etc/lsyncd.conf" #LSYNCD_OPTIONS=" " ===================================================== [2] boo: https://bugzilla.opensuse.org/show_bug.cgi?id=975118 Who can help to fix this annoying bug, please? Thanks! -- 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] Looking for devel project for owfs
by Thomas Zimmermann 12 Feb '17

12 Feb '17

Hi, I'm having owfs for some years in one of my home projects, and I think it is time to get it a devel project. OWFS is a collection of tools to communicate with devices using the 1-wire bus of Dallas/Maxim. The functionality is provided by several tools. One is the one wire file system which provides a file system structure to access the information. Another one is owhttpd which provides access via http. owserver which provides access via an own network protocol. Also several binding libraries for a direct access are provided. Webpage: http://owfs.org Package: https://build.opensuse.org/package/show/home:Heinervdm/owfs I'm unsure about where to submit it. - Base:System where i2c-tools can be found? - utilities because it's a utilitiy? - hardware because it provides tools to communicate with hardware? - filesystems because it provides some filesystem? - somewhere else? I would be thankful for your proposals. Thanks, Thomas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 3

[opensuse-packaging] -debuginfo package naming change proposal
by Richard Biener 10 Feb '17

10 Feb '17

Hi, currently we have an inconsistency with naming debuginfo packages for multilib packages (-32bit, -64bit). Packages that build multilibs themselves like gcc produce for example libgcc_s1-32bit to which then rpm appends -debuginfo to form libgcc_s1-32bit-debuginfo. This is upstream rpm behavior. Now we have another way of producing multilib packages, namely via the baselibs.conf machinery which has a default rule to produce libgcc_s1-debuginfo-32bit. This is inconsistent and results in gdb making invalid suggestions about debuginfo packages to install (it suggests glibc-32bit-debuginfo instead of glibc-debuginfo-32bit). The proposal is to fix the SUSE specific baselibs.conf script to instead produce X-32bit-debuginfo from X-debuginfo. If there are no objections to this plan we'll go forward with this. Richard. -- Richard Biener <rguenther(a)suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, 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 1

[opensuse-packaging] PyPI or not PyPI?
by Mikhail Terekhov 10 Feb '17

10 Feb '17

Hi, There are at least three ways to use PyPI as a source URL for python packages: https://pypi.python.org/pypi - a canonical (production) site https://pypi.org - a pre production (test) version of the Warehouse that according its documentation will _eventually_ power the canonical site. https://pypi.io - just redirects to https://pypi.org Which one is considered as a standard? The production or the test one? Regards, Mikhail -- 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] Building against 13.1
by Axel Braun 10 Feb '17

10 Feb '17

Hi, I have branched a package that I need for 13.1. The repo is marked as deleted, but OBS offers to 'Add additional path to this repository' There is for example http://download.opensuse.org/distribution/13.1/repo/oss/ or http://download.opensuse.org/update/13.1/ available which may work - but the OBS website does not accept the entries. Any recommendation? Thanks Axel -- 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] Flash Player installation patch in kdelibs4
by Karl Cheng 10 Feb '17

10 Feb '17

Continuing on from sr#455389: Currently there is a patch in the kdelibs4 package which basically detects when a webpage loaded via kdelibs4 attempts to load the Flash Player plugin, then directs the user to install the Flash Player package via a one-click install file which no longer exists. Two options were suggested: - Replace the notice with a link to https://en.opensuse.org/Adobe_Flash_Player - Drop the patch entirely What should be done in this case? -- - Karl Cheng (Qantas94Heavy) -- 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] RFC: package guideline / new system user handling
by Thorsten Kukuk 07 Feb '17

07 Feb '17

Hi, as already announced/discussed two weeks ago on the factory list, we want to make changes to how system users are created and handled. The current handling of system accounts on openSUSE is a little bit "chaotic". We have aaa_base creating a lot of standard users, but nobody knows if they are still needed at all. Same for groups. Additional, we have some accounts, which 99,99% of the users will never need (like uucp), but will always be created, including the home directories. And to make the chaos really perfect, we have systemd (/usr/lib/sysusers.d/basic.conf), which creates system users and groups, which partly are also part of aaa_base. That's very confusing and error prune. I would like to propose the following addition to the "Users and Groups" section (https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups) ==== System users, which are used by a variety of applications, by standard filesystem directories or are standard users which should exist on every Unix compatible system, should be provided by special RPMs. This RPMs provides and the user and groups: ``` Provides: user(<name>) Provides: group(<name>) ``` This RPMs are also responsible to create and provide the home directory. Applications needing a special system user should require them: ``` Requires(pre): user(<name>) Requires(pre): group(<name>) ``` With this, the system users will only be created if they are needed. And an admin can easy find out, if a system user is still required or can be deleted. systemd-sysusers (sysusers.d(5)) is used to create this accounts. This allows to verify how the system account should look like. An example spec file for the uucp system user should contain the following lines: ``` Source1: system-user-uucp.conf BuildRequires: sysuser-tools %package -n system-user-uucp Summary: System user and group uucp %sysusers_requires %build %sysusers_generate_pre %{SOURCE1} uucp %pre -n system-user-uucp -f uucp.pre %files -n system-user-uucp %defattr(-,root,root) %dir %attr(0750,uucp,uucp) %{_sysconfdir}/uucp ``` ==== A reference implementation, which I would submit to Factory if approved, can be found at: https://build.opensuse.org/project/show/home:kukuk:sysusers Not all system accounts are converted yet, but to start, we don't need to do that. This will be a moving target, but should be easy and quick doable for most system user. Should this replace all usages of useradd? We don't think so. There is no reason to do so, except one package creates an account a ot of other packages need, too. Thanks, Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, 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

3 4