#588 AlreadyUploadedError even when replace=True (since 1.63)
Closed: Fixed 2 years ago by frostyx. Opened 2 years ago by frostyx.

Since 1.63 version, the Commands.upload method throws AlreadyUploadedError even
though replace=True is specified.

I don't know if this is a bug or feature, but for me, it is an unexpected regression from 1.62 where it worked properly. We discovered this issue in Copr and needed to downgrade to 1.62 until it is resolved because it breaks some package builds.

For comparison, I am attaching two log files from Copr DistGit
https://gist.github.com/FrostyX/f26e4c830fbdceb38d3ee6e6089cff81
You can see the traceback there.

For us, the most important thing is to get the commit hash, which we do like so

commands.load_commit()
foo = commands.commithash

So if there is a way to obtain the commithash for already uploaded sources, we can workaround this in Copr codebase. But I think AlreadyUploadedError shouldn't be exposed from pyrpkg when using replace=True.


With the newest rpkg's patch (rpkg-1.63-4), it should have been fixed. Could you, please, check?

Thank you @onosek,
I installed python3-rpkg-1.63-5.fc35.noarch and it fixes the issue.

Metadata Update from @frostyx:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @onosek:
- Issue set to the milestone: 1.64

a year ago

Login to comment on this ticket.

Metadata