nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Lesson learned: iwconvert / temp_workarea

Adam Stoller

(TeamSite 5.0.2 SP1 => 6.1 SP1 / Solaris 8)

I learned today that the temp_workarea that iwconvert creates are VERY important to keep around, un-touched, until after the FINAL conversion.

Apparently iwconvert uses this workarea as a means of maintaining state between runs (I've requested a FR be opened for fixing this, will post more details about the FR when opened).

If you run iwconvert for a branch, then remove the temp_workarea, the create new editions on the source server and run iwconvert again - all UNMODIFIED files between the last edition converted and the new edition being converted will be DELETED on the target server - because they don't exist in the temp_workarea and they don't exist as deltas between the two edition, it assumes they were intended to be deleted.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Migrateduser

Thank you for posting this. We had some serious upgrade issues and appreciate your time to post it.

- c.

Migrateduser

That sounds a lot like the issue we're having now. I don't recall deleting all the temp_workareas, but this upgrade had such a stop-start-repeat cycle, that I may have - and we weren't experiencing it on all branches, but most.

Carol

What goes up must come down. Ask any system administrator.