On Thu, Jan 8, 2009 at 2:05 PM, Steve Langasek
<email address hidden> wrote:
> To be clear, this doesn't fix the issue when upgrading from hardy to
> intrepid, which is still affected; it only provides the infrastructure
> for handling this case in future upgrades.
Makes sense.
> I'm not sure that, this far into the intrepid support cycle, it's
> justified to make this intrusive of a change via SRU for a one-time
> upgrade bug that most users will have already dealt with.
I agree. As long as it doesn't crop up again moving forward, problem
solved. :-)
-Greg
--
Greg Lund-Chaix
OSU Open Source Lab
<email address hidden> ~ (971) 533-7742
On Thu, Jan 8, 2009 at 2:05 PM, Steve Langasek
<email address hidden> wrote:
> To be clear, this doesn't fix the issue when upgrading from hardy to
> intrepid, which is still affected; it only provides the infrastructure
> for handling this case in future upgrades.
Makes sense.
> I'm not sure that, this far into the intrepid support cycle, it's
> justified to make this intrusive of a change via SRU for a one-time
> upgrade bug that most users will have already dealt with.
I agree. As long as it doesn't crop up again moving forward, problem
solved. :-)
-Greg
--
Greg Lund-Chaix
OSU Open Source Lab
<email address hidden> ~ (971) 533-7742