I am trying to install github.com/elastic/go-elasticsearch, which uses go modules. In their go.mod file, they name their package github.com/elastic/go-elasticsearch/v7 (note the added v7 for namespacing).

However, this does not work with glide.

When I try to get glide to

The following are produced by choco.exe, thus this isn't in documentation issues. All referenced output is via Chocolatey v0.10.15

Commands
 * install - installs packages from various sources

ENHANCEMENT: "various sources" just seems misleading. What percentage of free or commercial users actually install packages from multiple sources? I'd guess most use one source or two sources;

Current Behavior

After installing conda 4.6, conda env export -f base.yaml produces an empty output file.

Steps to Reproduce

This is not reproducible, it happens sometimes and disappears as suddenly as it happened. Checking the conda 4.6.1 source code at https://github.com/conda/conda/blob/6461a1abe4c255424104913ab6d089c9453cba4e/conda_env/cli/main_export.py#L105 it looks like the ou

Background: I have a pull request into a repository where the npm module isn't up-to-date with master, and I'd like to test out my branch in a module that depends on it through a bunch of different deep dependencies. It seems like patch-package would be a great solution for this.

Problem: When I append .patch to my GitHub URL it gives me a patch, but when I pass it to patch -p1 it

What Renovate type are you using?

I am using Renovate in a private project hosted on Gitlab.com

Describe the bug

It's not a bug but a simple typo. If you start using Renovate, it will usually create a "Pin dependencies" pull request. The PR template contains a

hab sup run is used to start a Supervisor, and hab svc load is used to instruct a running Supervisor to load a new service.

However, as a way to have allow Habitat containers to start-and-load a service in a single ENTRYPOINT, hab sup run takes options and arguments of hab svc load to effectively perform both operations at once.

However, this has led to confusion, in that it is cur

Could it be possible to have a warning message when installing a rock that contains a module that is already provided by another rock? Or is there already an option for this and I didn't find it?

At least with Luarocks version 3.2.1 I verified that there are no warnings for this case.

However it seems that Luarocks is aware of the collision and installs the new module under another name and

According to the conda build documentation and the referenced PEP-386 verlib, version numbers should not start with 'v'. This is violated in the following 13 recipes:

$ grep -R "{% set version *= *['\"]v"   . 
./recipes/perl-bio-viennangs/met

See title.
https://github.com/nerdvegas/rez/blob/master/src/rezplugins/package_repository/filesystem.py#L456

Using the default GOPATH (not explicitly setting it) results in an error saying that git is not in PATH (it is):

> retool do
retool: syncing
retool: downloading github.com/vektra/mockery/cmd/mockery
retool: fatal err: execution error on "go get -d github.com/vektra/mockery/cmd/mockery": go: missing Git command. See https://golang.org/s/gogetcmd
package github.com/vektra/mockery/c

install.packages("pacman") always add's help

$ docker run -ti alpine-R

R version 3.6.0 (2019-04-26) -- "Planting of a Tree"
Copyright (C) 2019 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-musl (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for di

Package and Environment Details (include every applicable attribute)

• Package Name/Version: openssl/1.1.1d
• Operating System+version: Linux CentOS 7.7.1908
• Compiler+version: GCC 7.3.1 (devtoolset-7)
• Docker image: **centos:7.7.190

Resources were originally designed with other files in mind but the documentation and some of the field names/behaviour is still very much plugin oriented.

• Figure out if there are any constraints that make this feature more difficult to use
• Write non-plugin oriented documentation

Outstanding Tasks

• Identify other test.bats that also use the '[['; raise single PR and fix

Context

The 7zip example in standards-for-tests.md has tests that use double brackets e.g.

Completed Tasks

• Waiting on PR #2839, which updates the test stan

Pull request #58 includes some sample code in the vignette to demonstrate how to use the file:/// URI to point to a local miniCRAN repository.

We should in general improve the documentation to demonstrate this, e.g:

• vignette
• in makeRepo()
• in README
• in package level documentation

Also, create documentation with instructions on how to expose a miniCRAN via HTTP, to act like a "real" mi

This is kind of like #27, but I don' think people who are just starting out should worry about how to set up a package to go into opam.

What I have in mind is a guide that tells you how to release a package in simple cases, but notes likely potential gotchas, and has links to further info for more complex cases and for understaning the process under the hood.

This is something I'm trying to

While trying to solve fedora-infra/bodhi#3193 today, I found that the hawkey tutorial still teaches users about the removed hawkey.Repo API: https://hawkey.readthedocs.io/en/latest/tutorial-py.html#loading-repositories

I also noticed that the hawkey [changelog](https://hawkey.readthedocs.io/en/latest/cha

Homebrew usually informs its users that they need to symlink *.plist files to ~/Library/LaunchAgents/ for the services to get loaded on login. But doing this with brewdo fails because _homebrew owns the plist files and anything in ~/Library/LaunchAgents/ that are not owned by the owner of the ~ gets something like this:

/usr/local/Cellar/jenkins/1.635/homebrew.mxcl.jenkins.plist: