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