Mailinglist Archive: opensuse-packaging (104 mails)

< Previous Next >
Re: [opensuse-packaging] No Leap repos anymore in devel:languages:python?

On 29/08/2018 06:25, Eric Schirra wrote:
Am Dienstag, 28. August 2018, 03:46:39 CEST schrieb Simon Lees:

As far as I can see all the packages in d:l:p that are also in
tumbleweed should be in devel:languages:python:backports so I guess I
should ask what your trying to achieve.

This is not right.
Only packages which start with python are in backports.
Every other packages (e.g. certbot) must separate insert in the sync
script. I think this is not a good idea.
And you find nobody who do that.
You have infinite discussion. :-(

There are less then 20 packages in d:l:p and almost all of them
including things like certbot are utilities rather then python libraries
and would probably be better in a different devel repo.

But i need at beginning many python packages which are not in distro at that

This should be less of an issue given that everything in d:l:p should
now be in the distro.

Other example are python packages which are needed for other packages in
other repos.
Also infinite discussion with no result.
You see no more if this package (e.g. calibre) is build for 42.3, 15.0 and

I've personally tried to avoid doing this in the past but if you really
need to, what I tend to do and what is probably better is to link the
packages you need into the other devel projects, then only enable it to
build for the distro's you need.

Have try this.
I have try request a branch for a python package which calibre need.
The repoowner declined it and say i should make a linkpac. But in meta it is
the same.
For linkpac i have no rights.
Now repoowner make a linkpac but disable it for tumbleweed.
Many days, weeks the package was not in Tumbleweed and so the new version for
calibre could not build.

This is possibly still better then what was happening before were some
projects were linking to d:l:p without some people realizing which would
mean that packages would build in the devel repo but would then fail
when submitted to tumbleweed and it was a pain to work out why. In
general it shouldn't normally take long for version updates to make it
from submission to acceptance in tumbleweed, and if there is an issue
you can always as the repo maintainer if they are willing to enable the
tumbleweed build for a short time.


Simon Lees (Simotek)

Emergency Update Team
SUSE Linux Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

< Previous Next >