[opensuse-packaging] No Leap repos anymore in devel:languages:python?
Hi packagers, Stefan observed that in d:l:p no Leap repositories are available anymore. There are Arm, PowerPC, zSystems, and Tumbleweed. Are there any reasons why they completely vanished? Can the Leap repos be readded again? I think, a lot of other repositories depend on it. :) (Please keep Stefan in CC) Thanks! -- Gruß/Regards, Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com http://lizards.opensuse.org/author/thomas-schraitle/ GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 22/08/2018 21:13, Thomas Schraitle wrote:
Hi packagers,
Stefan observed that in d:l:p no Leap repositories are available anymore. There are Arm, PowerPC, zSystems, and Tumbleweed.
Are there any reasons why they completely vanished? Can the Leap repos be readded again? I think, a lot of other repositories depend on it. :)
(Please keep Stefan in CC)
Thanks!
See https://lists.opensuse.org/opensuse-factory/2018-04/msg00698.html which I cross posted to this list on 20-04-2018 -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 2018-08-23 02:35, Simon Lees wrote:
On 22/08/2018 21:13, Thomas Schraitle wrote:
Hi packagers,
Stefan observed that in d:l:p no Leap repositories are available anymore. There are Arm, PowerPC, zSystems, and Tumbleweed.
Are there any reasons why they completely vanished? Can the Leap repos be readded again? I think, a lot of other repositories depend on it. :)
(Please keep Stefan in CC)
Thanks!
See https://lists.opensuse.org/opensuse-factory/2018-04/msg00698.html which I cross posted to this list on 20-04-2018
Why are the remaining 1.285 packages not provided for Leap anymore?
On Friday, 24 August 2018 20:11:04 ACST, Sebastian wrote:
On 2018-08-23 02:35, Simon Lees wrote:
On 22/08/2018 21:13, Thomas Schraitle wrote:
Hi packagers,
Stefan observed that in d:l:p no Leap repositories are available anymore. There are Arm, PowerPC, zSystems, and Tumbleweed.
Are there any reasons why they completely vanished? Can the Leap repos be readded again? I think, a lot of other repositories depend on it. :) ... See https://lists.opensuse.org/opensuse-factory/2018-04/msg00698.html which I cross posted to this list on 20-04-2018
Why are the remaining 1.285 packages not provided for Leap anymore?
If you are talking about the packages that were moved to d:l:p:misc the answer is because no one has stepped up to actively maintain them. If there are some packages there that you'd like to use myself and others on this list would be happy to help you learn, many likely only need minimal changes to get them to the point where they are acceptable in tumbleweed. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 2018-08-25 07:59, Simon Lees wrote:
On Friday, 24 August 2018 20:11:04 ACST, Sebastian wrote:
On 2018-08-23 02:35, Simon Lees wrote:
On 22/08/2018 21:13, Thomas Schraitle wrote:
Hi packagers,
Stefan observed that in d:l:p no Leap repositories are available anymore. There are Arm, PowerPC, zSystems, and Tumbleweed.
Are there any reasons why they completely vanished? Can the Leap repos be readded again? I think, a lot of other repositories depend on it. :) ... See https://lists.opensuse.org/opensuse-factory/2018-04/msg00698.html which I cross posted to this list on 20-04-2018 Why are the remaining 1.285 packages not provided for Leap anymore?
If you are talking about the packages that were moved to d:l:p:misc the answer is because no one has stepped up to actively maintain them. If there are some packages there that you'd like to use myself and others on this list would be happy to help you learn, many likely only need minimal changes to get them to the point where they are acceptable in tumbleweed.
No, I mean the packages in devel:languages:python: https://build.opensuse.org/project/show/devel:languages:python
On Monday, 27 August 2018 20:18:29 ACST, Sebastian wrote:
On 2018-08-25 07:59, Simon Lees wrote:
On Friday, 24 August 2018 20:11:04 ACST, Sebastian wrote: ...
No, I mean the packages in devel:languages:python: https://build.opensuse.org/project/show/devel:languages:python
From the package description: Backporting of packages against older distribution releases should not be happening in this project, only build verification. If a package is needed on any of the older openSUSE products then maintenance update is to be created. Alternatively for SLE products submission by an interested party should be done by openSUSE:Backports project. If you just need the newest packages, please consider using devel:languages:python:backports instead. 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. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Am Montag, 27. August 2018, 13:26:09 CEST schrieb Simon Lees:
On Monday, 27 August 2018 20:18:29 ACST, Sebastian wrote:
On 2018-08-25 07:59, Simon Lees wrote:
On Friday, 24 August 2018 20:11:04 ACST, Sebastian wrote: ...
No, I mean the packages in devel:languages:python: https://build.opensuse.org/project/show/devel:languages:python
From the package description: Backporting of packages against older distribution releases should not be happening in this project, only build verification. If a package is needed on any of the older openSUSE products then maintenance update is to be created. Alternatively for SLE products submission by an interested party should be done by openSUSE:Backports project. If you just need the newest packages, please consider using devel:languages:python:backports instead.
Why maintenance update? I only would have a working version in devel. So it can put in newer Leap version. Or if somebody would have newest package in Leap. In my book, before the change, it was simpler, quicker and need many less work than now. It was much, much better than now.
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. :-(
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 Tumbleweed. Regards Eric -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 27/08/2018 23:15, Eric Schirra wrote:
Am Montag, 27. August 2018, 13:26:09 CEST schrieb Simon Lees:
On Monday, 27 August 2018 20:18:29 ACST, Sebastian wrote:
On 2018-08-25 07:59, Simon Lees wrote:
On Friday, 24 August 2018 20:11:04 ACST, Sebastian wrote: ...
No, I mean the packages in devel:languages:python: https://build.opensuse.org/project/show/devel:languages:python
From the package description: Backporting of packages against older distribution releases should not be happening in this project, only build verification. If a package is needed on any of the older openSUSE products then maintenance update is to be created. Alternatively for SLE products submission by an interested party should be done by openSUSE:Backports project. If you just need the newest packages, please consider using devel:languages:python:backports instead.
Why maintenance update? I only would have a working version in devel. So it can put in newer Leap version. Or if somebody would have newest package in Leap. In my book, before the change, it was simpler, quicker and need many less work than now. It was much, much better than now.
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.
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 Tumbleweed.
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. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
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.
hmm. But i need at beginning many python packages which are not in distro at that time.
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 Tumbleweed.
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. Regards Eric -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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.
hmm. But i need at beginning many python packages which are not in distro at that time.
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 Tumbleweed.
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) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (4)
-
Eric Schirra -
Sebastian -
Simon Lees -
Thomas Schraitle