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 2022-11-16 15:42:22
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/wayland-protocols (Old)
and /work/SRC/openSUSE:Factory/.wayland-protocols.new.1597 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "wayland-protocols"
Wed Nov 16 15:42:22 2022 rev:31 rq:1035814 version:1.29
Changes:
--------
--- /work/SRC/openSUSE:Factory/wayland-protocols/wayland-protocols.changes
2022-10-15 16:36:18.733988293 +0200
+++
/work/SRC/openSUSE:Factory/.wayland-protocols.new.1597/wayland-protocols.changes
2022-11-16 15:42:27.651624933 +0100
@@ -1,0 +2,15 @@
+Mon Nov 14 16:26:13 UTC 2022 - Fusion Future <[email protected]>
+
+- Update to version 1.29:
+ + linux-dmabuf: fix references to tranche_formats
+ + content-type: fix enum name in
+ wp_content_type_v1.set_content_type
+- Changes from version 1.28:
+ + xdg-shell:
+ - Replace an HTTP link with HTTPS
+ - window menus are optional
+ - Add specific errors
+ + Add xdg-shell.unresponsive error
+ + xwayland_shell_v1: New protocol
+
+-------------------------------------------------------------------
Old:
----
wayland-protocols-1.27.tar.xz
wayland-protocols-1.27.tar.xz.sig
New:
----
wayland-protocols-1.29.tar.xz
wayland-protocols-1.29.tar.xz.sig
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ wayland-protocols.spec ++++++
--- /var/tmp/diff_new_pack.NaD3Fj/_old 2022-11-16 15:42:28.243627986 +0100
+++ /var/tmp/diff_new_pack.NaD3Fj/_new 2022-11-16 15:42:28.247628007 +0100
@@ -18,7 +18,7 @@
Name: wayland-protocols
-Version: 1.27
+Version: 1.29
Release: 0
Summary: Wayland protocols that add functionality not available in the
core protocol
License: MIT
++++++ wayland-protocols-1.27.tar.xz -> wayland-protocols-1.29.tar.xz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.27/meson.build
new/wayland-protocols-1.29/meson.build
--- old/wayland-protocols-1.27/meson.build 2022-10-10 10:20:28.000000000
+0200
+++ new/wayland-protocols-1.29/meson.build 2022-11-14 12:27:21.000000000
+0100
@@ -1,5 +1,5 @@
project('wayland-protocols',
- version: '1.27',
+ version: '1.29',
meson_version: '>= 0.55.0',
license: 'MIT/Expat',
)
@@ -42,6 +42,7 @@
'ext-session-lock': ['v1'],
'single-pixel-buffer': ['v1'],
'xdg-activation': ['v1'],
+ 'xwayland-shell': ['v1'],
}
protocol_files = []
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.27/stable/xdg-shell/xdg-shell.xml
new/wayland-protocols-1.29/stable/xdg-shell/xdg-shell.xml
--- old/wayland-protocols-1.27/stable/xdg-shell/xdg-shell.xml 2022-10-10
10:20:28.000000000 +0200
+++ new/wayland-protocols-1.29/stable/xdg-shell/xdg-shell.xml 2022-11-14
12:27:21.000000000 +0100
@@ -50,6 +50,8 @@
summary="the client provided an invalid surface state"/>
<entry name="invalid_positioner" value="5"
summary="the client provided an invalid positioner"/>
+ <entry name="unresponsive" value="6"
+ summary="the client didnât respond to a ping event in time"/>
</enum>
<request name="destroy" type="destructor">
@@ -58,7 +60,7 @@
Destroying a bound xdg_wm_base object while there are surfaces
still alive created by this xdg_wm_base object instance is illegal
- and will result in a protocol error.
+ and will result in a defunct_surfaces error.
</description>
</request>
@@ -77,7 +79,7 @@
itself is not a role, the corresponding surface may only be assigned
a role extending xdg_surface, such as xdg_toplevel or xdg_popup. It is
illegal to create an xdg_surface for a wl_surface which already has an
- assigned role and this will result in a protocol error.
+ assigned role and this will result in a role error.
This creates an xdg_surface for the given surface. An xdg_surface is
used as basis to define a role to a given surface, such as xdg_toplevel
@@ -94,7 +96,8 @@
<request name="pong">
<description summary="respond to a ping event">
A client must respond to a ping event with a pong request or
- the client may be deemed unresponsive. See xdg_wm_base.ping.
+ the client may be deemed unresponsive. See xdg_wm_base.ping
+ and xdg_wm_base.error.unresponsive.
</description>
<arg name="serial" type="uint" summary="serial of the ping event"/>
</request>
@@ -108,7 +111,9 @@
Compositors can use this to determine if the client is still
alive. It's unspecified what will happen if the client doesn't
respond to the ping request, or in what timeframe. Clients should
- try to respond in a reasonable amount of time.
+ try to respond in a reasonable amount of time. The âunresponsiveâ
+ error is provided for compositors that wish to disconnect unresponsive
+ clients.
A compositor is free to ping in any way it wants, but a client must
always respond to any xdg_wm_base object it created.
@@ -137,7 +142,7 @@
For an xdg_positioner object to be considered complete, it must have a
non-zero size set by set_size, and a non-zero anchor rectangle set by
set_anchor_rect. Passing an incomplete xdg_positioner object when
- positioning a surface raises an error.
+ positioning a surface raises an invalid_positioner error.
</description>
<enum name="error">
@@ -225,7 +230,8 @@
specified (e.g. 'bottom_right' or 'top_left'), then the child surface
will be placed towards the specified gravity; otherwise, the child
surface will be centered over the anchor point on any axis that had no
- gravity specified.
+ gravity specified. If the gravity is not in the âgravityâ enum, an
+ invalid_input error is raised.
</description>
<arg name="gravity" type="uint" enum="gravity"
summary="gravity direction"/>
@@ -451,10 +457,16 @@
</description>
<enum name="error">
- <entry name="not_constructed" value="1"/>
- <entry name="already_constructed" value="2"/>
- <entry name="unconfigured_buffer" value="3"/>
- <entry name="invalid_serial" value="4"/>
+ <entry name="not_constructed" value="1"
+ summary="Surface was not fully constructed"/>
+ <entry name="already_constructed" value="2"
+ summary="Surface was already constructed"/>
+ <entry name="unconfigured_buffer" value="3"
+ summary="Attaching a buffer to an unconfigured surface"/>
+ <entry name="invalid_serial" value="4"
+ summary="Invalid serial number when acking a configure event"/>
+ <entry name="invalid_size" value="5"
+ summary="Width or height was zero or negative"/>
</enum>
<request name="destroy" type="destructor">
@@ -518,10 +530,10 @@
the wl_surface associated with this xdg_surface.
The width and height must be greater than zero. Setting an invalid size
- will raise an error. When applied, the effective window geometry will be
- the set window geometry clamped to the bounding rectangle of the
- combined geometry of the surface of the xdg_surface and the associated
- subsurfaces.
+ will raise an invalid_size error. When applied, the effective window
+ geometry will be the set window geometry clamped to the bounding
+ rectangle of the combined geometry of the surface of the xdg_surface and
+ the associated subsurfaces.
</description>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
@@ -542,6 +554,8 @@
If the client receives multiple configure events before it
can respond to one, it only has to ack the last configure event.
+ Acking a configure event that was never sent raises an invalid_serial
+ error.
A client is not required to commit immediately after sending
an ack_configure request - it may even ack_configure several times
@@ -622,6 +636,8 @@
not a valid variant of the resize_edge enum"/>
<entry name="invalid_parent" value="1"
summary="invalid parent toplevel"/>
+ <entry name="invalid_size" value="2"
+ summary="client provided an invalid min or max size"/>
</enum>
<request name="set_parent">
@@ -687,7 +703,7 @@
application identifiers and how they relate to well-known D-Bus
names and .desktop files.
- [0] http://standards.freedesktop.org/desktop-entry-spec/
+ [0] https://standards.freedesktop.org/desktop-entry-spec/
</description>
<arg name="app_id" type="string"/>
</request>
@@ -701,7 +717,8 @@
This request asks the compositor to pop up such a window menu at
the given position, relative to the local surface coordinates of
the parent surface. There are no guarantees as to what menu items
- the window menu contains.
+ the window menu contains, or even if a window menu will be drawn
+ at all.
This request must be used in response to some sort of user action
like a button press, key press, or touch down event.
@@ -890,11 +907,11 @@
request.
Requesting a maximum size to be smaller than the minimum size of
- a surface is illegal and will result in a protocol error.
+ a surface is illegal and will result in an invalid_size error.
The width and height must be greater than or equal to zero. Using
- strictly negative values for width and height will result in a
- protocol error.
+ strictly negative values for width or height will result in a
+ invalid_size error.
</description>
<arg name="width" type="int"/>
<arg name="height" type="int"/>
@@ -931,11 +948,11 @@
request.
Requesting a minimum size to be larger than the maximum size of
- a surface is illegal and will result in a protocol error.
+ a surface is illegal and will result in an invalid_size error.
The width and height must be greater than or equal to zero. Using
strictly negative values for width and height will result in a
- protocol error.
+ invalid_size error.
</description>
<arg name="width" type="int"/>
<arg name="height" type="int"/>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.27/staging/content-type/content-type-v1.xml
new/wayland-protocols-1.29/staging/content-type/content-type-v1.xml
--- old/wayland-protocols-1.27/staging/content-type/content-type-v1.xml
2022-10-10 10:20:28.000000000 +0200
+++ new/wayland-protocols-1.29/staging/content-type/content-type-v1.xml
2022-11-14 12:27:21.000000000 +0100
@@ -121,7 +121,7 @@
The content type is double-buffered state, see wl_surface.commit for
details.
</description>
- <arg name="content_type" type="uint" enum="content_type"
+ <arg name="content_type" type="uint" enum="type"
summary="the content type"/>
</request>
</interface>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.27/staging/xwayland-shell/README
new/wayland-protocols-1.29/staging/xwayland-shell/README
--- old/wayland-protocols-1.27/staging/xwayland-shell/README 1970-01-01
01:00:00.000000000 +0100
+++ new/wayland-protocols-1.29/staging/xwayland-shell/README 2022-11-14
12:27:21.000000000 +0100
@@ -0,0 +1,4 @@
+Xwayland shell protocol
+
+Maintainers:
+Joshua Ashton <[email protected]>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.27/staging/xwayland-shell/xwayland-shell-v1.xml
new/wayland-protocols-1.29/staging/xwayland-shell/xwayland-shell-v1.xml
--- old/wayland-protocols-1.27/staging/xwayland-shell/xwayland-shell-v1.xml
1970-01-01 01:00:00.000000000 +0100
+++ new/wayland-protocols-1.29/staging/xwayland-shell/xwayland-shell-v1.xml
2022-11-14 12:27:21.000000000 +0100
@@ -0,0 +1,162 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="xwayland_shell_v1">
+
+ <copyright>
+ Copyright © 2022 Joshua Ashton
+
+ Permission is hereby granted, free of charge, to any person obtaining a
+ copy of this software and associated documentation files (the "Software"),
+ to deal in the Software without restriction, including without limitation
+ the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ and/or sell copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following conditions:
+
+ The above copyright notice and this permission notice (including the next
+ paragraph) shall be included in all copies or substantial portions of the
+ Software.
+
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+ THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.
+ </copyright>
+
+ <description summary="Protocol for associating X11 windows to wl_surfaces">
+ This protocol adds a xwayland_surface role which allows an Xwayland
+ server to associate an X11 window to a wl_surface.
+
+ Before this protocol, this would be done via the Xwayland server
+ providing the wl_surface's resource id via the a client message with
+ the WL_SURFACE_ID atom on the X window.
+ This was problematic as a race could occur if the wl_surface
+ associated with a WL_SURFACE_ID for a window was destroyed before the
+ client message was processed by the compositor and another surface
+ (or other object) had taken its id due to recycling.
+
+ This protocol solves the problem by moving the X11 window to wl_surface
+ association step to the Wayland side, which means that the association
+ cannot happen out-of-sync with the resource lifetime of the wl_surface.
+
+ This protocol avoids duplicating the race on the other side by adding a
+ non-zero monotonic serial number which is entirely unique that is set on
+ both the wl_surface (via. xwayland_surface_v1's set_serial method) and
+ the X11 window (via. the `WL_SURFACE_SERIAL` client message) that can be
+ used to associate them, and synchronize the two timelines.
+
+ The key words "must", "must not", "required", "shall", "shall not",
+ "should", "should not", "recommended", "may", and "optional" in this
+ document are to be interpreted as described in IETF RFC 2119.
+
+ Warning! The protocol described in this file is currently in the testing
+ phase. Backward compatible changes may be added together with the
+ corresponding interface version bump. Backward incompatible changes can
+ only be done by creating a new major version of the extension.
+ </description>
+
+ <interface name="xwayland_shell_v1" version="1">
+ <description summary="context object for Xwayland shell">
+ xwayland_shell_v1 is a singleton global object that
+ provides the ability to create a xwayland_surface_v1 object
+ for a given wl_surface.
+
+ This interface is intended to be bound by the Xwayland server.
+
+ A compositor must not allow clients other than Xwayland to
+ bind to this interface. A compositor should hide this global
+ from other clients' wl_registry.
+ A client the compositor does not consider to be an Xwayland
+ server attempting to bind this interface will result in
+ an implementation-defined error.
+
+ An Xwayland server that has bound this interface must not
+ set the `WL_SURFACE_ID` atom on a window.
+ </description>
+
+ <enum name="error">
+ <entry name="role" value="0" summary="given wl_surface has another
role"/>
+ </enum>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the Xwayland shell object">
+ Destroy the xwayland_shell_v1 object.
+
+ The child objects created via this interface are unaffected.
+ </description>
+ </request>
+
+ <request name="get_xwayland_surface">
+ <description summary="assign the xwayland_surface surface role">
+ Create an xwayland_surface_v1 interface for a given wl_surface
+ object and gives it the xwayland_surface role.
+
+ It is illegal to create an xwayland_surface_v1 for a wl_surface
+ which already has an assigned role and this will result in the
+ `role` protocol error.
+
+ See the documentation of xwayland_surface_v1 for more details
+ about what an xwayland_surface_v1 is and how it is used.
+ </description>
+
+ <arg name="id" type="new_id" interface="xwayland_surface_v1"/>
+ <arg name="surface" type="object" interface="wl_surface"/>
+ </request>
+ </interface>
+
+ <interface name="xwayland_surface_v1" version="1">
+ <description summary="interface for associating Xwayland windows to
wl_surfaces">
+ An Xwayland surface is a surface managed by an Xwayland server.
+ It is used for associating surfaces to Xwayland windows.
+
+ The Xwayland server associated with actions in this interface is
+ determined by the Wayland client making the request.
+
+ The client must call wl_surface.commit on the corresponding wl_surface
+ for the xwayland_surface_v1 state to take effect.
+ </description>
+
+ <enum name="error">
+ <entry name="already_associated" value="0" summary="given wl_surface is
already associated with an X11 window"/>
+ <entry name="invalid_serial" value="1" summary="serial was not valid"/>
+ </enum>
+
+ <request name="set_serial">
+ <description summary="associates a Xwayland window to a wl_surface">
+ Associates an Xwayland window to a wl_surface.
+ The association state is double-buffered and will be applied at
+ the time wl_surface.commit of the corresponding wl_surface is called.
+
+ The `serial_lo` and `serial_hi` parameters specify a non-zero
+ monotonic serial number which is entirely unique and provided by the
+ Xwayland server equal to the serial value provided by a client message
+ with a message type of the `WL_SURFACE_SERIAL` atom on the X11 window
+ for this surface to be associated to.
+
+ The serial value in the `WL_SURFACE_SERIAL` client message is specified
+ as having the lo-bits specified in `l[0]` and the hi-bits specified
+ in `l[1]`.
+
+ If the serial value provided by `serial_lo` and `serial_hi` is not
+ valid, the `invalid_serial` protocol error will be raised.
+
+ An X11 window may be associated with multiple surfaces throughout its
+ lifespan. (eg. unmapping and remapping a window).
+
+ For each wl_surface, this state must not be committed more than once,
+ otherwise the `already_associated` protocol error will be raised.
+ </description>
+ <arg name="serial_lo" type="uint" summary="The lower 32-bits of the
serial number associated with the X11 window"/>
+ <arg name="serial_hi" type="uint" summary="The upper 32-bits of the
serial number associated with the X11 window"/>
+ </request>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the Xwayland surface object">
+ Destroy the xwayland_surface_v1 object.
+
+ Any already existing associations are unaffected by this action.
+ </description>
+ </request>
+ </interface>
+</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.27/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
new/wayland-protocols-1.29/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
---
old/wayland-protocols-1.27/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
2022-10-10 10:20:28.000000000 +0200
+++
new/wayland-protocols-1.29/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
2022-11-14 12:27:21.000000000 +0100
@@ -413,16 +413,16 @@
configuration. In particular, compositors should avoid sending the exact
same parameters multiple times in a row.
- The tranche_target_device and tranche_modifier events are grouped by
+ The tranche_target_device and tranche_formats events are grouped by
tranches of preference. For each tranche, a tranche_target_device, one
- tranche_flags and one or more tranche_modifier events are sent, followed
+ tranche_flags and one or more tranche_formats events are sent, followed
by a tranche_done event finishing the list. The tranches are sent in
descending order of preference. All formats and modifiers in the same
tranche have the same preference.
To send parameters, the compositor sends one main_device event, tranches
(each consisting of one tranche_target_device event, one tranche_flags
- event, tranche_modifier events and then a tranche_done event), then one
+ event, tranche_formats events and then a tranche_done event), then one
done event.
</description>
@@ -495,9 +495,9 @@
<event name="tranche_done">
<description summary="a preference tranche has been sent">
- This event splits tranche_target_device and tranche_modifier events in
+ This event splits tranche_target_device and tranche_formats events in
preference tranches. It is sent after a set of tranche_target_device
- and tranche_modifier events; it represents the end of a tranche. The
+ and tranche_formats events; it represents the end of a tranche. The
next tranche will have a lower preference.
</description>
</event>
