Spec URL: https://raw.githubusercontent.com/siwinski/rpms/53df993d19dd90d88677f0c568db09cf29e2432a/php-google-auth/php-google-auth.spec SRPM URL: https://siwinski.fedorapeople.org/SRPMS/php-google-auth-0.11.1-1.fc25.src.rpm Description: This is Google's officially supported PHP client library for using OAuth 2.0 authorization and authentication with Google APIs. Fedora Account System Username: siwinski
BTW, I just noticed (bug #1386152) you plan to create a php-google-apiclient2, so shouldn't this package avoid conflicts with v1 ?
(In reply to Remi Collet from comment #1) > BTW, I just noticed (bug #1386152) you plan to create a > php-google-apiclient2, so shouldn't this package avoid conflicts with v1 ? I'm rethinking that comment... https://bugzilla.redhat.com/show_bug.cgi?id=1386152#c7
Created attachment 1268608 [details] phpci.log phpCompatInfo version 5.0.6 DB version 1.19.0 built Mar 17 2017 06:44:54 CET static analyze results
Created attachment 1268609 [details] review.txt Generated by fedora-review 0.6.1 (f03e4e7) last change: 2016-05-02 Command line :/usr/bin/fedora-review -b 1431363 Buildroot used: fedora-rawhide-x86_64 Active plugins: Generic, PHP, Shell-api
[x]: Package complies to the Packaging Guidelines === APPROVED ===
THANKS for the review. Pkgdb request submitted for rawhide and f26 (just like php-google-apiclient1).
Package request has been approved: https://admin.fedoraproject.org/pkgdb/package/rpms/php-google-auth
php-google-auth-0.11.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4a54a24fea
php-google-auth-0.11.1-1.fc26 has been pushed to the Fedora 26 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-2017-4a54a24fea
php-google-auth-0.11.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.