On 03/30/12 20:56, Johan Grönqvist wrote:
2012-03-30 03:54, dE . skrev:On 03/30/12 10:51, Johan Grönqvist wrote:2012-03-29 22:08, dE . skrev: I _think_ (I have not tried it systematically) it is solved by <http://snapshot.debian.org>.Yes, I'm aware of that, but adding entries manually is not convenient.I agree with that, but hopefully, it will not be required often.You may also be aware of the CUT initiative (at <http://cut.debian.net/>). It seems to be an attempt to solve the same problem in a different way.I was wondering if users could only partially upgrade; using snapshot.debian.org will downgrade the whole system,No, I imagine you would keep the testing repo, add a snapshot one, and keep some packages at the snapshot versions, while following testing for the rest, until the problem has been resolved.
Yes, then it sounds like a better idea. But the process has to be automated to show a previous older version.
Maybe apt can automatically add the right snapshot line (of the last update).
make situations messy (dependency issues -- new packages installed, but the repo has older packages).Yes, mixing sources may lead to messy dependency issues. I would personally instead upgrade to the version in unstable, most of the time, as unstable will often get fixed rather quickly. The advantage is that I would have a mixed testing/sid system for a while, and then gradually revert to a testing only system, as packages migrate to testing.
On second thought this'll be a general problem when providing old versions -- even when it's in the official tree.