Moritz Friedrich

Hey @hrabbit take a look at [matchory/elasticsearch](https://github.com/matchory/elasticsearch) - we're actively maintaining a fork without this issue and support for newer versions :)

@weseldridge if you're still in the market, we've forked this library and migrated it to Elasticsearch 7.10, plus tons of other improvements: [matchory/elasticsearch](https://github.com/matchory/elasticsearch). We rely on this package ourselves and...

@Ocramius you don't plan on supporting your fork longer-term, do you? :/

Yeah @akondas I'd also like to say thank you so much for this! I've dealt with Satis too long, and now Repman is here :tada:

Well, I guess in most cases people will use a Repman organization to host private packages from their Git(Hub|Lab) organizations, so I guess opting in to having all repositories that...

I have the same issue, Repman cloud and BitBucket for me. Installation from composer works, but it's a bit irritating to check repman and see errors for all packages...

+1, Please merge the PR. The deprecation notice reported by @davidmpaz is also hugely annoying, this is what my logs look like right now _every time_ a collection is used:...

Hi @DusanKasan, have you got around implementing the outstanding issues? Do you need help with anything? I'm eagerly waiting for the problems you mentioned in this issue to be solved,...

awesome :+1: I'll see what I can come up with.

To add to this, just as @gggeek, I was wondering why exactly recipes must be separated from the package repository. It would be great to include sample configuration and environment...