Should I use lowercase or uppercase for the package name?

[kitgary]

Hi,

I am using two hooks, https://github.com/rogierlommers/logrus-redis-hook and https://github.com/bshuster-repo/logrus-logstash-hook, one is using upper case while the other one is using lowercase. Therefore I got this annoying error
can't load package: package github.com/sirupsen/logrus/examples/hook: case-insensitive import collision: "github.com/Sirupsen/logrus" and "github.com/sirupsen/logrus"

How can I solve this issue?
As there is a thread mentioned that the change has been reverted, so should I use uppercase or lowercase package name?

I am very confused!

Thanks

[robks]

Having similar trouble with Glide, I'm using logrus with the Postgres hook, and glide can't load the repo. Here's my vote for leaving it uppercase, so all dependencies don't break.

[montanaflynn]

Also hitting this, we've switched to lowercase, filed issues in upstream packages but it's a bit of a mess if they have dependencies that use logrus as well...

[sirupsen]

We have to converge to lower-case because reverting would break things for people too. Unfortunately, this is messy either way, caused by the author renaming to lower-case. We have to convert everything to lowercase, as regretful as it is.

[n1koo]

So I ended up working around this by levering glide aliasing support. Eg in your glide.yaml do :

- package: github.com/sirupsen/logrus
  version: master
- package: github.com/Sirupsen/logrus
  repo: git@github.com:/sirupsen/logrus
  vcs: git
  version: master

the version: master is optional but I wanted to make sure I get #547 in

[rohanthewiz]

As a convenience, posting this here for Glide:
Glide has a cache that needs to be busted, so once you update imports to 'sirupsen' do this:
glide install --force
FYI: The glide cache is located at ~/.glide/cache

[sagikazarmark]

I understand that renaming the account was incredibly important (clearly, the difference matters), but since you realized the consequences, can you please tag a new release so that we can stop using the latest master (as you advised us not to do it)?

[iheitlager]

Be sure to clear your glide cache as @rohanthewiz is telling us. Renaming is a b!@#$, but yah .....

Also we had issues with renaming on osx in the previous renaming, if so follow this:

1. delete vendor/github.com/Sirupsen folder, commit
2. (if you want to be sure remove references in glide.yml/glide.lock
3. rename references in you project, commit
4. clear cache
5. glide update

[mattfarina]

@sdboyer FYI.... when thinking of dep.

[sagikazarmark]

@iheitlager clearing the cache does not help this:

https://github.com/sirupsen/logrus/blob/v0.11.5/hooks/test/test.go#L6

[iheitlager]

well you need to remove the version pinning, i can see master is updated to lower case

https://github.com/sirupsen/logrus/blob/master/hooks/test/test.go

[sagikazarmark]

well you need to remove the version pinning

Well, that's a terrible idea. There are reasons why we version software.

[iheitlager]

don't use version 0.11.5 I would say, that one is not compatible

[sagikazarmark]

So which (preferably newer) version should I use than?

[rohanthewiz]

I've been fine on this one:

# glide.yaml
- package: github.com/sirupsen/logrus
  version: 33a34430d1c3dc71777fdd677864928e5b5812bc

Hopefully we'll get a semantic release soon.