#5853 latte-integrale f20 build fails with bogus duplicate key message
Closed: Invalid None Opened 10 years ago by jjames.

This may be related to ticket 5827. I just bumped NEVR and built latte-integrale in Rawhide for a new release. That worked fine. Then I did a git merge so I can build the same new release for F-20. That failed:

FAILED: Fault: <Fault 1: '<class \'pg.DatabaseError\'>: error \'ERROR: duplicate key value violates unique constraint "rpminfo_unique_nvra"\n\' in \'INSERT INTO rpminfo (build_id, name, arch, buildtime, payloadhash, epoch, version, buildroot_id, release, external_repo_id, id, size) VALUES (497355, \'4ti2-devel\', \'armv7hl\', 1392066338, \'61bf5cfa9addec21ad42902d0b9f20e0\', NULL, \'1.6.2\', 1996468, \'1\', 0, 4800582, 81768)\''>

which is impossible since this is a brand new release, and could not have been built for F-20 previously. Is this leftover damage from ticket 5827? If so, can somebody clean it up for me, please?


Did you try simply resubmitting the failed build? It usually helps me in my private koji instance. It looks as a race condition somewhere in the koji backend.

Did you try simply resubmitting the failed build? It usually helps me in my private koji instance. It looks as a race condition somewhere in the koji backend.

http://koji.fedoraproject.org/koji/buildinfo?buildID=497343

the issue you are hitting is due to you not using the dist tag on the 4ti2 sub packages so the f21 builds already have that rpm, koji enforces unique nvrea globally

http://koji.fedoraproject.org/koji/buildinfo?buildID=497343

the issue you are hitting is due to you not using the dist tag on the 4ti2 sub packages so the f21 builds already have that rpm, koji enforces unique nvrea globally

Good grief. This business with two packages with separate release numbers being bundled into a single release tarball by upstream has been nothing but trouble. Thanks for figuring this out for me. Me goes off to add a %{?dist} tag...

Good grief. This business with two packages with separate release numbers being bundled into a single release tarball by upstream has been nothing but trouble. Thanks for figuring this out for me. Me goes off to add a %{?dist} tag...

Metadata Update from @jjames:
- Issue set to the milestone: Fedora 20 Final

7 years ago

Login to comment on this ticket.

Metadata