When I look at the latest version of Seaside-Tests-Core at
squeaksource.com, and when I look at the repo in-image in a Metacello browser, the latest version is: Seaside-Tests-Core-lr.219 However, version 305 of ConfigurationOfSeaside30 lists the version as: Seaside-Tests-Core-as.220 I cannot see the "as.220" version. Also, the build at http://jenkins.lukas-renggli.ch/job/Seaside%203.0/ seems to have picked up the "as.220" version. But I don't see ConfigurationOfSeaside30 being used to build that image. Does anyone else see the same thing, or know what's going on? |
More data from my build cache:
~/pub/builder/cache$ ls -l */Seaside-Core-as* ... 275758 Feb 7 07:32 Seaside 3.0/Seaside-Core-as.695.mcz ... 281915 Mar 10 07:32 Seaside 3.0/Seaside-Core-as.712.mcz ... 275758 Feb 7 08:32 WIP Seaside 3.0/Seaside-Core-as.695.mcz ... 281914 Mar 10 08:32 WIP Seaside 3.0/Seaside-Core-as.712.mcz I can no longer see Seaside-Core-as.712.mcz in the repo. Notice how the file sizes are different for as.712, but they're the same value for as.695 The time stamp is from when my builds are triggered. The date stamp is the date the file was cached from the repo. |
maybe it is at the seaside.gemstone.com/ss repo?
Am 2011-04-30 um 04:05 schrieb Yanni Chiu: > More data from my build cache: > > ~/pub/builder/cache$ ls -l */Seaside-Core-as* > ... 275758 Feb 7 07:32 Seaside 3.0/Seaside-Core-as.695.mcz > ... 281915 Mar 10 07:32 Seaside 3.0/Seaside-Core-as.712.mcz > ... 275758 Feb 7 08:32 WIP Seaside 3.0/Seaside-Core-as.695.mcz > ... 281914 Mar 10 08:32 WIP Seaside 3.0/Seaside-Core-as.712.mcz > > I can no longer see Seaside-Core-as.712.mcz in the repo. > > Notice how the file sizes are different for as.712, but they're the same value for as.695 > > The time stamp is from when my builds are triggered. The date stamp is the date the file was cached from the repo. > > |
What is the status of the projects hosted there?
Do they got synched from squeaksource? Stefs > maybe it is at the seaside.gemstone.com/ss repo? > Am 2011-04-30 um 04:05 schrieb Yanni Chiu: > >> More data from my build cache: >> >> ~/pub/builder/cache$ ls -l */Seaside-Core-as* >> ... 275758 Feb 7 07:32 Seaside 3.0/Seaside-Core-as.695.mcz >> ... 281915 Mar 10 07:32 Seaside 3.0/Seaside-Core-as.712.mcz >> ... 275758 Feb 7 08:32 WIP Seaside 3.0/Seaside-Core-as.695.mcz >> ... 281914 Mar 10 08:32 WIP Seaside 3.0/Seaside-Core-as.712.mcz >> >> I can no longer see Seaside-Core-as.712.mcz in the repo. >> >> Notice how the file sizes are different for as.712, but they're the same value for as.695 >> >> The time stamp is from when my builds are triggered. The date stamp is the date the file was cached from the repo. >> >> > > |
In reply to this post by Yanni Chiu
Yanni,
We have had a bit of a dance lately with packages in the Seaside30 repo and the configuration. I don't know the actual details, but at various points in time over the last month those "mystery packages" have appeared, disappeared, reappeared, then disappeared again and I was lucky enough to be updating the config for 3.0.5 work at each of those points? The "mystery packages" are not intended to go into the 3.0.5 release, so they can be safely ignored. I think the can be found in the SeasideWIP (not sure of name) repo, but I haven't looked. Since the Seaside builds load the latest packages so they pick up whatever is in the repository ... Dale On Apr 29, 2011, at 5:18 PM, Yanni Chiu wrote: > When I look at the latest version of Seaside-Tests-Core at > squeaksource.com, and when I look at the repo in-image in a Metacello > browser, the latest version is: > Seaside-Tests-Core-lr.219 > > However, version 305 of ConfigurationOfSeaside30 lists the version as: > Seaside-Tests-Core-as.220 > > I cannot see the "as.220" version. > > Also, the build at http://jenkins.lukas-renggli.ch/job/Seaside%203.0/ > seems to have picked up the "as.220" version. But I don't see > ConfigurationOfSeaside30 being used to build that image. > > Does anyone else see the same thing, or know what's going on? > > |
Free forum by Nabble | Edit this page |