Bug 39073 - 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
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-04 11:36 CEST by Jens Thorp-Hansen
Modified: 2021-05-14 16:34 CEST (History)
6 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 Jens Thorp-Hansen univentionstaff 2015-08-04 11:36:34 CEST
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 Philipp Hahn univentionstaff 2015-08-10 11:48:50 CEST
See Bug 37937 comment 5 for the real issue, which is fixed for UCS-4.0+e188, but as the broken package information from UCS-4.0-0 will we included until UCS-5, that warning persist until then.
Comment 2 Michael Grandjean univentionstaff 2015-12-15 16:26:05 CET
Observed by customer during UCS@school Workshop
Comment 3 Jens Thorp-Hansen univentionstaff 2016-06-08 15:18:12 CEST
happened again at: 
Ticket#2016060821000567
Comment 4 Stephan Hendl 2016-12-06 07:46:57 CET
Also seen in UCS-4.1-4, Errata 350.
Comment 5 Philipp Hahn univentionstaff 2018-06-06 11:54:46 CEST
Again noticed during 2016060821000567,2018051421000311

Instead of waiting for UCS-5 I could manually remove the broken package from out FTP site and replace it with the fixed version from e188. This would not be the first change to an already published UCS release...
Comment 6 Stephan Hendl 2018-07-26 08:18:42 CEST
Again seen in UCS-4.3-1, Errata 151
Comment 7 Stefan Gohmann univentionstaff 2019-01-03 07:18:30 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
Comment 8 Stephan Hendl 2019-01-03 08:52:30 CET
(In reply to Stefan Gohmann from comment #7)
> This issue has been filled against UCS 4.1. The maintenance with bug and
> security fixes for UCS 4.1 has ended on 5st of April 2018.
> 
> Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please
> contact
> your partner or Univention for any questions.
> 
> If this issue still occurs in newer UCS versions, please use "Clone this
> bug" or simply reopen the issue. In this case please provide detailed
> information on how this issue is affecting you.

The issue occurs in 4.3-1 as you can see from Comment 6. So please adjust the Version Number.
Comment 9 Ingo Steuwer univentionstaff 2021-05-14 15:41:26 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.