Bug 2034589 - Update version to 2.4.14 on F34
Summary: Update version to 2.4.14 on F34
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: onedrive
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zamir SUN
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-21 12:19 UTC by fednuc
Modified: 2022-04-02 01:56 UTC (History)
3 users (show)

Fixed In Version: onedrive-2.4.16-1.fc34
Clone Of:
Environment:
Last Closed: 2022-04-02 01:56:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description fednuc 2021-12-21 12:19:33 UTC 
Description of problem:

Currently there are no 2.4.14 packages for F34: https://koji.fedoraproject.org/koji/packageinfo?packageID=26044

The 2.4.14 version fixes broken sync. of shared folders: https://github.com/abraunegg/onedrive/issues/1712


Version-Release number of selected component (if applicable):

2.4.13
Comment 1 alex.braunegg 2022-03-23 07:44:01 UTC 
@zsun

Please can you update all Fedora packages to v2.4.16
Comment 2 Fedora Update System 2022-03-25 13:27:53 UTC 
FEDORA-2022-1629bb17f8 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1629bb17f8
Comment 3 Fedora Update System 2022-03-25 22:55:24 UTC 
FEDORA-2022-1629bb17f8 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1629bb17f8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1629bb17f8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2022-04-02 01:56:30 UTC 
FEDORA-2022-1629bb17f8 has been pushed to the Fedora 34 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.