[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#612819: marked as done (pu: package libapache-mod-jk/1.2.30-1)

Your message dated Sat, 19 Mar 2011 14:30:29 +0000
with message-id <1300545030.15823.3680.camel@hathi.jungle.funky-badger.org>
and subject line Closing bugs for packages released in 6.0.1
has caused the Debian Bug report #612819,
regarding pu: package libapache-mod-jk/1.2.30-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

612819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612819
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@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_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 to squeeze but they are not
updating their kernel just yet and by doing so, the upgrades
of libapache2-mod-jk are broken due to this feature not
supported in older kernels.

IMO, it doesn't make sense to upload this to unstable.
The goal of this update is just to ease the upgrade of some
users that can't update their Linux kernel yet.

For wheezy this should not be an issue because by then the
kernels not supporting SOCK_CLOEXEC will be very outdated.

--- libapache-mod-jk-1.2.30.orig/native/configure
+++ libapache-mod-jk-1.2.30/native/configure
@@ -23025,10 +23025,14 @@ int main(void)
+    /* Recent Linux kernels support SOCK_CLOEXEC flag with socket(2) syscall,
+       if JK modules are built under kernels with SOCK_CLOEXEC support but
+       deployed under kernels without support, the modules just don't work.
+       Better disable this on squeeze and allow its usage on wheezy and beyond.
     if ((s = socket(AF_INET, SOCK_STREAM | SOCK_CLOEXEC, 0)) == -1)
-    exit(0);
+    */
+    exit(3);

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
Version: 6.0.1


These bugs all refer to stable updates which formed part of the 6.0.1
point release; I'm therefore closing them.



--- End Message ---

Reply to: