Daniel wrote:
cmcadams wrote:
Robert Kaiser wrote:
cmcadams wrote:
Here's a link to the bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=547523
That's exactly a "Migrations fails if it's dawn and the weather is nice"
report, I don't expect any developer to be able to reproduce and
investigate the problem based on what's in there.
The goal of a bug report is to get it fixed.
Due to that, please include the information you have that a developer
can need to fix it. We know hundreds of cases where migration works, so
even the summary is wrong.
Robert Kaiser
Nothing in the report is wrong. I supplied the circumstances and result.
I'm sorry I can't supply you with register dumps.
Given that I can't encompass all possible situations in my lone setup, I
think you've just said a fix won't be happening, except by accident.
So be it. I'm not the due-diligence sheriff.
Craig
Craig, looking at your bugzilla report, you specifally state at Step one
that you un-install SM 1.1.18 before you install SM 2. What happens if
you install SM 2 whilst you still have SM 1.1.18 installed??
Daniel
No, because the best opinion I could find before installing 2.03 was
not to. It's something to try. I also see what Robert was saying...and
it may pay me to experiment, trying out different install targets, and
whatever else I can vary along the way. What I find may even be of use
to the developers. :)
My major problem is that my C: partition is pared down so much (for
the sake of fast partition backups, as I mentioned far, far above
somewhere) it's problematic installing Seamonkey to the default
location. And there's an extended partition sitting on top of C:,
complicating things a tad more.
Might be a few days. Fun time is done for this weekend.
Craig
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
