@ArthurBorsboom: added libsecret, libgirepository dependencies
@micwoj92: fixed spdx license id
Git Clone URL: | https://aur.archlinux.org/oama-bin.git (read-only, click to copy) |
---|---|
Package Base: | oama-bin |
Description: | Provide OAuth2 renewal and authorization capabilities |
Upstream URL: | https://github.com/pdobsan/oama |
Licenses: | BSD-3-Clause |
Conflicts: | mailctl-bin, oama, oama-git |
Provides: | oama |
Replaces: | mailctl-bin |
Submitter: | petrus7 |
Maintainer: | petrus7 |
Last Packager: | petrus7 |
Votes: | 11 |
Popularity: | 0.98 |
First Submitted: | 2024-05-12 23:57 (UTC) |
Last Updated: | 2025-01-17 20:51 (UTC) |
@ArthurBorsboom: added libsecret, libgirepository dependencies
@micwoj92: fixed spdx license id
Please use spdx license identifier.
The package might be missing a (new?) dependency.
[root@web1 ~]# oama access support@xxxxxxxxxxx.com
oama: error while loading shared libraries: libgirepository-1.0.so.1: cannot open shared object file: No such file or directory
[root@web1 ~]#
After installing package gobject-introspection oama works again.
[root@web1 ~]# sudo pacman -Syu gobject-introspection
File renames mismatch has been fixed.
install: cannot stat 'LICENSE': No such file or directory
ERROR: A failure occured in package().
-> error making: oama-bin-exit status 4
-> Failed to istall the following packages. Manual intervention is required:
oama-bin - exit status 4
Solved by editing PKGBUILD...
License
in place of LICENSE
and Readme
in place of README
PKGBUILD is broken since release 0.16-1 due to file renames upstream, see https://github.com/pdobsan/oama/commit/138d070.
Fix is quite simple:
diff --git a/PKGBUILD b/PKGBUILD
index 497ab37..3419146 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -39,8 +39,8 @@ package() {
cd $release-$CARCH
install -Dm755 ${_pkgname} ${pkgdir}/usr/bin/${_pkgname}
- install -Dm644 LICENSE ${pkgdir}/usr/share/${_pkgname}/LICENSE
- install -Dm644 README.md ${pkgdir}/usr/share/${_pkgname}
+ install -Dm644 License ${pkgdir}/usr/share/${_pkgname}/LICENSE
+ install -Dm644 Readme.md ${pkgdir}/usr/share/${_pkgname}
install -Dm644 cabal.project.freeze ${pkgdir}/usr/share/${_pkgname}
cp -r configs ${pkgdir}/usr/share/${_pkgname}
@ArthurBorsboom, thank you. I have fixed it, also extended optional dependencies.
Install of v0.14-2 shows release notes of v0.13-3
...
oama version 0.13.3
Get google always return a refresh_key even with private client_id,secret
...
@Igneo676 I appreciate your concerns but don't share your priorities. I might not have chosen the best way to do it in retrospect but don't want to spend more time on this deprecation issue.
Both of your problems can be solved easily. Ignore mailctl-bin in pacman.conf. You can install the last proper version of mailctl-bin on a new systems by cloning its AUR repo, and installing the version you need by makepkg.
@petrus7 please don't force an error on build here. If you're looking to specify that the package is deprecated, please include it in the package itself with a notification instead of at build time
For one, if I'm setting up a new computer today and I haven't migrated to oama, then I'm now forced to do the switch instead of being able to migrate at my own pace. Not to mention the general confusion when my upgrades now fail on my computers
Pinned Comments
petrus7 commented on 2024-05-13 10:39 (UTC) (edited on 2024-11-20 08:56 (UTC) by petrus7)
Please, report
oama
related issues upstream and use this place for AUR related problems only.