Bug 1615018

Summary: grive2: Update to include recent upstream bugfixes
Product: [Fedora] Fedora Reporter: Cezary Zemis <cezary.zemis>
Component: grive2Assignee: Zamir SUN <sztsian>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 28CC: 9dnmlarl, lupinix.fedora, sztsian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-10 23:19:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
SPEC file for 0.5.1 none

Description Cezary Zemis 2018-08-11 11:48:48 UTC
Created attachment 1475220 [details]
SPEC file for 0.5.1

Description of problem:
Fedora comes with outdated version of grive2, in some cases incompatible with Google Drive. Grive2-0.5.1-dev is available, compiles and works well in Fedora 28. 


Version-Release number of selected component (if applicable):
0.5.0-13.20171122git84c57c1.fc28

Attached there is a SPEC file I use to create my own RPM.

Comment 1 Zamir SUN 2018-08-13 02:51:02 UTC
Can you specify where you see 0.5.1 release? I did not see it anywhere.

Currently, we are running on git commit 
84c57c121e03b070f80e1d8fd66749eead7a4d9e

which was released on 20171122.

And the commit you uploaded in the spec file
ae06eccb38b2fe250c9ddeac3e3973f80b8a0aa9 
was released on 20160115, which is a year older than the current one in Fedora.

Comment 2 Tibbs Brookside 2018-08-30 11:17:09 UTC
I do not believe that 0.5.1 has been released yet. I'm not sure if the developer is going to be producing "releases" any more as the wiki just says to pull from the master.

The latest release on github is 0.5.0 (ae06ecc) from 14 Jan 2016.

As far as I can see, although the spec file provided sets some variables, the source file specified doesn't appear to exist so it just uses the latest master as the source. Currently this is:

cf51167 from Aug 19, 2018.

I am also keen to see an update to the package based on a newer commit, specifically 93cae25 from Jul 28, 2018 as this will hopefully fix an issue with 403 "Rate Limit Exceeded" errors.

Comment 3 Cezary Zemis 2018-08-30 11:28:14 UTC
Guys, you're right. 0.5.1 is still being developed, and current code used in Fedora 28's package is newer then I had. I also tested that current package (usually) works with Google Drive.

Comment 4 Zamir SUN 2018-08-30 13:35:30 UTC
(In reply to Tibbs Brookside from comment #2)
> I am also keen to see an update to the package based on a newer commit,
> specifically 93cae25 from Jul 28, 2018 as this will hopefully fix an issue
> with 403 "Rate Limit Exceeded" errors.

This makes sense. I can look into the newer commits and possible build a bugfix version. But a long time before this happen could be expected, as I am really busy recently.

Also fixing the title to reflect what I will do.

Comment 5 Fedora Update System 2018-11-30 11:32:45 UTC
grive2-0.5.0-18.20180820gitcf51167.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-9c9446a9e0

Comment 6 Fedora Update System 2018-12-01 02:42:57 UTC
grive2-0.5.0-18.20180820gitcf51167.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-9c9446a9e0

Comment 7 Randy Barlow 2018-12-10 23:19:57 UTC
An update associated with this bug has been pushed to stable.