Bug 51149
| Summary: | univention-antivir-mail: make UCR templates python3-compatible | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Florian Best <best> |
| Component: | Assignee: | Florian Best <best> | |
| Status: | CLOSED FIXED | QA Contact: | Sönke Schwardt-Krummrich <schwardt> |
| Severity: | normal | ||
| Priority: | P5 | CC: | schwardt |
| Version: | UCS 4.4 | ||
| Target Milestone: | UCS 4.4-4-errata | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| 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: | |||
|
Description
Florian Best
univention-antivir-mail.yaml 2ef0fe825700 | YAML Bug #51149 univention-antivir-mail (10.0.0-2) a43c7a876eb4 | Bug #51149: make UCR templates compatible to python3 OK: code change OK: installation OK: changelog entry OK: advisory OK: functional change OK: package built and installable ??: changes applied to python3 branch Do we merge all patches to python3/5.0-0 or do we wait for the weekly rebase? (In reply to Sönke Schwardt-Krummrich from comment #2) > > ??: changes applied to python3 branch > > Do we merge all patches to python3/5.0-0 or do we wait for the weekly rebase? Did it now. I regulary do "git cherry -v python3/5.0-0 4.4-4 | grep '^+' | grep -v -i -e yaml -e advisory -e announce" to find the un-cherrypicked commits. OK: changes applied to python3 branch → VERIFIED |