Hi Marcel,
On Fri, May 29, 2020 at 04:19:22PM +0200, Marcel Taeumel wrote:
> Hi Dave!
>
> Thanks for the heads up. A concrete timeframe would be nice.?? :-)
Let's plan for this Thursday 4:00pm EST (2020-06-04T20:00:00+00:00).
My schedule is uncertain, so I may need to change it.
Dave
>
> Best,
> Marcel
> Am 29.05.2020 15:29:09 schrieb David T. Lewis <lewis(a)mail.msen.com>:
> Our current squeaksource.com image is running on an older Squeak version,
> and its SqueakSource packages are out of date with respect to the
> source.squeak.org server.
>
> I had looked into doing a squeaksource.com update a couple of years ago,
> but at that time I was not able to complete it due to some issues with
> ReferenceStream serialization, which is required for exporting the SS
> repository and importing it into an new image.
>
> The earlier issues with ReferenceStream serialization are resolved in
> Squeak 5.3, so it is now possible to export the serialized respository
> from the old image and import it into a Squeak 5.3 image.
>
> I have prepared a Squeak 5.3 based image for squeaksource.com, and I'd
> like to try swapping it into service some time soon. This will be a quick
> switchover (about one minute or less), and in the event of problems the
> rollback to the prior version will happen within a few minutes.
>
> However, the actual process of exporting the repository and importing it
> to the new image takes about six hours on my PC, so the overall conversion
> will take quite a while for me to do, and I will need to pick a day when
> I have some free time before I do it.
>
> This is just a heads-up that I have the new image prepared, and am planning
> to deploy it some time in the coming days or weeks. I will send email to
> squeak-dev prior to actually flipping the switch.
>
> Dave
>
Our current squeaksource.com image is running on an older Squeak version,
and its SqueakSource packages are out of date with respect to the
source.squeak.org server.
I had looked into doing a squeaksource.com update a couple of years ago,
but at that time I was not able to complete it due to some issues with
ReferenceStream serialization, which is required for exporting the SS
repository and importing it into an new image.
The earlier issues with ReferenceStream serialization are resolved in
Squeak 5.3, so it is now possible to export the serialized respository
from the old image and import it into a Squeak 5.3 image.
I have prepared a Squeak 5.3 based image for squeaksource.com, and I'd
like to try swapping it into service some time soon. This will be a quick
switchover (about one minute or less), and in the event of problems the
rollback to the prior version will happen within a few minutes.
However, the actual process of exporting the repository and importing it
to the new image takes about six hours on my PC, so the overall conversion
will take quite a while for me to do, and I will need to pick a day when
I have some free time before I do it.
This is just a heads-up that I have the new image prepared, and am planning
to deploy it some time in the coming days or weeks. I will send email to
squeak-dev prior to actually flipping the switch.
Dave
I must be overlooking something.
A process listing shows this:
root 671 665 0 2017 ? 00:00:00 readproctitle service errors: ..............................................................................................................................................................................................................................................................................................................................................svscan: warning: unable to stat squeaksource: file does not exist
And I can see the squeaksource image being endlessly restarted.
What changed: I stopped the service (sudo -d /service/squeaksource), replaced
the image, and started it again (sudo -u /service/squeaksource).
I restored the previously working image, and still have the same problem (I
put the right image back after that verification).
I can't spot what I am overlooking here. I'll see if I can get it running
manually outside of the supervise system.
:-/
Dave
On Wed, May 13, 2020 at 04:42:18PM +0200, Fabio Niephaus wrote:
> Thank you, Dave!
>
> On Wed, May 13, 2020 at 4:41 PM David T. Lewis <lewis(a)mail.msen.com> wrote:
> >
> > I restarted source.squeak.org and am not having difficulties getting it
> > restarted. I'll report back as soon as possible.
> >
> > Dave
> >
> >
> > On Tue, May 12, 2020 at 09:39:05PM -0400, David T. Lewis wrote:
> > > On Tue, May 12, 2020 at 05:55:53PM -0700, tim Rowledge wrote:
> > > >
> > > >
> > > > > On 2020-05-12, at 5:45 PM, David T. Lewis <lewis(a)mail.msen.com> wrote:
> > > > >
> > > > > Tim,
> > > > >
> > > > > Indeed, the SqueakSource-tpr.1127 update looks suspicious. It changes
> > > > > #deliverMailFrom:to:text: and the changed method now calls an unimplemented
> > > > > method:
> > > > >
> > > > > SMTPClient>>deliverMailFrom:to:text:usingServer:userName:password:
> > > >
> > > > Hmm. According to the history I see before me this is in Network-tpr.238
> > > > in trunk. It's in my running 19666 level image and MC swears it has not
> > > > been removed.
> > > >
> > >
> > > Ok, that makes sense. When I updated the source.squeak.org image,
> > > I updated the packages that I found in the ss repository. I did not
> > > update the other packages in the image (it is based on a Squeak 5.2
> > > release image) and I should not do that.
> > >
> > > I cannot follow up tonight, but it sounds like the best thing is for
> > > me to revert any non-essential changes, and restart the image with
> > > just the essential changes (Chris' patch.st to fix moving packages
> > > from inbox to treated or trunk, plus my update for commented MCMs).
> > >
> > > Sorry for the mail problem, I will get it straightened out tomorrow.
> > >
> > > Dave
> > >
> > >
> >
>