On Thu, Sep 30, 2021 at 03:54:02PM +0000, Andrew M.A. Cater wrote: > Have you missed a step - you have gone direct from stable -> unstable [Sid] > > Please don't do that: the instructions you had were meant to give > you an easier route to do this.
I think this is the first time I've ever seen that advice. Traditionally, going directly from stable to unstable has always been a "supported" path, insofar as unstable has any kind of support at all. (All support for unstable is of course unofficial and provided on a volunteer basis.) > Initial small stable == minimal number of packages as a basis to work from. > > Upgrade to testing [will eventually be Debian 12 - codename bookworm > == kernel and libraries update to a probably working testing. > > Upgrade to unstable == sid == never released, continuously in development > == upgrade of minimal numbers of packages, then install the rest (and be > prepared to help debug breakages) That's fine too. The jump from testing to unstable should be pretty small. > > The command fetched the packages successfully, but the next step: is > > stuck at 37%. > > You may have hit a situation where the upgrade path isn't successful. > Maybe repeat the install of stable and try again? Sounds more like a network glitch to me. Either the mirror stopped responding for some reason, or the ISP's routers decided to take a restroom break, or the (wireless?) interface on the local Debian system has decided to take up a career as a paperweight. Reinstalling stable is not what I'd suggest here. "Wait a minute and try again" would be a good first step. "See if you can reach other things on the Internet" would rule out some of the possible reasons.
