Bug#612819: pu: package libapache-mod-jk/1.2.30-1

2011-02-13 Thread Adam D. Barratt
On Sun, 2011-02-13 at 13:22 -0430, Miguel Landaeta wrote: > On Sun, Feb 13, 2011 at 12:46 PM, Adam D. Barratt > wrote: > > Fixing this in stable using the proposed patch would be okay; thanks for > > working on this. [...] > What would be the next step for this? > A sponsor must upload the fix to

Bug#612819: pu: package libapache-mod-jk/1.2.30-1

2011-02-13 Thread Miguel Landaeta
On Sun, Feb 13, 2011 at 12:46 PM, Adam D. Barratt wrote: > Fixing this in stable using the proposed patch would be okay; thanks for > working on this. > > Are there plans for packaging the 1.2.31 upstream release in unstable > soon?  I ask because currently stable and unstable have the same versio

Bug#612819: pu: package libapache-mod-jk/1.2.30-1

2011-02-13 Thread Adam D. Barratt
On Thu, 2011-02-10 at 16:41 -0500, Miguel Landaeta wrote: > libapache2-mod-jk 1.2.26 was built under a Linux kernel > without support for SOCK_CLOEXEC flag in socket(2) syscall. > OTOH, libapache2-mod-jk 1.2.30 was built under a Linux > kernel supporting that flag. > > Several users are upgrading

Bug#612819: pu: package libapache-mod-jk/1.2.30-1

2011-02-10 Thread Miguel Landaeta
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu The reason of this is to fix #609886 properly and allow upgrades of libapache2-mod-jk from lenny to squeeze. libapache2-mod-jk 1.2.26 was built under a Linux kernel without support for SOCK_CLO