Google disabled OOB authorization, so it's broken now. See: https://github.com/odeke-em/drive/issues/1140 https://github.com/odeke-em/drive/issues/1146 There are no commits since 2021. Consider treecleaning.
Per Zac's comment, this should be removed. This stopped working for existing users on 2023-01-23 when google changed the OOB auth method for drive. For all new users, it's been broke since 2022-02-08. Upstream is also yet again dead, so again, no reason to keep it. If a repo news item is desired, rclone seems to have migrated to the new flow: https://github.com/rclone/rclone/issues/6514 . Finally, I'll note Zac is listed as the maintainer. If he's asking for it be removed, that should probably be actioned.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba6f1c6fd9b9434bd2c07cf7233ee38cb6ab430a commit ba6f1c6fd9b9434bd2c07cf7233ee38cb6ab430a Author: Brian Harring <ferringb@gmail.com> AuthorDate: 2023-11-10 04:51:11 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2023-11-10 05:59:23 +0000 net-misc/drive: treeclean Dead upstream and fully broken since 2023-02 due to google auth changes. Closes: https://bugs.gentoo.org/658028 Closes: https://bugs.gentoo.org/903862 Signed-off-by: Brian Harring <ferringb@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/33751 Signed-off-by: Zac Medico <zmedico@gentoo.org> net-misc/drive/Manifest | 2 -- net-misc/drive/drive-0.4.0_p20210208.ebuild | 33 ----------------------------- net-misc/drive/metadata.xml | 11 ---------- 3 files changed, 46 deletions(-)
I do think a news item should have been created. I only found out this had been removed from the tree when 'emerge @golang-rebuild' failed... because this had been removed. After spending time trying to figure out if this ebuild was from the official Gentoo tree, an added repo, my internal local repo, or the local testing repo on my workstation, I found it was from gentoo (from the repository file under /var/db/pkg). A news item could have made me (and anyone else using the ebuild) aware it was scheduled for removal, that upstream has been dead for a while, and that Google made that change that will break this. I was unaware of the potential breakage since my authentication must still be cached since 'drive' is still working fine for me. Thanks for the 'rclone' suggestion, I'll check it out. I just wanted to voice that I think a news item about all this would have been helpful.
(In reply to Scott Jones from comment #3) > I do think a news item should have been created. I only found out this had > been removed from the tree when 'emerge @golang-rebuild' failed... because > this had been removed. Procedural note: normal last-rites (as in, a p.mask & 30 days notice) or even last-rites-but-we-removed-it-already would work too, I think.
