Package Details: gam 5.11-1

Git Clone URL: (read-only, click to copy)
Package Base: gam
Description: Command-line tool for Google GSuite admins to manage settings quickly and easily
Upstream URL:
Licenses: Apache
Submitter: altercation
Maintainer: None
Last Packager: ainola
Votes: 3
Popularity: 0.000000
First Submitted: 2015-08-18 14:14
Last Updated: 2020-06-22 19:59

Pinned Comments

ainola commented on 2020-09-24 05:38

Anyone interested in maintaining this package will need to help upstream with an exorcism to make this software more palatable.

Latest Comments

1 2 3 Next › Last »

ainola commented on 2020-09-24 05:38

Anyone interested in maintaining this package will need to help upstream with an exorcism to make this software more palatable.

ainola commented on 2020-02-16 03:49

This package is still in need of lots of work. If someone is willing to fix/patch the remaining usability issues and work with upstream to make it more package-friendly, I'd be happy to give maintainership.

ekkelett commented on 2018-11-20 09:42

It seems that python2-oauth2client is a missing dependency for gam.

altercation commented on 2018-11-06 16:51


Thanks for the pointer. It looks like it wasn't looking for XDG_CONFIG_DIRS, but rather for $XDG_CONFIG_HOME/gam. I worked around this issue for now by:

export XDG_CONFIG_HOME=/home/es/gam/domainname

and then in that directory I have the config files in a gam subdirectory, so the entire path for stored config files/secrets/service json files is:


This works for now and I hope anyone else that wants to use multiple domains can use this method as a work-around. If someone else uses it, I'd recommend not leaving XDG_CONFIG_HOME set to that value as you'll get all sorts of stuff written to that directory otherwise.

ainola commented on 2018-11-06 10:46

@altercation, that's because of me, unfortunately. Since gam assumes that the user will only use the extracted package, all of the configs end up in the same directory as the sources. in order to conform to the XDG paths I wrote a patch that will use XDG_CONFIG_DIR for now.

Presently, the only way to accomplish what you want would be to not apply that patch since you seem to set the configs manually anyway. I've been meaning to try and fix upstream but I've been a tad busy lately!

altercation commented on 2018-11-05 22:32

Hi ainola, quick question: I've been using the environment variables to quickly switch between a couple different domains I manage. My script is something like this:

$ cat gamswitch

export GAMCACHE=/home/es/.cache/gam/$1

export CLIENTSECRETS=/home/es/gam/$1/client_secrets.json

export OAUTHFILE=/home/es/gam/$1/oauth2.txt

I then call it like this:

$ . gamswitch domainname

which sources it into the current BASH env nicely.

The issue I've hit is related to the CONFIG directory. gam is throwing the following error:

WARNING: [Errno 2] No such file or directory: u'/home/es/.config/gam/oauth2service.json'

Clearly I need to be either setting a generic gam config directory variable or assigning another environment variable for that json file.

Do you know if this patched version has a generic gam config directory environment variable that it uses?

ainola commented on 2018-08-11 18:31

Another update.... it works now, but I can't find why the oauth2.txt file isn't created in the .config/gam dir. So for now one must finish the authentication flow with the upstream package and then copy oauth2.txt into .config/gam/oauth2.txt.

Patches welcome? At this rate, I'll have it finished by 2020.

ainola commented on 2018-05-21 23:38

I've pushed an update that likely still doesn't work, but it's on its way to getting there...

ainola commented on 2018-05-21 22:45

@gdamjan, shame on me for not updating it.... but it's quite a pain to do! I've been following progress on cleaning up the repo but in the meantime I should have updated it in its current form if possible. Time slipped away, I guess.

Did you have an interest in updating it?

gdamjan commented on 2018-05-21 17:23

@ainola are you updateing this package?