February 2019 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] New macro to limit resources allocation per thread
by Tomas Chvatal 23 Aug '19

23 Aug '19

Hello all, For use in libreoffice, chromium and others I've created macro that should allow you to limit jobs based on some constraints you can set later on in the spec to avoid OOM crashes. The usage is pretty straight forward (Once it is accepted in Tumbleweed): === BuildRequires: memory-constraints %build # require 2GB mem per thread %limit_build -m 2000 make %{?_smp_mflags} ==== Here the _smp_mflags vaule for 8GB machine would be 4 while default is number of cores (lets say 16)... Both macros %jobs and %_smp_mflags are overriden as such the integration should be really painless if you need to do something like this. Tom

7 12

[opensuse-packaging] Project example binaries - arch-dependent-file-in-usr-share error
by Chris Coutinho 28 Feb '19

28 Feb '19

Hello, I'm attempting to build a package for numerical simulations, that includes examples in /usr/share/<name>. I'm running into the 'arch-dependent-file-in-usr-share' error because there are sample binaries included in some sub-directories, and I'm looking to this list for some guidance. I read the guidelines on https://en.opensuse.org/openSUSE:Packaging_checks And the suggestion was to put the binaries into %libexecdir/packagename Am I supposed to move the binaries there manually and add the path to PATH in the spec file? Regards, Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] Dealing with Python3's implicit namespace packages
by John Paul Adrian Glaubitz 28 Feb '19

28 Feb '19

Hello! Recently, Microsoft switched their Python Azure SDK to use implicit namespace packages (PEP 420 [1]) for Python3. This means, that in order to create a Python namespace, packages no longer need to carry an __init__.py in each namespace directory. This means, that the RPM packages of the Python Azure namespace packages will contain empty directories only. I have tried to convert one of the Azure namespace packages such that for Python3, the RPM contains empty directories only [2]. Unfortunately, I cannot get the package to build this way. RPM keeps complaining that the %{python_sitelib} directory doesn't exist for Python3 even though I marked it with "%dir" and tried various variants to create %{python_sitelib}/azure for Python3 manually. Does anyone have any idea how to deal with implicit namespace packages? Thanks, Adrian > [1] https://www.python.org/dev/peps/pep-0420/ > [2] https://build.opensuse.org/package/show/home:glaubitz:branches:devel:langua… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

Re: [opensuse-packaging] Dealing with Python3's implicit namespace packages
by aplanas＠suse.de 28 Feb '19

28 Feb '19

On Thursday, February 28, 2019 2:00:31 PM CET John Paul Adrian Glaubitz wrote: > Does anyone have any idea how to deal with implicit namespace packages? You create the directory in the section %prep, but later is removed by the system: /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/python-azure- nspkg-3.0.2-7.1.x86_64 I do not have experiences with namespaces packages in python, but I wonder why you create the directory manually and is not created by setuptools? I for some reason you need to create this directory, try in the %install section. -- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- 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] Dealing with Python3's implicit namespace packages
by John Paul Adrian Glaubitz 28 Feb '19

28 Feb '19

Hello! Recently, Microsoft switched their Python Azure SDK to use implicit namespace packages (PEP 420 [1]) for Python3. This means, that in order to create a Python namespace, packages no longer need to carry an __init__.py in each namespace directory. This means, that the RPM packages of the Python Azure namespace packages will contain empty directories only. I have tried to convert one of the Azure namespace packages such that for Python3, the RPM contains empty directories only [2]. Unfortunately, I cannot get the package to build this way. RPM keeps complaining that the %{python_sitelib} directory doesn't exist for Python3 even though I marked it with "%dir" and tried various variants to create %{python_sitelib}/azure for Python3 manually. Does anyone have any idea how to deal with implicit namespace packages? Thanks, Adrian > [1] https://www.python.org/dev/peps/pep-0420/ > [2] https://build.opensuse.org/package/show/home:glaubitz:branches:devel:langua… -- 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] Start service or application at build time?
by Eric Schirra 28 Feb '19

28 Feb '19

Hello, i have a question to packaging. Is it allowed to start a service or application in build time to test some things? Particularly when the service is running farther when an error rise up and the build was stop. Imho this should not be done. But iss it generally forbidden? -- Regards Eric -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] Include source package A in build for B
by Axel Braun 26 Feb '19

26 Feb '19

Hi, I'm currently trying to build the orthanc-postgresql package. Problem is that most Orthanc plugins re-use a part of the C++ code of Orthanc, independently of the development headers. To solve this issue, we can put the source code distribution "Orthanc-1.5.5.tar.gz" file into a folder called "ThirdPartyDownloads" located next to the "PostgreSQL/CMakeLists.txt" file. Providing the source package is IMO not the smartest idea, as this requires maintenance of version for orthanc not only in hte orthanc package, but as well in each plugin package Can I somehow include the orthanc.src.rpm in the build for the plugin? 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 12

[opensuse-packaging] Python packages failing
by Sean Marlow 25 Feb '19

25 Feb '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, With the move to Python 3.7 in Tumbleweed I see many packages failing build against Tumbleweed due to the following error: nothing provides python(abi) = 3.6 needed by {python_dependency} Where {python_dependency} is any number of python packages such as boto3. Any suggestions in how to resolve these errors? I see for example that boto3 is building fine in factory. And the package which requires boto3 passes against factory is well. Given Tumbleweed is a snapshot of factory is the only fix to wait for a new snapshot of Tumbleweed? Thanks, - -- Sean Marlow Public Cloud Developer sean.marlow(a)suse.com -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEqA16xWoe2L38VgYCJ30GzZDdUEsFAlxurqYACgkQJ30GzZDd UEvmJxAAuxtJ5yRQJ6QDOx3z1j2YAxVrY6KY62S0onpJ/4Un9KngKWvnh+TmyWEG BoJk4EvlAzHLitVlmjfvX7Bg3ErRl5MH6A1U6RSaYasj6FRVNlnujTNbzUt5LHKd VtjBrVVK+XtLT0dvPeCEf2PLurk+sHGl+4jlSe8GxpwpV4Q/6gHKFak7QKS0NMST jy/ID97Gi11fAeESCrpZ3Vcr/F70IKK0YGo0rcA2aE2lSJzhU/epMw/xE5Ox6Nuu c3MTUlEYnTJfF9FFY5j5Dr9mwUwuWb82y1ykJjn5Ip01uj8R/cLkHXclWA1CVVJa LcXnwD+yzyy0qNSIc0rV9i0v4xUyNIkRtOPvXC0JtnLHRPaSWNfd1lRt8I8DvpJf dz5DP4Nx8L3LfJcYlQY3hJeHI+bPEPdX0P8IqhDSpOVpqhbEwojiW4H68sdBLk9S L1sk513bVOvBOeC0YeO1jXrMGfBFBCVUhXvjZaQRW2xkqxf4eSN6FArpuTT3woJr DKjlT+VwDV2713W6NRR04JhuzMRRBYiKWFWqNIJOlNpfrIEJosetPvm/TH6rnAb5 z6JpCd8XfcXhxgoTsoB7944DUIgWZ5lZGtJzxgwc/qUxFgJewp01X6v7d9wvOvwF aYpNXKUUBoijZtQW6Rpvgz7HSxVahbilVxPFRDWtsFS/Gh+1HRY= =jNV3 -----END PGP SIGNATURE----- N��r��y隊Z)z{.��ZrF��x>�{.n�+��Ǩ��r��i�m��0��ޙ��$j��0��Ǩ�

2 3

[opensuse-packaging] How to start systemd service after package install?
by Matwey V. Kornilov 12 Feb '19

12 Feb '19

Hello, I have the following gap in my knowledge. I have erlang-epmd package with the following %postin script %service_add_post epmd.service epmd.socket You may check that epmd.socket is enabled in /usr/lib/systemd/system-preset/90-default-openSUSE.preset However, unit epmd.socket is in enabled but inactive state just after the package installation. I am not sure, but I remember that many years ago I already had checked this case and it seems that the socket was enabled and active at that time. What is the recommended way to start the socket unit just after installation? I see that cups.socket is also inactive just after cups installation, but erlang really relies on epmd.socket running. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 23

Re: [opensuse-packaging] Re: How to start systemd service after package install?
by aplanas＠suse.de 12 Feb '19

12 Feb '19

On Tuesday, February 12, 2019 11:57:41 AM CET Matwey V. Kornilov wrote: > 12.02.2019 12:32, aplanas(a)suse.de пишет: > 1. User may not expect that the package contains some services. > epmd.socket is internal erlang thing. Uhmm very true. But in this case there is a second service, rabbitmq.service, that is using 'BindsTo' and 'After' over epmd [1]. So when the user start the rabbitmq service, is also staring the hidden one. Or I am missing something? > 2. epmd.socket is listening on 127.0.0.1 by default. Though currently it > leads to constant complaining, this was required by security team at the > time when epmd.socket was introduced. It is minimal working local > configuration and it should be fine until you really need distribution > setup. You are right. > 3. erlang has its own default hard-coded way to start epmd. It just > execs new epmd process every time when it cannot connect to existing > one. So, while epmd.socket is not active, any erl command invocation > leads to starting new epmd process that listens on 0.0.0.0. Is it more > secure? Oh oh I see. I remember this issue. Is there any configuration file for epmd? Or the only way to avoid this second issue is via ERL_EPMD_ADDRESS env var? -- [1] https://build.opensuse.org/package/view_file/network:messaging:amqp/ rabbitmq-server/rabbitmq-server.service?expand=1 -- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0