Bug 51330 - management/univention-join: migrate to python3
management/univention-join: migrate to python3
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.4
Other Linux
: P5 normal with 1 vote (vote)
: UCS 5.0
Assigned To: Jan Luttermann
Florian Best
:
: 53123 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-05-19 14:32 CEST by Florian Best
Modified: 2021-05-25 16:02 CEST (History)
2 users (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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2020-05-19 14:32:28 CEST
The UMC module of management/univention-join has to be python3-compatible.
Comment 1 Jan Luttermann univentionstaff 2021-01-08 16:28:23 CET
Migraded UMV module join to python 3
fixed with MR !58
Comment 2 Florian Best univentionstaff 2021-01-28 19:51:29 CET
OK: I fixed one additional error (TypeError: cannot use a string pattern on a bytes-like object):
76dcb634ac33 | fixup! Bug #51330: Migrated Join UMC module to python 3

OK: changelog entry

univention-join (12.0.3-1)
d78dfe02437b | Bug #51330: Migrated Join UMC module to python 3
f163e90427c4 | Bug #49898: Run univention-join-hooks with python3

changelog-5.0-0.xml
8711528749f4 | Bug #51330: added changelog
Comment 3 Florian Best univentionstaff 2021-04-19 13:53:47 CEST
*** Bug 53123 has been marked as a duplicate of this bug. ***
Comment 4 Florian Best univentionstaff 2021-05-25 16:02:33 CEST
UCS 5.0 has been released:
 https://docs.software-univention.de/release-notes-5.0-0-en.html
 https://docs.software-univention.de/release-notes-5.0-0-de.html

If this error occurs again, please use "Clone This Bug".