March 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Selecting GCC version
by Matthias Fehring 03 Apr '18

03 Apr '18

Hello, is there a simple way to force the GCC version used to build a package? openSUSE Leap 42.2 for example uses GCC 4.8 as default compiler, but also provides packages for GCC 5.3. Simply using BuildRequires gcc5 pulls gcc5 in but still uses gcc48 to build the package (especially in Build Service). So is there maybe some Buid Service or spec file switch (bcond) to select the used GCC version? Best greetings Matthias Fehring P.S. Not sure if it is a problem with my browser settings, but when I try to search lists.opensuse.org, it is not possible for me to limit the results to a specific list. Even if I set one, I get results from all lists, what makes searching almost impossible, because most results are commit messages. -- Das Gesetz hat zum Schneckengang verdorben, was Adlerflug geworden wäre. (Friedrich Schiller - Die Räuber) www.buschmann23.de GPG-Key: 0x614C3258 GPG Fingerprint: D786 DDF8 4CA9 00BC CDE0 9A5F CCC5 125D 6E87 D4FC

6 13

[opensuse-packaging] release-notes-openSUSE requires google-opensans-fonts
by Felix Miata 23 Apr '17

23 Apr '17

TW $SUBJECT can't be right, but trying to zypper rm opensans wants to remove releasenotes. :-( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 8

[opensuse-packaging] devel:language:python Factory/Tumbleweed build target changes
by Todd Rme 17 Apr '17

17 Apr '17

I have just implemented some changes for the various factory targets of devel:languages:python. Most importantly, the openSUSE_Factory_ARM, openSUSE_Factory_PowerPC, and openSUSE_Factory_zSystems build targets have been rolled into the openSUSE_Tumbleweed build target. They are now architectures of openSUSE_Tumbleweed rather than stand-alone repositories. The existing repositories are still there. Assuming there are no problems they will be disabled on in 2 days (Sunday, April 2) and will be deleted in one week (Friday, April 7 2017). Second, the opensuse_factory_staging build target has already been deleted. It was purely a testing repository, so nobody should have been using it to begin with. Thank you, Todd -- 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] Package publishing: per target or per arch?
by Todd Rme 03 Apr '17

03 Apr '17

I am a bit unclear about the rules for when build packages are pushed to repositories. I have been told that it only occurs for a given build target when all architectures for that target have finished building. However, when I look at download.opensuse.org, it seems packages are getting pushed from one architecture while another is still building according to build.opensuse.org. So I was hoping to get a better understanding of how OSC decides whether to publish a package. It is important because it has an impact on how we structure our build targets. -- 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 with gcc7 error
by Dave Plater 31 Mar '17

31 Mar '17

Hi, I've been running around in circles trying to fix multimedia:libs/libdbus-c++'s gcc7 build errors, in home:plater. I fixed one which was a type conversion error but I'm struggling with this: In file included from ../../include/dbus-c++/server.h:34:0, from ../../include/dbus-c++/dbus.h:33, from propsgs-server.h:4, from propsgs-server.cpp:1: ../../include/dbus-c++/dispatcher.h: In static member function 'static void DBus::Threading<Mx, Cv>::init()': ../../include/dbus-c++/dispatcher.h:262:5: error: no matching function for call to '_init_threading(DBus::Mutex* (&)(), void (&)(DBus::Mutex*), void (&)(DBus::Mutex*), void (&)(DBus::Mutex*), DBus::CondVar* (&)(), void (&)(DBus::CondVar*), void (&)(DBus::CondVar*, DBus::Mutex*), bool (&)(DBus::CondVar*, DBus::Mutex*, int), void (&)(DBus::CondVar*), void (&)(DBus::CondVar*))' ); ^ ../../include/dbus-c++/dispatcher.h:247:13: note: candidate: void DBus::_init_threading() void DXXAPI _init_threading(); ^~~~~~~~~~~~~~~ ../../include/dbus-c++/dispatcher.h:247:13: note: candidate expects 0 arguments, 10 provided ../../include/dbus-c++/dispatcher.h:249:13: note: candidate: void DBus::_init_threading(DBus::MutexNewFn, DBus::MutexFreeFn, DBus::MutexLockFn, DBus::MutexUnlockFn, DBus::CondVarNewFn, DBus::CondVarFreeFn, DBus::CondVarWaitFn, DBus::CondVarWaitTimeoutFn, DBus::CondVarWakeOneFn, DBus::CondVarWakeAllFn) <near match> void DXXAPI _init_threading( ^~~~~~~~~~~~~~~ propsgs-server.cpp doesn't even call DBus::_init_threading() and although searching brings nothing up, if this isn't a gcc7 bug. These problems only occur in tests and examples so I can disable them but I would really like to understand this build error. 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 20

[opensuse-packaging] -Wl,-rpath={%_libdir} has no effect when building using OBS
by Xing 31 Mar '17

31 Mar '17

Dear All, I'm trying to build and package openbabel. It needs the "RUNPATH" tag to run correctly or the "obabel" command will not find the plugin directories. Openbabel uses CMAKE and on OBS "-DCMAKE_SKIP_RPATH=ON" is set automatically by the %cmake marco. I can use "-DCMAKE_C_FLAGS="-Wl,-rpath={%_libdir}" and "-DCMAKE_CXX_FLAGS=-Wl,-rpath={%_libdir}" to force passing the flags to gcc and build with RUNPATH on my local computer directly (without using "osc build "). However it gcc will just ignore the "-Wl,-rpath" flag when I use "osc build" or the online building service and no RUNPATH information is written to the binary and .so files. Does any one know why gcc behaves differently like this (invoke directly vs via OBS) and how to insert the "RUNPATH" information into the final .rpm files? Thanks and best wishes, Xing -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 7

Re: [opensuse-packaging] Service for bitbucket
by Axel Braun 29 Mar '17

29 Mar '17

Hallo Frank, Am Montag, 27. März 2017, 14:47:37 CEST schrieb Frank Schreiner: > On Sonntag, 26. März 2017 10:48:52 CEST you wrote: > > Am Sonntag, 26. März 2017, 10:17:28 CEST schrieb Adrian Schröter: > > > On Sonntag, 26. März 2017, 09:56:06 CEST wrote Axel Braun: > > > > Morning all, > > > > > > > > does anyone know of an OBS Service to pull sources from bitbucket? > > > > I had a look at > > > > http://openbuildservice.org/help/manuals/obs-reference-guide/ > > > > cha.obs.source_service.html > > > > but there is nothing listed - overview of available sources would be > > > > great! > > > > > > It is not supported yet, but it should not be too hard to add. > > > > > > Just have a look at the tar/obs_scm service. But please look in this > > > repo > > > > > > here atm: > > > https://github.com/M0ses/obs-service-tar_scm/ > > > > Thanks Adrian, that helped a lot! > > Bitbucket talks hg, so that helps as well > > > > First test was half way successful, I could clone the source tree, but the > > service was looking for a 'hgreview': > > ... > > Command failed(255): "*** failed to import extension hgreview: No module > > named hgreview\nhg: parse error at 0: syntax error in revset '*** failed > > to > > import extension hgreview: No module named hgreview\n327'\n" > > Aborting: service call failed: /usr/lib/obs/service/tar_scm --scm hg > > --url > > https://bitbucket.org/jonaswolz/yajhfc --filename yajhfc --extension > > tar.bz > > -- outdir > > /home/docb/buildservice/home:DocB/yajhfc/tmpFeOoUT.tar_scm.service .... > > > > So is OBS Service expecting a module hgreview, or does the service need to > > import this (python) module? > > No, as far as I can see obs-service-tar_scm is only expecting a working "hg" > command installed. We are not using any hg related python libs. > > The following hg calls are executed by tar_scm > > ['hg', 'update', self.revision], > ['hg', 'clone', self.url, self.clone_dir] > ['hg', 'pull'], cwd=self.clone_dir, > ['hg', 'id', '-n'], self.clone_dir)[1] > ['hg', 'log', ...] > > for more information have a look into > > /usr/lib/obs/service/TarSCM/scm/hg.py > > For me, it looks like a broken installation of hg tools, as all of the above > commands worked well on our appliance. mercurial is installed and working. I can clone a git repositry from bitbucket, no problem when I run hg clone manually: hg clone https://bitbucket.org/jonaswolz/yajhfc *** failed to import extension hgreview: No module named hgreview So, for whatever reason my installation asks for this hgreview (funny enough, I had packed this some time ago myself) https://build.opensuse.org/package/show/devel:tools:scm/hgreview As this is now fixed, the service file works as well :-) Now I need to find out how to get the version number (0.6.1) into the filename - currently it seems to set the revision (327) 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] directories not owned by a package:
by Christian 29 Mar '17

29 Mar '17

Hi, don't think it is a good idea to have several packages owning 'same' directory, isn't it ? ovhpc-01:/usr/lib/tmpfiles.d # rpm -q --whatprovides $(pwd) dmraid-1.0.0.rc16-34.3.x86_64 clamav-0.99.2-25.1.x86_64 amavisd-new-2.8.1-11.1.x86_64 screen-4.0.4-21.2.x86_64 lvm2-2.02.120-72.8.x86_64 dirmngr-1.1.1-10.1.x86_64 systemd-228-135.1.x86_64 which one is the correct one ? and how to fix build error: [ 26s] xyzserver-1.67-0.x86_64.rpm: directories not owned by a package: [ 26s] - /usr/lib/tmpfiles.d without using... %dir %{_prefix}/lib/tmpfiles.d ...and producing a further package providing same DIR. Cheers -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 11

[opensuse-packaging] Have you a link to the source code which builds the isos [openSUSE-xxxxx-NET-x86_64.iso]
by doiggl＠velocitynet.com.au 29 Mar '17

29 Mar '17

Hello, Have you a link to the source code which builds the iso[1] cd and links in the oss and non-oss parts to the build. It has links to /non-oss/ /oss/ Questions: - which files establish the links used in the built iso for /oss/ and /non-oss/? - Have you a link to a build log of a sucessful iso build ? Thanks --Glenn [1] e.g release for: http://ftp.gwdg.de/pub/opensuse/distribution/leap/42.2/iso/openSUSE-Leap-42… it has links for oss and non-oss in iso # other https://en.opensuse.org/Portal:Factory -- 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] Wrong naming of python-python-axolotl in the spec: python-python_axolotl (note the _)?
by Johannes Kastl 28 Mar '17

28 Mar '17

Hi guys, I just stumbled upon the python-python-axolotl package in d:l:p today. I linkpac'd it and it built, but was not enough to fulfill a dependency (gajim-plugin-gajim-omemo needs the axolotl stuff). I checked the spec and found a mismatch: devel:languages:python/python-python-axolotl The package is called python-python-axolotl The spec is called python-python-axolotl.spec In the spec, the name of the package is python-python_axolotl (note the "_" instead of the "-" ). Is there any reason for that? I changed my copy to have the same name in the spec as the package, and it builds and it works. (I also updated it to 0.1.39, but that's just a side note). If desired, I can sr it to d:l:p. But maybe there should be an additional "Obsoletes python-python_axolotl" in there, to make sure the transition smooth. Johannes

2 2

[opensuse-packaging] Failure building docker-compose: have choice for python-six needed by python-setuptools: python-six python2-six
by Robert Munteanu 28 Mar '17

28 Mar '17

Hi, I am trying to understand why docker-compose [1] does not build for Factory. The error is unresolvable: have choice for python-six needed by python-setuptools: python-six python2-six I am not sure how to approach this, any hints are welcome. Is this something to set in the project config? Thanks, Robert [1]:https://build.opensuse.org/package/show/Virtualization:containers/docker… -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 5

[opensuse-packaging] Problem packaging a library
by Luigi Baldoni 28 Mar '17

28 Mar '17

Hello everyone, I'm attempting to package a library plus a few dependent executables. Said library is alas static-only, but since about twelve executables depend on it, it seemed like a waste and therefore I patched the source to build it shared. But then I got stuck. I don't think I can set a SOVERSION because there would be no guarantee of API/ABI compatibilty upwards, but its SONAME ends with a digit and rpmlint seems to be confused by this. I've read https://en.opensuse.org/openSUSE:Shared_library_packaging_policy and it doesn't seem to cover this particular case. Should I rename the library? Force a version? Ignore rpmlint's warnings or what else? Thanks -- View this message in context: http://opensuse.14.x6.nabble.com/Problem-packaging-a-library-tp5083912.html Sent from the opensuse-packaging mailing list archive at Nabble.com. -- 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] python singlespec: how to convert your package
by jan matejek 27 Mar '17

27 Mar '17

Dear packagers, this is an overview of how singlespec works and how to use it for your package. First, some key concepts: * It will allow you to build Python 2 and Python 3 (and PyPy 3 in the future) package from a single spec file, with very little manual effort. This means that if you're maintaining a separate python3-something in d:l:py3, you can now switch over to the common python-something in d:l:py. * It is designed to work on specs called "python-something". There is some support for "python2-something" and "python3-something", but it is mostly untested. If your spec file name doesn't start with "python", don't even try. (Yet.) * (if you're building for Factory,) all your dependencies must be converted first. That's because the macros will BuildRequire "python2-things", which only exist for packages that are already converted. The devel:languages:python:singlespec already has basic packages, and not all of them will be in d:l:py immediately, so if you want to play now, build against this project. I'll also be accepting SRs into it. * In general, if you're unsure, please submit to d:l:py:singlespec first. Also examine linkdiffs of packages in d:l:py:singlespec to get an idea of how it can look like. https://build.opensuse.org/project/show/devel:languages:python:singlespec * Individual macros are documented on github https://github.com/openSUSE/python-rpm-macros * I'm working on an autoconverter that performs most of the following steps automatically. I intend to use it to convert most of d:l:py into d:l:py:singlespec:staging, and then review and submit packages one by one. So maybe if you wait, you can save yourself some work ;) Conversion steps: 0. If you want to build for anything other than Factory, you need to include compatibility shims. This definition of the %python_module macro goes on top of your spec: %{?!python_module:%define python_module() python-%1 python3-%1} and a buildrequire: BuildRequires: python-rpm-macros 1. Wrap all your "BuildRequires: python-something": BuildRequires: %{python_module something} Do not do this in Requires or any other fields. If you have a buildrequire that should only apply to one python, say, python-enum34 only for python 2, do not wrap it. 2. At the end of the spec preamble, before %description, place the macro: %python_subpackages on a line by itself 3. Replace "python setup.py build" with %python_build and "python setup.py install" with %python_install. These already contain the usual arguments (--prefix, --root), so usually you don't need to add any. If you configure CFLAGS or something like that, export them first: CFLAGS="-fwrapv" python setup.py build -> export CFLAGS="-fwrapv" %python_build If you are running any other commands based on python, use %python_exec. "python setup.py test" -> "%python_exec setup.py test" This works for usual test runners too: "nosetests" -> "%python_exec %{_bindir}/nosetests" 4. If you're doing something more complicated ... say, removing files from %python2_sitelib and %python3_sitelib, use %python_expand. "%python_expand rm -f %{$python_sitelib}/foo/undesirable.txt" Yes, that is "%$python_sitelib". Beware. If you put only "%python_sitelib", it will not work, because "%python_sitelib" gets expanded before %python_expand touches it. In general, after %python_expand, "$python" is replaced by all pythons even in macro names. If you need more lines, wrap in braces: %{python_expand firstline secondline $python thirdline} Note that the first line must not be empty. 5. change "%files" to "%files %{python_files}" If you have subpackages, say "%files foo", then change to "%files %{python_files foo}". 6. If some files are only in one python version, mark them as %python2_only or %python3_only in the filelist. If there's more of them, you can use %ifpython2 ... %endif If the entry in question is a __pycache__ directory, use %pycache_only or %ifpycache. 7. If you are using update-alternatives, remove them. Instead mark the executable as %python3_only: %python3_only %{_bindir}/yourbinary In most cases, we only need one version of the executable. If the purpose of the tool is, e.g., reading EXIF metadata, we don't care if python 2 or 3 reads them. (And the library files are still installed for both.) (If you are sure that you need executables for all python versions, look at what python-bottle does: https://build.opensuse.org/package/view_file/devel:languages:python:singles… note the installation inside %python_expand. Usually, packages don't install versioned executables by themselves, so you need to do it manually. If your package does, good for you.) 8. Take the time to enable automatic tests :) have a nice weekend m.

14 52

[opensuse-packaging] invalid license only in leap 42.3
by Sebastian 27 Mar '17

27 Mar '17

Dear list, I need some help for the package hollywood, where I have this license string: "Apache-2.0 AND CC0-1.0" The package builds fine for Factory: https://build.opensuse.org/package/show/openSUSE:Factory/hollywood But not for Leap 42.3: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:42.3/hollyw… rpmlint says: [ 33s] hollywood.noarch: E: invalid-license (Badness: 100000) Apache-2.0 AND CC0-1.0 [ 33s] hollywood.src: E: invalid-license (Badness: 100000) Apache-2.0 AND CC0-1.0 [ 33s] The specified license string is not recognized. Please refer to [ 33s] https://spdx.org/licenses/ for the list of known licenses and their exact [ 33s] spelling. Does rpmlint on Leap 42.3 probably not understand the logical "AND"? The both licenses are valid according to spdx. Thanks for your help, Sebastian -- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers

3 2

[opensuse-packaging] Re: python singlespec: broken python3 packages
by Andreas Schwab 27 Mar '17

27 Mar '17

On Mär 23 2017, Mikhail Terekhov <termim(a)gmail.com> wrote: > On Thu, Mar 23, 2017 at 4:35 AM, Andreas Schwab <schwab(a)suse.de> wrote: > >> On Mär 22 2017, Mikhail Terekhov <termim(a)gmail.com> wrote: >> >> > After conversion to singlespec some python3 packages became broken, ex: >> > >> > https://build.opensuse.org/package/show/KDE:Qt5/python-sip >> > https://build.opensuse.org/package/show/KDE:Qt5/qscintilla-qt5 >> > >> > The logs in web interface say that patches to python3-* files could not >> be >> > applied. >> > Obviously the python3-* files has been deleted during conversion. >> > I've tried to branch these packages but the branches also can't be >> compiled >> > with the same errors. >> > >> > How to fix this problem? >> >> The python-qscintilla-qt5 link should not have a diff in the first >> place. Check out with "osc co -u" and remove project.diff and its >> reference in _link. >> >> > There is no project.diff or its mention in the _link file after "osc co -u" > ... Someone recreated the link in the mean time. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- 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] python singlespec : explanation about pyc pyo
by Bruno Friedmann 26 Mar '17

26 Mar '17

See [1] as reference During build with the new singlespec way I'm getting warning about python3-htmlmin.noarch: W: files-duplicate /usr/lib/python3.6/site-packages/ htmlmin/__pycache__/decorator.cpython-36.opt-1.pyc /usr/lib/python3.6/site- packages/htmlmin/__pycache__/decorator.cpython-36.pyc Why did we have now two kinds of pyc being exactly the same file ? Is there a bug in one of the python macros ? Thanks for the potential explanation. [1] https://build.opensuse.org/package/show/ home:bruno_friedmann:branches:devel:languages:python3/python3-htmlmin -- 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

1 1

[opensuse-packaging] Service for bitbucket
by Axel Braun 26 Mar '17

26 Mar '17

Morning all, does anyone know of an OBS Service to pull sources from bitbucket? I had a look at http://openbuildservice.org/help/manuals/obs-reference-guide/ cha.obs.source_service.html but there is nothing listed - overview of available sources would be great! 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] XML/Parser/Expat.pm installed in BR but not found
by Sascha Manns 25 Mar '17

25 Mar '17

Hello list, i haved installed perl(XML::Parser) in my Buildroot: [ 42s] perl-XML-Parser-2.44-1.105 ################### But while the build process i'm getting: [ 77s] + /usr/bin/perl -CDAS -I /home/abuild/rpmbuild/BUILD/Publican- v4.3.2/blib/lib /home/abuild/rpmbuild/BUILD/Publican- v4.3.2/blib/script/publican build --formats=html-desktop --publish -- langs=en-US --common_config=/home/abuild/rpmbuild/BUILD/Publican- v4.3.2/blib/datadir -- common_content=/home/abuild/rpmbuild/BUILD/Publican- v4.3.2/blib/datadir/Common_Content --nocolours [ 78s] FATAL ERROR: en-US/Book_Info.xml: [ 78s] No such file or directory at /usr/lib/perl5/vendor_perl/5.24.0/x86_64-linux-thread- multi/XML/Parser/Expat.pm line 474. [ 78s] at line 6, column 0, byte 272 [ 78s] Handler couldn't resolve external entity at line 6, column 0, byte 272 [ 78s] error in processing external entity reference at line 6, column 0, byte 272 at /usr/lib/perl5/vendor_perl/5.24.0/x86_64-linux- thread-multi/XML/Parser.pm line 187. [ 78s] at /home/abuild/rpmbuild/BUILD/Publican- v4.3.2/blib/script/publican line 1001. The full Buildlog is there: https://build.opensuse.org/build/Documentat ion:Publican/openSUSE_Tumbleweed/x86_64/publican/_log The Specfile: https://build.opensuse.org/package/view_file/Documentatio n:Publican/publican/publican.spec?expand=1 Maybe anyone knows why it doesn't find the perl modules? Greetings Sascha -- Sascha Manns | openSUSE Member Email: saigkill(a)opensuse.org | Blog: http://saigkill.tuxfamily.org GPG: 0x62ECD463 -- 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] Try to update wkhtmltopdf
by Sascha Manns 24 Mar '17

24 Mar '17

Hello list, currently i'm trying to upgrade wkhtmltopdf. The build breaks with: [ 68s] g++ -c -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_WEBKIT -DVERSION=0.12.4 -DFULL_VERSION=0.12.4 -DBUILDING_DLL -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_SVG_LIB -DQT_XMLPATTERNS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/default -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include/QtXmlPatterns -I/usr/include/QtSvg -I/usr/include/QtWebKit -I/usr/include -I../../include -I. -o outline.o ../lib/outline.cc [ 68s] ../lib/pdfsettings.cc: In function 'QString wkhtmltopdf::settings::unitRealToStr(const UnitReal&, bool*)': [ 68s] ../lib/pdfsettings.cc:308:3: warning: this 'if' clause does not guard... [-Wmisleading-indentation] [ 68s] if (ok) *ok=false; break; [ 68s] ^~ [ 68s] ../lib/pdfsettings.cc:308:22: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if' [ 68s] if (ok) *ok=false; break; [ 68s] ^~~~~ [ 68s] ../lib/multipageloader.cc: In constructor 'wkhtmltopdf::ResourceObject::ResourceObject(wkhtmltopdf::MultiPageLoad erPrivate&, const QUrl&, const wkhtmltopdf::settings::LoadPage&)': [ 68s] ../lib/multipageloader.cc:219:10: error: 'class wkhtmltopdf::MyQWebPage' has no member named 'setDevicePixelRatio' [ 68s] webPage.setDevicePixelRatio(devicePixelRatio); // Fix CSS media queries (does not affect anything else). [ 68s] ^~~~~~~~~~~~~~~~~~~ [ 68s] g++ -c -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_WEBKIT -DVERSION=0.12.4 -DFULL_VERSION=0.12.4 -DBUILDING_DLL -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_SVG_LIB -DQT_XMLPATTERNS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/default -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include/QtXmlPatterns -I/usr/include/QtSvg -I/usr/include/QtWebKit -I/usr/include -I../../include -I. -o tocstylesheet.o ../lib/tocstylesheet.cc [ 68s] g++ -c -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_WEBKIT -DVERSION=0.12.4 -DFULL_VERSION=0.12.4 -DBUILDING_DLL -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_SVG_LIB -DQT_XMLPATTERNS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/default -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include/QtXmlPatterns -I/usr/include/QtSvg -I/usr/include/QtWebKit -I/usr/include -I../../include -I. -o imagesettings.o ../lib/imagesettings.cc [ 68s] make[1]: *** [Makefile:382: multipageloader.o] Error 1 [ 68s] make[1]: *** Waiting for unfinished jobs.... [ 70s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/wkhtmltox-0.12.4/src/lib' [ 70s] make: *** [Makefile:41: sub-src-lib-make_default-ordered] Error 2 [ 70s] error: Bad exit status from /var/tmp/rpm-tmp.zo01c0 (%build) The full Log is on https://build.opensuse.org/build/Documentation:Publi can/openSUSE_Tumbleweed/i586/wkhtmltopdf/_log Maybe anyone knows what the error is there? Greetings Sascha -- Sascha Manns | openSUSE Member Email: saigkill(a)opensuse.org | Blog: http://saigkill.tuxfamily.org GPG: 0x62ECD463 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 11

[opensuse-packaging] Packaging hints for transactional updates
by Thorsten Kukuk 23 Mar '17

23 Mar '17

Hi, I started to collect issues with RPMs and transational-updates and how to avoid them: https://en.opensuse.org/openSUSE:Packaging_for_transactional-updates Luckily, until now it's not much and most RPMs are fine. 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

13 49

[opensuse-packaging] where are .desktop files stored?
by Olaf Hering 23 Mar '17

23 Mar '17

My silly grep over 10k .spec files gives this list of directories where *.desktop files are stored. Who is the consumer of .desktop files and why are there some many different places to store them? And: Is a simple "%_datadir/applications" not good enough for most of them? It would be so easy. And compatible. Olaf 560 %_datadir/applications 224 /opt/kde3/share/applications/kde 171 %_kf5_applicationsdir 140 /opt/kde3/share/services 122 %_kde4_servicesdir 105 %_kf5_servicesdir 63 %yast_desktopdir 58 %_kde4_applicationsdir 55 %_sysconfdir/xdg/autostart 30 %_kf5_servicetypesdir 29 %_datadir/xfce4/panel/plugins 28 /opt/kde3/share/servicetypes 28 /opt/kde3/share/services/kaddressbook 25 %_datadir/xsessions 22 /opt/kde3/share/applnk/.hidden 22 %_kde4_servicesdir/kded 20 /opt/kde3/share/mimelnk/application 16 /opt/kde3/share/services/kontact 13 /usr/share/applications 13 /opt/kde3/share/services/kded 13 %_kf5_configdir/autostart 11 %_datadir/mimelnk/application 9 /opt/kde3/share/autostart 8 /opt/kde3/share/applnk/System/ScreenSavers 8 %_kf5_sharedir/%name/extras/multimedia 7 /opt/kde3/share/apps/kicker/applets 7 %_kde4_servicesdir/ServiceMenus 7 %_datadir/applications/kde4 6 %desktopdir 6 %_kde4_servicetypes 6 %_datadir/xfce4/panel-plugins 5 /opt/kde3/share/apps/konqueror/servicemenus 5 /opt/kde3/share/appl*/* 5 %_kde4_servicetypesdir 5 %_datadir/kde4/services 5 %_datadir/autostart 4 %_libdir/gnome-settings-daemon-3.0/gtk-modules 4 %_kde4_appsdir/solid/actions 4 %_datadir/solid/actions 4 %_datadir/kservices5 3 /opt/kde3/share/mimelnk/text 3 /opt/kde3/share/mimelnk/fonts 3 /opt/kde3/share/applnk/Settings/WebBrowsing 3 %buildroot/%_datadir/applications 3 %_libdir/%name/share/applications 3 %_datadir/xgreeters 3 %_datadir/system-config-selinux 3 %_datadir/kde4/services/ServiceMenus 2 /usr/share/autoinstall/modules 2 /opt/kde3/share/services/kresources/kcal 2 /opt/kde3/share/services/kresources 2 /opt/kde3/share/services/kdemmbackends 2 /opt/kde3/share/apps/remoteview 2 %_prefix/share/applications/YaST2 2 %_kf5_servicesdir/ServiceMenus 2 %_kde4_servicesdir/phononbackends 2 %_kde4_appsdir/kwin 2 %_kde4_appsdir/konqueror/dirtree/remote 2 %_jvmdir/%sdkdir/jre/lib/desktop 2 %_datadir/wayland-sessions 2 %_datadir/kservices5/ServiceMenus 2 %_datadir/kde4/services/phononbackends 2 %_datadir/gnome/wm-properties 2 %_datadir/gnome/autostart 2 %_datadir/gdm/greeter/applications 2 %_datadir/applications/YaST2 1 Swift/resources 1 /usr/share/xsessions 1 /opt/kde3/share/services/searchproviders 1 /opt/kde3/share/mimelnk/interface 1 /opt/kde3/share/mimelnk/inode 1 /opt/kde3/share/mimelnk/audio 1 /opt/kde3/share/mimelnk/* 1 /opt/kde3/share/apps/kttsd 1 /opt/kde3/share/apps/konqueror/dirtree/remote 1 /opt/kde3/share/apps/kicker/extensions 1 /opt/kde3/share/apps/khtml/kpartplugins 1 /opt/kde3/share/apps/khelpcenter/searchhandlers 1 /opt/kde3/share/apps/kabc/formats 1 /opt/kde3/share/applnk/Development 1 /opt/kde3/share/applnk 1 /etc/xdg/autostart 1 %yast_desktopdir/groups 1 %kdeprefix/share/applications 1 %gnome_prefix/share/applications 1 %gnome_prefix/share/application-registry 1 %gnome_datadir/applications 1 %_kf5_sharedir/xsessions 1 %_kf5_sharedir/locale/* 1 %_kf5_sharedir/akonadi/agents 1 %_kf5_sharedir/%name/extras/system 1 %_kf5_servicesdir/kded 1 %_kde4_servicesdir/qimageioplugins 1 %_kde4_appsdir/remoteview 1 %_kde4_appsdir/konqsidebartng/virtual_folders/services 1 %_datadir/tracker/miners 1 %_datadir/susehelp/meta 1 %_datadir/services/kded 1 %_datadir/remoteview 1 %_datadir/konqsidebartng/virtual_folders/services 1 %_datadir/kdm/sessions 1 %_datadir/kde4/apps/ksmserver/windowmanagers 1 %_datadir/gdm/autostart/LoginWindow 1 %_datadir/applications/kde 1 %_datadir/appdata 1 %_datadir/akonadi/agents 1 %_datadir/Thunar/sendto

4 7

[opensuse-packaging] python singlespec: broken python3 packages
by Mikhail Terekhov 23 Mar '17

23 Mar '17

Hello, After conversion to singlespec some python3 packages became broken, ex: https://build.opensuse.org/package/show/KDE:Qt5/python-sip https://build.opensuse.org/package/show/KDE:Qt5/qscintilla-qt5 The logs in web interface say that patches to python3-* files could not be applied. Obviously the python3-* files has been deleted during conversion. I've tried to branch these packages but the branches also can't be compiled with the same errors. How to fix this problem? Regards, Mikhail -- 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] X11:wxWidgets/python-wxWidgets broken due to deleted link openSUSE:Factory/python-wxWidgets
by Joop Boonen 22 Mar '17

22 Mar '17

An OBS package issue exists. X11:wxWidgets/python-wxWidgets broken due to deleted link openSUSE:Factory/python-wxWidgets . https://build.opensuse.org/package/show/X11:wxWidgets/python-wxWidgets Warning: Files could not be expanded: openSUSE:Factory/python-wxWidgets: package 'python-wxWidgets' does not exist Can this please be fixed. By moving the openSUSE:Factory/python-wxWidgets to this location (X11:wxWidgets/python-wxWidgets). Reagds, Joop. -- 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] how will zypper treat conflicts/provides/obsoletes?
by jan matejek 22 Mar '17

22 Mar '17

hello, what will happen if a packageA has something like: Provides: packageB = %version-%release Obsoletes: packageB < %version-%release Conflicts: packageB < %version-%release will zypper use it to upgrade from packageB to packageA? will the Conflicts clause ensure that packageB is completely removed before installing packageA? will something else happen? will nothing at all happen? What I'm actually after is the second question - making sure that in an upgrade, packageB is completely removed, %postun scriptlets and all, before even starting to install packageA. Is a Conflics clause a way to ensure that? Are there any (other) options? thanks m.

4 5

[opensuse-packaging] Last AC3 patent expired
by Luigi Baldoni 21 Mar '17

21 Mar '17

See https://ac3freedomday.org. Is this of any relevance to multimedia:libs or multimedia:apps ? Can something be brought over from packman or enabled (e.g. in ffmpeg)? Regards -- View this message in context: http://opensuse.14.x6.nabble.com/Last-AC3-patent-expired-tp5083284.html Sent from the opensuse-packaging mailing list archive at Nabble.com. -- 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] Package scheduled for removal from openSUSE:Factory
by Dimstar / Dominique Leuenberger 17 Mar '17

17 Mar '17

Dear packagers and users, The package swipl has been scheduled for removal after it has been failing to build for 170 days without any reaction from the maintainers [0] >> zypper info swipl >Information for package swipl: >------------------------------ >Repository : Tumbleweed >Name : swipl >Version : 7.2.2-1.8 >Description : > Edinburgh-style Prolog compiler including modules, autoload, > libraries, Garbage collector, stack expandor, C interface, GNU > readline and GNU Emacs interface, a very fast compiler,and an X11 > interface using XPCE > (see http://www.swi.psy.uva.nl/projects/xpce). If you care for this package - then this is your chance now to step up and claim maintainership and save it - not by words, but by actions. If you intend on working on it, please shoot me a message so I'm aware of it, including an estimated timeframe when you expect to have a fix ready. A couple more days or less won't hurt of course. But without any reaction, this package is history in a couple days. Cheers, Dominique [0] https://bugzilla.opensuse.org/show_bug.cgi?id=1023722 -- Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org>

2 2

[opensuse-packaging] Package using stdlib.h broken on Factory
by Ferdinand Thiessen 17 Mar '17

17 Mar '17

Hi, I noticed that if a package is using stdlib.h, then the build will fail on Factory with "E: a implicit-fortify-decl". To show this I have created this package: https://build.opensuse.org/package/show/home:susnux/a If I read the man page ( https://linux.die.net/man/3/ptsname ), it shows that only _XOPEN_SOURCE is needed for the prototype: > char *ptsname(int fd); But it only works on Factory if _GNU_SOURCE is defined. Do I miss something? Regards, Ferdinand -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 2

[opensuse-packaging] Move /etc/init.d hierachy to own RPM
by Thorsten Kukuk 17 Mar '17

17 Mar '17

Hi, All packages from my default installation are now free of init.d scripts/insserv usage (at least when the last package maintainers accept and/or submit their packages to Factory finally). I would like to use this opportunity to set an example and make it visible to people, that systemd is the default and init scripts are legacy, deprecated and should be converted to systemd units. Why? If you install a system, you will not have insserv or other tools to activate and run init scripts installed by default anymore. But there is still the /etc/init.d hierachy. So I would like to move that directories to an own RPM, prefereable "insserv-compat". Why "insserv-compat"? And what does this mean for existing packages? - packages having correct insserv requires will not notice this - packages with broken insserv requires, but which builds currently by accident, will continue to build by accident. - packages messing up with their requires and currently don't build, will continue to not build until somebody fixes them. But this is completly independent of this change - rpm will fail to build until either somebody converted rpmconfigcheck to a systemd unit file or we drop it. Opinions? Objections? If nobody has good reasons against this, I will make this change in 2-3 weeks. 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

4 10

[opensuse-packaging] Build issues against openSUSE Tumbleweed
by Dimstar / Dominique Leuenberger 15 Mar '17

15 Mar '17

Dear hackers and packagers, My sincere apologies - once again we are struck by a delete request having impacts way beyond what we expect to to touch. As part of the cleanup activities, gcc5 has been removed from the distro. This also impacts libffi4; The distro has gained a new libffi implementation (libffi7, version 3.2.1) which has been around for a while. As we now deleted libffi4, though, it became apparent that not everything is yet rebuilt against libffi7 (no real surprise there: we have the rebuild strategy of least changes implemented) So far nothing bad - except: as libffi4 has been removed from openSUSE:Factory, this not only impacts /standard (which we would not have a problem - ever), but also /snapshot. Which means all the builds against openSUSE:Tumbleweed will be broken at least until the next snapshot can be published (0313 that is). I apologize for this issue caused and will be trying to find a workaround for now to get you guys going again. Please stay tuned. Cheers, Dominique -- Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org>

3 5

[opensuse-packaging] update-alternatives and manpage conventions
by jan matejek 14 Mar '17

14 Mar '17

I am now writing better support for update-alternatives in the python singlespec macros. The way it works now, it is very well suited to enforce naming conventions. So.... what are these? :) Far as I could figure out, you install manpages as "manpage.1" and some magic converts it to "manpage.1.gz"? Should the alternatives entry be /etc/alternatives/manpage.1 or /etc/alternatives/manpage.1.gz ? Should the %ghost %{_mandir}/man1/manpage.1 be called that, or should it be manpage.1.gz? Or does it depend on whether the original manpage.1 is gzipped or not? -- at the moment, the enforced convention in singlespec is that base %_mandir names depend on the original file, and /etc/alternatives entries are always named without ".gz". Should that be changed to something else? -- Relatedly, is it common in any packages to make alternatives for something other than /usr/bin and %_mandir? I know that Java plays with /usr/lib/jvm, but other than that? thanks m.

2 2

[opensuse-packaging] python singlespec for only existing in d:l:p3
by Bruno Friedmann 13 Mar '17

13 Mar '17

Hi there, today I receive the first changes for an only existing in python3 (d:l:p3) package to be converted to singlespec. Now I wonder if we should start the conversion into d:l:p3 like in the sr. Once build in d:l:p3 we submit it to python-singlespec repo and then back to d:l:p ? Or what is the best workflow we can choose, to first not loose the work done in d:l:p3 and get them all to factory in the end. Thanks for your ideas. Example https://build.opensuse.org/request/show/478944 -- 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

4 5

[opensuse-packaging] Re: [sle-desktop] Autotools version mismatch in GNOME on SLE12-SP2 and Leap 42.2
by Felix Zhang 13 Mar '17

13 Mar '17

Hi Yifan, Thanks very much for this advice. On a second thought, this issue potentially affects an amount of packages on Leap 42.2. So cross-posting to opensuse-packaging(a)opensuse.org. Thanks, Felix On 2017/3/7 11:36, Yifan Jiang wrote: > Hi Felix, > > I guess "research" is also a good place to append the question, making it > visible to OBS and toolchain guys :-) > > - Yifan > > > On Mon, Mar 06, 2017 at 09:20:10PM +0800, Felix Zhang wrote: >> Hi all, >> >> I noticed that the autotools files in our GNOME packages are generated >> by autotools 1.15. As I didn't find these files included in the upstream >> repos. I guess they come from openSUSE:Factory at the time we >> constructed SLE12-SP2 and Leap 42.2. >> >> However, on SP2 and 42.2 we kept autotools 1.13 from updating to 1.15. >> >> This mismatch hit me when I was trying to backport CVE patches for >> gtk-vnc (bsc#1024266, bsc#1024268) which have modifications on a >> Makefile.am thus automake is required to regenerate Makefile.in - a >> build time error complained that automake-1.15 is not found: >> >> https://build.suse.de/package/live_build_log/home:zhangxiaofei:branches:Dev… >> >> I understand there must be good reasons not updating autotools. So my >> question is, what's a good way to get around such failures please? >> >> Thanks very much in advance for your tips. :-) >> >> >> Best regards, >> >> Felix >> >> > > > >

5 7

[opensuse-packaging] python singlespec: wiki page
by jan matejek 13 Mar '17

13 Mar '17

Hello all, I have created a page on the openSUSE wiki, listing the conversion steps and explaining some things. I will try to keep it up to date with new developments. This also supersedes the "how to convert your package" e-mail. https://en.opensuse.org/openSUSE:Packaging_Python_Singlespec Also, at some point the content should be merged into Packaging:Python, but this turned out to be a bigger task :) So for now I'll place a link to it and leave it at that. Please let me know if you think that something should be added, removed, changed, etc. Also it would be nice if someone could look at the CSS for the wiki, and ensure that <code> and <pre> tags are more readable -- for me, the monospace font is about half the size of the regular font. regards m.

4 9

[opensuse-packaging] Announcing golang-packaging version 15.0.0
by Thomas Hipp 13 Mar '17

13 Mar '17

Hi, I'd like to announce the new version of golang-packaging[0]. This is a complete rewrite using only Bash instead of Ruby. Except for the rewrite, there are no major changes, so packaging works (almost) just like before. The changes include: * static libraries (*.a files) are not shipped; only source files * macro %{go_filelist} -> %{gofilelist}, to be consistent * removed previously deprecated macros The wiki[1] page has been updated to reflect the recent changes. There you can also find an updated spec file template. Also, all packages in devel:languages:go[2] have been updated, and are now using the new golang-packaging version. Happy packaging! Best wishes Thomas [0] https://github.com/openSUSE/golang-packaging/ [1] https://en.opensuse.org/openSUSE:Packaging_Go [2] https://build.opensuse.org/project/show/devel:languages:go -- Thomas Hipp Docker Developer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) PGP fingerprint: 48D6 A5F4 2D60 57BF 9A37 8004 5DE8 949A 899C 8D99

1 0

[opensuse-packaging] status report jmatejek 2017-03-03 (week 09)
by jan matejek 11 Mar '17

11 Mar '17

[green] - singlespec * looking into SLE11 situation * converting packages * talking to people * fixing problems * developing a macro to automate creation of update-alternatives - updating pythons for SLE12 (2.7.13, 3.4.6, bsc#1027282) - bsc#1026174 - Python 3.6 broke pylint which sits rather low on the dep tree, so looking into that, converting packages to singlespec while doing it, and preparing astroid/pylint packages from unreleased github checkouts [workload] 9 [outlook] - cleaning up singlespec repo - mass autoconversion - finishing the update-alternatives macro - maybe work on python-rpm-macros-compat for SLE11 - !! writing conversion guidelines, with usual mistakes !! * mistake #1: using %python_module in Requires [good] This is, very surprisingly, very painless. [bad] setuptools_scm

2 1

[opensuse-packaging] Unsubscribe
by Marko Denda 11 Mar '17

11 Mar '17

-- 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] Can't build packages locally - what's going on?
by Greg Freemyer 08 Mar '17

08 Mar '17

I'm confused. I've tried to build 3 packages and none are working. The complaint I notice is about permissions for /dev/null. Three examples of what is failing right now: osc co /home:gregfreemyer:Tools-for-forensic-boot-cd calc cd /home:gregfreemyer:Tools-for-forensic-boot-cd/calc osc build osc co security:forensics dc3dd cd security:forensics/dc3dd osc build osc co openSUSE:Leap:42.1:Update libewf cd openSUSE:Leap:42.1:Update/libewf osc build --local Greg -- Greg Freemyer -- 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] Kernel tools packaging for Factory
by Andreas Färber 07 Mar '17

07 Mar '17

Hello, For v4.7, the kvm_stat utility was removed from QEMU and added to the kernel. We therefore had to adapt qemu packaging, and Bruce added a Virtualization/kvm_stat package built from kernel-source. https://build.opensuse.org/package/show/Virtualization/kvm_stat As part of the Factory submission review, although it was accepted, it was suggested that we add it as sub-package to devel:tools/linux-tools instead. I have done that now. https://build.opensuse.org/package/show/devel:tools/linux-tools However, linux-tools is not in Factory. Therefore we can't drop our kvm_stat package yet, which was the intended purpose of the submission. Are there any plans to submit linux-tools to Factory, or what is holding it up? Should this rather be integrated with kernel-source somehow, like dtb-source recently, so that it rebuilds with kernel updates and can take build breakages like for v4.10 into account? Thanks, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (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

3 3

[opensuse-packaging] New packages: libtwaindsm2 and libopenusb
by Erico Mendonca 06 Mar '17

06 Mar '17

Hello all, I ported two new packages to OBS: https://build.opensuse.org/package/show/home:emendonca/libtwaindsm2 https://build.opensuse.org/package/show/home:emendonca/libopenusb - libtwaindsm2: this is the official TWAIN Group stack for Linux. It's used for implementing the TWAIN protocol for scanner/camera applications. The code resides on SourceForge. - libopenusb: it's a MT-safe version of libusb. Also resides on SourceForge. I wrote the SPECs from scratch. I made a few patches to fix GCC 4.8+ compiler errors. The reason I ported these was because they are necessary for some proprietary scanner drivers for Linux, which I had to repackage for a customer. I submitted these to the "hardware" repository a couple of weeks ago, but the requests never got reviewed. Could someone take a look if everything's alright? -- Erico -- 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] New packages: libtwaindsm2 and libopenusb
by Erico Mendonca 06 Mar '17

06 Mar '17

Hello all, I ported two new packages to OBS: https://build.opensuse.org/package/show/home:emendonca/libtwaindsm2 https://build.opensuse.org/package/show/home:emendonca/libopenusb - libtwaindsm2: this is the official TWAIN Group stack for Linux. It's used for implementing the TWAIN protocol for scanner/camera applications. The code resides on SourceForge. - libopenusb: it's a MT-safe version of libusb. Also resides on SourceForge. I wrote the SPECs from scratch. I made a few patches to fix GCC 4.8+ compiler errors. The reason I ported these was because they are necessary for some proprietary scanner drivers for Linux, which I had to repackage for a customer. I submitted these to the "hardware" repository a couple of weeks ago, but the requests never got reviewed. Could someone take a look if everything's alright? Erico Mendonça Dedicated Support Engineer SUSE Rua Joaquim Floriano, 466 12° andar Itaim Bibi Tel: +55 11 3627-0970 Cel: +55 61 8594-9557 erico.mendonca(a)suse.com

3 2

[opensuse-packaging] Salt wants to be removed due to missing python-PyYAML
by Richard Brown 05 Mar '17

05 Mar '17

When attempting to upgrade with dup --no-allow-vendor-change Problem: salt-2016.3.4-1.1.x86_64 requires python-yaml, but this requirement cannot be provided deleted providers: python-PyYAML-3.12-1.1.x86_64 Solution 1: Following actions will be done: deinstallation of salt-2016.3.4-1.1.x86_64 deinstallation of salt-zsh-completion-2016.3.4-1.1.noarch deinstallation of salt-minion-2016.3.4-1.1.x86_64 Solution 2: keep python-PyYAML-3.12-1.1.x86_64 Solution 3: break salt-2016.3.4-1.1.x86_64 by ignoring some of its dependencies Does salt need to be modified to work with the new singlespec paradigm? -- 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] Using wxWidgets3 and gcc5 leads to crash
by Ferdinand Thiessen 05 Mar '17

05 Mar '17

Hi, I am packaging a program which uses wxWidgets and also needs c++11 regex support. This means I have to use gcc >= 5 because the default gcc in Leap (4.8) is completely broken with regex (no errors when compiling but when starting the program it crashes with "std::regex exception"). I am using wxWidgets 3 and gcc5: > BuildRequires: wxWidgets-devel >= 3 > %if 0%{?suse_version} <= 1320 > BuildRequires: gcc5-c++ > %else > BuildRequires: gcc-c++ >= 5 > %endif This seems to work because one of the built binaries (which does not use wxWidgets but std::regex) now works, but the binary using wxWidgets now crashes with this error: > 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 your program used 3.0 (wchar_t,compiler with C++ ABI 1009,STL containers,compatible with 2.8). So my question is: Is there a way (for me) to fix this? Because the only way I can imagine is to rebuild wxWidgets3 for Leap. Regards, Ferdinand -- 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] My first boot CD via KIWI?
by Greg Freemyer 05 Mar '17

05 Mar '17

SuseStudio doesn't have 42.2 or Tumbleweed in it and I'd like to build a boot CD/DVD for one of them. As a first step I copied a couple packages from: openSUSE:Factory:Live To my surprise, it doesn't build. Anyone know what I need to do? ============== This is my new project which I hope will build boot media: https://build.opensuse.org/package/show/security:forensics/kiwi-dfir-livecd… I deleted the extra spec files and it starts to build, but it dies with: [ 521s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/security:forensics/openSUSE_Tumbleweed/a89606dc534…' /home/abuild/rpmbuild/SOURCES/kiwi-image-livecd-gnome.spec [ 522s] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.MPeqex [ 522s] + umask 022 [ 522s] + cd /home/abuild/rpmbuild/BUILD [ 522s] + cd /home/abuild/rpmbuild/BUILD [ 522s] + rm -rf kiwi-image-livecd-gnome-Tumbleweed [ 522s] + /usr/bin/mkdir -p kiwi-image-livecd-gnome-Tumbleweed [ 522s] + cd kiwi-image-livecd-gnome-Tumbleweed [ 522s] + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . [ 522s] + exit 0 [ 522s] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.fR5H0c [ 522s] + umask 022 [ 522s] + cd /home/abuild/rpmbuild/BUILD [ 522s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/kiwi-image-livecd-gnome-Tumbleweed-3.1.x86_64 [ 522s] ++ dirname /home/abuild/rpmbuild/BUILDROOT/kiwi-image-livecd-gnome-Tumbleweed-3.1.x86_64 [ 522s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT [ 522s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/kiwi-image-livecd-gnome-Tumbleweed-3.1.x86_64 [ 522s] + cd kiwi-image-livecd-gnome-Tumbleweed [ 522s] + export KIWI_IGNORE_OLD_MOUNTS=1 [ 522s] + KIWI_IGNORE_OLD_MOUNTS=1 [ 522s] ++ echo kiwi-image-livecd-gnome [ 522s] ++ cut -d- -f4 [ 522s] + desktop=gnome [ 522s] + type=livecd [ 522s] + config=livecd-gnome [ 522s] + rm -rf tmp out [ 522s] + mkdir tmp out [ 522s] + rm -rf /home/rpmdir [ 522s] + mkdir -p /home/rpmdir/rpms [ 522s] mkdir: cannot create directory '/home/rpmdir': Permission denied [ 522s] error: Bad exit status from /var/tmp/rpm-tmp.fR5H0c (%build) Thanks Greg -- Greg Freemyer -- 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] Pre require does not work?
by Dr. Werner Fink 04 Mar '17

04 Mar '17

Hi, just found this [ 87s] /var/tmp/rpm-tmp.JEB8CE: line 2: /usr/sbin/groupadd: No such file or directory [ 87s] error: %prein(texlive-filesystem-2016.108-20.1.noarch) scriptlet failed, exit status 127 [ 87s] error: texlive-filesystem-2016.108-20.1.noarch: install failed [ 87s] /var/tmp/rpm-tmp.rJ6r3Q: line 2: /usr/sbin/groupadd: No such file or directory [ 87s] error: %prein(texlive-kpathsea-bin-2016.20160523.svn40473-35.3.armv7hl) scriptlet failed, exit status 127 [ 87s] error: texlive-kpathsea-bin-2016.20160523.svn40473-35.3.armv7hl: install failed [...] [ 155s] /var/tmp/rpm-tmp.4CmP4O: line 3: /usr/share/texmf/texconfig/update: No such file or directory [ 155s] /var/tmp/rpm-tmp.RJDvjs: line 3: /usr/share/texmf/texconfig/update: No such file or directory [ 156s] /var/tmp/rpm-tmp.ahy1H5: line 3: /usr/share/texmf/texconfig/update: No such file or directory the script /usr/share/texmf/texconfig/update does belong to the package texlive-filesystem, but there are some pre requires in the spec file(s) as well, like Requires(pre): /usr/bin/getent Requires(pre): /usr/sbin/groupadd Requires(post): %fillup_prereq Requires(post): permissions Requires(pre): /usr/bin/perl Requires(pre): /usr/bin/clear Requires(pre): /usr/bin/dialog Requires(pre): coreutils Requires(pre): ed Requires(pre): findutils Requires(pre): grep Requires(pre): sed What does going wrong here? Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

4 7

[opensuse-packaging] what commands go into build module [spec file] to create rpm ?
by doiggl＠velocitynet.com.au 04 Mar '17

04 Mar '17

Hello As said. what commands go into build module [spec file] to create rpm ? I copied source by unzipping it, then creating the .tar.gz file from source browsed Source: https://sourceforge.net/projects/geneotree/files/latest/download?source=dir… from: geneotree3_61_full.zip to: geneotree-3.61.tar.gz I use x86_64 -64 bit opensuse. Help wanted. Thanks --Glenn spec: https://build.opensuse.org/package/view_file/home:doiggl/geneotree/geneotre… urls: source: https://sourceforge.net/projects/geneotree/?source=typ_redirect build attempt: https://build.opensuse.org/package/show/home:doiggl/geneotree :logs https://build.opensuse.org/build/home:doiggl/openSUSE_Factory/i586/geneotre… https://build.opensuse.org/build/home:doiggl/openSUSE_Factory/x86_64/geneot… >download and rename # wget -c "https://sourceforge.net/projects/geneotree/files/latest/download?source=dir…" # mv -v "download?source=directory" geneotree3_61_full.zip ‘download?source=directory’ -> ‘geneotree3_61_full.zip’ file listing: # unzip -t geneotree3_61_full.zip Archive: geneotree3_61_full.zip testing: geneotree/ OK testing: geneotree/admin.php OK testing: geneotree/affichage_carte.php OK testing: geneotree/affichage_carte_pdf.php OK testing: geneotree/affichage_carte_prep.php OK testing: geneotree/arbre_ascendant.php OK testing: geneotree/arbre_ascendant_pdf.php OK testing: geneotree/arbre_descendant.php OK testing: geneotree/arbre_descendant_pdf.php OK testing: geneotree/arbre_mixte.php OK testing: geneotree/arbre_mixte_pdf.php OK testing: geneotree/chartjs/ OK testing: geneotree/chartjs/Chart.min.js OK testing: geneotree/compare.php OK testing: geneotree/config.php OK testing: geneotree/consanguinite.php OK testing: geneotree/consanguinite_pdf.php OK testing: geneotree/fiche.php OK testing: geneotree/fiche_media.php OK testing: geneotree/fiche_pdf.php OK testing: geneotree/fpdf/ OK testing: geneotree/fpdf/ellipse.php OK testing: geneotree/fpdf/font/ OK testing: geneotree/fpdf/font/courier.php OK testing: geneotree/fpdf/font/helvetica.php OK testing: geneotree/fpdf/font/helveticab.php OK testing: geneotree/fpdf/font/helveticabi.php OK testing: geneotree/fpdf/font/helveticai.php OK testing: geneotree/fpdf/font/makefont/ OK testing: geneotree/fpdf/font/makefont/cp1250.map OK testing: geneotree/fpdf/font/makefont/cp1251.map OK testing: geneotree/fpdf/font/makefont/cp1252.map OK testing: geneotree/fpdf/font/makefont/cp1253.map OK testing: geneotree/fpdf/font/makefont/cp1254.map OK testing: geneotree/fpdf/font/makefont/cp1255.map OK testing: geneotree/fpdf/font/makefont/cp1257.map OK testing: geneotree/fpdf/font/makefont/cp1258.map OK testing: geneotree/fpdf/font/makefont/cp874.map OK testing: geneotree/fpdf/font/makefont/iso-8859-1.map OK testing: geneotree/fpdf/font/makefont/iso-8859-11.map OK testing: geneotree/fpdf/font/makefont/iso-8859-15.map OK testing: geneotree/fpdf/font/makefont/iso-8859-16.map OK testing: geneotree/fpdf/font/makefont/iso-8859-2.map OK testing: geneotree/fpdf/font/makefont/iso-8859-4.map OK testing: geneotree/fpdf/font/makefont/iso-8859-5.map OK testing: geneotree/fpdf/font/makefont/iso-8859-7.map OK testing: geneotree/fpdf/font/makefont/iso-8859-9.map OK testing: geneotree/fpdf/font/makefont/koi8-r.map OK testing: geneotree/fpdf/font/makefont/koi8-u.map OK testing: geneotree/fpdf/font/makefont/makefont.php OK testing: geneotree/fpdf/font/symbol.php OK testing: geneotree/fpdf/font/times.php OK testing: geneotree/fpdf/font/timesb.php OK testing: geneotree/fpdf/font/timesbi.php OK testing: geneotree/fpdf/font/timesi.php OK testing: geneotree/fpdf/font/zapfdingbats.php OK testing: geneotree/fpdf/fpdf.css OK testing: geneotree/fpdf/fpdf.php OK testing: geneotree/gedcom/ OK testing: geneotree/gedcom/napoleon.ged OK testing: geneotree/gedcom/royal.ged OK testing: geneotree/gedcom/uspresident.ged OK testing: geneotree/geo/ OK testing: geneotree/geo/communes.dat OK testing: geneotree/geo/communes_perso.dat OK testing: geneotree/geo/FR_01.jpg OK testing: geneotree/geo/FR_02.jpg OK testing: geneotree/geo/FR_03.jpg OK testing: geneotree/geo/FR_04.jpg OK testing: geneotree/geo/FR_05.jpg OK testing: geneotree/geo/FR_06.jpg OK testing: geneotree/geo/FR_07.jpg OK testing: geneotree/geo/FR_08.jpg OK testing: geneotree/geo/FR_09.jpg OK testing: geneotree/geo/FR_10.jpg OK testing: geneotree/geo/FR_11.jpg OK testing: geneotree/geo/FR_12.jpg OK testing: geneotree/geo/FR_13.jpg OK testing: geneotree/geo/FR_14.jpg OK testing: geneotree/geo/FR_15.jpg OK testing: geneotree/geo/FR_16.jpg OK testing: geneotree/geo/FR_17.jpg OK testing: geneotree/geo/FR_18.jpg OK testing: geneotree/geo/FR_19.jpg OK testing: geneotree/geo/FR_20.jpg OK testing: geneotree/geo/FR_21.jpg OK testing: geneotree/geo/FR_22.jpg OK testing: geneotree/geo/FR_23.jpg OK testing: geneotree/geo/FR_24.jpg OK testing: geneotree/geo/FR_25.jpg OK testing: geneotree/geo/FR_26.jpg OK testing: geneotree/geo/FR_27.jpg OK testing: geneotree/geo/FR_28.jpg OK testing: geneotree/geo/FR_29.jpg OK testing: geneotree/geo/FR_2A.jpg OK testing: geneotree/geo/FR_2B.jpg OK testing: geneotree/geo/FR_30.jpg OK testing: geneotree/geo/FR_31.jpg OK testing: geneotree/geo/FR_32.jpg OK testing: geneotree/geo/FR_33.jpg OK testing: geneotree/geo/FR_34.jpg OK testing: geneotree/geo/FR_35.jpg OK testing: geneotree/geo/FR_36.jpg OK testing: geneotree/geo/FR_37.jpg OK testing: geneotree/geo/FR_38.jpg OK testing: geneotree/geo/FR_39.jpg OK testing: geneotree/geo/FR_40.jpg OK testing: geneotree/geo/FR_41.jpg OK testing: geneotree/geo/FR_42.jpg OK testing: geneotree/geo/FR_43.jpg OK testing: geneotree/geo/FR_44.jpg OK testing: geneotree/geo/FR_45.jpg OK testing: geneotree/geo/FR_46.jpg OK testing: geneotree/geo/FR_47.jpg OK testing: geneotree/geo/FR_48.jpg OK testing: geneotree/geo/FR_49.jpg OK testing: geneotree/geo/FR_50.jpg OK testing: geneotree/geo/FR_51.jpg OK testing: geneotree/geo/FR_52.jpg OK testing: geneotree/geo/FR_53.jpg OK testing: geneotree/geo/FR_54.jpg OK testing: geneotree/geo/FR_55.jpg OK testing: geneotree/geo/FR_56.jpg OK testing: geneotree/geo/FR_57.jpg OK testing: geneotree/geo/FR_58.jpg OK testing: geneotree/geo/FR_59.jpg OK testing: geneotree/geo/FR_60.jpg OK testing: geneotree/geo/FR_61.jpg OK testing: geneotree/geo/FR_62.jpg OK testing: geneotree/geo/FR_63.jpg OK testing: geneotree/geo/FR_64.jpg OK testing: geneotree/geo/FR_65.jpg OK testing: geneotree/geo/FR_66.jpg OK testing: geneotree/geo/FR_67.jpg OK testing: geneotree/geo/FR_68.jpg OK testing: geneotree/geo/FR_69.jpg OK testing: geneotree/geo/FR_70.jpg OK testing: geneotree/geo/FR_71.jpg OK testing: geneotree/geo/FR_72.jpg OK testing: geneotree/geo/FR_73.jpg OK testing: geneotree/geo/FR_74.jpg OK testing: geneotree/geo/FR_75.jpg OK testing: geneotree/geo/FR_76.jpg OK testing: geneotree/geo/FR_77.jpg OK testing: geneotree/geo/FR_78.jpg OK testing: geneotree/geo/FR_79.jpg OK testing: geneotree/geo/FR_80.jpg OK testing: geneotree/geo/FR_81.jpg OK testing: geneotree/geo/FR_82.jpg OK testing: geneotree/geo/FR_83.jpg OK testing: geneotree/geo/FR_84.jpg OK testing: geneotree/geo/FR_85.jpg OK testing: geneotree/geo/FR_86.jpg OK testing: geneotree/geo/FR_87.jpg OK testing: geneotree/geo/FR_88.jpg OK testing: geneotree/geo/FR_89.jpg OK testing: geneotree/geo/FR_90.jpg OK testing: geneotree/geo/FR_91.jpg OK testing: geneotree/geo/FR_92.jpg OK testing: geneotree/geo/FR_93.jpg OK testing: geneotree/geo/FR_94.jpg OK testing: geneotree/geo/FR_95.jpg OK testing: geneotree/geo/geo.dat OK testing: geneotree/geo/US_AK.jpg OK testing: geneotree/geo/US_AL.jpg OK testing: geneotree/geo/US_AR.jpg OK testing: geneotree/geo/US_AZ.jpg OK testing: geneotree/geo/US_CA.jpg OK testing: geneotree/geo/US_CO.jpg OK testing: geneotree/geo/US_CT.jpg OK testing: geneotree/geo/US_DE.jpg OK testing: geneotree/geo/US_FL.jpg OK testing: geneotree/geo/US_GA.jpg OK testing: geneotree/geo/US_HI.jpg OK testing: geneotree/geo/US_IA.jpg OK testing: geneotree/geo/US_ID.jpg OK testing: geneotree/geo/US_IL.jpg OK testing: geneotree/geo/US_IN.jpg OK testing: geneotree/geo/US_KS.jpg OK testing: geneotree/geo/US_KY.jpg OK testing: geneotree/geo/US_LA.jpg OK testing: geneotree/geo/US_MA.jpg OK testing: geneotree/geo/US_MD.jpg OK testing: geneotree/geo/US_ME.jpg OK testing: geneotree/geo/US_MI.jpg OK testing: geneotree/geo/US_MN.jpg OK testing: geneotree/geo/US_MO.jpg OK testing: geneotree/geo/US_MS.jpg OK testing: geneotree/geo/US_MT.jpg OK testing: geneotree/geo/US_NC.jpg OK testing: geneotree/geo/US_ND.jpg OK testing: geneotree/geo/US_NE.jpg OK testing: geneotree/geo/US_NH.jpg OK testing: geneotree/geo/US_NJ.jpg OK testing: geneotree/geo/US_NM.jpg OK testing: geneotree/geo/US_NV.jpg OK testing: geneotree/geo/US_NY.jpg OK testing: geneotree/geo/US_OH.jpg OK testing: geneotree/geo/US_OK.jpg OK testing: geneotree/geo/US_OR.jpg OK testing: geneotree/geo/US_PA.jpg OK testing: geneotree/geo/US_RI.jpg OK testing: geneotree/geo/US_SC.jpg OK testing: geneotree/geo/US_SD.jpg OK testing: geneotree/geo/US_TN.jpg OK testing: geneotree/geo/US_TX.jpg OK testing: geneotree/geo/US_US.jpg OK testing: geneotree/geo/US_US2.jpg OK testing: geneotree/geo/US_UT.jpg OK testing: geneotree/geo/US_VA.jpg OK testing: geneotree/geo/US_VT.jpg OK testing: geneotree/geo/US_WA.jpg OK testing: geneotree/geo/US_WI.jpg OK testing: geneotree/geo/US_WV.jpg OK testing: geneotree/geo/US_WY.jpg OK testing: geneotree/graphes.php OK testing: geneotree/graphes_pdf.php OK testing: geneotree/index.php OK testing: geneotree/install.php OK testing: geneotree/lang.php OK testing: geneotree/languages/ OK testing: geneotree/languages/lang.en.inc.php OK testing: geneotree/languages/lang.fr.inc.php OK testing: geneotree/languages/lang.hu.inc.php OK testing: geneotree/lisezmoi.txt OK testing: geneotree/listes.php OK testing: geneotree/listes_pdf.php OK testing: geneotree/media.php OK testing: geneotree/media_pdf.php OK testing: geneotree/menu.php OK testing: geneotree/picture/ OK testing: geneotree/picture/200px-Christian_IX_af_Henrik_Olrik.jpg OK testing: geneotree/picture/200px-Roman_I_Musat.jpg OK testing: geneotree/picture/220px-Queenmaryformalportrait_edit3.jpg OK testing: geneotree/picture/275px-Kate_in_Ottawa_for_Canada_Day_2011.jpg OK testing: geneotree/picture/336px-Princess_diana_bristol_1987_01.jpg OK testing: geneotree/picture/389px-H.M._The_Queen_Mother_Allan_Warren.jpg OK testing: geneotree/picture/417px-HRH_The_Duke_of_Edinburgh_Allan_Warren.jpg OK testing: geneotree/picture/433px-Elizabeth_II_greets_NASA_GSFC_employees,_May_8,_2007_edit.jpg OK testing: geneotree/picture/483px-Carlos_de_Gales_(2011).jpg OK testing: geneotree/picture/alice.0.mountbatten.jpg OK testing: geneotree/picture/andrew.0.von_schleswig_holstein_sonderburg_glucksburg.jpg OK testing: geneotree/picture/Bill_Clinton.jpg OK testing: geneotree/picture/claude_george.0.bowes_lyon.jpg OK testing: geneotree/picture/george.5.windsor.jpg OK testing: geneotree/picture/hillary-rodham-clinton-official.jpg OK testing: geneotree/picture/King_George_VI_of_England,_formal_photo_portrait,_circa_1940-1946.jpg OK testing: geneotree/picture/Ludwig_Alexander_von_Battenberg.jpg OK testing: geneotree/picture/napoleon1.jpg OK testing: geneotree/picture/Nina_Cecilia_Cavendish-Bentinck.jpg OK testing: geneotree/picture/Olga_of_Greece_VI.jpg OK testing: geneotree/picture/Prince_William_2011.jpg OK testing: geneotree/picture/Reuters-clinton-chelsea.jpg OK testing: geneotree/picture/victoria.0.von_hessen_und_bei_rhein.jpg OK testing: geneotree/picture/wilhelm.2.von_schleswig_holstein_sonderburg_glucksburg.jpg OK testing: geneotree/readme.txt OK testing: geneotree/source.php OK testing: geneotree/source_pdf.php OK testing: geneotree/stat.php OK testing: geneotree/stat_pdf.php OK testing: geneotree/themes/ OK testing: geneotree/themes/aliceblue.css OK testing: geneotree/themes/antiquewhite.css OK testing: geneotree/themes/aqua.css OK testing: geneotree/themes/aquamarine.css OK testing: geneotree/themes/arbre.jpg OK testing: geneotree/themes/arbre.png OK testing: geneotree/themes/arrow-icon-bottom.png OK testing: geneotree/themes/arrow-icon-middle.png OK testing: geneotree/themes/arrow-icon-top.png OK testing: geneotree/themes/azure.css OK testing: geneotree/themes/beige.css OK testing: geneotree/themes/bisque.css OK testing: geneotree/themes/blanchedalmond.css OK testing: geneotree/themes/bord_A4_paysage.jpg OK testing: geneotree/themes/bord_A4_portrait.jpg OK testing: geneotree/themes/bord_LE_paysage.jpg OK testing: geneotree/themes/bord_LE_portrait.jpg OK testing: geneotree/themes/burlywood.css OK testing: geneotree/themes/cadetblue.css OK testing: geneotree/themes/chartreuse.css OK testing: geneotree/themes/cornsilk.css OK testing: geneotree/themes/cyan.css OK testing: geneotree/themes/darkkhaki.css OK testing: geneotree/themes/darksalmon.css OK testing: geneotree/themes/darkseagreen.css OK testing: geneotree/themes/darkturquoise.css OK testing: geneotree/themes/deepskyblue.css OK testing: geneotree/themes/eggplant.css OK testing: geneotree/themes/en.gif OK testing: geneotree/themes/es.gif OK testing: geneotree/themes/excel.gif OK testing: geneotree/themes/fleche_bas.png OK testing: geneotree/themes/fleche_droite.png OK testing: geneotree/themes/fleche_haut.png OK testing: geneotree/themes/fleche_losa.png OK testing: geneotree/themes/fleche_mid.png OK testing: geneotree/themes/fleche_prec.png OK testing: geneotree/themes/fleche_suiv.png OK testing: geneotree/themes/fr.gif OK testing: geneotree/themes/gainsboro.css OK testing: geneotree/themes/geneotre.ico OK testing: geneotree/themes/geo.gif OK testing: geneotree/themes/gold.css OK testing: geneotree/themes/goldenrod.css OK testing: geneotree/themes/gray.css OK testing: geneotree/themes/green.css OK testing: geneotree/themes/greenyellow.css OK testing: geneotree/themes/home.gif OK testing: geneotree/themes/honeydew.css OK testing: geneotree/themes/hu.gif OK testing: geneotree/themes/icon-excel.png OK testing: geneotree/themes/icon-folder-grey.png OK testing: geneotree/themes/icon-home.png OK testing: geneotree/themes/icon-maps.png OK testing: geneotree/themes/icon-print.png OK testing: geneotree/themes/icon-print2.png OK testing: geneotree/themes/index.css OK testing: geneotree/themes/it.gif OK testing: geneotree/themes/ivory.css OK testing: geneotree/themes/khaki.css OK testing: geneotree/themes/lavender.css OK testing: geneotree/themes/lavenderblush.css OK testing: geneotree/themes/lawngreen.css OK testing: geneotree/themes/lemonchiffon.css OK testing: geneotree/themes/lightblue.css OK testing: geneotree/themes/lightcyan.css OK testing: geneotree/themes/lightgoldenrod.css OK testing: geneotree/themes/lightgray.css OK testing: geneotree/themes/lightgreen.css OK testing: geneotree/themes/lightpink.css OK testing: geneotree/themes/lightred.css OK testing: geneotree/themes/lightsalmon.css OK testing: geneotree/themes/lightseagreen.css OK testing: geneotree/themes/lightskyblue.css OK testing: geneotree/themes/lightsteelblue.css OK testing: geneotree/themes/lightyellow.css OK testing: geneotree/themes/lime.css OK testing: geneotree/themes/limegreen.css OK testing: geneotree/themes/linen.css OK testing: geneotree/themes/liste.png OK testing: geneotree/themes/mediumaquamarine.css OK testing: geneotree/themes/mediumseagreen.css OK testing: geneotree/themes/mediumturquoise.css OK testing: geneotree/themes/mintcream.css OK testing: geneotree/themes/mistyrose.css OK testing: geneotree/themes/moccasin.css OK testing: geneotree/themes/navajowhite.css OK testing: geneotree/themes/oldlace.css OK testing: geneotree/themes/orange.css OK testing: geneotree/themes/palegoldenrod.css OK testing: geneotree/themes/palegreen.css OK testing: geneotree/themes/paleturquoise.css OK testing: geneotree/themes/papayawhip.css OK testing: geneotree/themes/peachpuff.css OK testing: geneotree/themes/picture.png OK testing: geneotree/themes/pink.css OK testing: geneotree/themes/plum.css OK testing: geneotree/themes/powderblue.css OK testing: geneotree/themes/print.gif OK testing: geneotree/themes/pt.gif OK testing: geneotree/themes/reset.png OK testing: geneotree/themes/sandybrown.css OK testing: geneotree/themes/seashell.css OK testing: geneotree/themes/silver.css OK testing: geneotree/themes/skyblue.css OK testing: geneotree/themes/source.png OK testing: geneotree/themes/springgreen.css OK testing: geneotree/themes/tan.css OK testing: geneotree/themes/thistle.css OK testing: geneotree/themes/turquoise.css OK testing: geneotree/themes/wheat.css OK testing: geneotree/themes/white.css OK testing: geneotree/themes/whitesmoke.css OK testing: geneotree/themes/wikipedia.css OK testing: geneotree/themes/wood.css OK testing: geneotree/themes/wood.jpg OK testing: geneotree/themes/yellow.css OK testing: geneotree/themes/yellowgreen.css OK testing: geneotree/_boites.inc.php OK testing: geneotree/_caracteres.inc.php OK testing: geneotree/_graphes.inc.php OK testing: geneotree/_recup_ascendance.inc.php OK testing: geneotree/_recup_cousin_inc.php OK testing: geneotree/_recup_descendance.inc.php OK testing: geneotree/_sql.inc.php OK testing: geneotree/_stat.inc.php OK testing: geneotree/_upload.inc.php OK No errors detected in compressed data of geneotree3_61_full.zip. -- 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] How to update lib name in baselib.conf automatically
by Dave Plater 03 Mar '17

03 Mar '17

It seems that baselibs.conf doesn't take macros and with versioned lib names a packager can easily forget to update the library name in baselibs.conf. This is a problem with libraries It also seems that you can't create baselibs.conf at build time either, I tried copying back to SOURCE/ but that results in an empty baselibs.conf. Maybe precheckin_baselibs.sh will work? Any suggestions? Thanks Dave Plater -- 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] python singlespec: package transition process
by Thomas Bechtold 02 Mar '17

02 Mar '17

Hi, currently there are plenty of packages in devel:languages:python:singlespec that are already in devel:languages:python . Can we agree to remove the packages from devel:languages:python:singlespec when they are available in devel:languages:python to avoid confusion? Best, Tom -- 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] python singlespec: py2pack support added
by Thomas Bechtold 02 Mar '17

02 Mar '17

Hi, py2pack has singlespec support now[1]. It's on the way to Factory (SR 461852). Please use it for new packages and fill bugs (issues on github) if you have any problems. TIA, Tom [1] https://github.com/openSUSE/py2pack/pull/77 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0