Copying packages between repositories (was Re: [Pkg] The Trunk: Morphic-cmm.441.mcz)

On 14.06.2010, at 02:09, [hidden email] wrote:

> Name: Morphic-cmm.441
> Ancestors: Morphic-cmm.441

Hi Chris,

you appear to do something odd when committing packages.

I assume you save to a local repository for testing, then save again to the public repository, paste in the previous commit comment, and edit the auto-generated version name.

This is not a good idea.

These still are two different versions (different UUID). Having the same name/number twice is confusing. Having version "Morphic-cmm.441" be the parent of "Morphic-cmm.441" is strange.

The Right Way to copy a version to a different repository is to, indeed, copy that version to a different repository. Not save it again. That is, select the previous version in your local repository, and hit the "Copy" button, then select the destination repository.

Have fun,

- Bert -

Hi Bert.  No, I never save an already-saved package.  I am quite
familiar with copying packages between repositories and averse to the
waste associated with creating new package versions with no (and,
often, even with only *few*) changes.  In fact, had I saved another
version, Monticello typically would have incremented the version
number anyway, so I think something else happened.

I don't know what, though.  But this is the version that I was trying
to save very soon after a saving of a dependent package.  I had gotten
both "Save" windows up and ready, and I think MC must've gotten
confused somwhere along the way.

It looks like the ancestry somehow got "disconnected" from this
version.  I have just rolled back to Morphic-cmm.440, re-applied my
changes, and saved as new, unique version, therefore leaving this
strange one out of the ancestry.

Thanks for raising it to my attention!

 - Chris

On Mon, Jun 14, 2010 at 3:17 AM, Bert Freudenberg <[hidden email]> wrote: