Sam Grayson

I get this error when I use `branch = true`. @wohali @joshfriend can you confirm this with your repo?

My question is: does turning off `branch = true` fix the crash in your repo?

I'm working on randomizing the env var in this tool, [benchexec][1] in [issue 809][2]. However, this still does not randomize the link order. [1]: https://github.com/sosy-lab/benchexec/ [2]: https://github.com/sosy-lab/benchexec/issues/809

> the bug itself is very likely in coverage.py itself since coverage.py is the one reading/writing the data and it ends up not agreeing with itself. Meanwhile, coverage.py people say...

It seems that `magit.info` **is** still generated, but it exists in `docs/`. I was able to resolve this by: ``` diff --git a/recipes/magit.rcp b/recipes/magit.rcp index 7468977b..9880b91e 100644 --- a/recipes/magit.rcp +++...

It also seems that `magit` should `depends` on `compat` which can be found in ELPA. The README says to use `el-get-elpa-build-local-recipes` to install ELPA packages. Can you also make that...

I think the question is how should a package not in ELPA depend on a package in ELPA? The solution might be to just package `compat` for el-get. I am...

> how should [the package] depend [on another package] I'm wondering how that relationship should be represented in the `el-get` recipe when the packages come from different repositories.

Given that pyca/cryptography#6371 has been closed, I'm wondering what the direction forward is. It seems like the options are: support only one version of cryptography or hard-code a table of...

To make that feasible, I suggest using the existing usage paradigm: actions and action options. - `clean` should be a new action that calls `make clean` - `print` should be...