Hi!
O no. Had promise myself to stop wining about 16.0.
Interesting that I receive a update of the package ’ suse-lifecycle
’ in my Leap 16 dailydriver…
The following 6 packages are going to be upgraded:
MozillaFirefox libpng16-16 libpng16-16-x86-64-v3 makedumpfile microsoft-edge-stable suse-lifecycle
And the information there:
https://www.suse.com/lifecycle is outdated.
…and regards
And your question is?
Hi Hui!
It is in the Open-chat category. Question? Please go back to RB times.I find it interesting that SLED15 will continue to 2031. All included(Gnome).
https://www.suse.com/lifecycle#suse-linux-enterprise-desktop-15
But why are this pack in leap16?
Regards
openSUSE Leap 16 follows the same lifecycle as SLES. SLED does absolutely not matter in this case.
https://en.opensuse.org/Lifetime
There is a difference between SLED snd SLES.
Yes
I know. (Flagship SLES15)Flag) SLED15 does diffidently matter in this case.
Regards
As SLED and SLES are different products, and Leap 16 is based on SLES 16 it is still unclear what you want to articulate.
And if you believe that SUSE provides wrong informations on their website, please contact SUSE (not openSUSE) and kindly show them their mistake.
Fine. Whatever. Where do you think all of this +50 000 that are advertised users come from, Serverinstallations maybe.
Regards
@jonte1 Enough! There are numerous SUSE based packages in Leap 16.0, users have the ability to switch (migrate) products if required.
We’ve told you before, this is not the place to bring SUSE issues. You need to take these issues to SUSE. The openSUSE project cannot do anything about it.
With Tumbleweed:
> LANG=C zypper search lifecycle
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+-------------------------+---------------------------------------------+--------
i | lifecycle-data-openSUSE | End of life dates for specific packages | package
i+ | zypper-lifecycle-plugin | Zypper subcommand for lifecycle information | package
Note: For an extended search including not yet activated remote resources please use 'zypper
search-packages'.
>
But – <Tool for displaying life cycle information>
Sorry, SUSE is in of control things. But why is suse-lifecykle package in my Leap16 Dist? Projekt openSUSE. Easy to get paranoid.
Regards
…
openSUSE Leap uses sources and binaries from SUSE Linux Enterprise (SLE), which gives Leap a level of stability unmatched by other Linux distributions, and combines that with community developments to give users, developers and sysadmins the best stable Linux experience available.
It’s upstream from Leap. But still, if you have questions for SUSE, you need to ask SUSE.
Why do you feel like this? Leap 16 is built from the same base as SLE, so SUSE-provided packages like suse-lifecycle are expected. It’s just shared infrastructure, not anything unusual.
As an everyday “regular” user out here, I’m confused what the “issue” is from the OP.
I logged into my Leap 16 machine, fired up Myrlyn, then did a Software search using the phrase “lifecycle” and chose the “Contains” search option … Myrlyn showed there is about six packages available (I might have the exact count rwong).
Anyway, after reading the package descriptions, I have no interest in the information they offer - nothing important and they don’t offer any advantage for my install. It’s simply information.
You’re not alone in that. It would be helpful if he would clearly state what he expects to get out of this discussion.
BTW this seems to be a little-known (and relatively new) feature in Myrlyn:
You can remain in “Auto” search mode now even if you prefer “contains” as the default: Click on the little wrench to toggle the default between “starts with” and “contains”.
More details and some screenshots here.
The mentioned package suse-lifecycle is a small utility program intended to provide support information for specific software included with SLES 16, SLES SAP 16, and SLE HA 16. It’s presumably only of limited use for most Leap users. But since Leap’s partial link to SLES is part of its appeal, it shouldn’t be a problem to include it. (Say if you’re prototyping something on Leap with the intention of deploying to SLES.)
Or if you are the sort of person (like me) who finds it interesting that Go gets a version bump twice yearly in those SUSE products, you might appreciate the tool or its data files. Either way, it shouldn’t hurt you in any way.
It looks like openSUSE doesn’t ship it’s own yaml data file for Leap for the tool but I guess there wouldn’t be much point since Leap’s support works differently. That may have something to do with the $2040 per year price difference. (Pricing not guaranteed. Lower prices may be available. Or not.)
