Bug 1216805 - font update needed for gb18030-2022 compliance [Build 20231031-1] openQA test fails in gb18030
Summary: font update needed for gb18030-2022 compliance [Build 20231031-1] openQA test...
Status: RESOLVED FIXED
Alias: None
Product: PUBLIC SUSE Linux Enterprise Desktop 15 SP4
Classification: openSUSE
Component: GNOME (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Cliff Zhao
QA Contact:
URL: https://openqa.suse.de/tests/12749189...
Whiteboard: GB
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-02 08:05 UTC by Jia Zhaocong
Modified: 2024-02-27 04:09 UTC (History)
7 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jia Zhaocong 2023-11-02 08:05:06 UTC
Test shows that char glyph from 9FD1 to 9FEF missing. They are required by GB18030-2022 standard.

Package google-noto-sans-cjk-fonts should be updated to latest version (currently 2.004 on Tumbleweed).

This update should apply to all SLE-SPx versions.

## Observation

openQA test in scenario sle-15-SP4-Desktop-DVD-Updates-x86_64-qam-regression-gb18030@64bit fails in
[gb18030](https://openqa.suse.de/tests/12749189/modules/gb18030/steps/92)

## Test suite description
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: zcjia@suse.com


## Reproducible

Fails since (at least) Build [20231031-1](https://openqa.suse.de/tests/12749186)


## Expected result

Last good: [20231101-1](https://openqa.suse.de/tests/12746923) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Desktop-DVD-Updates&machine=64bit&test=qam-regression-gb18030&version=15-SP4)
Comment 4 Yifan Jiang 2023-11-13 09:57:57 UTC
Hi Cliff,

As the bug was reported the update should apply to all SLE-15 SPx versions, I am not clear why it only submitted and discussed in SLE-15-SP4. 

By the fact the packages in SLE-15-SP3, SLE-15-SP4, SLE-15-SP5, SLE-15-SP6 inherited from SLE-15-SP2 (e.g. https://build.suse.de/package/show/SUSE:SLE-15-SP4:Update/google-noto-serif-cjk-fonts), and SLE-15-SP1 inherited from SLE-15, shouldn't we submit to the following projects:

- SUSE:SLE-15:Update
- SUSE:SLE-15-SP2:Update

in that case all the product lines will have the fix. Did I misunderstanding anything?
Comment 5 Yifan Jiang 2023-11-13 09:58:46 UTC
Hi Markus,

Do you have any insight on the above commment? Thanks!
Comment 6 Marcus Meissner 2023-11-13 10:32:29 UTC
The question is really for which SLES 15 service pack do you want to have those.

https://jira.suse.com/browse/PED-7262

says 15 SP1, SP2, SP3, SP4 and SP6.

The submissions only went to SP4 (so SP4, SP5, SP6).

I can rebase your submissions to 15-SP1 and supply it for all of them if this is intended. (no need for new submits)

Would this be wanted?
Comment 7 Marcus Meissner 2023-11-13 12:35:40 UTC
Given that we have packages in 15-SP2 codestream, and 15-SP1 is LTSS EOL on 31.12.

I would suggest to do 15 SP2, SP3, SP4, SP5 and SP6 to be more simplified.
Comment 8 Yifan Jiang 2023-11-13 13:03:25 UTC
Thanks Marcus for your quick reply!

Hi Guido,  I blurly remember there was a mentioning *all* the SLE-15 products need this certification but couldn't find the email/documentation by now. Based on Marcus' analysis, how do you think it from the project's perspective, do we need the certification compliance applied on SLE-15 (SP0) and SLE-15-SP1 as well?
Comment 9 Guido Colangiuli 2023-11-24 10:38:22 UTC
In order to keep all on the same page: we agreed with Marcus to release from SP2 and above for now.

Meanwhile I asked to Sunny to verify any requirement regarding this topic with the certification authority (CESI). If ad only if CESI have a specific requirement on the old version we will plan a release for SP0 and SP1. For now this scenario have a very low probability.

Thanks, Guido.
Comment 10 Maintenance Automation 2023-11-27 12:30:02 UTC
SUSE-RU-2023:4585-1: An update that contains one feature and has one fix can now be installed.

Category: recommended (moderate)
Bug References: 1216805
Jira References: PED-4918
Sources used:
Basesystem Module 15-SP4 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1
Basesystem Module 15-SP5 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1
SUSE Linux Enterprise High Performance Computing 15 SP2 LTSS 15-SP2 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1
SUSE Linux Enterprise High Performance Computing ESPOS 15 SP3 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1
SUSE Linux Enterprise Server 15 SP2 LTSS 15-SP2 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1
SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1
SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1
SUSE Enterprise Storage 7.1 (src): google-noto-sans-cjk-fonts-20201202.2.004-150200.10.7.1, google-noto-fonts-20220607-150200.11.3.3, google-noto-serif-cjk-fonts-20201202.2.001-150200.3.4.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
Comment 11 Jia Zhaocong 2024-02-27 04:08:28 UTC
The font update is released and the certification has passed.

Closing this bug.
Comment 12 Jia Zhaocong 2024-02-27 04:09:17 UTC
Closing.