May 2020 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] How to handle -doc packages?
by Ludwig Nussel 13 Jul '20

13 Jul '20

Hi, Some packages split out their man pages or other documentation into a sub package. More often than not that subpackage then is recommended. IOW installed by default which is undesirable. We also have a pattern for documenation though. So IMO it makes sense to link installing such documenation packages to the pattern. The question is how though. Assuming we have foo, foo-doc and patterns-base-documentation I see several ways: 1. pattern is in charge a. in patterns-base-documentation Recommends: foo-doc b. in patterns-base-documentation Recommends: foo-doc if foo 2. package is in charge a. in foo Recommends: foo-doc if patterns-base-documentation b. in foo-doc Supplements: packageand(foo:patterns-base-documentation) 1) pro: when looking at the pattern eg. in YaST one can actually see an overview of what documentation is available. con: pattern needs to be adjusted for every change in packaging. Extra step and easy to forget. 2) pro: packager can add, split, merge or drop packages any time con: package installation is a bit more black magic. The pattern leads to pulling in more packages than expected. Thoughts? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 27

[opensuse-packaging] Compiler Cache (Ccache) support in Open Build Service
by Sumit Jamgade 18 Jun '20

18 Jun '20

Hello, Long running compilation can now leverage ccache[1] to speed up the build process. This feature can be enabled per package in the project config: BuildFlags: useccahe:<packagename> example: https://build.opensuse.org/projects/home:sjamgade:branches:science:machinel… Once enabled per package, it will be enabled for all architectures and repositories. https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.prjconfig.… (grep ccache) --- The ccache tar file is collected only on *successful builds with changed result*. It is extracted for every build at /.ccache/ if enabled. This build artifact is not versioned and only the latest tar is stored. It can be downloaded from the webui or osc. https://build.opensuse.org/package/binaries/home:sjamgade:branches:science:… osc getbinaries --ccache -M standard home:sjamgade:branches:science:machinelearning tensorflow openSUSE_Tumbleweed x86_64 _ccache.tar osc getbinaries --ccache $prj $pkg $repo $arch _ccache.tar This archive can be further used for local builds too. osc build --pkg-ccache /full/path/to/_ccache.tar (please use the latest osc) --- Ccache config file is stored in /.ccache/ccache.conf and is writable by the build user. So, it could also be disabled (or configured as per package requirements) echo "disable = true" >> /.ccache/ccache.conf For possible build time comparisons: https://build.opensuse.org/packages/tensorflow:standard/job_history/home:sj… Thank you, Sumit Jamgade and OBS Team [1] - https://ccache.dev/ PS: Some packages (eg: tensorflow) need extra plumbing in spec file to enable access to /.ccache and use of ccache cmd: export CC_PREFIX=ccache; ln -s /.ccache/ ~/.ccache -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 8

[opensuse-packaging] Is there a way to wipe old packages from a repo?
by Mathias Homann 31 May '20

31 May '20

Hi, it seems that there is "old junk" in the repo for my home project, i.e. rpm packages for stuff that I don't build in my home anymore, and that I don't even **have** there anymore. How can I get rid of the rpm packages? Cheers Mathias -- Mathias Homann Mathias.Homann(a)openSUSE.org OBS: lemmy04 Jabber (XMPP): lemmy(a)tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- 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] Need help check on Veyon package before submiiting to openSUSE security team.
by andythe_great 30 May '20

30 May '20

Hello, I build Veyon package with help form malcolmlewis. https://build.opensuse.org/package/show/home:andythe_great:branches:home:lr… The RPMLINT error show E: polkit-untracked-privilege which it suggest to ask security team about it. I just want to make sure the spec file is correct before submitting to them. Some thing I am not sure is Requires(post): permissions, should I use Requires(post) or Prereq: permissions? I could not fix position-independent-executable-suggested warning even if I add -fPIE flag to it. Kind Regards, Andy -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

Re: [opensuse-packaging] What's happened with shared-mime-info? SOLVED
by Dave Plater 20 May '20

20 May '20

On 5/19/20, Ben Greiner <code(a)bnavigator.de> wrote: > Hi, > > > Fixed in https://build.opensuse.org/request/show/807255 > > > Am 19.05.20 um 12:40 schrieb Dave Plater: >> >> >> On 18/05/2020 17:23, Stefan Brüns wrote: >>> >>> Claiming ownership of a file below e.g./usr/share/mime/audio/ is >>> wrong, as >>> the mime type may be registered from several packages. > > > -%attr(0644,root,root) %ghost %{_datadir}/mime/audio/x-bzt.xml > -%attr(0644,root,root) %ghost %{_datadir}/mime/audio/x-bzt-xml.xml This is the developers mime creation but I see that it occurs when update-mime-database is run so should be removed. > > >> Just to make this clear, the package buzztrax which BuildRequires >> shared-mime-info which owns - /usr/share/mime/audio now fails because >> shared-mime-info no longer has ownership of this directory: >> [ 387s] buzztrax-0.10.2+git20191209-100.16.x86_64.rpm: directories >> not owned by a package: >> [ 387s] - /usr/share/mime/audio >> >> I'm surprised that such a major change in the package shared-mime-info >> wasn't documented. >> >> Thanks >> Dave P >> > > These RPMlint warnings probably need to be addressed too: > > > buzztrax-plugins.x86_64: W: desktopfile-without-binary > /usr/share/applications/buzztrax-songio-buzz.desktop buzztrax-edit > the .desktop file is for a file not present in the package. You should > check > the requires or see if this is not a error This is the package's developer's addition. > > buzztrax-plugins.x86_64: W: empty-%post > buzztrax.x86_64: W: empty-%post > buzztrax-plugins.x86_64: W: empty-%postun This is fixed, all of those macros have been null placeholders for a while now but I was wary of removing something that wasn't broken, maybe obs service should do it on checkin.. > > > > Regards, > Ben > I've found the answer to my question. The autotools version of the shared-mime-info runs update-mime-database at the end of make install, the meson version doesn't but the package does during installation. This is why, although the package creates them, they aren't owned by shared-mime-info anymore. Running update-mime-database shouldn't be run during make install, it should be run during rpm installation. Regards Dave P -- 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] What's happened with shared-mime-info?
by Dave Plater 19 May '20

19 May '20

Hi, package openSUSE:Factory/buzztrax started to fail to build around 9 May due to a shared-mime-info directory no longer existing, in fact none of the files under /usr/share/mime/application exist anymore and the directories under /usr/share/mime/ such as audio don't exist anymore. I searched the changes file and the packages NEWS file but can't find any information about this change, is this possibly as a result of the switch to meson build? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 7

[opensuse-packaging] Is OBS suspended for build?
by Konstantin Voinov 17 May '20

17 May '20

Hi, Yesterday I've found that all my projects don't starts building. Not on "rebuild trigger" or any other command. But there wasn't any announce about OBS maintenance . -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 3

Re: [opensuse-packaging] Re: Is OBS suspended for build?
by İsmail Dönmez 17 May '20

17 May '20

Hi, On 17 May 07:16 2020, Mathias Homann wrote: > > Am 17.05.2020 um 05:20 schrieb Malcolm: > > On Sun 17 May 2020 09:49:14 AM CDT, Konstantin Voinov wrote: > > > >> Hi, > >> > >> Yesterday I've found that all my projects don't starts building. Not > >> on "rebuild trigger" or any other command. > >> But there wasn't any announce about OBS maintenance . > > Hi > > backend-home is broken for i586 and x86_64 builds, likely will get > > sorted after the weekend... > > https://build.opensuse.org/monitor > > > Is it normal to take several hours for them to start back up? A cold start is very slow, but luckily they are back up now. - ismail -- Hard work pays off in the future, but laziness pays off right now. SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)

1 0

Re: [opensuse-packaging] Re: Is OBS suspended for build?
by İsmail Dönmez 17 May '20

17 May '20

Hi On 17 May 03:20 2020, Malcolm wrote: > On Sun 17 May 2020 09:49:14 AM CDT, Konstantin Voinov wrote: > > >Hi, > > > >Yesterday I've found that all my projects don't starts building. Not > >on "rebuild trigger" or any other command. > >But there wasn't any announce about OBS maintenance . > Hi > backend-home is broken for i586 and x86_64 builds, likely will get > sorted after the weekend... > https://build.opensuse.org/monitor Thank you for the heads up, I restarted the schedulers on back-home and they are in cold start. It'll take some time until they start processing again. I'll keep an eye on it during the day. Regards, ismail -- Hard work pays off in the future, but laziness pays off right now. SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)

1 0

[opensuse-packaging] Trying to package pi-hole for arm boards
by Paul Gonin 13 May '20

13 May '20

Hi ! I started a new project to build pi-hole packages for arm boards (armv7l & aarch64) I found packages built in a personal space, but those are only available for x86 (and i586) https://build.opensuse.org/package/show/home:Smar:pi-hole/pi-hole So I branched it and enabled armv7l & aarch64 https://build.opensuse.org/project/show/home:paulgonin:branches:home:Smar:p… I am puzzled by the results. The builds succeeded on some cases tumbleweed armv7l & aarch64 as well as SLE15SP1 aarch64... but failed on Leap15.1 armv7l & aarch64 and SLES15SP1 armv7l Apparently some packages are 'unresolvable'. (nothing provides sususer-tools, rpm-build & gcc-PIE). I checked from a rpi2 with Leap15.1 and those packages are available (with zypper se) Any guidance from a more experienced packager / open build service on how to move forward and resolve that situation ? thanks ! Paul -- 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] pkgconfig(libfprint-2) not found
by Axel Braun 12 May '20

12 May '20

Hi, I'm building a package for TW against libfprint-2: libfprint-devel-1.90.1-61.1.x86_64.rpm provides pkgconfig(libfprint-2) = 1.90.1 but this is not found (although it is in TW standard) Any idea why? Affected package: https://build-test-1.opensuse.org/package/show/ home:DocB:branches:home:DocB:branches:hardware/fingerprint-gui (removing pkgconfig(libfprint-2) in favour of libfprint-devel fixes the issue, but I would be interested why it is not found.....) Cheers Axel -- 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] Build failure for scilab: unbound module Num [ocaml]
by Atri Bhattacharya 12 May '20

12 May '20

Hi, Scilab has been failing to build for Factory [1] with an error that I have not been able to understand or fix (perhaps because of my lack of expertise with ocaml). I would appreciate any help fixing this. I shall file a drop request from Factory in a couple of weeks if we cannot get it building. I have filed a bug upstream too [2]. Here is the relevant portion of the build log: [ 152s] /usr/bin/time ocamlopt -o modelicac -I ./src/modelica_compiler -I ./src/xml2modelica -I /usr/lib64/ocaml/num num.cmxa ./src/modelica_compiler/parseTree.ml ./src/modelica_compiler/linenum.ml ./src/modelica_compiler/parser.ml ./src/modelica_compiler/lexer.ml ./src/modelica_compiler/precompilation.ml ./src/modelica_compiler/compilation.ml ./src/modelica_compiler/instantiation.ml ./src/modelica_compiler/graphNodeSet.ml ./src/modelica_compiler/symbolicExpression.ml ./src/modelica_compiler/squareSparseMatrix.ml ./src/modelica_compiler/bipartiteGraph.ml ./src/modelica_compiler/hungarianMethod.ml ./src/modelica_compiler/causalityGraph.ml ./src/modelica_compiler/optimization.ml ./src/modelica_compiler/xMLCodeGeneration.ml ./src/modelica_compiler/optimizingCompiler.ml ./src/modelica_compiler/scicosCodeGeneration.ml ./src/modelica_compiler/scicosOptimizingCompiler.ml [ 153s] File "./src/modelica_compiler/symbolicExpression.ml", line 23, characters 5-8: [ 153s] 23 | open Num [ 153s] ^^^ [ 153s] Error: Unbound module Num [ 153s] Command exited with non-zero status 2 Thanks and best wishes. [1] <https://build.opensuse.org/package/live_build_log/science/scilab/openSUSE_T…> [2] <http://bugzilla.scilab.org/show_bug.cgi?id=16429> -- Atri Bhattacharya Tue 12 May 00:22:31 CEST 2020 Sent from openSUSE Tumbleweed on my laptop. -- 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] OBS will switch authentification system tomorrow!
by Adrian Schröter 11 May '20

11 May '20

Tomorrow, 12th May 05:00 UTC we will switch OBS (build.opensuse.org and api.opensuse.org) to the new (SUSE hosted) authentification system. Please find details how to set your new password and about the current state here: https://idp-portal-info.suse.com/ For the brave ones only ======================= You can already set your future password and use OBS via the test frontends. It is still the same instance behind and the same content. Use https://build-test-1.opensuse.org or https://api-test-1.opensuse.org for osc if you want to do the switch right now. -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, 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

[opensuse-packaging] unresolvable, but binaries have been built?
by Detlef Steuer 11 May '20

11 May '20

Hi! I'm in the process to bring all of CRAN (cran.r-projet.org) into OBS. On Saturday night I started a mass upload of packages that had been built successfully on my local machine. The test repository is home:dsteuer:AutomaticCRAN Now, a few thousand packages later nearly all packages are in state unresolvable. A lot because they refer to other unresolvables. That part is easy to understand. But there are many, many packages, i.e. R-abnormality, which say "unresolvable" but have binaries available, obviously built after upload. Furthermore they refer to things not mentioned in the spec file. In this case: "have choice for perl(XML::Twig) needed by perl-Net-DBus: R-gdata perl-XML-Twig" Neither perl(XML::Twig) nor R-gdata are needed for R-abnormality. Probably I'm missing something simple. And for future attempte: If I do a local osc build and that works just fine, is it wrong to simply assume it will work on the server? All in all there will be 16000 packages uploaded in the end, I hope. Regards Detlef -- 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] factory_auto declines package with commented out patch
by Atri Bhattacharya 08 May '20

08 May '20

Hi, It seems factory_auto declines packages where a patch needing to be rebased is commented out from the sources entirely, yet this is the only way to avoid applying the patch when using `%autosetup`. See, for example, sr#773323 which has Patch12 marked as 'NEEDS-REBASE' and commented out. It has been duly declined. Is there any way, short of doing away with `%autosetup`, to get this through factory_auto? Thanks for any advice. [1] https://build.opensuse.org/request/show/773323 -- Atri Bhattacharya Sent from openSUSE Tumbleweed 20200214 on tp-yoga260. -- 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] Build failures when building VTK 9.0 with mpi support
by Atri Bhattacharya 07 May '20

07 May '20

Hi, I am trying to get VTK updated to version 9.0 released a couple of days ago, and I mostly have it [1]. However, I have not been able to get the MPI-supported flavours to build due to a linking error that looks like this: ``` [ 1199s] [ 93%] Linking CXX shared library ../../lib64/java/vtk-Linux-x86_64/libvtkFiltersParallelGeometryJava.so [ 1199s] cd /home/abuild/rpmbuild/BUILD/VTK-9.0.0/build/Wrapping/Java && /usr/bin/cmake -E cmake_link_script CMakeFiles/vtkFiltersParallelGeometryJava.dir/link.txt --verbose =1 [ 1199s] /usr/lib64/mpi/gcc/openmpi2/bin/mpicxx -fPIC -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-prote ction -Werror=return-type -flto=auto -ffat-lto-objects -DNDEBUG -O2 -g -DNDEBUG -Wl,-lc -flto=auto -ffat-lto-objects -Wl,--as-needed -Wl,--no-undefined -Wl,-z,now -shared -Wl,-soname,libvtkFiltersParallelGeometryJava.so -o ../../lib64/java/vtk-Linux-x86_64/libvtkFiltersParallelGeometryJava.so CMakeFiles/vtkFiltersParallelGeometryJava.dir/CMa keFiles/vtkFiltersParallelGeometryJava/vtkPConnectivityFilterJava.cxx.o CMakeFiles/vtkFiltersParallelGeometryJava.dir/CMakeFiles/vtkFiltersParallelGeometryJava/vtkPDataSetGh ostGeneratorJava.cxx.o CMakeFiles/vtkFiltersParallelGeometryJava.dir/CMakeFiles/vtkFiltersParallelGeometryJava/vtkPDistributedDataFilterJava.cxx.o CMakeFiles/vtkFiltersParal lelGeometryJava.dir/CMakeFiles/vtkFiltersParallelGeometryJava/vtkPStructuredGridConnectivityJava.cxx.o CMakeFiles/vtkFiltersParallelGeometryJava.dir/CMakeFiles/vtkFiltersPar allelGeometryJava/vtkPStructuredGridGhostDataGeneratorJava.cxx.o CMakeFiles/vtkFiltersParallelGeometryJava.dir/CMakeFiles/vtkFiltersParallelGeometryJava/vtkPUniformGridGhost DataGeneratorJava.cxx.o CMakeFiles/vtkFiltersParallelGeometryJava.dir/CMakeFiles/vtkFiltersParallelGeometryJava/vtkPUnstructuredGridGhostCellsGeneratorJava.cxx.o CMakeFiles/ vtkFiltersParallelGeometryJava.dir/CMakeFiles/vtkFiltersParallelGeometryJava/vtkFiltersParallelGeometryModuleJava.cxx.o -Wl,-rpath,"\$ORIGIN/../../:\$ORIGIN:/usr/lib64/jvm/ java/lib:/usr/lib64/jvm/java/lib/server" ../../lib64/libvtkFiltersParallelGeometry.so.9.0.0 ../../lib64/java/vtk-Linux-x86_64/libvtkCommonSystemJava.so ../../lib64/java/vtk- Linux-x86_64/libvtkFiltersParallelJava.so ../../lib64/java/vtk-Linux-x86_64/libvtkParallelMPIJava.so ../../lib64/libvtkFiltersParallel.so.9.0.0 ../../lib64/libvtkFiltersExtr action.so.9.0.0 ../../lib64/java/vtk-Linux-x86_64/libvtkFiltersGeometryJava.so ../../lib64/libvtkFiltersHybrid.so.9.0.0 ../../lib64/libvtkFiltersGeometry.so.9.0.0 ../../lib6 4/libvtkFiltersModeling.so.9.0.0 ../../lib64/libvtkFiltersSources.so.9.0.0 ../../lib64/java/vtk-Linux-x86_64/libvtkCommonExecutionModelJava.so ../../lib64/libvtkFiltersTextu re.so.9.0.0 ../../lib64/libvtkFiltersGeneral.so.9.0.0 ../../lib64/libvtkFiltersCore.so.9.0.0 ../../lib64/libvtkParallelMPI.so.9.0.0 ../../lib64/java/vtk-Linux-x86_64/libvtkC ommonCoreJava.so ../../lib64/libvtkJava.so.9.0.0 /usr/lib64/jvm/java/lib/libjawt.so /usr/lib64/jvm/java/lib/server/libjvm.so ../../lib64/libvtkParallelCore.so.9.0.0 ../../li b64/libvtkCommonExecutionModel.so.9.0.0 ../../lib64/libvtkCommonDataModel.so.9.0.0 ../../lib64/libvtkCommonSystem.so.9.0.0 ../../lib64/libvtkCommonTransforms.so.9.0.0 ../../ lib64/libvtkCommonMisc.so.9.0.0 ../../lib64/libvtkCommonMath.so.9.0.0 ../../lib64/libvtkCommonCore.so.9.0.0 ../../lib64/libvtksys.so.9.0.0 -ldl -Wl,-rpath-link,/home/abuild/ rpmbuild/BUILD/VTK-9.0.0/build/lib64/java/vtk-Linux-x86_64:/home/abuild/rpmbuild/BUILD/VTK-9.0.0/build/lib64 [ 1199s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/libvtkFiltersParallelGeometryJava.so.ou8EgG.ltrans0.ltrans.o: in function `vtkPConnect ivityFilter_Typecast': [ 1199s] /home/abuild/rpmbuild/BUILD/VTK-9.0.0/build/Wrapping/Java/CMakeFiles/vtkFiltersParallelGeometryJava/vtkPConnectivityFilterJava.cxx:18: undefined reference to `vtkCo nnectivityFilter_Typecast' [ 1199s] collect2: error: ld returned 1 exit status [ 1199s] make[2]: *** [Wrapping/Java/CMakeFiles/vtkFiltersParallelGeometryJava.dir/build.make:297: lib64/java/vtk-Linux-x86_64/libvtkFiltersParallelGeometryJava.so] Error 1 [ 1199s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/VTK-9.0.0/build' [ 1199s] make[1]: *** [CMakeFiles/Makefile2:21809: Wrapping/Java/CMakeFiles/vtkFiltersParallelGeometryJava.dir/all] Error 2 [ 1199s] make[1]: *** Waiting for unfinished jobs.... ``` The serial flavour -- without mpi support -- builds just fine, which leads me to believe the issue may be some env variable or path that is not exported when the MPI prefixes and paths are redefined. But, I don't know for sure. Any pointers to help sort this out will be highly appreciated. I have also tried to elicit a comment or suggestion from upstream [2]. Thanks in advance for any help. [1] <https://build.opensuse.org/package/show/home:badshah400:branches:science/vtk> [2] <https://discourse.vtk.org/t/building-vtk-9-0-fails-when-using-mpi-support/3…> -- Atri Bhattacharya Wed 6 May 20:09:12 CEST 2020 Sent from openSUSE Tumbleweed on my laptop. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 1

Re: [opensuse-packaging] problems with -lto-auto in R-RcppParallel
by Richard Biener 06 May '20

06 May '20

On Wed, 6 May 2020, Martin Liška wrote: > On 5/6/20 8:45 AM, Richard Biener wrote: > > I think it should check $(MAKE) actually points to an executable ... > > (or simply somehow try and then fall back to 'make'). It could > > be MAKE = echo as well if the project is not using make after all. > > Hi. > > Note that the code is there for 10 years :) I wouldn't check if > $(MAKE) is executable, but checking of an option in the env variable > seems to me reasonable. > > What about: > > $ MAKE="make -s" gcc main.o -flto=16 > lto-wrapper: fatal error: an option found in ‘MAKE’ environment variable: > ‘make -s’, use ‘MAKEFLAGS’ instead > compilation terminated. > /usr/bin/ld: error: lto-wrapper failed > collect2: error: ld returned 1 exit status > > ? Well ... if we do not find a jobserver then we clear MAKEFLAGS, so that seems like a bad suggestion? So in that light Michas suggestion seems to be better (hopefully there's some utility for proper splitting in libiberty, buildargv looks close). Richard. > Martin > > -- Richard Biener <rguenther(a)suse.de> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)

1 0

[opensuse-packaging] problems with -lto-auto in R-RcppParallel
by Detlef Steuer 06 May '20

06 May '20

Hi! This package: https://build.opensuse.org/package/show/devel:languages:R:released/R-RcppPa… does not compile in OBS OpenSUSE. It works for Fedora, debian etc. The only possible problem we could find, was the usage of -flto-auto for the included tbb library. Upstream is https://github.com/RcppCore/RcppParallel, an issue was filed some time ago, but upstream has no idea either. Thankful for any idea, because some very interesting R-packages depend on RcppParallel, that I would like to add to OBS. Regards Detlef -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

Re: [opensuse-packaging] packaging qt5 Application
by Axel Braun 05 May '20

05 May '20

Hi Dmitriy, Am Donnerstag, 30. April 2020, 19:42:45 CEST schrieb Dmitriy Perlow: > Hello. Seems that cmake(PolkitQt5-1) is it. Thank you! With some other hints I ended up in a compilation error [ 74s] g++ -c -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fno- strict-aliasing -O2 -D_REENTRANT -Wall -Wextra -fPIC -DLIBEXECDIR=\"/usr/lib/ fingerprint-gui\" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB - DQT_CORE_LIB -I. -I. -I../../include -I../../upek/include -isystem /usr/ include/qt5/Qca-qt5/QtCrypto -isystem /usr/include/qt5 -isystem /usr/include/ qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtXml -isystem /usr/include/qt5/QtCore -I. -I. -I/usr/lib64/qt5/mkspecs/linux-g++ -o GlobalsImg.o ../../src/GlobalsImg.cpp [ 78s] In file included from /usr/include/qt5/QtCore/qobject.h:46, [ 78s] from /usr/include/qt5/QtCore/qabstractanimation.h: 43, [ 78s] from /usr/include/qt5/QtCore/QtCore:6, [ 78s] from /usr/include/qt5/QtWidgets/QtWidgetsDepends:3, [ 78s] from /usr/include/qt5/QtWidgets/QtWidgets:3, [ 78s] from ../../src/GlobalsImg.cpp:1: [ 78s] /usr/include/glib-2.0/gio/gdbusintrospection.h:155:25: error: expected unqualified-id before 'public' [ 78s] 155 | GDBusSignalInfo **signals; [ 78s] | ^~~~~~~ [ 78s] make[2]: *** [Makefile:737: GlobalsImg.o] Error 1 ....which shows that the issues is somewhere deep down in the engine room. Having reported this upstream, https://github.com/Tilka/fingerprint-gui, the author has archived the project after the report :-( There are some more forks on github, will check if one or another is still developed Cheers Axel -- 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] update package with git revision
by Jason Craig 04 May '20

04 May '20

I'm trying to update the python-ZODB[1] package so that it will build and doesn't get dropped from e.g. Leap 15.2. The basic problem is that a test (or possibly multiple tests) started failing with the latest version of python-transaction. This problem is fixed upstream but there hasn't been a new version of ZODB released with the fix in it. So I'm using a git revision as the source for the package, but this raises the question of what to do with the version number of the package. Reading some documentation[2], it would appear I should use a version like "5.5.1+git56", but this causes RPM to not find the egg-info directory in %files because the version specified in setup.py is "5.6.0.dev0". So should I a) use version 5.5.1+git56, change the %files section so it picks up the egg-info directory or b) use version 5.6.0.dev0, but then when 5.6.0 is released upstream wouldn't RPM think that 5.6.0.dev0 is still the newer version? c) do something else. Also, the GitHub tarball unzips into a directory named with the commit SHA. Is there a best practice for how to handle this with %setup -n? Just change it manually and change it back to use the package's version later? Should I %define something with the revision and use that macro? thanks, -- Jason Craig [1] https://build.opensuse.org/package/show/home:poorboywilly:branches:devel:la… [2] https://en.opensuse.org/openSUSE:Package_naming_guidelines#SCM_snapshots -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 6

[opensuse-packaging] Fwd: Prep'ing python-volatiliity replacement package volatility3 for factory submission. Can someone please review the license and the Obsoletes/Provides statements
by Greg Freemyer 04 May '20

04 May '20

All, I'm prepping https://build.opensuse.org/package/show/security:forensics/volatility3 for submission to factory, but: - I'm not sure which license to use. I've copied the contents of the LICENSE.txt file below my signature (see below) - Because this is a replacement package I'm obsoleting python-volatility (python2 only), but the fact the version number for this is lower than it was for python-volatility leaves me in doubt if I did it right. I would normally say: Obsoletes: python-volatility <= 2.6.1 But because the version number for the new package is less than 2.6.1 that is causing [ 18s] volatility3.noarch: W: self-obsoletion python-volatility <= 2.6.1 obsoletes python-volatility = 1.0.0+beta.1 [ 18s] volatility3.noarch: W: self-obsoletion volatility <= 2.4 obsoletes volatility = 1.0.0+beta.1 [ 18s] The package obsoletes itself. This is known to cause errors in various tools [ 18s] and should thus be avoided, usually by using appropriately versioned Obsoletes [ 18s] and/or Provides and avoiding unversioned ones. So, I'm just using = in the spec file currently. Obsoletes: python-volatility = 2.6.1 - I carried over the *.changes file. Not sure that should happen, or if I should start from a clean changes file. Advice appreciated, Thanks Greg -- Greg Freemyer Advances are made by answering questions. Discoveries are made by questioning answers. — Bernard Haisch =============== contents of LICENSE.txt file ================== Volatility Software License Version 1.0 dated October 3, 2019. This license covers the Volatility software, Copyright 2019 Volatility Foundation. Software The software referred to in this license includes the software named above, and any data (such as operating system profiles or configuration information), and documentation provided with the software. Purpose This license gives you permission to use, share, and build with this software for free, but requires you to share source code for changes, additions, and software that you build with it. Acceptance In order to receive this license, you must agree to its rules. The rules of this license are both obligations under that agreement and conditions to your license. You must not do anything with this software that triggers a rule that you cannot or will not follow. Copyright Each contributor licenses you to do everything with this software that would otherwise infringe that contributor's copyright in it. Notices You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to https://www.volatilityfoundation.org/license/vsl-v1.0. You must not remove any copyright notice in the Software. Patent Each contributor licenses you to do everything with this software that would otherwise infringe any patent claims they can license or become able to license. Reliability No contributor can revoke this license. Copyleft If you make any Additions available to others, such as by providing copies of them or providing access to them over the Internet, you must make them publicly available, according to this paragraph. "Additions" includes changes or additions to the software, and any conte nt or materials, including any training materials, you create that contain any portion of the software. "Additions" also includes any translations or ports of the software. "Additions" also includes any software designed to execute the software and parse its results, suc h as a wrapper written for the software, but does not include shell or execution menu software designed to execute software generally. When this license requires you to make Additions available: - You must publish all source code for software under this license, in the preferred form for making changes, through a freely accessible distribution system widely used for similar source code, so the developer and others can find and copy it. - You must publish all data or content under this license, in a format customarily used to make changes to it, through a freely accessible distribution system, so the developer and others can find and copy it. - You are responsible to ensure you have rights in Additions necessary to comply with this section. Contributing If you contribute (or offer to contribute) any materials to Volatility Foundation for the software, such as by submitting a pull request to the repository for the software or related content run by Volatility Foundation, you agree to contribute them under the under the B SD 2-Clause Plus Patent License (in the case of software) or the Creative Commons Zero Public Domain Dedication (in the case of content), unless you clearly mark them "Not a Contribution." Trademarks This license grants you no rights to any trademarks or service marks. Termination If you violate any term of this license, your license ends immediately. No Liability As far as the law allows, the software comes as is, without any warranty or condition, and no contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim. Versions Volatility Foundation is the steward of this license and may publish new versions of this license with new version numbers. You may use the software under the version of this license under which you received the software, or, at your choice, any later version. -- 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] Need help understanding E: lto-no-text-in-archive RPMLINT error.
by andythe_great 02 May '20

02 May '20

Hello, I have been trying to build Avogadrolibs https://github.com/OpenChemistry/avogadrolibs https://build.opensuse.org/package/live_build_log/home:andythe_great/avogad… However, this error prevent it from building. E: lto-no-text-in-archive (Badness: 10000) I found this documentation: https://en.opensuse.org/openSUSE:LTO#LTO_enablement_in_openSUSE:Factory Which it says to add the flag %global _lto_cflags %{?_lto_cflags} -ffat-lto-objects to fix the issue which it did. But Science repo maintainer won't accept it as a fix. https://build.opensuse.org/request/show/780593 So I ask in openSUSE forum, which was told that it got something to do with reproducibility. https://forums.opensuse.org/showthread.php/539911-How-to-detect-GCC-using-C… I decide to ask the Avogadro dev to fix the issue but neither me, openSUSE forum admin or Avogadro dev understand why should it be done. https://github.com/OpenChemistry/avogadrolibs/issues/455 Which the issue remain unsolved, so I would like to know what E: lto-no-text-in-archive means so I can tell the Avogadro dev why they should fix it and why it is exclusive to openSUSE. Thanks Andy -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5