Re: arm build of wireshark

On Saturday 22 March 2008 09:35:35 Luk Claes wrote: > > If you're sure the internal compiler error has been fixed, then a > rebuild is in order... FYI, I can reproduce the ICE on my NSLU2 while compiling the same file. Joost -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsu

Re: Why is package cln not in testing yet?

Richard, On Fri, Mar 21, 2008 at 05:57:16PM +0100, Philipp Kern wrote: > And I guess the stay will again be prolonged until we get kdelibs hinted > into testing. Sorry about that. good news and thanks for waiting. cln and libqalculate were forced into testing today, and with the binNMUs for gin

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

On Sat, Mar 22, 2008 at 6:10 PM, Aurelien Jarno <[EMAIL PROTECTED]> wrote: > Carlos O'Donell a écrit : > > > On Sat, Mar 22, 2008 at 4:33 PM, Matthias Klose <[EMAIL PROTECTED]> wrote: > >> For all ports besides alpha and hppa we plan to make GCC-4.3 the > >> default compilers for lenny. > >> >

about the communication style (Re: #380360)

severity 380360 wishlist thanks so apparently this is a non-issue. I do hope that a comment on irc "We also need to have a chat at some point about python-minimal in general" is not the general style used by the release team to start a discussion about the RC severity of bug reports. Matthias

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

Carlos O'Donell writes: > On Sat, Mar 22, 2008 at 5:10 PM, Matthias Klose <[EMAIL PROTECTED]> wrote: > > Carlos O'Donell writes: > > > > - gij/gcj shows bus errors on hppa (either 4.2 or 4.3). > > > > > > Has gij/gcj ever worked on hppa-linux? > > > > at least the gij/gcj before adding suppor

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

Carlos O'Donell a écrit : > On Sat, Mar 22, 2008 at 4:33 PM, Matthias Klose <[EMAIL PROTECTED]> wrote: >> For all ports besides alpha and hppa we plan to make GCC-4.3 the >> default compilers for lenny. >> >> - both alpha and hppa show regressions in the glibc testsuite when >>built with GCC

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

On Sat, Mar 22, 2008 at 5:10 PM, Matthias Klose <[EMAIL PROTECTED]> wrote: > Carlos O'Donell writes: > > > - gij/gcj shows bus errors on hppa (either 4.2 or 4.3). > > > > Has gij/gcj ever worked on hppa-linux? > > at least the gij/gcj before adding support for generics (1.5) did > work. Now

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

Carlos O'Donell writes: > > - gij/gcj shows bus errors on hppa (either 4.2 or 4.3). > > Has gij/gcj ever worked on hppa-linux? at least the gij/gcj before adding support for generics (1.5) did work. Now that a working runtime is required for the compiler makes things different. Please try to r

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

On Sat, Mar 22, 2008 at 4:33 PM, Matthias Klose <[EMAIL PROTECTED]> wrote: > For all ports besides alpha and hppa we plan to make GCC-4.3 the > default compilers for lenny. > > - both alpha and hppa show regressions in the glibc testsuite when >built with GCC-4.3 What is the list of regress

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

Matthias Klose writes: > For all ports besides alpha and hppa we plan to make GCC-4.3 the > default compilers for lenny. amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch reenabling the cld instruction when stringops are used; this patch is neither in the gcc-4_3-branch or in the tr

[alpha, hppa] GCC-4.3 as the default compilers for lenny?

For all ports besides alpha and hppa we plan to make GCC-4.3 the default compilers for lenny. - both alpha and hppa show regressions in the glibc testsuite when built with GCC-4.3 - gcj has a lot of regressions in 4.3 on alpha (but doesn't work in 4.2 either). - gij/gcj shows bus errors

Re: [Pkg-octave-devel] broken buildd (was: Suitesparse transition)

* Torsten Werner <[EMAIL PROTECTED]> [2008-03-22 20:49]: > On Sat, Mar 22, 2008 at 7:07 PM, Rafael Laboissiere <[EMAIL PROTECTED]> wrote: > > Could someone please give shogun back on arm, hoping that cats will not > > pick > > it up? > > I did a binary only upload because cats did pick it up.

Re: [Pkg-octave-devel] broken buildd (was: Suitesparse transition)

On Sat, Mar 22, 2008 at 7:07 PM, Rafael Laboissiere <[EMAIL PROTECTED]> wrote: > Could someone please give shogun back on arm, hoping that cats will not pick > it up? I did a binary only upload because cats did pick it up. Cheers, Torsten -- http://twerner.blogspot.com -- To UNSUBSCRIBE, e

Re: [Pkg-octave-devel] broken buildd (was: Suitesparse transition)

* Thomas Weber <[EMAIL PROTECTED]> [2008-03-20 10:20]: > On 20/03/08 09:19 +0100, Torsten Werner wrote: > > Hi, > > > > please see > > : > > > > lrwxrwxrwx 1 root root 29 May 23 2007 /etc/alter

kdelibs needs a binNMU because of openexr

kdelibs4c2a dependson libopenexr2ldbl which is no longer in unstable. I'm told that this is becuase of an openexr transition. Please binNMU kdelibs so that kdelibs4c2a will be built against the current version of openexr. Thanks stew signature.asc Description: Digital signature

Re: binNMUs for libffi transition

On Sat, Mar 22, 2008 at 05:50:00PM +0100, Sebastian Dröge wrote: > After that has finished please schedulebinNMUs for the > packages below on all archs (with dep-wait on the pygobject binNMU and > libffi-dev >= 3.0.4-1). Please explain. Several of this sources don't build-depend on a bin

Re: support of multiple python versions, python-dbg interpreter, fixing bashisms

severity 446636 important user debian-release@lists.debian.org usertags 446636 goal-python2.5 thanks Here is an updated patch with the extra build of the -dbg package removed. > and the main benefit is to support an action (changing your default > python version) that isn't supported in Debian an

Re: [SRM] Update of dns-flood-detector

Hi Philipp, On Saturday 22 March 2008 12:53, you wrote: > Then please depend on psmisc. Your method is *not* reliable. It > depends on the PID sequence number. You are using a shell script and > invoke `ps aux | grep $DAEMON' which means that $DAEMON will appear > as part of the cmdline of the

binNMUs for libffi transition

Hi, could someone schedule a binNMU for pygobject (against libffi-dev 3.0.4-1). After that has finished please schedulebinNMUs for the packages below on all archs (with dep-wait on the pygobject binNMU and libffi-dev >= 3.0.4-1). deskbar-applet emesene exaile gdesklets gedit gnome-games gnome-orca

Re: [SRM] Update of dns-flood-detector

On Sat, Mar 22, 2008 at 12:44:46AM +0100, Jan Wagner wrote: > On Friday 21 March 2008 23:36, Philipp Kern wrote: > > The approach looks weird to me. Wouldn't it be more sensible to just > > write out a pid file in the daemon? (i.e. in daemonize, and probably > > add a configuration option for it)

[SRM] Please review apache2 2.2.3-4+etch5

Hi, please review apache2 2.2.3-4+etch5 for inclusion in etch r4. Here is the changelog: apache2 (2.2.3-4+etch5) stable; urgency=low * Fix a regression introduced by the patch for CVE-2007-6421 which could lead to a segfault when viewing the balancer manager page. (Closes: #468289) *

Re: Please binNMU apache2-mpm-itk

Stefan Fritsch wrote: > Hi, Hi > apache2 2.2.8-3 is now installed on all architectures. Please binNMU > apache2-mpm-itk to build against this version. Scheduled. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Please binNMU apache2-mpm-itk

Hi, apache2 2.2.8-3 is now installed on all architectures. Please binNMU apache2-mpm-itk to build against this version. Thanks. Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: arm build of wireshark

Joost Yervante Damad wrote: > Hello, Hi > the build of wireshark failed on arm [1]. Yes, with an internal compiler error, aka a bug in gcc. > I'm not really sure what is the appropriate next step, either a binNMU or a > hint for a rebuild? If you're sure the internal compiler error has been f

arm build of wireshark

Hello, the build of wireshark failed on arm [1]. It appears to be an issue with the toolchain or the build machine ? I'm not really sure what is the appropriate next step, either a binNMU or a hint for a rebuild? if binNMU: wireshark_0.99.8-1, failed to build probably due to build machine iss

Re: Give back petsc [was: Re: Suitesparse transition]

* Rafael Laboissiere <[EMAIL PROTECTED]> [2008-03-20 22:43]: > * Adam C Powell IV <[EMAIL PROTECTED]> [2008-03-20 16:06]: > > > One other note: libmesh and petsc4py may need to be rebuilt after petsc > > goes in, didn't see those on your igloo. Let me know if you want to > > bin-NMU them; otherw