Bugzilla

The `mozlog` was updated on PyPi, and Barret was still able to reproduce, so we did a long pair debugging session and we think we figured out the problem. Barret has had the same `mozilla-unified` for a very long time, and it looks like our 'first-party' modules used `egg-info` directories in the past (but seemingly no longer do?). We had to dig into the internals of `pip` to figure out that's where it was getting the wrong version number from, but the solution was to just delete the `egg-info` folder for `mozlog` (and `mozterm`) on the system, and everything worked.

That explains why Glandium and I (and most people, really) weren't able to reproduce. Anyone with a very old `mozilla-unified` directory probably has this problem.

I think the solution to this will probably be to update the [.gitignore](https://searchfox.org/mozilla-central/source/.gitignore#21-25) and [.hgignore](https://searchfox.org/mozilla-central/source/.hgignore#21-23) rules (and having anyone encountering this issue run `hg purge` afterwards), but I need to investigate a bit further before I make that change. I want to understand why we don't have/need `egg-info` directories for 'first-party' modules anymore.

For now, you should be able to navigate to `mozilla-unified\testing\mozbase\mozlog` and delete the `egg-info` directory there and this issue should go away (let me know if it doesn't).

The `mozlog` module was updated on PyPi, and Barret was still able to reproduce, so we did a long pair debugging session and we think we figured out the problem. Barret has had the same `mozilla-unified` for a very long time, and it looks like our 'first-party' modules used `egg-info` directories in the past (but seemingly no longer do?). We had to dig into the internals of `pip` to figure out that's where it was getting the wrong version number from, but the solution was to just delete the `egg-info` folder for `mozlog` (and `mozterm`) on the system, and everything worked.

That explains why Glandium and I (and most people, really) weren't able to reproduce. Anyone with a very old `mozilla-unified` directory probably has this problem.

I think the solution to this will probably be to update the [.gitignore](https://searchfox.org/mozilla-central/source/.gitignore#21-25) and [.hgignore](https://searchfox.org/mozilla-central/source/.hgignore#21-23) rules (and having anyone encountering this issue run `hg purge` afterwards), but I need to investigate a bit further before I make that change. I want to understand why we don't have/need `egg-info` directories for 'first-party' modules anymore.

For now, you should be able to navigate to `mozilla-unified\testing\mozbase\mozlog` and delete the `egg-info` directory there and this issue should go away (let me know if it doesn't).