Bug#522162: reassign 522162 to libglib2.0-0

2009-04-10 Thread Josselin Mouette
Le vendredi 10 avril 2009 à 14:36 +0200, Ludovic Aubry a écrit : > If you know of a magic way of telling which packages are newer than those > from > lenny automatically I can investigate in that direction. apt-show-versions should do the trick. -- .''`. Debian 5.0 "Lenny" has been relea

Bug#522162: reassign 522162 to libglib2.0-0

2009-04-10 Thread Ludovic Aubry
On Friday 10 April 2009 12:56:15 Josselin Mouette wrote: > Le vendredi 10 avril 2009 à 12:34 +0200, Ludovic Aubry a écrit : > > Well, I downgraded to 2.16.6-1+lenny1 and 2.16.6-1 and couldn't > > reproduce the problem with either version. > > Maybe there was a locally installed library somewhere?

Bug#522162: reassign 522162 to libglib2.0-0

2009-04-10 Thread Josselin Mouette
Le vendredi 10 avril 2009 à 12:34 +0200, Ludovic Aubry a écrit : > Well, I downgraded to 2.16.6-1+lenny1 and 2.16.6-1 and couldn't > reproduce the problem with either version. Maybe there was a locally installed library somewhere? -- .''`. Debian 5.0 "Lenny" has been released! : :' : `. `'

Bug#522162: reassign 522162 to libglib2.0-0

2009-04-10 Thread Ludovic Aubry
On Thursday 09 April 2009 15:21:25 Josselin Mouette wrote: > Le jeudi 09 avril 2009 à 15:02 +0200, Ludovic Aubry a écrit : > > reassign 522162 libglib2.0-0 2.16.6-1+lenny1 > > Do you have a backtrace of the crash, at least with glib debugging > symbols? > > Does it also happen with 2.16.6-1 or is i

Bug#522162: reassign 522162 to libglib2.0-0

2009-04-09 Thread Josselin Mouette
Le jeudi 09 avril 2009 à 15:02 +0200, Ludovic Aubry a écrit : > reassign 522162 libglib2.0-0 2.16.6-1+lenny1 Do you have a backtrace of the crash, at least with glib debugging symbols? Does it also happen with 2.16.6-1 or is it a regression in the proposed-updates package? -- .''`. Debian