Got an error with 'poetry update' about poetry-dynamic-versioning HOT 3 CLOSED

@meksor Thanks! That's exactly the info I needed. I was able to reproduce it, so I've added a fix/test in Dunamai (mtkennerly/dunamai@33281c8). I'll make a new Dunamai release shortly.

from poetry-dynamic-versioning.

Could you run this command in your clone and check the output?

git for-each-ref "refs/tags/**" --merged HEAD --format "%(refname)@{%(objectname)@{%(creatordate:iso-strict)@{%(*committerdate:iso-strict)@{%(taggerdate:iso-strict)"

It should either be empty or produce several lines in this format:

refs/tags/v0.1.0@{9abeb12f3ec8dd91b2f2db0e0a0b7529050b99f7@{2019-03-26T06:51:22-04:00@{2019-03-26T06:25:37-04:00@{2019-03-26T06:51:22-04:00

The only difference is a direct load of code from a repo - BitBucket - into the source.

I don't quite understand what you mean by this. Could you elaborate?

from poetry-dynamic-versioning.

Hey there!
I was having the same problem, the output to the command you posted was something along the lines of:
warning: ignoring broken ref refs/tags/__init__.py

This was due to an utterly broken and useless IDE extension which I had installed and ran once accidentally. This extension is meant to generate __init__ files for python modules, but it insidiously also put these init files in my .git folder as well...

Anyway, seems it has something to do with corrupting your git "state" in a way where git will not complain unless you try to run one of these commands.
It's probably best to add an error message forwarding the original git output if it is malformed?

from poetry-dynamic-versioning.