In #895176: Upgrade fails because of integrity constraint violation in system_update_7060, the existing system_update_7061() became system_update_7062(), so to avoid rerunning it on update (which would drop keys and recreate them unnecessarily) we need to bump the system version number.

CommentFileSizeAuthor
#1 system-version-up.patch688 bytesgábor hojtsy

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Needs review
StatusFileSize
new system-version-up.patch688 bytes

Needs review.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Needs review » Fixed

Committed.

David_Rothstein’s picture

David_Rothstein commented

Does this actually do anything?

Normally system.module's updates will run first, so system_update_7062() will have already run by the time anyone calls this.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Fixed » Needs work

Also, $module is not defined. Huh. Anyway, rerunning that update is (I believe) harmless but takes some time, which I intended to avoid.

David_Rothstein’s picture

David_Rothstein commented
Issue summary: View changes
Status: Needs work » Closed (won't fix)

Closing this since no one is likely to need Drupal 7 HEAD to HEAD upgrade path patches anymore, and to clear out the queue for possible Drupal 8 usage (#2455949: [policy, no patch] Re-activate the head2head project and use it for beta2beta upgrades in the short-term).