[opensuse-factory] Python-singelspec plans for Leap
Hi, what are the plans to bring singlespec packages into Leap 42.3? Is there a timeline? And also thoughts about retrofit to 42.2/42.1? Thx Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, May 10, 2017 at 7:22 AM, Axel Braun
Hi,
what are the plans to bring singlespec packages into Leap 42.3? Is there a timeline? And also thoughts about retrofit to 42.2/42.1?
Singlespec packages are being moved to leap shortly after they are accepted in Factory. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-05-10 13:22, Axel Braun wrote:
what are the plans to bring singlespec packages into Leap 42.3? Is there a timeline? And also thoughts about retrofit to 42.2/42.1?
I thought, such major changes could be left out there and only arrive in the next major version (Leap 15.0) but since I'm not much involved there, others might have different plans. Ciao Bernhard M.
On mercredi, 10 mai 2017 17.27:49 h CEST Bernhard M. Wiedemann wrote:
On 2017-05-10 13:22, Axel Braun wrote:
what are the plans to bring singlespec packages into Leap 42.3? Is there a timeline? And also thoughts about retrofit to 42.2/42.1?
I thought, such major changes could be left out there and only arrive in the next major version (Leap 15.0)
but since I'm not much involved there, others might have different plans.
Ciao Bernhard M.
Well as it's more technical things that real big changes, I wouldn't stop the progress move. If something is missing, people will have to use d:l:p repository anyways. The launch of 42.3 should invite people to stop using dlp3 -- 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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/11/2017 12:57 AM, Bernhard M. Wiedemann wrote:
On 2017-05-10 13:22, Axel Braun wrote:
what are the plans to bring singlespec packages into Leap 42.3? Is there a timeline? And also thoughts about retrofit to 42.2/42.1?
I thought, such major changes could be left out there and only arrive in the next major version (Leap 15.0)
but since I'm not much involved there, others might have different plans.
Your correct that the changes won't go back to Leap 42.1/42.2 (with the exception of using the d:l:p repo), the only way to do changes there is with a maintenance update and that doesn't fit the criteria. For the unreleased 42.3 which is the next release it does make a lot of sense to support it though, given many of the smaller python libs come directly from factory each leap point release and using single spec has a minimal impact on packages that don't use it (other then maybe needing to add a provides python2-XXX. I have some python modules that I maintain which would normally get a bugfix update for 42.3 but won't without singlespec as the factory version already uses it. -- 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
hello, the python-rpm-macros package is headed to SLE 12, which means that it will be available in Leap 42.3 (for sure) and older Leaps as well (probably). This means that it will be possible to build singlespec-based packages in Leap. They will be in "legacy" mode, that means that Python 2 packages will still be called "python-foo". Because of that, we might encounter some problems in cases where the new singlespec package is buildrequiring "python2-foo". Singlespec-enabled packages should automatically provide this symbol; unmodified packages, not surprisingly, will not. These will be solved on a case-by-case basis. The submission currently seems to be waiting on Factory acceptance (sr#494836 for 42.3, sr#494698 for Factory), so "a couple days" would be my expectation of a timeline. All of it is designed so that we can submit singlespec packages where it makes sense, without having to convert the entire Leap 42.3 release. Most likely only new submissions from Factory are going to be singlespec, and core packages will remain on SLE12 versions. This is especially true of 42.2 and 42.1 -- we gain the ability to add singlespec packages to the distribution, or upgrade existing packages to singlespec, but we will not be converting packages just for the fun of it. regards m. On 10.5.2017 13:22, Axel Braun wrote:
Hi,
what are the plans to bring singlespec packages into Leap 42.3? Is there a timeline? And also thoughts about retrofit to 42.2/42.1?
Thx Axel
participants (6)
-
Axel Braun -
Bernhard M. Wiedemann -
Bruno Friedmann -
jan matejek -
Simon Lees -
Todd Rme