Debian Patches

Status for tango/10.0.2+dfsg1-4

Patch Description Author Forwarded Bugs Origin Last update
0001-debian-fix_database_scripts.patch debian/fix_database_scripts
update the database creation script to deal with the debian path		 =?utf-8?b?UGljY2EgRnLDg8KpZMODwqlyaWMtRW1tYW51ZWw=?= no 2011-03-22
0002-debian-my.cnf.in.patch debian/my.cnf.in
set the right parameters for the mysql configuration file		 =?utf-8?q?Picca_Fr=C3=A9d=C3=A9ric-Emmanuel?= <picca@debian.org> no 2012-09-15
0003-remove-upstream-built-doc-from-cmake.patch doc/html is being excluded in d/copyright.

So we need to remove this subdir from doc/CMakeLists.txt		 =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n?= <santiago@freexian.com> not-needed 2024-09-25
0001-assets-CMakeLists.txt-Use-new-package-root-variable-.patch [PATCH 1/2] assets/CMakeLists.txt: Use new package root variable to override location

From 5192f5ff7a95cae1ae22f2452eb39fd4ba924794 Mon Sep 17 00:00:00 2001

Since the move to using find_package in cppTango, ca0754ba (Merge branch
'use-find_package-for-deps' into 'release/9.5.0', 2023-09-14), our
hack to override the tangoidl include directory does not work anymore.

This was hidden as the tsd/debian12:v1 docker image used for testing also
contained tangoidl.

Fix that by using the correct tangoidl_ROOT variable for overriding.		 Thomas Braun <thomas.braun@byte-physics.de> no https://gitlab.com/tango-controls/TangoSourceDistribution/-/merge_requests/157 2023-12-08
0001-Fix-timestamp-columns-in-Mariadb-10.11-and-newer.patch [PATCH] Fix timestamp columns in Mariadb 10.11 and newer
This problem appears in MariaDb 10.11 since default value of
explicit_defaults_for_timestamp changed from OFF to ON, setting it to
OFF (set global explicit_defaults_for_timestamp=OFF;) make the
create_db_tables.sql.in work properly.

Initial patch by Santiago Ruano Rincón with refinements by Graziano
Scalamera.

Upgrade script and tests by the author.		 Thomas Braun <thomas.braun@byte-physics.de> no https://gitlab.com/tango-controls/TangoDatabase/-/merge_requests/95 2024-10-27
1090173-sphinx-conf.patch Update sphinx config to fix FTBFS Fixes the following error:
ERROR: Invalid value `None` in intersphinx_mapping['http://docs.python.org/'].
Expected a two-element tuple or list.

===================================================================		 Santiago Ruano Rincón <santiago@freexian.com> not-needed debian backport, https://gitlab.com/tango-controls/tango-doc/-/commit/494e82de2c7912d89a11ceff6768772bfed1b6e9
0001-EventConsumerKeepAliveThread-send-actual-IDL-when-ex.patch [PATCH 1/2] EventConsumerKeepAliveThread: send actual IDL when execute ZmqEventSubscriptionChange

When we executed ZmqEventSubscriptionChange we sent as client IDL 0, which means for the server, "Guess my IDL", as it was introduced in 01ffb8f4.

After IDL6 release, due to IDL6 devices subscribing to ...idl5_... events, they were re-subscribed as IDL5 devices.

Now we send the actual maximum IDL, supported by the client as we do at the subscription process		 matveyev <yury.matveev@desy.de> no 2025-08-11
0002-Catch2-tests-add-Event-re-subscribes-with-the-same-I.patch [PATCH 2/2] Catch2 tests: add "Event re-subscribes with the same IDL" test

In test we check, that after server restart EventConsumerKeepAliveThread re-subscribe all events to the same maximum supported by client IDL

Test does analysis of debug printouts, due to I have not found any other working solution to check, which IDL was requested		 matveyev <yury.matveev@desy.de> no 2025-08-11
0001-catch2_event_old_client-Add-test-to-catch-duplicate-.patch [PATCH 1/5] catch2_event_old_client: Add test to catch duplicate event issue

This test reproduces the issue described in #1521.

There are three test cases added here which cover different places where
we have the duplicate events issue.

The first test case covers the case where events are being pushed
manually both with and without change detection. This finds the
duplicate event issue in the
`ZmqEventSupplier::detect_and_push_<x>_event` methods along with the
`ZmqEventSupplier::push_event_loop` method.

The second test case covers events sent by the polling loop, this also
triggers the issue with the
`ZmqEventSupplier::detect_and_push_<x>_event` and is included mostly so
that we can check periodic events work.

The final test case covers attribute configuration events, which
triggers the duplicate event issue with the
`EventSupplier::push_att_config_event` method.		 Thomas Ives <tri@observatorysciences.co.uk> no 2025-08-28
0002-DServer-zmq_event_subscription_changed-Map-client-id.patch [PATCH 2/5] DServer::zmq_event_subscription_changed: Map client idl versions...

... to event data versions.

We didn't introduce new AttributeValue data structures with IDLv6, so we
shouldn't being sending an event for each client version selected.
Instead, we should be sending a ZMQ event for each type of data
structure, one that each client can use.		 Thomas Ives <tri@observatorysciences.co.uk> no 2025-09-01
0003-push_att_conf_events-Use-event-data-to-determine-ver.patch [PATCH 3/5] push_att_conf_events: Use event data to determine vers
Do not need to consider the version of the device pushing the event when
deciding if we need to add the idl5_ prefix to the event name. Instead,
the thing that matters is who the event is aimed at. This can be
determined from the SuppliedEventData based on which pointer is not
nullptr.		 Thomas Ives <tri@observatorysciences.co.uk> no 2025-09-01
0004-catch2_event_reconnection-Use-log-from-new-mapping-f.patch [PATCH 4/5] catch2_event_reconnection: Use log from new mapping function Thomas Ives <tri@observatorysciences.co.uk> no 2025-09-01
0005-Attribute-set_upd_properties-Handle-no-database-case.patch [PATCH 5/5] Attribute::set_upd_properties: Handle no database case gracefully

When trying to set the attribute configuration without database, we used
to crash inside Attribute::db_access as the returned pointer from get_database() was not valid.

We now skip the database update similiar to what is done in
DeviceImpl::set_attribute_config.		 Thomas Braun <thomas.braun@byte-physics.de> no 2025-05-01

All known versions for source package 'tango'

Links