severity 684817 serious thanks On 20/08/12 at 12:51 +0200, Lucas Nussbaum wrote: > On 18/08/12 at 21:49 -0700, Don Armstrong wrote: > > tag 684817 unreproducible > > retitle 684817 segfault in lilypond > > thanks > > > > > > > > On Tue, 14 Aug 2012, Lucas Nussbaum wrote: > > > > > During a rebuild of all packages in *wheezy*, your package failed to > > > build on amd64. > > > > I've rebuild this on wheezy on amd64. The actual error is a segfault > > in lilypond (or something which lilypond is calling) which I am unable > > to reproduce in a wheezy pbuilder chroot (nor have I seen this > > particular error before.) The pango warning is just a red herring; it > > happens all over the place and is a bug in pango. > > > > If you are able to reproduce this build failure, please send me a > > coredump and a backtrace so I have a chance of tracking down what is > > happening. If it doesn't reproduce, it should be downgraded, but I'd > > like to see a backtrace if you can possibly get one (and it doesn't > > look like stack smashing.) > > Hi, > > My build ran with DEB_BUILD_OPTIONS=parallel=10. Maybe the failure only > occurs with parallel builds. > > Anyway, while I could reproduce the failure starting the build inside > sbuild, I could not reproduce it in a normal chroot. Feel free to either > close or downgrade (there's a reasonable path to building the package > even if it fails inside sbuild => probably not RC).
Hi, Just a note to say that I can still reproduce this. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
