Database thinks it's patched at wrong level after upgrade?

I'm getting this wacky patch upgrade order. Is it actually at 1.3.7 do you think, or does it just think it is?

Database Patch Level: 1.3.7
v1.3.7 [2011-06-24 00:09:42] (Version Update 1.3.6->1.3.7)
v1.3.9h [2011-06-24 00:07:33] (Version Update 1.3.8->1.3.9h)
v1.3.8 [2011-06-24 00:07:32] (Version Update 1.3.7->1.3.8)
v1.3.7 [2011-06-24 00:07:32] (Version Update 1.3.6->1.3.7)
v1.3.6 [2011-06-24 00:07:32] (Version Update 1.3.5->1.3.6)
v1.3.5 [2011-06-24 00:07:32] (Version Update 1.3.0.2->1.3.5)
v1.3.0.2 [2011-06-24 00:07:31] (Version Update 1.3.0.1->1.3.0.2)
v1.3.0.1 [2011-06-24 00:07:31] (Version Update 1.3.0->1.3.0.1)
v1.3.0 [2011-06-24 00:07:31] (Version Update 1.2.7->1.3.0)
v1.2.7 [2006-03-23 05:13:11] (Fresh Installation)

Last upgrade exception was:

sql/mysql_upgrade_zencart_137_to_138.sql

Cannot insert configuration_key "ORDER_COMMENTS_PACKING_SLIP" because it already exists

Anyone have a clue?

PL

Are you having a problem with the site or are you just concerned about the odd display order?

Well, the admin area has a big warning stating that the DB version is wrong. If it's not wrong, can I make it think it's right?

I've not gotten deep enough into the upgrade to determine whether anything is actually wrong. My upgrade path is to upgrade the old database and do everything else fresh - it's a store with only a dozen or so products.

PL

For some reason it seems as though you went back and did the 1.3.6-to-1.3.7 step over again after all the others had been done already.

plumloopy:

My upgrade path is to upgrade the old database and do everything else fresh - it's a store with only a dozen or so products.
If there's been no orders since you attempted the upgrade the other day, then what you've stated (starting the db upgrade again with a fresh copy of the db before you started) would be the easiest approach.

The store is offline, I guess I'll do that then.

PL