When I browse trunk repository, I only see .mcd for the latest changes, not the .mcz. The update does not load these. |
On 15 December 2013 17:28, Nicolas Cellier
<[hidden email]> wrote: > When I browse trunk repository, I only see .mcd for the latest changes, not > the .mcz. > The update does not load these. > Did something change recently? I'm seeing something similar. I can update to Morphic-fbs.702, but I can see versions up to 705 in the repository. Trying to update doesn't fetch those versions. One thing that might have affected this - but I'd have expected to hear bug reports a week or two ago - was my changes to updating, moving the setSystemVersion logic from Utilities to the MCConfiguration. Otherwise, I've played around with update-fbs.270, changing Toolbuilder-Tests to ToolBuilder-TEsts, and moving it before Morphic. But I wouldn't think that would break anything. frank |
On 15 December 2013 18:51, Frank Shearar <[hidden email]> wrote:
> On 15 December 2013 17:28, Nicolas Cellier > <[hidden email]> wrote: >> When I browse trunk repository, I only see .mcd for the latest changes, not >> the .mcz. >> The update does not load these. >> Did something change recently? > > I'm seeing something similar. I can update to Morphic-fbs.702, but I > can see versions up to 705 in the repository. Trying to update doesn't > fetch those versions. > > One thing that might have affected this - but I'd have expected to > hear bug reports a week or two ago - was my changes to updating, > moving the setSystemVersion logic from Utilities to the > MCConfiguration. > > Otherwise, I've played around with update-fbs.270, changing > Toolbuilder-Tests to ToolBuilder-TEsts, and moving it before Morphic. > But I wouldn't think that would break anything. I noticed that something I need to do after monkeying with update-fbs.270 is that I must "update" 271 and 272 in the same way. Seeing as I _deleted_ a package referenced in those update maps (ToolBuilderTests), might that cause this issue? (If so, where's a decent error message? "Tried to update to a map, but it references <foo>, which is not in this repository" or something). I'm updating the maps now, so let's hope that fixes things. frank |
On 15 December 2013 19:07, Frank Shearar <[hidden email]> wrote:
> On 15 December 2013 18:51, Frank Shearar <[hidden email]> wrote: >> On 15 December 2013 17:28, Nicolas Cellier >> <[hidden email]> wrote: >>> When I browse trunk repository, I only see .mcd for the latest changes, not >>> the .mcz. >>> The update does not load these. >>> Did something change recently? >> >> I'm seeing something similar. I can update to Morphic-fbs.702, but I >> can see versions up to 705 in the repository. Trying to update doesn't >> fetch those versions. >> >> One thing that might have affected this - but I'd have expected to >> hear bug reports a week or two ago - was my changes to updating, >> moving the setSystemVersion logic from Utilities to the >> MCConfiguration. >> >> Otherwise, I've played around with update-fbs.270, changing >> Toolbuilder-Tests to ToolBuilder-TEsts, and moving it before Morphic. >> But I wouldn't think that would break anything. > > I noticed that something I need to do after monkeying with > update-fbs.270 is that I must "update" 271 and 272 in the same way. > Seeing as I _deleted_ a package referenced in those update maps > (ToolBuilderTests), might that cause this issue? (If so, where's a > decent error message? "Tried to update to a map, but it references > <foo>, which is not in this repository" or something). > > I'm updating the maps now, so let's hope that fixes things. Well, I'm now able to update Collections to Collections-ul.547, and my image has been recompiling LRUCache for a rather long time. No response to cmd-. so I'll try again with a fresh image. frank |
On 15 December 2013 19:28, Frank Shearar <[hidden email]> wrote:
> On 15 December 2013 19:07, Frank Shearar <[hidden email]> wrote: >> On 15 December 2013 18:51, Frank Shearar <[hidden email]> wrote: >>> On 15 December 2013 17:28, Nicolas Cellier >>> <[hidden email]> wrote: >>>> When I browse trunk repository, I only see .mcd for the latest changes, not >>>> the .mcz. >>>> The update does not load these. >>>> Did something change recently? >>> >>> I'm seeing something similar. I can update to Morphic-fbs.702, but I >>> can see versions up to 705 in the repository. Trying to update doesn't >>> fetch those versions. >>> >>> One thing that might have affected this - but I'd have expected to >>> hear bug reports a week or two ago - was my changes to updating, >>> moving the setSystemVersion logic from Utilities to the >>> MCConfiguration. >>> >>> Otherwise, I've played around with update-fbs.270, changing >>> Toolbuilder-Tests to ToolBuilder-TEsts, and moving it before Morphic. >>> But I wouldn't think that would break anything. >> >> I noticed that something I need to do after monkeying with >> update-fbs.270 is that I must "update" 271 and 272 in the same way. >> Seeing as I _deleted_ a package referenced in those update maps >> (ToolBuilderTests), might that cause this issue? (If so, where's a >> decent error message? "Tried to update to a map, but it references >> <foo>, which is not in this repository" or something). >> >> I'm updating the maps now, so let's hope that fixes things. > > Well, I'm now able to update Collections to Collections-ul.547, and my > image has been recompiling LRUCache for a rather long time. No > response to cmd-. so I'll try again with a fresh image. Well, that worked. So we have a bug in the updater, where you can't update to a map when the repository doesn't contain all the versions in the map. (This is an erroneous state of affairs anyway: the bug is not explaining that there's a problem, never mind what the problem is.) Sound right? frank |
In reply to this post by Frank Shearar-3
On Sun, Dec 15, 2013 at 06:51:07PM +0000, Frank Shearar wrote:
> On 15 December 2013 17:28, Nicolas Cellier > <[hidden email]> wrote: > > When I browse trunk repository, I only see .mcd for the latest changes, not > > the .mcz. > > The update does not load these. > > Did something change recently? > > I'm seeing something similar. I can update to Morphic-fbs.702, but I > can see versions up to 705 in the repository. Trying to update doesn't > fetch those versions. > > One thing that might have affected this - but I'd have expected to > hear bug reports a week or two ago - was my changes to updating, > moving the setSystemVersion logic from Utilities to the > MCConfiguration. > Updating has probably been broken for a while. I was having problems with it a couple of days ago, but I had enough other problems getting my working image updated that I did not think to say anything about it. > Otherwise, I've played around with update-fbs.270, changing > Toolbuilder-Tests to ToolBuilder-TEsts, and moving it before Morphic. > But I wouldn't think that would break anything. I don't know the background on this, but I have a Toolbuilder-Tests package that is marked dirty. I'm assuming that you moved the tests to ToolBuilderTests and that you now want the Tool[Bb]uilder-Tests package to be empty. If so you may need to save the empty package one final time, with a commit comment explaining why it is empty. Dave |
On 15 December 2013 19:43, David T. Lewis <[hidden email]> wrote:
> On Sun, Dec 15, 2013 at 06:51:07PM +0000, Frank Shearar wrote: >> On 15 December 2013 17:28, Nicolas Cellier >> <[hidden email]> wrote: >> > When I browse trunk repository, I only see .mcd for the latest changes, not >> > the .mcz. >> > The update does not load these. >> > Did something change recently? >> >> I'm seeing something similar. I can update to Morphic-fbs.702, but I >> can see versions up to 705 in the repository. Trying to update doesn't >> fetch those versions. >> >> One thing that might have affected this - but I'd have expected to >> hear bug reports a week or two ago - was my changes to updating, >> moving the setSystemVersion logic from Utilities to the >> MCConfiguration. >> > > Updating has probably been broken for a while. I was having problems > with it a couple of days ago, but I had enough other problems getting > my working image updated that I did not think to say anything about it. It's worked well enough for me not to notice, and I only ever work on the cutting edge. Frontierman & all. >> Otherwise, I've played around with update-fbs.270, changing >> Toolbuilder-Tests to ToolBuilder-TEsts, and moving it before Morphic. >> But I wouldn't think that would break anything. > > I don't know the background on this, but I have a Toolbuilder-Tests > package that is marked dirty. I'm assuming that you moved the tests > to ToolBuilderTests and that you now want the Tool[Bb]uilder-Tests > package to be empty. If so you may need to save the empty package > one final time, with a commit comment explaining why it is empty. Originally the tests were in ToolBuilder-Kernel. Instead of moving them to ToolBuilder-Tests, the right place, I forgot that ToolBuilder was already a sensible package, and saved the tests in ToolBuilderTests. Chris pointed out my madness, and I messed up by pulling the tests into Toolbuilder-Tests (note the lowercase 'b'). So I tried _again_ and got it right (this time, I hope) with a ToolBuilder-Tests (with an uppercase 'B'). I updated update-fbs.270 with this new package name, so if you take an image from pre-270 you _should_ end up with a clean ToolBuilder-Tests package. I suspect that if you had an image past -270, you'd end up with a dirty Toolbuilder-Tests. frank > Dave |
Free forum by Nabble | Edit this page |