| |
@@ -1,7 +1,7 @@
|
| |
%global modname dbusmock
|
| |
|
| |
Name: python-%{modname}
|
| |
- Version: 0.30.0
|
| |
+ Version: 0.30.1
|
| |
Release: 1%{?dist}
|
| |
Summary: Mock D-Bus objects
|
| |
|
| |
@@ -52,6 +52,30 @@
|
| |
%{python3_sitelib}/*%{modname}*
|
| |
|
| |
%changelog
|
| |
+ * Sat Dec 23 2023 Packit <hello@packit.dev> - 0.30.1-1
|
| |
+ Over the years, this template has accumulated some hacks and bad API
|
| |
+ which made PairDevice()'s handling of the Modalias/Class/Icon properties
|
| |
+ buggy and hard to understand:
|
| |
+ * These are *static* device properties, they are not supposed to change
|
| |
+ during pairing.
|
| |
+ * Commit ee29a4403359b6a added these as some kind of "dynamic fallback
|
| |
+ default" when they were not initialized by the caller after
|
| |
+ AddDevice().
|
| |
+ * Commit 59d6af0dca3e silently broke that fallback default by changing
|
| |
+ AddDevice() to set these device properties to empty strings.
|
| |
+ * Commit fae4be7f49c0861 added another really bad API for setting Class
|
| |
+ in PairDevice()(). That API didn't fit into D-Bus (see commit
|
| |
+ 8968284e8b which had to make it a non-default parameter) and also
|
| |
+ broke the API, and moreover it is totally unintuitive -- the device
|
| |
+ class has nothing to do with pairing.
|
| |
+ Clean up all of these: Set the static property defaults in AddDevice()
|
| |
+ right away, so that the caller can adjust them afterwards. Re-drop the
|
| |
+ `class_` argument in PairDevice(). Adjust the documentation of
|
| |
+ AddDevice() to point out that properties should be changed after calling
|
| |
+ that.
|
| |
+ Consequently, PairDevice() will stop claiming that the static properties
|
| |
+ changed. This also gets rid of some redundant code.
|
| |
+
|
| |
* Thu Nov 30 2023 Packit <hello@packit.dev> - 0.30.0-1
|
| |
- api: Add pytest support and helpers
|
| |
- api: Factor the server spawning into a new SpawnedMock object (thanks Peter Hutterer)
|
| |
Upstream tag: 0.30.1
Upstream commit: 63264e18
If you need to do any change in this pull request, you can clone Packit's fork and push directly to the source branch of this PR (provided you have commit access to this repository):
Alternatively, if you already have the package repository cloned, you can just fetch the Packit's fork:
If you have the
koji_build
job configured as well, make sure to configure theallowed_pr_authors
and/orallowed_committers
(see the docs) since by default, Packit reacts only to its own PRs.Before pushing builds/updates, please remember to check the new version against the packaging guidelines.
For example, please: