Bug 48412 - univention-repository-x unicode warning deb822.py
univention-repository-x unicode warning deb822.py
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Update - Repository administration
UCS 4.3
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-01-03 09:17 CET by Stephan Hendl
Modified: 2021-05-14 16:34 CEST (History)
7 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.011
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016060821000567,2018051421000311
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Hendl 2019-01-03 09:17:50 CET
+++ This bug was initially created as a clone of Bug #39073 +++

In univention-repository-x (at least -create and -update) a warning is thrown:

/usr/lib/python2.7/dist-packages/debian/deb822.py:200: UnicodeWarning: decoding from utf-8 failed; attempting to detect the true encoding
  UnicodeWarning)

It has no known negative impact but if a cron-job is used and configured to send warnings per mail - this will trigger an e-mail every time the cron-job is running - which is at least annoying. 

appears in: https://forge.univention.org/bugzilla/show_bug.cgi?id=38248 and at least one OTRS ticket (by Landtag Brandenburg).
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:42:47 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.