Github shows a 2.0.3 release https://github.com/google/google-api-php-client/releases Also no 1.1.8 release is listed and it appears that it changed the api used from v2 to v3 I think as owncloud is showing an error in google drive external files integration which matches the change in api, where did 1.1.8 source from so that I can verify this?
Note that it appears the 1.1.7 release did use the V2 API and not the V3 one ... so 1.1.8 (which is not listed on the github page) was a breaking change.
Ah I was blind and now I see ... hidden on the page somewhat .. https://github.com/google/google-api-php-client/releases/tag/v1.1.8 Here is the change: https://github.com/google/google-api-php-client/blob/v1.1.8/src/Google/Service/Drive.php https://github.com/google/google-api-php-client/blob/1.1.7/src/Google/Service/Drive.php Quite the major change for a changelog of: "fixes branch alias for dev v1-master"
Hey James -- Thanks for taking care of the php-google-apiclient issue! For v2, I plan on packaging that separately as php-googleapiclient2 so both major version will be available and can be dual-installed. There are going to be several packages for review in that stack. Would you like me to ping you when I have submitted those fore review?
(In reply to Shawn Iwinski from comment #3) > For v2, I plan on packaging that separately as php-googleapiclient2 Correction: php-google-apiclient2
No problem. Yeah sure cc me and drop me a ping to review
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
James -- I'm rethinking my original comment of allowing both Google APIs v1 and v2. Can I just upgrade this package (php-google-apiclient) to v2? What dists can I push it to if I can update it? -- v2 requires PHP >= 5.4 so theoretically it can be pushed to all Fedoras and EPEL7+. Current latest version is 2.1.2.
The way the APIs are used are just too different. Unless both owncloud and nextcloud refactor to use v2 we'll need to have the v1 in place for these.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.