Bug 56098 - UCS 5.0-4: Adjust --endversion in join scripts
Summary: UCS 5.0-4: Adjust --endversion in join scripts
Status: VERIFIED WORKSFORME
Alias: None
Product: UCS
Classification: Unclassified
Component: General
Version: UCS 5.0
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 5.0-4
Assignee: Florian Best
QA Contact: Dirk Wiesenthal
URL:
Keywords:
Depends on:
Blocks: 56124
  Show dependency tree / graph
 
Reported: 2023-05-26 12:51 CEST by Florian Best
Modified: 2023-06-19 12:29 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2023-05-26 12:51:38 CEST 
In join scripts, we register extensions with

ucs_registerLDAPExtension --endversion $X

That $X has been set to 5.99 in some cases because we thought we can be forward compatible. But we cannot. Python 3.11 (upcoming UCS 5.2) has slight incompatibilities with Python 3.7. So we should not make promises until UCS 5.99, but only until 5.0-99. In UCS 5.2, though, we will have to write all our extensions backwards compatible and use --startversion 5.0-0 - but that is out of scope for this issue at hand.

https://git.knut.univention.de/univention/ucs/-/issues/1510
Comment 1 Dirk Wiesenthal univentionstaff 2023-06-19 12:29:33 CEST 
All extensions are in fact forward compatible. So we can work with 5.99