Various Cc's dropped, [EMAIL PROTECTED] added.
bod: we're talking about the grave perl bug, ie the patch for improving
the security model.
On Thu, Nov 13, 2003 at 03:28:35PM -0500, Matt Zimmerman wrote:
> On Thu, Nov 13, 2003 at 02:22:43PM -0600, Steve Langasek wrote:
> > On Thu, Nov 13, 2003 at
On Thu, Nov 13, 2003 at 07:37:14PM -0500, Nathanael Nerode wrote:
> >>Wouldn't it be more effective if you would try to fix these packages
>
> >>instead of proposing to remove them?
>
> No, it wouldn't.
>
> (1) I couldn't care less about these packages. I'm not competent to fix
> them and
> I
On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> Update:
>
>
> From the look of it, jack-audio-connection-kit is waiting only for
>
> * gem -- which seems to have experienced build failure for powerpc and hppa
> * wine -- which has a grave bug that it doesn't work on 2.6.0, I
Wouldn't it be more effective if you would try to fix these packages
instead of proposing to remove them?
No, it wouldn't.
(1) I couldn't care less about these packages. I'm not competent to fix them
and
I don't really want to.
(2) nurbs++ has been failing to build on HPPA since July, whi
Update:
From the look of it, jack-audio-connection-kit is waiting only for
* gem -- which seems to have experienced build failure for powerpc and hppa
* wine -- which has a grave bug that it doesn't work on 2.6.0, I posted a
workaround patch
and it will be ready for install.
regards,
On Thu, Nov 13, 2003 at 02:22:43PM -0600, Steve Langasek wrote:
> On Thu, Nov 13, 2003 at 09:13:37PM +0100, Adrian Bunk wrote:
> > But that's the decision of the perl maintainer and the security team.
>
> I think it's silly to claim that a flaw that's been well-known for ages
> constitutes an RC
On Thu, Nov 13, 2003 at 09:13:37PM +0100, Adrian Bunk wrote:
> > And although the patch in 220486 is a nice improvement if it works as
> > advertised, I don't think it should be considered RC given that suidperl
> > has been using the same flawed security model for years. So getting it
> > in syn
On Thu, Nov 13, 2003 at 10:36:20AM -0600, Steve Langasek wrote:
> On Thu, Nov 13, 2003 at 04:09:56PM +0100, Adrian Bunk wrote:
> > On Thu, Nov 13, 2003 at 12:28:39AM -0500, Nathanael Nerode wrote:
> >
> > > Are these four ready to be hinted in together, or am I missing something?
>
> > According
On Thu, Nov 13, 2003 at 04:09:56PM +0100, Adrian Bunk wrote:
> On Thu, Nov 13, 2003 at 12:28:39AM -0500, Nathanael Nerode wrote:
>
> > Are these four ready to be hinted in together, or am I missing something?
> According to update_output, at least PostgreSQL needs to go into
> testing before hei
On Thu, Nov 13, 2003 at 01:33:26AM -0500, Nathanael Nerode wrote:
> These are the qt2 packages. Currently they are held up because they
> break innovation3d and nurbs++ -- both of these have newer, c102
> versions in unstable which use qt3. They FTBFS on some architectures,
> so they can't go
On Thu, Nov 13, 2003 at 12:28:39AM -0500, Nathanael Nerode wrote:
> Are these four ready to be hinted in together, or am I missing something?
According to update_output, at least PostgreSQL needs to go into
testing before heimdal can go into testing.
PostgreSQL waits for glibc and perl.
glibc
On Thu, Nov 13, 2003 at 06:44:55AM -0600, Stephen R Marenka wrote:
> On Thu, Nov 13, 2003 at 11:29:18AM +0100, Michael Schmitz wrote:
>
> > > It seems to be listed as Building in wanna-build, but that was some time
> > > ago. Does anyone on m68k-build know?
> >
> > It's listed as building by adco
On Thu, Nov 13, 2003 at 11:29:18AM +0100, Michael Schmitz wrote:
> > It seems to be listed as Building in wanna-build, but that was some time
> > ago. Does anyone on m68k-build know?
>
> It's listed as building by adconrad-a4000t, started Oct. 20. There's no
> log of any sort. The previous build
> > Mozilla-firebird hasn't moved into testing because it is out of date
> > on m68k. Usually when this happens Bj�rn's page links to a log with
> > details on the failure, but as far as I can tell the build hasn't yet
> > been attempted. I know m68k sometimes runs late -- is it really
> > lagg
These are the qt2 packages. Currently they are held up because they
break innovation3d and nurbs++ -- both of these have newer, c102
versions in unstable which use qt3. They FTBFS on some architectures,
so they can't go in, but if they were removed from 'testing', it looks
like the qt2 packag
15 matches
Mail list logo