Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package wayland-protocols for
openSUSE:Factory checked in at 2025-12-17 17:30:50
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/wayland-protocols (Old)
and /work/SRC/openSUSE:Factory/.wayland-protocols.new.1939 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "wayland-protocols"
Wed Dec 17 17:30:50 2025 rev:48 rq:1323002 version:1.47
Changes:
--------
--- /work/SRC/openSUSE:Factory/wayland-protocols/wayland-protocols.changes
2025-11-27 15:18:57.522395176 +0100
+++
/work/SRC/openSUSE:Factory/.wayland-protocols.new.1939/wayland-protocols.changes
2025-12-17 17:34:14.018267474 +0100
@@ -1,0 +2,12 @@
+Mon Dec 15 15:26:01 UTC 2025 - llyyr <[email protected]>
+
+- Update wayland-protocols.keyring
+- Update to 1.47
+ * staging/color-management: loosen restriction on maxCLL and maxFALL
+ * staging/color-management: add ready2 event
+ * color-management: add absolute_no_adaptation rendering intent
+ * staging/color-management: forbid advertising deprecated
+ * staging/color-management: replace two-piece TF
+ * color-management: add wp_image_description_reference_v1
+
+-------------------------------------------------------------------
Old:
----
wayland-protocols-1.46.tar.xz
wayland-protocols-1.46.tar.xz.sig
New:
----
wayland-protocols-1.47.tar.xz
wayland-protocols-1.47.tar.xz.sig
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ wayland-protocols.spec ++++++
--- /var/tmp/diff_new_pack.2kqgPD/_old 2025-12-17 17:34:15.218317873 +0100
+++ /var/tmp/diff_new_pack.2kqgPD/_new 2025-12-17 17:34:15.226318209 +0100
@@ -1,7 +1,7 @@
#
# spec file for package wayland-protocols
#
-# Copyright (c) 2025 SUSE LLC
+# Copyright (c) 2025 SUSE LLC and contributors
# Copyright (c) 2015 Bjørn Lie, Bryne, Norway.
#
# All modifications and additions to the file contributed by third parties
@@ -18,7 +18,7 @@
Name: wayland-protocols
-Version: 1.46
+Version: 1.47
Release: 0
Summary: Wayland protocols that add functionality not available in the
core protocol
License: MIT
++++++ wayland-protocols-1.46.tar.xz -> wayland-protocols-1.47.tar.xz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.46/meson.build
new/wayland-protocols-1.47/meson.build
--- old/wayland-protocols-1.46/meson.build 2025-11-23 22:22:52.000000000
+0100
+++ new/wayland-protocols-1.47/meson.build 2025-12-15 16:16:01.000000000
+0100
@@ -1,5 +1,5 @@
project('wayland-protocols',
- version: '1.46',
+ version: '1.47',
meson_version: '>= 0.58.0',
license: 'MIT/Expat',
)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.46/staging/color-management/appendix.md
new/wayland-protocols-1.47/staging/color-management/appendix.md
--- old/wayland-protocols-1.46/staging/color-management/appendix.md
2025-11-23 22:22:52.000000000 +0100
+++ new/wayland-protocols-1.47/staging/color-management/appendix.md
2025-12-15 16:16:01.000000000 +0100
@@ -53,6 +53,22 @@
Note, that $`E < 0`$ and $`E > 1`$ are possible with limited range
quantization, as required by e.g. the calibration method in [ITU-R BT.814].
+### `compound_power_2_4`
+
+```math
+O = \begin{cases}
+\frac{E}{12.92}, & 0 \leq E < 0.04045\\
+\left( \frac{E + 0.055}{1.055} \right)^{2.4}, & 0.04045 \leq E \leq 1
+\end{cases}
+```
+
+The above is the IEC 61966-2-1 piece-wise transfer function,
+as recorded in [Khronos Data Format Specification][KDFS] 1.4.0
+Section 13.3, and restricted to the unit range.
+
+```math
+L = (L_W - L_B)O + L_B
+```
### `gamma22`
@@ -125,3 +141,4 @@
[ITU-R BT.814]:
https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/specs.md#itu-r-bt814
[ITU-R BT.1886]:
https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/specs.md#itu-r-bt1886
[ITU-R BT.2100]:
https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/specs.md#itu-r-bt2100
+[KDFS]: https://registry.khronos.org/DataFormat/
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.46/staging/color-management/color-management-v1.xml
new/wayland-protocols-1.47/staging/color-management/color-management-v1.xml
--- old/wayland-protocols-1.46/staging/color-management/color-management-v1.xml
2025-11-23 22:22:52.000000000 +0100
+++ new/wayland-protocols-1.47/staging/color-management/color-management-v1.xml
2025-12-15 16:16:01.000000000 +0100
@@ -77,7 +77,7 @@
only be done by creating a new major version of the extension.
</description>
- <interface name="wp_color_manager_v1" version="1">
+ <interface name="wp_color_manager_v1" version="2">
<description summary="color manager singleton">
A singleton global interface used for getting color management extensions
for wl_surface and wl_output objects, and for creating client defined
@@ -124,6 +124,14 @@
summary="ICC-absolute colorimetric"/>
<entry name="relative_bpc" value="4"
summary="media-relative colorimetric + black point compensation"/>
+ <entry name="absolute_no_adaptation" value="5" since="2">
+ <description summary="ICC-absolute colorimetric without adaptation">
+ This rendering intent is a modified absolute rendering intent that
+ assumes the viewer is not adapted to the display white point, so no
+ chromatic adaptation between surface and display is done.
+ This can be useful for color proofing applications.
+ </description>
+ </entry>
</enum>
<enum name="feature">
@@ -280,8 +288,7 @@
- United States Federal Communications Commission (2003) Title 47
Code
of Federal Regulations 73.682 (a) (20)
- Rec. ITU-R BT.1700-0 625 PAL and 625 SECAM
-
- Note: an sRGB display (IEC 61966-2-1) uses this transfer function.
+ - IEC 61966-2-1 (reference display)
</description>
</entry>
<entry name="gamma28" value="3">
@@ -318,18 +325,18 @@
- IEC 61966-2-4
</description>
</entry>
- <entry name="srgb" value="9">
- <description summary="sRGB piece-wise transfer function">
+ <entry name="srgb" value="9" deprecated-since="2">
+ <description summary="Deprecated (ambiguous sRGB transfer function)">
Transfer characteristics as defined by
- IEC 61966-2-1 sRGB
- Note: This is not appropriate for describing sRGB material.
- sRGB material is intended to be viewed on an sRGB display, and
- that is described by gamma22.
+ As a rule of thumb, use gamma22 for video, motion picture and
+ computer graphics, or compound_power_2_4 for ICC calibrated print
+ workflows.
</description>
</entry>
- <entry name="ext_srgb" value="10">
- <description summary="Extended sRGB piece-wise transfer function">
+ <entry name="ext_srgb" value="10" deprecated-since="2">
+ <description summary="Deprecated (Extended sRGB piece-wise transfer
function)">
Transfer characteristics as defined by
- IEC 61966-2-1 sYCC
</description>
@@ -379,6 +386,12 @@
ARIB STD-B67 or BT.2100.
</description>
</entry>
+ <entry name="compound_power_2_4" value="14" since="2">
+ <description summary="IEC 61966-2-1 encoding function">
+ Encoding characteristics as defined by IEC 61966-2-1, for displays
+ that invert the encoding function.
+ </description>
+ </entry>
</enum>
<request name="get_output">
@@ -512,6 +525,9 @@
<description summary="supported rendering intent">
When this object is created, it shall immediately send this event once
for each rendering intent the compositor supports.
+
+ A compositor must not advertise intents that are deprecated in the
+ bound version of the interface.
</description>
<arg name="render_intent" type="uint" enum="render_intent"
@@ -522,6 +538,9 @@
<description summary="supported features">
When this object is created, it shall immediately send this event once
for each compositor supported feature listed in the enumeration.
+
+ A compositor must not advertise features that are deprecated in the
+ bound version of the interface.
</description>
<arg name="feature" type="uint" enum="feature"
@@ -533,6 +552,9 @@
When this object is created, it shall immediately send this event once
for each named transfer function the compositor supports with the
parametric image description creator.
+
+ A compositor must not advertise transfer functions that are deprecated
+ in the bound version of the interface.
</description>
<arg name="tf" type="uint" enum="transfer_function"
@@ -544,6 +566,9 @@
When this object is created, it shall immediately send this event once
for each named set of primaries the compositor supports with the
parametric image description creator.
+
+ A compositor must not advertise names that are deprecated in the
+ bound version of the interface.
</description>
<arg name="primaries" type="uint" enum="primaries"
@@ -556,9 +581,23 @@
transfer functions and named primaries have been sent.
</description>
</event>
+
+ <request name="get_image_description" since="2">
+ <description summary="create an image description from a reference">
+ This request retrieves the image description backing a reference.
+
+ The get_information request can be used if and only if the request that
+ creates the reference allows it.
+ </description>
+
+ <arg name="image_description"
+ type="new_id" interface="wp_image_description_v1"/>
+ <arg name="reference"
+ type="object" interface="wp_image_description_reference_v1"/>
+ </request>
</interface>
- <interface name="wp_color_management_output_v1" version="1">
+ <interface name="wp_color_management_output_v1" version="2">
<description summary="output color properties">
A wp_color_management_output_v1 describes the color properties of an
output.
@@ -628,7 +667,7 @@
</request>
</interface>
- <interface name="wp_color_management_surface_v1" version="1">
+ <interface name="wp_color_management_surface_v1" version="2">
<description summary="color management extension to a surface">
A wp_color_management_surface_v1 allows the client to set the color
space and HDR properties of a surface.
@@ -716,7 +755,7 @@
</request>
</interface>
- <interface name="wp_color_management_surface_feedback_v1" version="1">
+ <interface name="wp_color_management_surface_feedback_v1" version="2">
<description summary="color management extension to a surface">
A wp_color_management_surface_feedback_v1 allows the client to get the
preferred image description of a surface.
@@ -739,27 +778,14 @@
summary="attempted to use an unsupported feature"/>
</enum>
- <event name="preferred_changed">
- <description summary="the preferred image description changed">
- The preferred image description is the one which likely has the most
- performance and/or quality benefits for the compositor if used by the
- client for its wl_surface contents. This event is sent whenever the
- compositor changes the wl_surface's preferred image description.
-
- This event sends the identity of the new preferred state as the
argument,
- so clients who are aware of the image description already can reuse it.
- Otherwise, if the client client wants to know what the preferred image
- description is, it shall use the get_preferred request.
-
- The preferred image description is not automatically used for anything.
- It is only a hint, and clients may set any valid image description with
- set_image_description, but there might be performance and color
accuracy
- improvements by providing the wl_surface contents in the preferred
- image description. Therefore clients that can, should render according
- to the preferred image description
+ <event name="preferred_changed" deprecated-since="2">
+ <description summary="the preferred image description changed (32-bit)">
+ Starting from interface version 2, 'preferred_changed2' is sent instead
+ of this event. See the 'preferred_changed2' event for the definition.
</description>
- <arg name="identity" type="uint" summary="image description id number"/>
+ <arg name="identity" type="uint"
+ summary="the 32-bit image description id number"/>
</event>
<request name="get_preferred">
@@ -816,9 +842,38 @@
<arg name="image_description"
type="new_id" interface="wp_image_description_v1"/>
</request>
+
+ <!-- Version 2 additions -->
+
+ <event name="preferred_changed2" since="2">
+ <description summary="the preferred image description changed">
+ The preferred image description is the one which likely has the most
+ performance and/or quality benefits for the compositor if used by the
+ client for its wl_surface contents. This event is sent whenever the
+ compositor changes the wl_surface's preferred image description.
+
+ This event sends the identity of the new preferred state as the
argument,
+ so clients who are aware of the image description already can reuse it.
+ Otherwise, if the client client wants to know what the preferred image
+ description is, it shall use the get_preferred request.
+
+ The preferred image description is not automatically used for anything.
+ It is only a hint, and clients may set any valid image description with
+ set_image_description, but there might be performance and color
accuracy
+ improvements by providing the wl_surface contents in the preferred
+ image description. Therefore clients that can, should render according
+ to the preferred image description
+ </description>
+
+ <arg name="identity_hi" type="uint"
+ summary="high 32 bits of the 64-bit image description id number"/>
+ <arg name="identity_lo" type="uint"
+ summary="low 32 bits of the 64-bit image description id number"/>
+ </event>
+
</interface>
- <interface name="wp_image_description_creator_icc_v1" version="1">
+ <interface name="wp_image_description_creator_icc_v1" version="2">
<description summary="holder of image description ICC information">
This type of object is used for collecting all the information required
to create a wp_image_description_v1 object from an ICC file. A complete
@@ -934,7 +989,7 @@
</request>
</interface>
- <interface name="wp_image_description_creator_params_v1" version="1">
+ <interface name="wp_image_description_creator_params_v1" version="2">
<description summary="holder of image description parameters">
This type of object is used for collecting all the parameters required
to create a wp_image_description_v1 object. A complete set of required
@@ -1005,14 +1060,16 @@
complete, the protocol error incomplete_set is raised. For the
definition of a complete set, see the description of this interface.
- The protocol error invalid_luminance is raised if any of the following
- requirements is not met:
+ When both max_cll and max_fall are set, max_fall must be less or equal
+ to max_cll otherwise the invalid_luminance protocol error is raised.
+
+ In version 1, these following conditions also result in the
+ invalid_luminance protocol error. Version 2 and later do not have this
+ requirement.
- When max_cll is set, it must be greater than min L and less or equal
to max L of the mastering luminance range.
- When max_fall is set, it must be greater than min L and less or equal
to max L of the mastering luminance range.
- - When both max_cll and max_fall are set, max_fall must be less or
equal
- to max_cll.
If the particular combination of the parameter set is not supported
by the compositor, the resulting image description object shall
@@ -1306,7 +1363,7 @@
</request>
</interface>
- <interface name="wp_image_description_v1" version="1">
+ <interface name="wp_image_description_v1" version="2">
<description summary="Colorimetric image description">
An image description carries information about the pixel color encoding
and its intended display and viewing environment. The image description
is
@@ -1383,8 +1440,43 @@
summary="ad hoc human-readable explanation"/>
</event>
- <event name="ready">
- <description summary="indication that the object is ready to be used">
+ <event name="ready" deprecated-since="2">
+ <description summary="the object is ready to be used (32-bit)">
+ Starting from interface version 2, the 'ready2' event is sent instead
+ of this event.
+
+ For the definition of this event, see the 'ready2' event. The
+ difference to this event is as follows.
+
+ The id number is valid only as long as the protocol object is alive. If
+ all protocol objects referring to the same image description record are
+ destroyed, the id number may be recycled for a different image
+ description record.
+ </description>
+
+ <arg name="identity" type="uint"
+ summary="the 32-bit image description id number"/>
+ </event>
+
+ <request name="get_information">
+ <description summary="get information about the image description">
+ Creates a wp_image_description_info_v1 object which delivers the
+ information that makes up the image description.
+
+ Not all image description protocol objects allow get_information
+ request. Whether it is allowed or not is defined by the request that
+ created the object. If get_information is not allowed, the protocol
+ error no_information is raised.
+ </description>
+
+ <arg name="information"
+ type="new_id" interface="wp_image_description_info_v1"/>
+ </request>
+
+ <!-- Version 2 additions -->
+
+ <event name="ready2" since="2">
+ <description summary="the object is ready to be used">
Once this event has been sent, the wp_image_description_v1 object is
deemed "ready". Ready objects can be used to send requests and can be
used through other interfaces.
@@ -1398,42 +1490,27 @@
cannot have the same id number simultaneously. The id number does not
change during the lifetime of the image description record.
- The id number is valid only as long as the protocol object is alive. If
- all protocol objects referring to the same image description record are
- destroyed, the id number may be recycled for a different image
- description record.
-
Image description id number is not a protocol object id. Zero is
reserved as an invalid id number. It shall not be possible for a client
to refer to an image description by its id number in protocol. The id
numbers might not be portable between Wayland connections. A compositor
shall not send an invalid id number.
+ Compositors must not recycle image description id numbers.
+
This identity allows clients to de-duplicate image description records
and avoid get_information request if they already have the image
description information.
</description>
- <arg name="identity" type="uint" summary="image description id number"/>
+ <arg name="identity_hi" type="uint"
+ summary="high 32 bits of the 64-bit image description id number"/>
+ <arg name="identity_lo" type="uint"
+ summary="low 32 bits of the 64-bit image description id number"/>
</event>
-
- <request name="get_information">
- <description summary="get information about the image description">
- Creates a wp_image_description_info_v1 object which delivers the
- information that makes up the image description.
-
- Not all image description protocol objects allow get_information
- request. Whether it is allowed or not is defined by the request that
- created the object. If get_information is not allowed, the protocol
- error no_information is raised.
- </description>
-
- <arg name="information"
- type="new_id" interface="wp_image_description_info_v1"/>
- </request>
</interface>
- <interface name="wp_image_description_info_v1" version="1">
+ <interface name="wp_image_description_info_v1" version="2">
<description summary="Colorimetric image description information">
Sends all matching events describing an image description object exactly
once and finally sends the 'done' event.
@@ -1626,4 +1703,22 @@
summary="Maximum frame-average light level (cd/m²)"/>
</event>
</interface>
+
+ <interface name="wp_image_description_reference_v1" version="1">
+ <description summary="Reference to an image description">
+ This object is a reference to an image description. This interface is
+ frozen at version 1 to allow other protocols to create
+ wp_image_description_v1 objects.
+
+ The wp_color_manager_v1.get_image_description request can be used to
+ retrieve the underlying image description.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the reference">
+ Destroy this object. This has no effect on the referenced image
+ description.
+ </description>
+ </request>
+ </interface>
</protocol>
++++++ wayland-protocols.keyring ++++++
Binary files /var/tmp/diff_new_pack.2kqgPD/_old and
/var/tmp/diff_new_pack.2kqgPD/_new differ
