Bug#681598: Anything else required?
On 11/03/2012 06:48 PM, Jeff Licquia wrote: On 10/22/2012 09:24 AM, Nikolaus Rath wrote: This problem continues to occur regularly. Is there something else I can do to help? I took another look to see if I could figure out what might be happening, and came up empty. About the only possibility left would be to debug the Python code when get_distro_information() fails to return a CODENAME, and figure out why. If you're up for that, definitely send along any information you find. If not, you could let me into your box when it's happening, and I could do the debugging. Of course, you'd have to trust that I wouldn't do anything bad while working on your system. I'll wait until it happens again and you can take a look. Can you send me your ssh key? You don't need root access, right? We'll have to coordinate a time, the machine doesn't have a fixed ip. Thanks! -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681598: Anything else required?
On 11/07/2012 06:21 PM, Nikolaus Rath wrote: I'll wait until it happens again and you can take a look. Can you send me your ssh key? You don't need root access, right? We'll have to coordinate a time, the machine doesn't have a fixed ip. Nope, shouldn't need root. I'll send the ssh key out-of-band. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681598: Anything else required?
On 10/22/2012 09:24 AM, Nikolaus Rath wrote: This problem continues to occur regularly. Is there something else I can do to help? I took another look to see if I could figure out what might be happening, and came up empty. About the only possibility left would be to debug the Python code when get_distro_information() fails to return a CODENAME, and figure out why. If you're up for that, definitely send along any information you find. If not, you could let me into your box when it's happening, and I could do the debugging. Of course, you'd have to trust that I wouldn't do anything bad while working on your system. Another idea that comes to mind: It occurs to me that some of your repos seem to be defined in sources.list, and some via files in sources.list.d. If you changed things such that all of your repos were in sources.list (i.e. sources.list.d is empty), and if the problem then went away, that might indicate a bug in apt. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681598: Anything else required?
Hi, This problem continues to occur regularly. Is there something else I can do to help? Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
