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-10-15 16:35:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/wayland-protocols (Old)
and /work/SRC/openSUSE:Factory/.wayland-protocols.new.2275 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "wayland-protocols"
Sat Oct 15 16:35:00 2022 rev:30 rq:1010933 version:1.27
Changes:
--------
--- /work/SRC/openSUSE:Factory/wayland-protocols/wayland-protocols.changes
2022-09-20 19:23:31.554464102 +0200
+++
/work/SRC/openSUSE:Factory/.wayland-protocols.new.2275/wayland-protocols.changes
2022-10-15 16:36:18.733988293 +0200
@@ -1,0 +2,14 @@
+Mon Oct 10 21:03:51 UTC 2022 - Bj??rn Lie <[email protected]>
+
+- Update to version 1.27:
+ + This release includes two new staging protocols:
+ - Content type hint: This protocol enables clients to provide
+ hints to the compositor about what kind of content it
+ provides, allowing compositors to optionally adapt its
+ behavior accordingly.
+ - Idle notify: This extension allows compositors to notify
+ clients about when the user is idle.
+ + Apart from these two new extensions, this release also brings
+ the usual clarifications, cleanups and fixes.
+
+-------------------------------------------------------------------
Old:
----
wayland-protocols-1.26.tar.xz
wayland-protocols-1.26.tar.xz.sig
New:
----
wayland-protocols-1.27.tar.xz
wayland-protocols-1.27.tar.xz.sig
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ wayland-protocols.spec ++++++
--- /var/tmp/diff_new_pack.Csc1BK/_old 2022-10-15 16:36:19.297989648 +0200
+++ /var/tmp/diff_new_pack.Csc1BK/_new 2022-10-15 16:36:19.301989658 +0200
@@ -18,14 +18,14 @@
Name: wayland-protocols
-Version: 1.26
+Version: 1.27
Release: 0
Summary: Wayland protocols that add functionality not available in the
core protocol
License: MIT
Group: Development/Libraries/C and C++
-URL: https://wayland.freedesktop.org/
-Source:
https://wayland.freedesktop.org/releases/%{name}-%{version}.tar.xz
-Source2:
https://wayland.freedesktop.org/releases/%{name}-%{version}.tar.xz.sig
+URL: https://wayland.freedesktop.org
+Source:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/%{version}/downloads/%{name}-%{version}.tar.xz
+Source2:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/%{version}/downloads/%{name}-%{version}.tar.xz.sig
Source3: %{name}.keyring
# PATCH-FIX-OPENSUSE
wayland-protocols-disable-pedantic-test-unstable-xdg-decoration-on-ppc64.patch
bsc#1192209 glfd#wayland/wayland-protocols#48 [email protected] -- Temporarily
disable the unstable xdg-decoration pedantic test on ppc64 until the upstream
issue is more clearly diagnosed
Patch0:
wayland-protocols-disable-pedantic-test-unstable-xdg-decoration-on-ppc64.patch
@@ -33,8 +33,8 @@
BuildRequires: c++_compiler
BuildRequires: c_compiler
BuildRequires: meson >= 0.55.0
-BuildRequires: python3-base
BuildRequires: pkgconfig
+BuildRequires: python3-base
BuildRequires: pkgconfig(wayland-scanner)
BuildArch: noarch
++++++ wayland-protocols-1.26.tar.xz -> wayland-protocols-1.27.tar.xz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.26/meson.build
new/wayland-protocols-1.27/meson.build
--- old/wayland-protocols-1.26/meson.build 2022-07-07 17:48:25.347891300
+0200
+++ new/wayland-protocols-1.27/meson.build 2022-10-10 10:20:28.000000000
+0200
@@ -1,5 +1,5 @@
project('wayland-protocols',
- version: '1.26',
+ version: '1.27',
meson_version: '>= 0.55.0',
license: 'MIT/Expat',
)
@@ -36,10 +36,12 @@
}
staging_protocols = {
- 'xdg-activation': ['v1'],
+ 'content-type': ['v1'],
'drm-lease': ['v1'],
+ 'ext-idle-notify': ['v1'],
'ext-session-lock': ['v1'],
'single-pixel-buffer': ['v1'],
+ 'xdg-activation': ['v1'],
}
protocol_files = []
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.26/stable/xdg-shell/xdg-shell.xml
new/wayland-protocols-1.27/stable/xdg-shell/xdg-shell.xml
--- old/wayland-protocols-1.26/stable/xdg-shell/xdg-shell.xml 2022-07-07
17:48:25.348891500 +0200
+++ new/wayland-protocols-1.27/stable/xdg-shell/xdg-shell.xml 2022-10-10
10:20:28.000000000 +0200
@@ -454,6 +454,7 @@
<entry name="not_constructed" value="1"/>
<entry name="already_constructed" value="2"/>
<entry name="unconfigured_buffer" value="3"/>
+ <entry name="invalid_serial" value="4"/>
</enum>
<request name="destroy" type="destructor">
@@ -549,6 +550,17 @@
A client may send multiple ack_configure requests before committing, but
only the last request sent before a commit indicates which configure
event the client really is responding to.
+
+ Sending an ack_configure request consumes the serial number sent with
+ the request, as well as serial numbers sent by all configure events
+ sent on this xdg_surface prior to the configure event referenced by
+ the committed serial.
+
+ It is an error to issue multiple ack_configure requests referencing a
+ serial from the same configure event, or to issue an ack_configure
+ request referencing a serial from a configure event issued before the
+ event identified by the last ack_configure request for the same
+ xdg_surface. Doing so will raise an invalid_serial error.
</description>
<arg name="serial" type="uint" summary="the serial from the configure
event"/>
</request>
@@ -608,6 +620,8 @@
<enum name="error">
<entry name="invalid_resize_edge" value="0" summary="provided value is
not a valid variant of the resize_edge enum"/>
+ <entry name="invalid_parent" value="1"
+ summary="invalid parent toplevel"/>
</enum>
<request name="set_parent">
@@ -628,6 +642,10 @@
the now-unmapped surface. If the now-unmapped surface has no parent,
its children's parent is unset. If the now-unmapped surface becomes
mapped again, its parent-child relationship is not restored.
+
+ The parent toplevel must not be one of the child toplevel's
+ descendants, and the parent must be different from the child toplevel,
+ otherwise the invalid_parent protocol error is raised.
</description>
<arg name="parent" type="object" interface="xdg_toplevel"
allow-null="true"/>
</request>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.26/staging/content-type/README
new/wayland-protocols-1.27/staging/content-type/README
--- old/wayland-protocols-1.26/staging/content-type/README 1970-01-01
01:00:00.000000000 +0100
+++ new/wayland-protocols-1.27/staging/content-type/README 2022-10-10
10:20:28.000000000 +0200
@@ -0,0 +1,5 @@
+Content type hint protocol
+
+Maintainers:
+Emmanuel Gil Peyrot <[email protected]>
+Xaver Hugl <[email protected]>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.26/staging/content-type/content-type-v1.xml
new/wayland-protocols-1.27/staging/content-type/content-type-v1.xml
--- old/wayland-protocols-1.26/staging/content-type/content-type-v1.xml
1970-01-01 01:00:00.000000000 +0100
+++ new/wayland-protocols-1.27/staging/content-type/content-type-v1.xml
2022-10-10 10:20:28.000000000 +0200
@@ -0,0 +1,128 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="content_type_v1">
+ <copyright>
+ Copyright ?? 2021 Emmanuel Gil Peyrot
+ Copyright ?? 2022 Xaver Hugl
+
+ 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>
+
+ <interface name="wp_content_type_manager_v1" version="1">
+ <description summary="surface content type manager">
+ This interface allows a client to describe the kind of content a surface
+ will display, to allow the compositor to optimize its behavior for it.
+
+ 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>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the content type manager object">
+ Destroy the content type manager. This doesn't destroy objects created
+ with the manager.
+ </description>
+ </request>
+
+ <enum name="error">
+ <entry name="already_constructed" value="0"
+ summary="wl_surface already has a content type object"/>
+ </enum>
+
+ <request name="get_surface_content_type">
+ <description summary="create a new toplevel decoration object">
+ Create a new content type object associated with the given surface.
+
+ Creating a wp_content_type_v1 from a wl_surface which already has one
+ attached is a client error: already_constructed.
+ </description>
+ <arg name="id" type="new_id" interface="wp_content_type_v1"/>
+ <arg name="surface" type="object" interface="wl_surface"/>
+ </request>
+ </interface>
+
+ <interface name="wp_content_type_v1" version="1">
+ <description summary="content type object for a surface">
+ The content type object allows the compositor to optimize for the kind
+ of content shown on the surface. A compositor may for example use it to
+ set relevant drm properties like "content type".
+
+ The client may request to switch to another content type at any time.
+ When the associated surface gets destroyed, this object becomes inert and
+ the client should destroy it.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the content type object">
+ Switch back to not specifying the content type of this surface. This is
+ equivalent to setting the content type to none, including double
+ buffering semantics. See set_content_type for details.
+ </description>
+ </request>
+
+ <enum name="type">
+ <description summary="possible content types">
+ These values describe the available content types for a surface.
+ </description>
+ <entry name="none" value="0">
+ <description summary="no content type applies">
+ The content type none means that either the application has no data
+ about the content type, or that the content doesn't fit into one of
+ the other categories.
+ </description>
+ </entry>
+ <entry name="photo" value="1">
+ <description summary="photo content type">
+ The content type photo describes content derived from digital still
+ pictures and may be presented with minimal processing.
+ </description>
+ </entry>
+ <entry name="video" value="2">
+ <description summary="video content type">
+ The content type video describes a video or animation and may be
+ presented with more accurate timing to avoid stutter. Where scaling
+ is needed, scaling methods more appropriate for video may be used.
+ </description>
+ </entry>
+ <entry name="game" value="3">
+ <description summary="game content type">
+ The content type game describes a running game. Its content may be
+ presented with reduced latency.
+ </description>
+ </entry>
+ </enum>
+
+ <request name="set_content_type">
+ <description summary="specify the content type">
+ Set the surface content type. This informs the compositor that the
+ client believes it is displaying buffers matching this content type.
+
+ This is purely a hint for the compositor, which can be used to adjust
+ its behavior or hardware settings to fit the presented content best.
+
+ The content type is double-buffered state, see wl_surface.commit for
+ details.
+ </description>
+ <arg name="content_type" type="uint" enum="content_type"
+ summary="the content type"/>
+ </request>
+ </interface>
+</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.26/staging/ext-idle-notify/README
new/wayland-protocols-1.27/staging/ext-idle-notify/README
--- old/wayland-protocols-1.26/staging/ext-idle-notify/README 1970-01-01
01:00:00.000000000 +0100
+++ new/wayland-protocols-1.27/staging/ext-idle-notify/README 2022-10-10
10:20:28.000000000 +0200
@@ -0,0 +1,4 @@
+idle_notify protocol
+
+Maintainers:
+Simon Ser <[email protected]>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.26/staging/ext-idle-notify/ext-idle-notify-v1.xml
new/wayland-protocols-1.27/staging/ext-idle-notify/ext-idle-notify-v1.xml
--- old/wayland-protocols-1.26/staging/ext-idle-notify/ext-idle-notify-v1.xml
1970-01-01 01:00:00.000000000 +0100
+++ new/wayland-protocols-1.27/staging/ext-idle-notify/ext-idle-notify-v1.xml
2022-10-10 10:20:28.000000000 +0200
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="ext_idle_notify_v1">
+ <copyright>
+ Copyright ?? 2015 Martin Gr????lin
+ Copyright ?? 2022 Simon Ser
+
+ 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>
+
+ <interface name="ext_idle_notifier_v1" version="1">
+ <description summary="idle notification manager">
+ This interface allows clients to monitor user idle status.
+
+ After binding to this global, clients can create ext_idle_notification_v1
+ objects to get notified when the user is idle for a given amount of time.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the manager">
+ Destroy the manager object. All objects created via this interface
+ remain valid.
+ </description>
+ </request>
+
+ <request name="get_idle_notification">
+ <description summary="create a notification object">
+ Create a new idle notification object.
+
+ The notification object has a minimum timeout duration and is tied to a
+ seat. The client will be notified if the seat is inactive for at least
+ the provided timeout. See ext_idle_notification_v1 for more details.
+
+ A zero timeout is valid and means the client wants to be notified as
+ soon as possible when the seat is inactive.
+ </description>
+ <arg name="id" type="new_id" interface="ext_idle_notification_v1"/>
+ <arg name="timeout" type="uint" summary="minimum idle timeout in msec"/>
+ <arg name="seat" type="object" interface="wl_seat"/>
+ </request>
+ </interface>
+
+ <interface name="ext_idle_notification_v1" version="1">
+ <description summary="idle notification">
+ This interface is used by the compositor to send idle notification events
+ to clients.
+
+ Initially the notification object is not idle. The notification object
+ becomes idle when no user activity has happened for at least the timeout
+ duration, starting from the creation of the notification object. User
+ activity may include input events or a presence sensor, but is
+ compositor-specific. If an idle inhibitor is active (e.g. another client
+ has created a zwp_idle_inhibitor_v1 on a visible surface), the compositor
+ must not make the notification object idle.
+
+ When the notification object becomes idle, an idled event is sent. When
+ user activity starts again, the notification object stops being idle,
+ a resumed event is sent and the timeout is restarted.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the notification object">
+ Destroy the notification object.
+ </description>
+ </request>
+
+ <event name="idled">
+ <description summary="notification object is idle">
+ This event is sent when the notification object becomes idle.
+
+ It's a compositor protocol error to send this event twice without a
+ resumed event in-between.
+ </description>
+ </event>
+
+ <event name="resumed">
+ <description summary="notification object is no longer idle">
+ This event is sent when the notification object stops being idle.
+
+ It's a compositor protocol error to send this event twice without an
+ idled event in-between. It's a compositor protocol error to send this
+ event prior to any idled event.
+ </description>
+ </event>
+ </interface>
+</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.26/staging/ext-session-lock/ext-session-lock-v1.xml
new/wayland-protocols-1.27/staging/ext-session-lock/ext-session-lock-v1.xml
--- old/wayland-protocols-1.26/staging/ext-session-lock/ext-session-lock-v1.xml
2022-07-07 17:48:25.349891400 +0200
+++ new/wayland-protocols-1.27/staging/ext-session-lock/ext-session-lock-v1.xml
2022-10-10 10:20:28.000000000 +0200
@@ -187,6 +187,14 @@
It is a protocol error to make this request if the locked event has
not been sent. In that case, the lock object may only be destroyed
using the destroy request.
+
+ Note that a correct client that wishes to exit directly after unlocking
+ the session must use the wl_display.sync request to ensure the server
+ receives and processes the unlock_and_destroy request. Otherwise
+ there is no guarantee that the server has unlocked the session due
+ to the asynchronous nature of the Wayland protocol. For example,
+ the server might terminate the client with a protocol error before
+ it processes the unlock_and_destroy request.
</description>
</request>
</interface>
