Hi! The last entry in Bug #617759 says that the reproducibility may depend on the speed of the system: The problem may not be triggered on slow machines. Since my amd64 machine is a 2.3 Ghz AMD Athlon XP, I could imagine that this is the reason why I cannot reproduce the problem. Since my request is only useful if it allows me to reproduce this issue afterwards, I'd say we have to wait whether #617759 leads to a solution - or I get a faster machine :-)
However, just in case we decide to track it down as I suggested at a later step: Please save your dpkg.log files before they are rotated away, such that we can compute your historic package state at a time where you didn't have this problem. WM > thanks a lot for your response. > > I'm not sure about how to proceed right now. I've read the bugreport > you've posted me and I'm not sure what I should take out of it. Should I > repost there? > > Regarding your recommendation of using snapshots in a chroot environment: > > The system I'm using is my everyday work environment (whereas I fully > agree with you that it's a bad idea to use testing for - but I've ran > unstable for many years for exactly the same system and did not have a > lot of critical issues. Also I think that this could be my way to help > Debian a bit, by testing it out real world ;-). Thus I try to not > manipulate the system itself too much. How would I accomplish the way > using the snapshot+chroot-approach, is there maybe some manual somehwere? > > Thanks a lot! > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
