[opensuse-factory] openSUSE Leap 15.1 in the works
Hi, As most of you already noticed Leap 15.1 is in the works on OBS in openSUSE:Leap:15.1. As with it's predecessors we use a rolling development process until the final release. The release is expected May 2019. Right now 15.1 calls itself Alpha even though a release in this early stage probably never has been so green in openQA. Following SLE 15 SP1 there are also no really deep changes on the horizon so far. We will stay with the same base system as 15.0. 15.1 automatically pulls maintenance updates from 15.0, as well as updates from SLE 15 SP1 that is in development too. Packages that originally came from Factory in 15.0 will not automatically update to Factory versions. To make individual packages in 15.1 follow Factory again, updates for such packages have to be submitted manually once from Factory to 15.1. Please refrain from mass submitting anything to 15.1. If you maintain a component that has good reasons to update a larger number of packages in 15.1, please get in touch with the release team¹ before submitting! We will also make an effort to automatically submit packages for you that were added to Factory after 15.0 and build fine for 15.1. Watch out for review requests as Factory package maintainers need to approve such submissions. In any case, larger updates and new components should get integrated latest in March to still allow for beta testing. If you have anything that comes late, please contact the release team. As usual all the details how to submit packages, file bugs etc for Leap 15.1 can be found in the wiki². And if not.. it's a wiki, please fill in the missing parts :-) cu Ludwig [1] mailto:opensuse-releaseteam@opensuse.org [2] https://en.opensuse.org/openSUSE:Packaging_for_Leap -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Dienstag, 20. November 2018 14:08:16 CET Ludwig Nussel wrote:
Hi,
As most of you already noticed Leap 15.1 is in the works on OBS in openSUSE:Leap:15.1. As with it's predecessors we use a rolling development process until the final release. The release is expected May 2019.
Right now 15.1 calls itself Alpha even though a release in this early stage probably never has been so green in openQA. Following SLE 15 SP1 there are also no really deep changes on the horizon so far. We will stay with the same base system as 15.0.
15.1 automatically pulls maintenance updates from 15.0, as well as updates from SLE 15 SP1 that is in development too. Packages that originally came from Factory in 15.0 will not automatically update to Factory versions. To make individual packages in 15.1 follow Factory again, updates for such packages have to be submitted manually once from Factory to 15.1.
Hi Ludwig, Leap 15.0 got some blaming in a well known and regarded german computer magazine due to the "outdated" kernel/graphics stack [1]. As far as I can see in [2], there were some updates, but it lacks support for VegaM (Intel CPU + AMD iGPU, already available), Vega12 (Marketing name: Radeon Pro Vega 16/20, e.g newest Macbook Pro) and Vega 20 (Radeon Instinct MI50/60) and the Raven APUs (Ryzen 3/5 2xxxG). Even Vega56/64 is still guarded by the module parameter amdgpu.exp_hw_support=1. Are there plans to also get these included until the release? Kind regards, and keep up the good work, Stefan [1] Sorry - subscription only: https://www.heise.de/ct/ausgabe/2018-14-OpenSuse-Leap-15-0-mit-weiterem-Upda... --- DE: Leap unterstützt moderne Hardware aber trotzdem schlechter als frischer ausgestattete Distributionen. So hat gerade der für moderne Radeon-Grafikchips zuständige Kernel-Treiber Amdgpu im letzten Jahr massive Fortschritte gemacht, die Leap fehlen. Die Distribution weiß daher nichts mit AMDs aktuellen High- End-GPUs der Vega-Serie anzufangen; bei vielen Radeon-Modellen der 400er- und 500er-Serie fehlen für besonders hochauflösende Displays und die Audio-Ausgabe wichtige Treiberfunktionen. --- EN: Leap supports modern hardware but still worse than freshly equipped distributions. For example, the kernel driver Amdgpu, which is responsible for modern Radeon graphics chips, has made massive progress over the last year, which Leap lacks. The distribution therefore does not know how to handle AMD's current high-end Vega series GPUs; Many Radeon models of the 400 and 500 series lack important driver functions for particularly high-resolution displays and the audio output. --- [2] https://kernel.opensuse.org/cgit/kernel/log/drivers/gpu/drm/amd/amdgpu? h=SLE15-SP1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
(Cc-ing involved people) On Tuesday, 20 November 2018 17:34 Brüns, Stefan wrote:
Leap 15.0 got some blaming in a well known and regarded german computer magazine due to the "outdated" kernel/graphics stack [1].
As far as I can see in [2], there were some updates, but it lacks support for VegaM (Intel CPU + AMD iGPU, already available), Vega12 (Marketing name: Radeon Pro Vega 16/20, e.g newest Macbook Pro) and Vega 20 (Radeon Instinct MI50/60) and the Raven APUs (Ryzen 3/5 2xxxG).
Even Vega56/64 is still guarded by the module parameter amdgpu.exp_hw_support=1.
Are there plans to also get these included until the release?
For the record: we don't have an openSUSE-15.1 branch yet so what is in 15.1 snapshots at the moment is most likely a copy of 15.0 kernel. There is going to be a DRM backport for SLE15-SP1 but AFAIK it's not in the branch yet. But I don't know which hardware is going to be supported, maybe Thomas or Petr could provide more details. Michal
Kind regards, and keep up the good work,
Stefan
[1] Sorry - subscription only: https://www.heise.de/ct/ausgabe/2018-14-OpenSuse-Leap-15-0-mit-weitere m-Update-Mechanismus-4085811.html --- DE: Leap unterstützt moderne Hardware aber trotzdem schlechter als frischer ausgestattete Distributionen. So hat gerade der für moderne Radeon-Grafikchips zuständige Kernel-Treiber Amdgpu im letzten Jahr massive Fortschritte gemacht, die Leap fehlen. Die Distribution weiß daher nichts mit AMDs aktuellen High- End-GPUs der Vega-Serie anzufangen; bei vielen Radeon-Modellen der 400er- und 500er-Serie fehlen für besonders hochauflösende Displays und die Audio-Ausgabe wichtige Treiberfunktionen. --- EN: Leap supports modern hardware but still worse than freshly equipped distributions. For example, the kernel driver Amdgpu, which is responsible for modern Radeon graphics chips, has made massive progress over the last year, which Leap lacks. The distribution therefore does not know how to handle AMD's current high-end Vega series GPUs; Many Radeon models of the 400 and 500 series lack important driver functions for particularly high-resolution displays and the audio output. ---
[2] https://kernel.opensuse.org/cgit/kernel/log/drivers/gpu/drm/amd/amdgp u? h=SLE15-SP1
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 21 Nov 2018 07:47:43 +0100, Michal Kubecek wrote:
(Cc-ing involved people)
On Tuesday, 20 November 2018 17:34 Brüns, Stefan wrote:
Leap 15.0 got some blaming in a well known and regarded german computer magazine due to the "outdated" kernel/graphics stack [1].
As far as I can see in [2], there were some updates, but it lacks support for VegaM (Intel CPU + AMD iGPU, already available), Vega12 (Marketing name: Radeon Pro Vega 16/20, e.g newest Macbook Pro) and Vega 20 (Radeon Instinct MI50/60) and the Raven APUs (Ryzen 3/5 2xxxG).
Even Vega56/64 is still guarded by the module parameter amdgpu.exp_hw_support=1.
Are there plans to also get these included until the release?
For the record: we don't have an openSUSE-15.1 branch yet so what is in 15.1 snapshots at the moment is most likely a copy of 15.0 kernel.
There is going to be a DRM backport for SLE15-SP1 but AFAIK it's not in the branch yet. But I don't know which hardware is going to be supported, maybe Thomas or Petr could provide more details.
The plan is to upgrade the whole DRM stack to 4.19+ kernel level, so essentially all new graphics devices as of 4.19 will be supported. vboxvideo might be out of scope, though, as it's in staging. We can take a look and backport if requested, too. The user-space stack will be updated to the decent versions as well. thanks, Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 22 Nov 2018 at 10:25, Takashi Iwai <tiwai@suse.de> wrote:
On Wed, 21 Nov 2018 07:47:43 +0100, Michal Kubecek wrote:
For the record: we don't have an openSUSE-15.1 branch yet so what is in 15.1 snapshots at the moment is most likely a copy of 15.0 kernel.
There is going to be a DRM backport for SLE15-SP1 but AFAIK it's not in the branch yet. But I don't know which hardware is going to be supported, maybe Thomas or Petr could provide more details.
The plan is to upgrade the whole DRM stack to 4.19+ kernel level, so essentially all new graphics devices as of 4.19 will be supported.
vboxvideo might be out of scope, though, as it's in staging. We can take a look and backport if requested, too.
The user-space stack will be updated to the decent versions as well.
For the record, the work you guys do in this area is downright amazing We're lucky to have you working on our kernel, and I realise I don't say thank you enough So, Thank You - Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 22 Nov 2018 10:25:27 +0100 Takashi Iwai <tiwai@suse.de> wrote:
On Wed, 21 Nov 2018 07:47:43 +0100, Michal Kubecek wrote:
(Cc-ing involved people)
On Tuesday, 20 November 2018 17:34 Brüns, Stefan wrote:
Leap 15.0 got some blaming in a well known and regarded german computer magazine due to the "outdated" kernel/graphics stack [1].
As far as I can see in [2], there were some updates, but it lacks support for VegaM (Intel CPU + AMD iGPU, already available), Vega12 (Marketing name: Radeon Pro Vega 16/20, e.g newest Macbook Pro) and Vega 20 (Radeon Instinct MI50/60) and the Raven APUs (Ryzen 3/5 2xxxG).
Even Vega56/64 is still guarded by the module parameter amdgpu.exp_hw_support=1.
Are there plans to also get these included until the release?
For the record: we don't have an openSUSE-15.1 branch yet so what is in 15.1 snapshots at the moment is most likely a copy of 15.0 kernel.
There is going to be a DRM backport for SLE15-SP1 but AFAIK it's not in the branch yet. But I don't know which hardware is going to be supported, maybe Thomas or Petr could provide more details.
The plan is to upgrade the whole DRM stack to 4.19+ kernel level, so essentially all new graphics devices as of 4.19 will be supported.
I have now created a kernel branch for Leap 15.1 and made my first kernel submission (SR#656220). However, we have not sorted out the DRM update yet. The policy requires us to split it into individual patches, but as you might know, upstream DRM development happens in a somewhat non-linear way, so this is a challenge... In short, the DRM part is still in the works. We definitely aim to have everything in place until end of the year. I hope you get an updated graphics stack for Christmas present. ;-) Petr T
vboxvideo might be out of scope, though, as it's in staging. We can take a look and backport if requested, too.
The user-space stack will be updated to the decent versions as well.
thanks,
Takashi
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am 20.11.18 um 14:08 schrieb Ludwig Nussel:
Right now 15.1 calls itself Alpha even though a release in this early stage probably never has been so green in openQA. Following SLE 15 SP1 there are also no really deep changes on the horizon so far. We will stay with the same base system as 15.0.
I thought I asked this before but cannot remember an outcome or where that might have been. Also read the wiki "packaging for Leap" but it's not clear on my question. Therefore following up here. Can the process be described for upgrade requests for packages which have their origin at SUSE:SLE-15:* ? There are several cases. I'm mainly interested in the view of the Factory package maintainer. (Others still require a review from that one anyway.) I'm somewhat responsible for a few packages from a Factory perspective. Still the packages on Leap are in sync with SLE15 and (probably) have a SLE maintainer (not necessarily known to the public since OBS does not always have that I _think_). I would like to see some of the packages being updated for 15.1 but I'm unsure if I can just submit into openSUSE:Leap:15.1 and magic will happen so these will be reviewed by the relevant people. Or is there no way anyway to touch those packages in normal cases? Thanks, Wolfgang
On Mon, Jan 28, 2019 at 04:10:30PM +0100, Wolfgang Rosenauer wrote:
Hi,
Am 20.11.18 um 14:08 schrieb Ludwig Nussel:
Right now 15.1 calls itself Alpha even though a release in this early stage probably never has been so green in openQA. Following SLE 15 SP1 there are also no really deep changes on the horizon so far. We will stay with the same base system as 15.0.
I thought I asked this before but cannot remember an outcome or where that might have been. Also read the wiki "packaging for Leap" but it's not clear on my question. Therefore following up here.
Can the process be described for upgrade requests for packages which have their origin at SUSE:SLE-15:* ?
There are several cases. I'm mainly interested in the view of the Factory package maintainer. (Others still require a review from that one anyway.)
I'm somewhat responsible for a few packages from a Factory perspective. Still the packages on Leap are in sync with SLE15 and (probably) have a SLE maintainer (not necessarily known to the public since OBS does not always have that I _think_).
I would like to see some of the packages being updated for 15.1 but I'm unsure if I can just submit into openSUSE:Leap:15.1 and magic will happen so these will be reviewed by the relevant people.
Or is there no way anyway to touch those packages in normal cases?
It could be done via bugzilla request and maintenance could forward it. Include me in CC. Internally we follow quite some buerocratic paths though, so not all requests we can handle :/ Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Wolfgang Rosenauer schrieb:
Am 20.11.18 um 14:08 schrieb Ludwig Nussel:
Right now 15.1 calls itself Alpha even though a release in this early stage probably never has been so green in openQA. Following SLE 15 SP1 there are also no really deep changes on the horizon so far. We will stay with the same base system as 15.0.
I thought I asked this before but cannot remember an outcome or where that might have been. Also read the wiki "packaging for Leap" but it's not clear on my question. Therefore following up here.
Can the process be described for upgrade requests for packages which have their origin at SUSE:SLE-15:* ?
There are several cases. I'm mainly interested in the view of the Factory package maintainer. (Others still require a review from that one anyway.)
I'm somewhat responsible for a few packages from a Factory perspective. Still the packages on Leap are in sync with SLE15 and (probably) have a SLE maintainer (not necessarily known to the public since OBS does not always have that I _think_).
In general it is desireable to have the SLE package maintainer also be the Factory package maintainer. However, some SLE packages actually just do not have a dedicated maintainer.
I would like to see some of the packages being updated for 15.1 but I'm unsure if I can just submit into openSUSE:Leap:15.1 and magic will happen so these will be reviewed by the relevant people.
There's no magic. As Marcus wrote opening a bug report is the official procedure and the best way especially if it's several packages or something bigger. The window of updating stuff in SLE is closing soon though. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 29/01/2019 03:10, Ludwig Nussel wrote:
Wolfgang Rosenauer schrieb:
Am 20.11.18 um 14:08 schrieb Ludwig Nussel:
Right now 15.1 calls itself Alpha even though a release in this early stage probably never has been so green in openQA. Following SLE 15 SP1 there are also no really deep changes on the horizon so far. We will stay with the same base system as 15.0.
I thought I asked this before but cannot remember an outcome or where that might have been. Also read the wiki "packaging for Leap" but it's not clear on my question. Therefore following up here.
Can the process be described for upgrade requests for packages which have their origin at SUSE:SLE-15:* ?
There are several cases. I'm mainly interested in the view of the Factory package maintainer. (Others still require a review from that one anyway.)
I'm somewhat responsible for a few packages from a Factory perspective. Still the packages on Leap are in sync with SLE15 and (probably) have a SLE maintainer (not necessarily known to the public since OBS does not always have that I _think_).
In general it is desireable to have the SLE package maintainer also be the Factory package maintainer. However, some SLE packages actually just do not have a dedicated maintainer.
All SLE packages should have a bugowner who is atleast responsible for handling L3 bugs, this person should also be a factory bugowner and ultimately responsible for the state of the package in factory under SUSE's internal factory first policy. We know of a number of packages where this isn't currently the case and I have been given some time in the coming months to address this. If you know of cases where packages in Leap / Tumbleweed should be coming from SLE but the bugowner isn't set accordingly and this is causing issues feel free to let me know and i'll address them first, otherwise i'll just work my way down the list. Cheers -- 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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Brüns, Stefan -
Ludwig Nussel -
Marcus Meissner -
Michal Kubecek -
Petr Tesarik -
Richard Brown -
Simon Lees -
Takashi Iwai -
Wolfgang Rosenauer