Bug#639865: Is there time to get an updated audit package into wheezy?

2012-06-20 Thread Julien Cristau
On Wed, Jun 20, 2012 at 09:08:43 -0700, Andrew Pollock wrote:

> I completely understand. I just thought I'd ask the question. So would
> introducing this into unstable have to wait until after the freeze, or after
> the release of wheezy?
> 
It would have to be after the release.  It could sit in experimental in
the mean time though.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#639865: Is there time to get an updated audit package into wheezy?

2012-06-20 Thread Andrew Pollock
On Wed, Jun 20, 2012 at 03:41:22AM +0200, Cyril Brulebois wrote:
> Hello Andrew.
> 
> Andrew Pollock  (19/06/2012):
> > I'm wondering if there's still time to update it (properly) before wheezy
> > freezes? It looks like it would involve a small library transition.
> > 
> > Assuming I get the maintainer's blessing to make such an upload, what say
> > the release managers?
> 
> This is horribly late. And knowing about the details would be a must at
> this point anyway (… but well, yes, we remember the libaudit fiasco).

What details would you like to know?
 
> > I believe this has been tried once before by an NMUer, and went horribly
> > wrong. If I understand correctly, this is because they didn't take the
> > library transition into consideration. I won't make that mistake :-)
> 
> As {a,the} maintainer of the X server, I wouldn't enjoy having to deal
> with possible audit-related breakages when trying to polish the X server
> and the X drivers for wheezy.

Would you expect breakage though? If the transition is handled correctly, I
wouldn't have thought this would be a huge deal (but then, this would be a
new experience for me).
 
> All in all, I think “far too late” is likely to be everyone's answer.
> See last paragraph of:
>   https://lists.debian.org/debian-devel-announce/2012/05/msg4.html
> 
> And it's been repeatedly announced we would likely freeze in June…

I completely understand. I just thought I'd ask the question. So would
introducing this into unstable have to wait until after the freeze, or after
the release of wheezy?

regards

Andrew


signature.asc
Description: Digital signature


Bug#639865: Is there time to get an updated audit package into wheezy?

2012-06-19 Thread Cyril Brulebois
Hello Andrew.

Andrew Pollock  (19/06/2012):
> I'm wondering if there's still time to update it (properly) before wheezy
> freezes? It looks like it would involve a small library transition.
> 
> Assuming I get the maintainer's blessing to make such an upload, what say
> the release managers?

This is horribly late. And knowing about the details would be a must at
this point anyway (… but well, yes, we remember the libaudit fiasco).

> I believe this has been tried once before by an NMUer, and went horribly
> wrong. If I understand correctly, this is because they didn't take the
> library transition into consideration. I won't make that mistake :-)

As {a,the} maintainer of the X server, I wouldn't enjoy having to deal
with possible audit-related breakages when trying to polish the X server
and the X drivers for wheezy.

All in all, I think “far too late” is likely to be everyone's answer.
See last paragraph of:
  https://lists.debian.org/debian-devel-announce/2012/05/msg4.html

And it's been repeatedly announced we would likely freeze in June…

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#639865: Is there time to get an updated audit package into wheezy?

2012-06-19 Thread Andrew Pollock
Hi,

The audit package in wheezy is quite old, and it seems like the maintainer
hasn't had time to update it lately[1]. There's some additional functionality
in the latest version that I'd like to see available in wheezy, and future
releases of Ubuntu.

I'm wondering if there's still time to update it (properly) before wheezy
freezes? It looks like it would involve a small library transition.

Assuming I get the maintainer's blessing to make such an upload, what say
the release managers?

I believe this has been tried once before by an NMUer, and went horribly
wrong. If I understand correctly, this is because they didn't take the
library transition into consideration. I won't make that mistake :-)

regards

Andrew

[1]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639865#27


signature.asc
Description: Digital signature