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

Bug#725990: marked as done (pu: package torque/2.4.16+dfsg-1+deb7u2)

Your message dated Wed, 13 Nov 2013 20:47:55 +0100
with message-id <20131113194755.GA19386@eldamar.local>
and subject line Re: Bug#725990: pu: package torque/2.4.16+dfsg-1+deb7u2
has caused the Debian Bug report #725990,
regarding pu: package torque/2.4.16+dfsg-1+deb7u2
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
immediately.)


-- 
725990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725990
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

Hi Stable Release Managers

I know you are currently busy for the point release, so no hurry for
this one. During preparing the torque DSA-2770-1 I noticed that torque
FTBFS on kfreebsd-amd64 and kfreebsd-i386, and also did on wheezy
(a newer freebsd-utils package must have broken that, as previous
upload and build to unstable now in wheezy was fine)

I have filed #725870 and uploaded a fix to unstable on top of my
previous NMU already. The builds are now fine also for kfreebsd-amd64
and kfreebsd-i386[1].

 [1] https://buildd.debian.org/status/package.php?p=torque

Could you accept the attached proposed debdiff trough
stable-proposed-updates? (I know it's to late for 7.2, but meant for
7.3).

Regards,
Salvatore

diff -Nru torque-2.4.16+dfsg/debian/changelog torque-2.4.16+dfsg/debian/changelog
--- torque-2.4.16+dfsg/debian/changelog	2013-10-08 20:24:47.000000000 +0200
+++ torque-2.4.16+dfsg/debian/changelog	2013-10-10 21:11:12.000000000 +0200
@@ -1,3 +1,12 @@
+torque (2.4.16+dfsg-1+deb7u2) wheezy; urgency=low
+
+  * Non-maintainer upload.
+  * Add fix-FTBFS-on-kfreebsd.patch patch.
+    Fix FTBFS on kfreebsd-{amd64,i386} due to use of deprecated header
+    <nlist.h>. Switch to use <bsd/nlist.h>. (Closes: #725870)
+
+ -- Salvatore Bonaccorso <carnil@debian.org>  Thu, 10 Oct 2013 21:08:17 +0200
+
 torque (2.4.16+dfsg-1+deb7u1) wheezy-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru torque-2.4.16+dfsg/debian/patches/fix-FTBFS-on-kfreebsd.patch torque-2.4.16+dfsg/debian/patches/fix-FTBFS-on-kfreebsd.patch
--- torque-2.4.16+dfsg/debian/patches/fix-FTBFS-on-kfreebsd.patch	1970-01-01 01:00:00.000000000 +0100
+++ torque-2.4.16+dfsg/debian/patches/fix-FTBFS-on-kfreebsd.patch	2013-10-10 21:11:12.000000000 +0200
@@ -0,0 +1,20 @@
+Description: Fix FTBFS on kfreebsd-{amd64,i386}
+ Fix FTBFS on kfreebsd-{amd64,i386} due to use of deprecated header
+ <nlist.h>. Switch to use <bsd/nlist.h>.
+Origin: vendor
+Bug-Debian: http://bugs.debian.org/725870
+Forwarded: no
+Author: Salvatore Bonaccorso <carnil@debian.org>
+Last-Update: 2013-10-10
+
+--- a/src/resmom/freebsd5/mom_mach.c
++++ b/src/resmom/freebsd5/mom_mach.c
+@@ -109,7 +109,7 @@
+ #include <fcntl.h>
+ #include <errno.h>
+ #include <pwd.h>
+-#include <nlist.h>
++#include <bsd/nlist.h>
+ #include <fstab.h>
+ #include <kvm.h>
+ #include <signal.h>
diff -Nru torque-2.4.16+dfsg/debian/patches/series torque-2.4.16+dfsg/debian/patches/series
--- torque-2.4.16+dfsg/debian/patches/series	2013-10-08 20:24:47.000000000 +0200
+++ torque-2.4.16+dfsg/debian/patches/series	2013-10-10 21:11:12.000000000 +0200
@@ -5,3 +5,4 @@
 xpbs_xpbsmon_tclIndex.patch
 tcl85.patch
 CVE-2013-4319.patch
+fix-FTBFS-on-kfreebsd.patch

--- End Message ---
--- Begin Message --- 
Dear Stable Release Managers,

I have included the patch in the most recent stable-security upload
(DSA-2796-1), so closing this request.

torque in unstable has a new FTBFS on kfreebsd architectures, but at
first glance this seems a problem in the freebsd-libs package (not
checked yet).

Regards,
Salvatore

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: