[opensuse-factory] openSUSE Leap 15.2 start of development
Hi, After the release is before the release. So engines for 15.2 are on already. It builds, passes openQA and even released the first iso image to download.opensuse.org¹ last week. As usual you can find the sources in openSUSE:Leap:15.2 in OBS². The project is in a very early stage so it's not much more than 15.1 + updates yet. 15.2 again will be a service pack like update in the 15 series of Leap. As such by default packages will *not* be updated to Factory versions automatically and it's discouraged to drop packages. The core packages will be inherited automatically from SLE15SP2 that also started development recently. From what we know already we will get version updates for the Kernel, GNOME and Qt from SLE. If you think a package you take care of needs to be updated, please check whether the package is inherited from Factory or SLE. If it's from Factory submit manually once to let the tools know to follow Factory. If the package is from SLE please file a bug report and/or get in touch with the maintainer on SLE side ASAP. Updates for packages coming from SLE need to be evaluated this year still to have a chance. Note that despite some version updates in core components we do not aim at providing the latest and greatest of everything in Leap 15. So no batch updates please! cu Ludwig [1] http://download.opensuse.org/distribution/leap/15.2/iso/ [2] https://build.opensuse.org/project/dashboard/openSUSE:Leap:15.2 -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, 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 8/14/19 7:41 PM, Ludwig Nussel wrote:
Hi,
After the release is before the release. So engines for 15.2 are on already. It builds, passes openQA and even released the first iso image to download.opensuse.org¹ last week.
As usual you can find the sources in openSUSE:Leap:15.2 in OBS². The project is in a very early stage so it's not much more than 15.1 + updates yet.
15.2 again will be a service pack like update in the 15 series of Leap. As such by default packages will *not* be updated to Factory versions automatically and it's discouraged to drop packages.
The core packages will be inherited automatically from SLE15SP2 that also started development recently. From what we know already we will get version updates for the Kernel, GNOME and Qt from SLE.
Do we know if this will also likely see a newer version of meson? A couple of my upstream are now requiring 0.47 due to new features, re writing the build script without those features isn't a simple task and may not be possible. These packages using such features would be good candidates to go into 15.2. -- 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
On Thu, 2019-08-15 at 10:01 +0930, Simon Lees wrote:
On 8/14/19 7:41 PM, Ludwig Nussel wrote:
Hi,
After the release is before the release. So engines for 15.2 are on already. It builds, passes openQA and even released the first iso image to download.opensuse.org¹ last week.
As usual you can find the sources in openSUSE:Leap:15.2 in OBS². The project is in a very early stage so it's not much more than 15.1 + updates yet.
15.2 again will be a service pack like update in the 15 series of Leap. As such by default packages will *not* be updated to Factory versions automatically and it's discouraged to drop packages.
The core packages will be inherited automatically from SLE15SP2 that also started development recently. From what we know already we will get version updates for the Kernel, GNOME and Qt from SLE.
Do we know if this will also likely see a newer version of meson? A couple of my upstream are now requiring 0.47 due to new features, re writing the build script without those features isn't a simple task and may not be possible. These packages using such features would be good candidates to go into 15.2.
Expecting meson 0.47+ is realistic. From what U heard, the target GNOME version shall be 3.32 or 3.34. Already GNOME 3.32 requires meson 0.47, going for GNOME 3.34 will even require meson 0.49.2+ Cheers Dominique
Hi Ludwig, Am Mittwoch, 14. August 2019, 12:11:44 CEST schrieb Ludwig Nussel:
After the release is before the release. So engines for 15.2 are on already. It builds, passes openQA and even released the first iso image to download.opensuse.org¹ last week.
Thanks for the info. Timeline just for completion: https://en.opensuse.org/openSUSE:Roadmap Cheers Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, August 14, 2019 5:11:44 AM CDT Ludwig Nussel wrote:
If you think a package you take care of needs to be updated, please check whether the package is inherited from Factory or SLE. If it's from Factory submit manually once to let the tools know to follow Factory. If the package is from SLE please file a bug report and/or get in touch with the maintainer on SLE side ASAP. Updates for packages coming from SLE need to be evaluated this year still to have a chance.
Checking where a package is currently originating can be done via several methods: - origin manager web interface [1] - the OBS supplemental userscript [2] - operator wrapper API server [3] - origin osc plugin `osc origin -p openSUSE:Leap:15.2 package adminer` (zypper in osc-plugin-origin) The first three browser based options require an active OBS session while the command line requires an active osc session. One can also submit from the desired origin using the web interface. After selecting a package of interest the potential origins will appear. Clicking on an origin will show a diff and the submit icon can be used to created a submit request from that origin to the target project (Leap 15.2). This makes it easy to see where packages originate, diff, and switch origin as desired. After a submission is accepted future updates will automatically be submitted. An example after selecting adminer package and clicking on the openSUSE:Factory potential origin [4]. The submit icon, on the end of Factory origin line, was used to create the request referenced in the table on the left. Enjoy! [1] https://github.com/openSUSE/openSUSE-release-tools/tree/master/userscript [2] https://osrt.opensuse.org/web/origin-manager/#openSUSE:Leap:15.2 [3] https://operator.opensuse.org/origin/package/openSUSE:Leap:15.2/adminer [4] https://paste.opensuse.org/view/raw/59108286 -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, August 16, 2019 4:14:58 PM CDT James Berry wrote:
[1] https://github.com/openSUSE/openSUSE-release-tools/tree/master/ userscript [2] https://osrt.opensuse.org/web/origin-manager/#openSUSE:Leap:15.2
1 and 2 are reversed. 1 is the userscript and 2 points to web interface. -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 8/17/19 6:44 AM, James Berry wrote:
On Wednesday, August 14, 2019 5:11:44 AM CDT Ludwig Nussel wrote:
If you think a package you take care of needs to be updated, please check whether the package is inherited from Factory or SLE. If it's from Factory submit manually once to let the tools know to follow Factory. If the package is from SLE please file a bug report and/or get in touch with the maintainer on SLE side ASAP. Updates for packages coming from SLE need to be evaluated this year still to have a chance.
Checking where a package is currently originating can be done via several methods:
- origin manager web interface [1] - the OBS supplemental userscript [2] - operator wrapper API server [3] - origin osc plugin `osc origin -p openSUSE:Leap:15.2 package adminer` (zypper in osc-plugin-origin)
Here is option 5 that probably doesn't require anything other then the
stuff you already have on your machine
osc -A https://api.opensuse.org cat openSUSE:Leap:15.1:Update 00Meta
lookup.yml | grep
On Friday, August 16, 2019 6:49:39 PM CDT Simon Lees wrote:
Here is option 5 that probably doesn't require anything other then the stuff you already have on your machine
osc -A https://api.opensuse.org cat openSUSE:Leap:15.1:Update 00Meta lookup.yml | grep
That method only works with previous tooling which had a fair number of edgecases. The last step on my list is to request deletion of that package so do not use it to source such information. Presumably curl or hitting a web- page is something one can do just as easily. -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Sorry for digging up this old post, but I tried to follow up on my packages today and and ran into issues with the origin manger web interface. Am Freitag, 16. August 2019, 23:14:58 CEST schrieb James Berry:
On Wednesday, August 14, 2019 5:11:44 AM CDT Ludwig Nussel wrote:
If you think a package you take care of needs to be updated, please check whether the package is inherited from Factory or SLE. If it's from Factory submit manually once to let the tools know to follow Factory. If the package is from SLE please file a bug report and/or get in touch with the maintainer on SLE side ASAP. Updates for packages coming from SLE need to be evaluated this year still to have a chance.
Checking where a package is currently originating can be done via several methods:
- origin manager web interface [1]
When going to https://osrt.opensuse.org/web/origin-manager/#openSUSE:Leap:15.2 which was linked both here and in the openSUSE:Leap:15.2 project on OBS, I can see only the table headers and below them a read message reading ERROR which disappears after a couple of seconds. Looking at the network requests in Firefox it seems that https:// operator.opensuse.org/origin/list/openSUSE:Leap:15.2 is called from JavaScript but returning a 502.
The first three browser based options require an active OBS session while the command line requires an active osc session.
I made sure that I am logged in to build.opensuse.org but this did not solve the issue. Now, this might just be me not being the smartest guy around. So is there anything else obvious that I might be doing wrong or is the system currently also broken for others?
One can also submit from the desired origin using the web interface. After selecting a package of interest the potential origins will appear.
While I am pretty sure none of my packages originate from SLES, this is the feature I'd have loved to use, simply to ensure I am submitting from the correct Project an OBS as sadly I failed to fully comprehend the desired workflow. When doing this manually, where do I need to submit from? Do I create a submit request from openSUSE:Factory to openSUSE:Leap:15.2? Thanks, Matthias -- Dr. Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke
Hi Again, Am Samstag, 19. Oktober 2019, 11:37:51 CEST schrieb Matthias Bach:
One can also submit from the desired origin using the web interface. After selecting a package of interest the potential origins will appear.
While I am pretty sure none of my packages originate from SLES, this is the feature I'd have loved to use, simply to ensure I am submitting from the correct Project an OBS as sadly I failed to fully comprehend the desired workflow.
When doing this manually, where do I need to submit from? Do I create a submit request from openSUSE:Factory to openSUSE:Leap:15.2?
I just found https://en.opensuse.org/openSUSE:Packaging_for_Leap. I wonder why I didn't stumble across that earlier but it answers my question. The problem with the the Origin Manager Web UI obviously remains but it's no longer blocking issue for me then. Sorry for the noise, Matthias -- Dr. Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke
participants (6)
-
Axel Braun -
Dominique Leuenberger / DimStar -
James Berry -
Ludwig Nussel -
Matthias Bach -
Simon Lees