| Summary: | Update package: paramiko | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Hook <matija> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | makowski.mageia, olivier |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | python-paramiko | CVE: | |
| Status comment: | |||
|
Description
Hook
2014-12-04 10:48:54 CET
Mageia 5 is still on 1.12. I think we should first update the package in Mageia 5 and then backport if really needed. Is there a lot of package that depends on python-paramiko? CC:
(none) =>
olivier python-paramiko updated to 1.15.2, with also Python 3 version Freeze push asked in Cauldron Mageia 5 CC:
(none) =>
makowski.mageia done for Mageia5 : python-paramiko-1.15.2-1.mga5.noarch python-paramiko-1.15.2-1.mga5.src python3-paramiko-1.15.2-1.mga5.noarch If really need, reopen the bug to ask a backport for Mageia4 Status:
NEW =>
RESOLVED |