Bug#709359: can't reproduce
> What I find a little strange is that even though it said it > failed, the package did install succesfully, while I think > the postinst should have returned an error in that case. Well that is something dpkg does, you could report a bug there if you want. Have you checked your logs to see if you had clients connected at the moment? -- Salvo Tomaselli http://web.student.chalmers.se/~saltom/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709359: can't reproduce
On Thu, May 23, 2013 at 12:21:59AM +0200, Kurt Roeckx wrote: > On Thu, May 23, 2013 at 12:15:47AM +0200, Salvo Tomaselli wrote: > > > I can't reproduce it with just downgrading and upgrading it again. > > We'll probably never know what happened. > > > > I am thinking your bug could have something to do with #129086. Perhaps you > > had some client connected to xinetd at the moment of the upgrade? > > I actually don't have any services enabled currently. So clearly > nothing was connected, nor could there be some port lingering or > something preventing me from re-opening that port. What I find a little strange is that even though it said it failed, the package did install succesfully, while I think the postinst should have returned an error in that case. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709359: can't reproduce
On Thu, May 23, 2013 at 12:15:47AM +0200, Salvo Tomaselli wrote: > > I can't reproduce it with just downgrading and upgrading it again. > We'll probably never know what happened. > > I am thinking your bug could have something to do with #129086. Perhaps you > had some client connected to xinetd at the moment of the upgrade? I actually don't have any services enabled currently. So clearly nothing was connected, nor could there be some port lingering or something preventing me from re-opening that port. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709359: can't reproduce
> I can't reproduce it with just downgrading and upgrading it again. We'll probably never know what happened. I am thinking your bug could have something to do with #129086. Perhaps you had some client connected to xinetd at the moment of the upgrade? Can you check some logs to see if that's the case? -- Salvo Tomaselli http://web.student.chalmers.se/~saltom/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709359: can't reproduce
On Wed, May 22, 2013 at 11:26:37PM +0200, Salvo Tomaselli wrote: > severity 709359 normal > tags 709359 - unreproducible > thanks > > Thanks for your report, > > I can't reproduce your problem. Could you downgrade xinetd and upgrade it > again and see what happens? I can't reproduce it with just downgrading and upgrading it again. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709359: can't reproduce
severity 709359 normal tags 709359 - unreproducible thanks Thanks for your report, I can't reproduce your problem. Could you downgrade xinetd and upgrade it again and see what happens? -- Salvo Tomaselli http://web.student.chalmers.se/~saltom/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
