July 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] How to "Provide" <name> for python singlespec packages without the "python2/3"-prefix?
by Oliver Kurz 10 Jul '17

10 Jul '17

With python singlespec my package names get prepended by python3- or python2- in all cases. Can I somehow achieve to provide a package name for one of the two python versions without any "python2/3-" prefix? For example: https://build.opensuse.org/package/view_file/network:messaging:matrix/matri… has Name: matrix-synapse but is a full python singlespec spec file yielding * python2-matrix-synapse * python3-matrix-synapse but I would like at least one package to be or "provide" matrix-synapse. If not possible I would also be ok to build it just with one python version to end up with just "matrix-synapse". But again: What's the proper way? Regards, Oliver -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 7

[opensuse-packaging] Re: singlespec python and SLE_12_SP2_Backports
by Scott Bahling 07 Jul '17

07 Jul '17

On Fri, 2017-07-07 at 17:03 +0200, jan matejek wrote: > hello, > > On 5.7.2017 12:31, Scott Bahling wrote: > > What was the outcome of this? Is there something we can do within the > > Backports projects to fix the issue? Currently the multi version build > > is blocking us from submitting packages that require the python3 > > packages, but we conflict with the python2 versions in SLE. > > i wrote a proof-of-concept patch for python-rpm-macros that allows building only python3 versions of > blacklisted packages from SLE, without modifying the packages in question. See it at [1] for the > time being. Cool! We could add this to the Backports projects. We currently have a bot that updates the Backports rpmlint blacklist as new packages are added to SLE 12. We could piggy back off that to update the blacklist in the python-rpm-macros package. > However, there is still a problem: there are conflicts with the src.rpm, because, for instance, > python-six.src.rpm already exists in SLE. > I don't have a very good idea what to do about this. Is it possible to somehow change name of the > src.rpm package? If not, you can fork the package under a different name, but it's going to be a > fork, so at that point you can modify the spec in any case. > Alternately, could the multibuild magic somehow fix this? Maybe we can adjust the checks in the Backports projects to ignore src packages. I need to discuss that idea with others to identify any risks of doing so. I gut feeling is that we can do it. -Scott > m. > > > [1] https://build.opensuse.org/package/show/home:matejcik:rpm-macros-build-test… > > > > > > -Scott > > > >

1 0

[opensuse-packaging] singlespec python and SLE_12_SP2_Backports
by Todd Rme 05 Jul '17

05 Jul '17

In devel:languages:python, the new singlespec approach is causing problems with SLE_12_SP2_Backports build target. The issue is that this build target fails if a package includes files from any package in SLE, and packages that have this problem include some really critical ones like setuptools. This is a problem because in most cases only the python2 versions of the files are available from SLE, but the build failure means the python3 versions do not get published. This results in critical python3 packages needed for singlespec builds not being available. Currently more than half of the packages are either disabled or unresolvable, and that number is going to grow to almost every package as the singlespec conversion continues. The simplest solution would be to just disable that repo by default. However, if there (or could be) some way to selectively disable building python2 versions of specific packages just for that build target it might be better. -- 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] Upgrade gretl to upstream version dilemma
by Stathis Agrapidis 05 Jul '17

05 Jul '17

Hi everybody, I am trying to upgrade package gretl [1] to a newer version from upstream here [2]. Everything is fine for the openSUSE releases. However, the new upstream version requires gnuplot version >= 5 with cairo doc support which is not there for SLE12. Should I upgrade and push it to the science project repo and disable the build for SLE12? I know that OBS will keep the old binaries unless instructed otherwise. What is the workflow for such a case? Any other suggestions? Thanks for your time, Stathis [1] https://build.opensuse.org/package/show/science/gretl [2] https://build.opensuse.org/package/show/home:efagra:branches:science/gretl -- 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] ... testing for modified permissions
by Christian 05 Jul '17

05 Jul '17

Hi, can someone help me please with this: -------------------------------------------------------------------- [ 159s] package: otrs [ 159s] SuSEconfig.permissions modified files that are not properly handled! [ 159s] this will break rpm -V, ask ro for details. [ 159s] diff for both runs of rpm -V: [ 159s] +.M...... /srv/otrs/var/tmp [ 159s] -------------------------------------------------------------------- Link to project/package: https://build.opensuse.org/package/live_build_log/network:otrs:Test/otrs/SL… -- 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

3 3