opensuse / release-notes-opensuse Goto Github PK

Hi,

In the "gap" package removal note:

gap: Removed because the package is not FHS-compliant. For more information, see .

The bugzilla link mentions "artha" package removal (you can see this in the screnshoot below)

Hi,

The release notes release-notes.pot file still refers to KDE4 and Qt 4 application. I propose to remove this paragraph since we're at Qt6 and Plasma 6 on Tumbleweed and Plasma 5 is mainstream for years.

See below reference to the line containing said paragraph.

Before making changes to the POT file I feel it safer to discuss this first.

Kind regards,

Natasha

Isn't it "repo-update" instead of "repo-sle-update"?

Hi,

Reviewing the release notes I came across this portion of text:

12 GB seems a bit meager for a btrfs filesystem. For Leap this is quite limited. As for TW and it's frequent update cycle it would be a problem because the snapshots will fill the filesystem in no time. Maybe another figure would be wise, but which figure should that be?

Kind regards,

Natasha

https://bugzilla.suse.com/show_bug.cgi?id=1185621

Hi,

I've noticed the RN for openSUSE Leap15.6 diverge quite a lot from the SLESD 15 SP6 RN. Both in contents (of course there is a divergence in software) and Layout. I am willing with the goal set to Leap 16 to get the RN more in line with the SLESD RN. I would like to know whether such an undertaking would be appreciated or unwanted/unneeded.

Kind regards,

Natasha

Description

There is an integration and compatibility issue between GNU/Linux Suse Linux ES 15 SP3/SP4 with Kubernetes/Rancher and virtual machines processed by Hypervisor VMWare ESXi 7.0.x. The issue impacts the integration of virtualized network layers Level0 – Level1 – Level2. My Managed Service & Infrastructure Delivery team detect this problem inside customer environment and replicate the issue is Almaviva Labs.

we discover that VXLAN (Flannel) network defined as Overlay Network of Kubernetes doesn’t properly work, in particular we understood that package encapsulation between different network levels was not correctly managed by Linux kernel on some GNU/Linux distribution, like Ubuntu 18.04, Ubuntu 20.04 e Open SUSE Leap 15.3, SUSE Linux ES 15 SP3/SP4, etc.
This compatibility issue inside virtualization software layer of network (vxlan encapsulation e checksum offloading) is even documented inside official documentation portal of RKE2: Known Issues and Limitations - RKE2 - Rancher’s Next Generation Kubernetes Distribution

Solutions

Below the identified solutions:

Team identifies multiple solutions to solve this issue, but some of them are not applicable in production environment:

1. Apply a downgrade of Hypervisor version, for example VMware vSphere (ESXi) 6.x.x. This is not suggested because apply a downgrade means have software not updated with less functionalities and last security patch.

2. Use a different GNU/Linux distribution like Red-Hat 8.5 or 9.x / Ubuntu 22.04.x LTS / Rocky Linux 8.5-9.x / Alma Linux 8.5-9.0;

3. Change the CNI plug-in of Kubernetes. This change requires a big effort in configuration and test to understand if there is some limitation or issues.

4. Change the virtual network adapter inside VMware vSphere Hypervisor (ESXi) 7.0.x to force the hypervisor to change modules and virtualization connectors between different internal stack so that the Overlay Network can properly work.

The team decided to apply the solution 4 and after setting change inside Hypervisor the issue is solved and pods inside Kubernetes properly communicate on Overlay network

Created by
Almaviva
Managed Service & Infrastructure Delivery

https://en.opensuse.org/openSUSE:Release_Notes
shows current opensuse 15.1, but when I use the link 'Deutsch' the german site an old version: https://de.opensuse.org/Versionshinweise

Further: Following the 'latest' link to https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.3/RELEASE-NOTES.de.html
it shows 'Veröffentlicht: 2019-07-01'
And the first sentence below:
'Das Ende der Betreuungszeit für openSUSE Leap 42.3 wurde jetzt erreicht.'

WTF. So released and end support date on the same day? ;-)

Well, this versioning with leap, tumbleweed, 42, 13, 15 is soo annoying/confusing. Stick to normal versioning 15, 15.1, ... please. Even renaming the '42er' releases to something 14? would help.

BTW: It would be great to have an official opensuse 15.1 vagrant box or documented how to reproducible build it.

https://app.vagrantup.com/boxes/search?utf8=%E2%9C%93&sort=updated&provider=virtualbox&q=opensuse+15.1

We're getting 404 after clicking on
https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/part-basics.html

Which is referenced from RN.
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.5/index.html#installation

Either we should make particular docs available again or drop the references.

fontinfo utility was removed as it was to my surprise in stable release for which it was never intended for.

Hi,

The first link on this line is not working. Where is it supposed to link to?

Should it be this link? https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.6/index.html

Kind regards,

Natasha

In the package, we have a .desktop file for susehelp. Not sure which software is picking that up still.

• KDE Help apparently still supports scrollkeeper but does not seem to pick it up..? Needs clarifying.
• Gnome's Yelp definitely does not pick this up, so we need to generate a .page file it. We have a DAPS function to create a Yelp .page, but this might still create some issues: Yelp (I think) expects files in a certain directory on the system where the release notes usually aren't. Changing those locations will also mean that other things might break.
• YaST: expects release notes apparently at a hardcoded location: https://github.com/yast/yast-installation/blob/master/src/lib/installation/clients/inst_release_notes.rb#L67

xml2po has issues with name spaces, poxml does not seem to be affected by this...

Seems like a word or something is missing in this string:
https://github.com/openSUSE/release-notes-openSUSE/blob/master/xml/release-notes.xml#L210(para)

Maybe it should be "moved from the ... to the ..." or "moved from the ... and ...".

Not sure if this is the correct repo to report this against but the release notes for the recently released Leap Micro 5.3 are missing from https://doc.opensuse.org/release-notes/x86_64/openSUSE/LeapMicro/5.3 (as linked on https://get.opensuse.org/leapmicro/5.3/#download ). They are present for Leap Micro 5.2.

Request to drop gap is here https://code.opensuse.org/leap/features/issue/24, let's make sure that we cover it in RN as well.

Context from Wolfgang:

Got in touch with Jan Engelhardt and he mentioned that gap was removed from Factory because it isn't FHS-compliant and upstream refused to change that.
The old version (as it is in Leap 15.2 and Backports) was working but new version might not.

So I guess it is better to remove it completely from Leap/Backports.