Bug 1790970 - Update python-can to latest upstream release
Summary: Update python-can to latest upstream release
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-can
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-14 15:52 UTC by Fabian Affolter
Modified: 2020-05-31 03:28 UTC (History)
1 user (show)

Fixed In Version: python-can-3.3.3-1.fc32
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-31 03:28:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Fabian Affolter 2020-01-14 15:52:51 UTC 
The latest release of python-can is 3.3.2 [1]


Feel free to add me (fab) as co-maintainer if you don't want to do it yourself.
Thanks.

[1] https://pypi.org/project/python-can/
Comment 1 Ben Cotton 2020-02-11 17:35:47 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
Comment 2 Fedora Update System 2020-05-22 12:59:52 UTC 
FEDORA-2020-6b7c936ad0 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6b7c936ad0
Comment 3 Fedora Update System 2020-05-23 04:36:48 UTC 
FEDORA-2020-6b7c936ad0 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-6b7c936ad0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6b7c936ad0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2020-05-31 03:28:52 UTC 
FEDORA-2020-6b7c936ad0 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.