Douglas A. Tutty wrote: > One of the later steps is to upgrade from latest sarge to latest-etch. > Etch is now at r1. The tested upgrade path is r0. Since so much > changed between r0 and r1, there may be problems; I don't know. Seems unlikely to me. We're talking about less change in the 4.1r1 release than happens in a given day in unstable. 37 packages were updated for non-security bigfixes, and 34 for security fixes. Security fixes shouldn't cause upgrade problems by definition, and the bug fixes were all made with a stable update in mind. I upgraded a box from sarge to 4.0r1 last month and it went just as documented in the release notes. -- see shy jo
Attachment:
signature.asc
Description: Digital signature