Bug#941933: Reassigning this to normaliz, where it belongs

[Adam Conrad]

reassign 941933 libnormaliz-dev
kthxbye

I'm reassigning this bug to normaliz.  As noted by the polymake maintainer,
this is a question of normaliz headers missing a dependency, not polymake
itself being buggy.

In Ubuntu, I patched[1] normaliz to have the arch:any header package depend
on libeantic-dev on the same arches where we build-depend on and enable the
integration, and that did indeed cause polymake to be buildable[2] once
again (well, okay, I also cut the concurrency in half to avoid an entirely
different bug, but that's not relevant to this one :P).

... Adam

[1] 
http://launchpadlibrarian.net/447693482/normaliz_3.7.1+ds-3_3.7.1+ds-3ubuntu1.diff.gz
[2] https://launchpad.net/ubuntu/+source/polymake/3.2r4-4ubuntu1

Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!

[Adam Conrad]

On Sat, Apr 13, 2019 at 11:34:59PM +0200, Hilmar Preuße wrote:
> 
> The official caffe package builds fine, see [1]. Therefore I suspect
> that you use a different source package. Please provide the source
> package anywhere so we can reproduce/investigate the issue.

I'm not sure what makes you think the official caffe package builds,
as the docs (arch:all) haven't built in over 130 days.

I assure you, the testing I did was on sid, with the sid package.

... Adam

Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!

[Adam Conrad]

reopen 924829
kthxbye

caffe still doesn't build with unstable's texlive-extra, a quick tail:

Package longtable Warning: Column widths have changed
(longtable)in table 5.5 on input line 97.

! Improper \prevdepth.
\tabu@verticalspacing ...tempdimc \the \prevdepth 
  \@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
  
? 
! Emergency stop.
\tabu@verticalspacing ...tempdimc \the \prevdepth 
  \@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
  
!  ==> Fatal error occurred, no output PDF file produced!

A full log can be found at:

  
https://people.debian.org/~adconrad/caffe_1.0.0+git20180821.99bd997-2build2_amd64.build

... Adam

Bug#921031: Dpkg::Source::Package missing use of ::Format

[Adam Conrad]

Package: dpkg
Version: 1.19.4
Followup-For: Bug #921031
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * scripts/Dpkg/Source/Package.pm: use Dpkg::Source:Format (closes: #921031)

Simple enough patch, this seems to resolve the dgit autopkgtest
regressions for us.

... Adam

-- System Information:
Debian Release: buster/sid
  APT prefers disco
  APT policy: (500, 'disco')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-13-lowlatency (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru dpkg-1.19.4ubuntu2/debian/control dpkg-1.19.4ubuntu3/debian/control
--- dpkg-1.19.4ubuntu2/debian/control   2019-02-18 07:21:59.0 -0700
+++ dpkg-1.19.4ubuntu3/debian/control   2019-02-19 07:37:22.0 -0700
@@ -1,8 +1,7 @@
 Source: dpkg
 Section: admin
 Priority: required
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Dpkg Developers 
+Maintainer: Dpkg Developers 
 Uploaders: Guillem Jover 
 Origin: debian
 Bugs: debbugs://bugs.debian.org
diff -Nru dpkg-1.19.4ubuntu2/scripts/Dpkg/Source/Package.pm 
dpkg-1.19.4ubuntu3/scripts/Dpkg/Source/Package.pm
--- dpkg-1.19.4ubuntu2/scripts/Dpkg/Source/Package.pm   2019-01-23 
05:04:28.0 -0700
+++ dpkg-1.19.4ubuntu3/scripts/Dpkg/Source/Package.pm   2019-02-19 
07:37:16.0 -0700
@@ -56,6 +56,7 @@
 use Dpkg::Path qw(check_files_are_the_same find_command);
 use Dpkg::IPC;
 use Dpkg::Vendor qw(run_vendor_hook);
+use Dpkg::Source::Format;
 
 my $diff_ignore_default_regex = '
 # Ignore general backup files

Bug#913776: mozjs60: FTBFS with icu63; upstream cherry-pick attached

[Adam Conrad]

Package: mozjs60
Version: 60.2.3-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * icu_61_updates.patch: Cherrypick from upstream for icu >= 61.

This should be fairly self-explanatory.  A clean cherry-pick from upstream
to fix tests on icu >= 61, unsticking the ICU transition currently underway.

... Adam

-- System Information:
Debian Release: buster/sid
  APT prefers disco
  APT policy: (500, 'disco')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-10-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru mozjs60-60.2.3/debian/patches/icu_61_updates.patch 
mozjs60-60.2.3/debian/patches/icu_61_updates.patch
--- mozjs60-60.2.3/debian/patches/icu_61_updates.patch  1969-12-31 
17:00:00.0 -0700
+++ mozjs60-60.2.3/debian/patches/icu_61_updates.patch  2018-11-14 
12:48:17.0 -0700
@@ -0,0 +1,70 @@
+
+# HG changeset patch
+# User André Bargull 
+# Date 1522161640 25200
+# Node ID 3214fb35ccd684ada1d5cd230563c80b7f795fe7
+# Parent  b8ff6d9ecca3199c1b6721645c17c46f8a860cd3
+Bug 1445465 - Part 3: Update tests. r=Waldo
+
+diff --git a/js/src/tests/non262/Intl/NumberFormat/StringBuffer.js 
b/js/src/tests/non262/Intl/NumberFormat/StringBuffer.js
+--- a/js/src/tests/non262/Intl/NumberFormat/StringBuffer.js
 b/js/src/tests/non262/Intl/NumberFormat/StringBuffer.js
+@@ -5,13 +5,33 @@
+ 
+ // The implementation of the format function uses the C++ StringBuffer class,
+ // which changes its storage model at 32 characters, and uses it in a way 
which
+ // also means that there's no room for null-termination at this limit.
+ // This test makes sure that none of this affects the output.
+ 
+ var format = new Intl.NumberFormat("it-IT", {minimumFractionDigits: 1});
+ 
+-assertEq(format.format(1123123123123123123123.1), 
"1.123.123.123.123.120.000.000,0");
+-assertEq(format.format(12123123123123123123123.1), 
"12.123.123.123.123.100.000.000,0");
+-assertEq(format.format(123123123123123123123123.1), 
"123.123.123.123.123.000.000.000,0");
++assertEq(format.format(1123123123123123123123.1), 
"1.123.123.123.123.123.100.000,0");
++assertEq(format.format(12123123123123123123123.1), 
"12.123.123.123.123.122.000.000,0");
++assertEq(format.format(123123123123123123123123.1), 
"123.123.123.123.123.120.000.000,0");
++
++// Ensure the ICU output matches Number.prototype.toFixed.
++function formatToFixed(x) {
++var mfd = format.resolvedOptions().maximumFractionDigits;
++var s = x.toFixed(mfd);
++
++// To keep it simple we assume |s| is always in exponential form.
++var m = s.match(/^(\d)\.(\d+)e\+(\d+)$/);
++assertEq(m !== null, true);
++s = m[1] + m[2].padEnd(m[3], "0");
++
++// Group digits and append fractional part.
++m = s.match(/\d{1,3}(?=(?:\d{3})*$)/g);
++assertEq(m !== null, true);
++return m.join(".") + ",0";
++}
++
++assertEq(formatToFixed(1123123123123123123123.1), 
"1.123.123.123.123.123.100.000,0");
++assertEq(formatToFixed(12123123123123123123123.1), 
"12.123.123.123.123.122.000.000,0");
++assertEq(formatToFixed(123123123123123123123123.1), 
"123.123.123.123.123.120.000.000,0");
+ 
+ reportCompare(0, 0, "ok");
+diff --git a/js/src/tests/non262/Intl/NumberFormat/formatToParts.js 
b/js/src/tests/non262/Intl/NumberFormat/formatToParts.js
+--- a/js/src/tests/non262/Intl/NumberFormat/formatToParts.js
 b/js/src/tests/non262/Intl/NumberFormat/formatToParts.js
+@@ -210,17 +210,16 @@ var arPercentFormatter =
+ 
+ assertParts(arPercentFormatter, -135.32,
+ [MinusSign("\u{061C}-"),
+  Integer("١٣"),
+  Group("٬"),
+  Integer("٥٣٢"),
+  Decimal("٫"),
+  Fraction("٠٠"),
+- Literal("\xA0"),
+  PercentSign("٪\u{061C}")]);
+ 
+ // Decimals.
+ 
+ var usDecimalOptions =
+   {
+ style: "decimal",
+ maximumFractionDigits: 7 // minimum defaults to 0
+
diff -Nru mozjs60-60.2.3/debian/patches/series 
mozjs60-60.2.3/debian/patches/series
--- mozjs60-60.2.3/debian/patches/series2018-10-05 05:07:35.0 
-0600
+++ mozjs60-60.2.3/debian/patches/series2018-11-14 12:48:47.0 
-0700
@@ -18,3 +18,4 @@
 tests-Use-DEB_HOST_ARCH_BITS-to-skip-some-tests-on-64-bit.patch
 Skip-some-i18n-tests-because-we-are-now-using-system-ICU.patch
 tests-Expect-a-test-to-fail-on-big-endian.patch
+icu_61_updates.patch

Bug#913181: ruby2.5: FTBFS with tzdata >= 2018f; patch attached

[Adam Conrad]

Package: ruby2.5
Version: 2.5.1-6
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * 0012-test-time-tzdata-2018f.patch: Adjust tz tests for new tzdata.


Due to changes in past timestamps in tzdata 2018f, ruby2.5's testsuite
fails.  I've included a cherrypick of the upstream commit that fixes
this.

It probably makes sense to fix #911717 (missing build-dep on tzdata) at
the same time.

... Adam


-- System Information:
Debian Release: buster/sid
  APT prefers disco
  APT policy: (500, 'disco')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-10-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ruby2.5-2.5.1/debian/control ruby2.5-2.5.1/debian/control
--- ruby2.5-2.5.1/debian/control2018-09-23 12:43:14.0 -0600
+++ ruby2.5-2.5.1/debian/control2018-11-04 15:38:57.0 -0700
@@ -1,8 +1,7 @@
 Source: ruby2.5
 Section: ruby
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian Ruby Team 

+Maintainer: Debian Ruby Team 

 Uploaders: Antonio Terceiro ,
Chris Hofstaedtler 
 Build-Depends: bison,
diff -Nru ruby2.5-2.5.1/debian/patches/0012-test-time-tzdata-2018f.patch 
ruby2.5-2.5.1/debian/patches/0012-test-time-tzdata-2018f.patch
--- ruby2.5-2.5.1/debian/patches/0012-test-time-tzdata-2018f.patch  
1969-12-31 17:00:00.0 -0700
+++ ruby2.5-2.5.1/debian/patches/0012-test-time-tzdata-2018f.patch  
2018-11-04 15:38:57.0 -0700
@@ -0,0 +1,38 @@
+Description: Cherrypick fix for tzdata 2018f
+Author: Adam Conrad 
+Origin: 
https://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/test/ruby/test_time_tz.rb?r1=65296&r2=65365
+Forwarded: not-needed
+Last-Update: 2018-11-04
+
+--- trunk/test/ruby/test_time_tz.rb2018/10/22 01:25:29 65296
 trunk/test/ruby/test_time_tz.rb2018/10/26 01:47:09 65365
+@@ -88,7 +88,9 @@
+   has_lisbon_tz &&= have_tz_offset?("Europe/Lisbon")
+   CORRECT_TOKYO_DST_1951 = with_tz("Asia/Tokyo") {
+ if Time.local(1951, 5, 6, 12, 0, 0).dst? # noon, DST
+-  Time.local(1951, 5, 6, 1, 0, 0).dst?   # DST with fixed tzdata
++  if Time.local(1951, 5, 6, 1, 0, 0).dst? # DST with fixed tzdata
++Time.local(1951, 9, 8, 23, 0, 0).dst? ? "2018f" : "2018e"
++  end
+ end
+   }
+ 
+@@ -388,12 +390,16 @@
+ Asia/Singapore  Thu Dec 31 16:29:59 1981 UTC = Thu Dec 31 23:59:59 1981 SGT 
isdst=0 gmtoff=27000
+ Asia/Singapore  Thu Dec 31 16:30:00 1981 UTC = Fri Jan  1 00:30:00 1982 SGT 
isdst=0 gmtoff=28800
+ End
+-  gen_zdump_test CORRECT_TOKYO_DST_1951 ? <<'End' : <<'End'
++  gen_zdump_test CORRECT_TOKYO_DST_1951 ? <<'End' + (CORRECT_TOKYO_DST_1951 < 
"2018f" ? <<'2018e' : <<'2018f') : <<'End'
+ Asia/Tokyo  Sat May  5 14:59:59 1951 UTC = Sat May  5 23:59:59 1951 JST 
isdst=0 gmtoff=32400
+ Asia/Tokyo  Sat May  5 15:00:00 1951 UTC = Sun May  6 01:00:00 1951 JDT 
isdst=1 gmtoff=36000
++End
+ Asia/Tokyo  Sat Sep  8 13:59:59 1951 UTC = Sat Sep  8 23:59:59 1951 JDT 
isdst=1 gmtoff=36000
+ Asia/Tokyo  Sat Sep  8 14:00:00 1951 UTC = Sat Sep  8 23:00:00 1951 JST 
isdst=0 gmtoff=32400
+-End
++2018e
++Asia/Tokyo  Sat Sep  8 14:59:59 1951 UTC = Sun Sep  9 00:59:59 1951 JDT 
isdst=1 gmtoff=36000
++Asia/Tokyo  Sat Sep  8 15:00:00 1951 UTC = Sun Sep  9 00:00:00 1951 JST 
isdst=0 gmtoff=32400
++2018f
+ Asia/Tokyo  Sat May  5 16:59:59 1951 UTC = Sun May  6 01:59:59 1951 JST 
isdst=0 gmtoff=32400
+ Asia/Tokyo  Sat May  5 17:00:00 1951 UTC = Sun May  6 03:00:00 1951 JDT 
isdst=1 gmtoff=36000
+ Asia/Tokyo  Fri Sep  7 15:59:59 1951 UTC = Sat Sep  8 01:59:59 1951 JDT 
isdst=1 gmtoff=36000
diff -Nru ruby2.5-2.5.1/debian/patches/series 
ruby2.5-2.5.1/debian/patches/series
--- ruby2.5-2.5.1/debian/patches/series 2018-11-04 01:39:53.0 -0700
+++ ruby2.5-2.5.1/debian/patches/series 2018-11-04 15:38:57.0 -0700
@@ -19,3 +19,4 @@
 rubygems-2388.patch
 0010-test-test_pair-fix-deadlock-in-test_connect_accept_n.patch
 0011-test-use-larger-keys-for-SSL-tests.patch
+0012-test-time-tzdata-2018f.patch

Bug#895463: keyutils FTBFS: Can't Determine Endianness

[Adam Conrad]

Package: keyutils
Version: 1.5.9-9.2
Followup-For: Bug #895463
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/endianness-and-PIE.patch: Adjust to work with file 5.33.

This is a follow-up to Steve's patch to make it also work with the
newer file, which reports PIE executables as 'pie executable'.

... Adam


-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-20-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru keyutils-1.5.9/debian/patches/endianness-and-PIE.patch 
keyutils-1.5.9/debian/patches/endianness-and-PIE.patch
--- keyutils-1.5.9/debian/patches/endianness-and-PIE.patch  2018-04-17 
22:21:12.0 -0600
+++ keyutils-1.5.9/debian/patches/endianness-and-PIE.patch  2018-05-07 
11:43:57.0 -0600
@@ -1,9 +1,10 @@
 Description: fix regexp match against `file /proc/$$/exe` for -fPIE bash
  Now that bash is built with PIE enabled, keyutils' check for endianness
  fails because file no longer returns "executable", but instead returns
- "shared object".  Update our regexps to be portable.
+ "shared object" for file << 5.33 and "pie executable" for file >= 5.33.
 Author: Steve Langasek 
-Last-Modified: 2018-04-17
+Author: Adam Conrad 
+Last-Modified: 2018-05-07
 
 Index: keyutils-1.5.9/tests/toolbox.inc.sh
 ===
@@ -14,11 +15,11 @@
  
  endian=`file -L /proc/$$/exe`
 -if expr "$endian" : '.* MSB executable.*' >&/dev/null
-+if expr "$endian" : '.* MSB \(executable\|shared object\).*' >&/dev/null
++if expr "$endian" : '.* MSB \(executable\|shared object\|pie executable\).*' 
>&/dev/null
  then
  endian=BE
 -elif expr "$endian" : '.* LSB executable.*' >&/dev/null
-+elif expr "$endian" : '.* LSB \(executable\|shared object\).*' >&/dev/null
++elif expr "$endian" : '.* LSB \(executable\|shared object\|pie 
executable\).*' >&/dev/null
  then
  endian=LE
  else

Bug#891672: libdbi-drivers FTBFS with freetds-dev 1.00.82-2

[Adam Conrad]

Package: libdbi-drivers
Version: 0.9.0-5
Followup-For: Bug #891672
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch


In Ubuntu, the attached patch was applied to achieve the following:

  * freetds-1.0-fix.patch: Upstream cherrypick to fix FTFBS with freetds 1.0.

This should be self-explanatory, it's a straight cherrypick from upstream.

... Adam

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-13-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libdbi-drivers-0.9.0/debian/patches/freetds-1.0-fix.patch 
libdbi-drivers-0.9.0/debian/patches/freetds-1.0-fix.patch
--- libdbi-drivers-0.9.0/debian/patches/freetds-1.0-fix.patch   1969-12-31 
17:00:00.0 -0700
+++ libdbi-drivers-0.9.0/debian/patches/freetds-1.0-fix.patch   2018-04-23 
07:00:13.0 -0600
@@ -0,0 +1,51 @@
+commit 3bf3e4a856604703c4070bdebbe42fe0068f540a
+Author: Jan Engelhardt 
+Date:   Fri Jan 27 09:55:41 2017 +0100
+
+freetds: resolve compile error with 1.0
+
+dbd_freetds.c: In function "dbd_connect":
+dbd_freetds.c:232:12: error: "CS_TDS_80" undeclared (first use in this 
function)
+  num = CS_TDS_80;
+
+freetds 1.0 has dropped the CS_TDS_80 identifier. In 0.95, it defined
+CS_TDS_80=CS_TDS_71, while 0.91 has no CS_TDS_71, which is why a full
+autoconf check is needed.
+
+diff --git a/acinclude.m4 b/acinclude.m4
+index 45db616..85eec28 100644
+--- a/acinclude.m4
 b/acinclude.m4
+@@ -562,6 +562,19 @@ if test "$ac_freetds" = "yes"; then
+   AC_SUBST(FREETDS_LIBS)
+   AC_SUBST(FREETDS_INCLUDE)
+   AC_SUBST(FREETDS_LDFLAGS)
++
++  AH_TEMPLATE([DBI_CS_TDS_80], [])
++  AC_MSG_CHECKING([CS_TDS_80])
++  AC_COMPILE_IFELSE([AC_LANG_SOURCE([
++  #include 
++  int x = CS_TDS_80;
++  ])], [
++  AC_DEFINE([DBI_CS_TDS_80], [CS_TDS_80])
++  AC_MSG_RESULT([CS_TDS_80])
++  ], [
++  AC_DEFINE([DBI_CS_TDS_80], [CS_TDS_71])
++  AC_MSG_RESULT([CS_TDS_71])
++  ])
+ else
+   AC_MSG_RESULT(no)
+ fi
+diff --git a/drivers/freetds/dbd_freetds.c b/drivers/freetds/dbd_freetds.c
+index 22fddfd..d01f13b 100644
+--- a/drivers/freetds/dbd_freetds.c
 b/drivers/freetds/dbd_freetds.c
+@@ -229,7 +229,7 @@ int dbd_connect(dbi_conn_t * conn)
+   switch (str[0]) {
+ //  We can use it if "CS_TDS_80" will be add to ct_con_props() by CS_SET 
action
+   case '8':
+-  num = CS_TDS_80;
++  num = DBI_CS_TDS_80;
+   break;
+   case '7':
+   num = CS_TDS_70;
diff -Nru libdbi-drivers-0.9.0/debian/patches/series 
libdbi-drivers-0.9.0/debian/patches/series
--- libdbi-drivers-0.9.0/debian/patches/series  2016-11-27 09:31:42.0 
-0700
+++ libdbi-drivers-0.9.0/debian/patches/series  2018-04-23 07:00:35.0 
-0600
@@ -5,3 +5,4 @@
 fix_ftbfs_on_hurd.patch
 dbd_sqlite3_resolve_a_stack_buffer_overflow.patch
 mysql-5.7.patch
+freetds-1.0-fix.patch

Bug#880072: [Pkg-javascript-devel] Bug#880072: node-mapnik doesn't appear to be linking correctly, making it unusable

[Adam Conrad]

On Sun, Oct 29, 2017 at 12:54:07PM +0100, Sebastiaan Couwenberg wrote:
> 
> I think the node-mapnik package and its node-tilelive-* rdeps should be
> removed from Debian (and by extension Ubuntu), and we should give up on
> ever packaging kosmtik (#805308).

If you file an ftp.d.o removal bug to that effect, I'll be more than
happy to also remove it from Ubuntu.  I certainly have no sentimental
attachment to it, after spending time arguing with it blocking some
transitions for me. :P

... Adam

Bug#880072: node-mapnik doesn't appear to be linking correctly, making it unusable

[Adam Conrad]

Package: node-mapnik
Version: 3.6.2+dfsg-1
Severity: grave
Justification: renders package unusable

On both Debian and Ubuntu, executing the simple autopkgtest command for
node-mapnik (nodejs -e "require('mapnik');") leads to an error resolving
symbols:

Debian:
---
Error: /usr/lib/nodejs/mapnik/lib/binding/mapnik.node: undefined symbol: 
_ZN6mapnik15freetype_engine10face_namesEv
at Error (native)
at Object.Module._extensions..node (module.js:597:18)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/lib/nodejs/mapnik/lib/mapnik.js:31:15)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)

Ubuntu:
---
Error: /usr/lib/nodejs/mapnik/lib/binding/mapnik.node: undefined symbol: 
_ZN6mapnik14save_to_stringINS_5imageINS_7rgba8_tESsRKT_RKSsRKNS_12rgba_paletteE
at Error (native)
at Object.Module._extensions..node (module.js:597:18)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/lib/nodejs/mapnik/lib/mapnik.js:31:15)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)

This pretty clearly makes the package entirely unusable (unless there's
some other way to use it correctly, and the autopkgtest is incorrect?)

... Adam

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-16-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages node-mapnik depends on:
ii  libc6  2.26-0ubuntu2
ii  libgcc11:7.2.0-12ubuntu1
pn  libmapnik3.0   
ii  libstdc++6 7.2.0-12ubuntu1
pn  mapnik-utils   
pn  node-pre-gyp   
pn  nodejs 
pn  nodejs-abi-48  
pn  nodejs-dev 

Versions of packages node-mapnik recommends:
pn  node-carto
pn  node-srs  
pn  node-zipfile  

node-mapnik suggests no packages.

Bug#879798: FTBFS: testsuite fails with dpkg 1.19, patch attached

[Adam Conrad]

On Thu, Oct 26, 2017 at 08:59:23PM +0200, Mattia Rizzolo wrote:
> On Wed, Oct 25, 2017 at 10:40:20PM -0600, Adam Conrad wrote:
> 
> We like to backport devscripts, and I'd rather not have backports deltas
> if possible...

I'd suggest that this commit already makes no-delta backports somewhat
problematic:

https://anonscm.debian.org/git/collab-maint/devscripts.git/commit/?id=921696fd6c92c4299accb1e2ef1ae48d13a47b0d

But ignoring that for a moment, how about this patch instead (tested
against dpkg 1.18.24ubuntu1 and 1.19.0.4ubuntu1):

diff -Nru devscripts-2.17.10/test/test_mk-origtargz 
devscripts-2.17.10ubuntu2/test/test_mk-origtargz
--- devscripts-2.17.10/test/test_mk-origtargz   2017-09-13 20:08:30.0 
-0600
+++ devscripts-2.17.10ubuntu2/test/test_mk-origtargz2017-10-26 
22:38:49.0 -0600
@@ -26,6 +26,12 @@
 PROGNAME="mk-origtargz.pl"
 fi
 
+if dpkg --compare-versions $(dpkg-query -W -f='${Version}' libdpkg-perl) lt 
1.19.0~; then
+SUBPROCESS_ERROR="gave error exit status 2"
+else
+SUBPROCESS_ERROR="subprocess returned exit status 2"
+fi
+
 cleanup(){
rm -rf $TMPDIR
unset LC_ALL
@@ -540,7 +546,7 @@
"tar: This does not look like a tar archive
 tar: Skipping to next header
 tar: Exiting with failure status due to previous errors
-$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
gave error exit status 2" \
+$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
$SUBPROCESS_ERROR" \
"" \
 ../foo-0.1.tar.gz --repack --compression xz
 }

... Adam

Bug#879798: FTBFS: testsuite fails with dpkg 1.19, patch attached

[Adam Conrad]

Package: devscripts
Version: 2.17.10
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * test/test_mk-origtargz: Adjust test for dpkg 1.19's ErrorHandling.pm.

Fairly self-explanatory, I'd think.  In dpkg 1.19, ErrorHandling.pm was
normalised to match libdpkg error messages, and this means the expected
error in the mk-origtargz test is now incorrect.  This patch fixes that.

... Adam

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-16-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru devscripts-2.17.10/test/test_mk-origtargz 
devscripts-2.17.10ubuntu1/test/test_mk-origtargz
--- devscripts-2.17.10/test/test_mk-origtargz   2017-09-13 20:08:30.0 
-0600
+++ devscripts-2.17.10ubuntu1/test/test_mk-origtargz2017-10-25 
22:29:09.0 -0600
@@ -540,7 +540,7 @@
"tar: This does not look like a tar archive
 tar: Skipping to next header
 tar: Exiting with failure status due to previous errors
-$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
gave error exit status 2" \
+$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
subprocess returned exit status 2" \
"" \
 ../foo-0.1.tar.gz --repack --compression xz
 }

Bug#813065: mgltools-gle: FTBFS in sid: Error: Unknown SWIG preprocessor directive: typemaps

[Adam Conrad]

Package: mgltools-gle
Version: 1.5.7~rc1+cvs.20140424-1
Followup-For: Bug #813065
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * typemap-comments.patch: Fix FTBFS with stricter new swig (LP: #1562470)

Turns out the FTBFS was just a result of using an incorrect comment style
in the code which the newer swig is stricter about.  This patch fixes that.

... Adam


-- System Information:
Debian Release: stretch/sid
  APT prefers yakkety
  APT policy: (500, 'yakkety')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-21-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/series mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/series
--- mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/series	1969-12-31 17:00:00.0 -0700
+++ mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/series	2016-04-30 22:22:43.0 -0600
@@ -0,0 +1 @@
+typemap-comments.patch
diff -Nru mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/typemap-comments.patch mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/typemap-comments.patch
--- mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/typemap-comments.patch	1969-12-31 17:00:00.0 -0700
+++ mgltools-gle-1.5.7~rc1+cvs.20140424/debian/patches/typemap-comments.patch	2016-04-30 22:23:05.0 -0600
@@ -0,0 +1,42 @@
+Description: Fix FTBFS with stricter new swig
+Author: Adam Conrad 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1562470
+
+--- mgltools-gle-1.5.7~rc1+cvs.20140424.orig/gle/gle.i
 mgltools-gle-1.5.7~rc1+cvs.20140424/gle/gle.i
+@@ -149,7 +149,7 @@ glePolyCone_c4f (int npoints,	 /* numpoi
+gleColor4f color_array[1],	/* colors at polyline verts */
+gleDouble radius_array[1]); /* cone radii at polyline verts */
+ 
+-#typemaps for Numeric arrays
++/* typemaps for Numeric arrays */
+ DOUBLE_ARRAY2D( contour, [1][2], ncp )
+ %apply double ARRAY2D[ANY][ANY] { double cont_normal[1][2] };
+ %apply double VECTOR_NULL[ANY] { double up[3] };
+@@ -172,7 +172,7 @@ gleExtrusion_c4f (int ncp, /* nu
+ gleDouble point_array[1][3], /* polyline vertices */
+ gleColor4f color_array[1]); /* colors at polyline verts */
+ 
+-#typemaps for Numeric arrays
++/* typemaps for Numeric arrays */
+ %apply double VECTOR[ANY] { double twist_array[1] };
+ 
+ /* extrude 2D contour, specifying local rotations (twists) */
+@@ -195,7 +195,7 @@ gleTwistExtrusion_c4f (int ncp,
+ gleDouble twist_array[1]);   /* countour twists (in degrees) */
+ 
+ 
+-#typemaps for Numeric arrays
++/* typemaps for Numeric arrays */
+ %apply double ARRAY3D_NULL[ANY][ANY][ANY] { double xform_array[1][2][3] };
+ 
+ /* extrude 2D contour, specifying local affine tranformations */
+@@ -218,7 +218,7 @@ gleSuperExtrusion_c4f (int ncp,  /* numb
+ gleColor4f color_array[1],/* color at polyline verts */
+ gleDouble xform_array[1][2][3]);   /* 2D contour xforms */
+ 
+-#typemaps for Numeric arrays
++/* typemaps for Numeric arrays */
+ %apply double ARRAY2D_NULL[ANY][ANY] { double startXform[2][3] };
+ %apply double ARRAY2D_NULL[ANY][ANY] { double dXformdTheta[2][3] };
+ 

Bug#819605: FTBFS: testsuite failed (patch attached)

[Adam Conrad]

Package: cupt
Version: 2.9.4
Followup-For: Bug #819605
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Unset APT_CONFIG to fix testsuite under newer sbuild (Closes: #819605)

Should be self-explanatory.  Thanks for considering the patch.

... Adam


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-20-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru cupt-2.9.4/test/TestCupt.pm cupt-2.9.4ubuntu1/test/TestCupt.pm
--- cupt-2.9.4/test/TestCupt.pm	2016-02-14 05:37:21.0 -0700
+++ cupt-2.9.4ubuntu1/test/TestCupt.pm	2016-04-16 16:10:07.0 -0600
@@ -134,6 +134,7 @@
 
 	$pre_conf =~ s//$cwd/g;
 	generate_file('pre.conf', $pre_conf);
+	$ENV{'APT_CONFIG'} = '';
 	$ENV{'CUPT_PRE_CONFIG'} = "./pre.conf";
 
 	generate_file(get_extended_states_path(), $options{'extended_states'}//'');

Bug#794906: uhd 3.8 ftbfs on arm64, 3.7 built fine before on arm64

[Adam Conrad]

Package: uhd
Version: 3.8.5-1
Followup-For: Bug #794906
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * 0099-revert-neon-changes.patch: Revert the NEON changes from upstream
commit 1b149f561370687ad65e3aa644a402f00dbd16ea to fix build on arm64.

This is obviously not the ideal solution, one should probably fix the
NEON bits to work for both ARM architectures, but this revert doesn't
change any public symbols and seems to work on armhf and arm64, so it
was the path of least resistance while we're pushing through the g++5
transition.

... Adam

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-3-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch
--- uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch	1969-12-31 17:00:00.0 -0700
+++ uhd-3.8.5/debian/patches/0099-revert-neon-changes.patch	2015-08-07 16:38:09.0 -0600
@@ -0,0 +1,113 @@
+Description: Revert the NEON changes from upstream commit
+ 1b149f561370687ad65e3aa644a402f00dbd16ea to fix arm64.
+Author: Adam Conrad 
+Bug-Debian: https://bugs.debian.org/794906
+
+--- uhd-3.8.5.orig/host/lib/convert/CMakeLists.txt
 uhd-3.8.5/host/lib/convert/CMakeLists.txt
+@@ -95,11 +95,8 @@ IF(CMAKE_COMPILER_IS_GNUCXX)
+ ENDIF(CMAKE_COMPILER_IS_GNUCXX)
+ 
+ IF(HAVE_ARM_NEON_H)
+-ENABLE_LANGUAGE(ASM)
+-
+ LIBUHD_APPEND_SOURCES(
+ ${CMAKE_CURRENT_SOURCE_DIR}/convert_with_neon.cpp
+-${CMAKE_CURRENT_SOURCE_DIR}/convert_neon.S
+ )
+ ENDIF()
+ 
+--- uhd-3.8.5.orig/host/lib/convert/convert_neon.S
 /dev/null
+@@ -1,37 +0,0 @@
+-//
+-// Copyright 2014 Ettus Research LLC
+-//
+-// This program is free software: you can redistribute it and/or modify
+-// it under the terms of the GNU General Public License as published by
+-// the Free Software Foundation, either version 3 of the License, or
+-// (at your option) any later version.
+-//
+-// This program is distributed in the hope that it will be useful,
+-// but WITHOUT ANY WARRANTY; without even the implied warranty of
+-// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+-// GNU General Public License for more details.
+-//
+-// You should have received a copy of the GNU General Public License
+-// along with this program.  If not, see <http://www.gnu.org/licenses/>.
+-//
+-
+-	.arch armv7-a
+-	.fpu neon
+-	.syntax unified
+-	.text
+-	.align 2
+-	.global neon_item32_sc16_swap_16n
+-	.type neon_item32_sc16_swap_16n, %function
+-neon_item32_sc16_swap_16n:
+-.loop_swap:
+-	vld2.16  {q0, q1}, [r0]!
+-	vld2.16  {q2, q3}, [r0]!
+-	vswp   q0, q1
+-	vswp   q2, q3
+-	vst2.16  {q0, q1}, [r1]!
+-	vst2.16  {q2, q3}, [r1]!
+-	subs   r2, #1
+-	bne  .loop_swap
+-	bx lr
+-	.size neon_item32_sc16_swap_16n, .-neon_item32_sc16_swap_16n
+-	.section .note.GNU-stack,"",%progbits
+--- uhd-3.8.5.orig/host/lib/convert/convert_with_neon.cpp
 uhd-3.8.5/host/lib/convert/convert_with_neon.cpp
+@@ -1,5 +1,5 @@
+ //
+-// Copyright 2011-2014 Ettus Research LLC
++// Copyright 2011-2012 Ettus Research LLC
+ //
+ // This program is free software: you can redistribute it and/or modify
+ // it under the terms of the GNU General Public License as published by
+@@ -19,12 +19,6 @@
+ #include 
+ #include 
+ 
+-extern "C" {
+-void neon_item32_sc16_swap_16n(void *, void *, int iter);
+-}
+-
+-static const int SIMD_WIDTH = 16;
+-
+ using namespace uhd::convert;
+ 
+ DECLARE_CONVERTER(fc32, 1, sc16_item32_le, 1, PRIORITY_SIMD){
+@@ -64,31 +58,3 @@ DECLARE_CONVERTER(sc16_item32_le, 1, fc3
+ 
+ item32_sc16_to_xx(input+i, output+i, nsamps-i, scale_factor);
+ }
+-
+-DECLARE_CONVERTER(sc16, 1, sc16_item32_le, 1, PRIORITY_SIMD){
+-const sc16_t *input = reinterpret_cast(inputs[0]);
+-item32_t *output = reinterpret_cast(outputs[0]);
+-
+-size_t i = nsamps / SIMD_WIDTH;
+-
+-if (i)
+-neon_item32_sc16_swap_16n((void *) input, (void *) output, i);
+-
+-i *= SIMD_WIDTH;
+-
+-xx_to_item32_sc16(input+i, output+i, nsamps-i, scale_factor);
+-}
+-
+-DECLARE_CONVERTER(sc16_item32_le, 1, sc16, 1, PRIORITY_SIMD){
+-const item32_t *input = reinterpret_cast(inputs[0]);
+-sc16_t *output = reinterpret_cast(outputs[0]);
+-
+-size_t i = nsamps / SIMD_WIDTH;
+-
+-if (i)
+-neon_item32_sc16_swap_16n((void *) input, (void *) output, i);
+-
+-i *= SIMD_WIDTH;
+-
+-item32_sc16_to_xx(input+i, output+i, nsamps-i

Bug#790101: FTBFS: Missing build-dependency on help2man; patch attached

[Adam Conrad]

Package: tex-common
Version: 6.01
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Add missing build-dependency on help2man.

Without this patch, the build fails with the following error:

cd scripts; help2man -n "generate hyphenation configuration for TeX engines" -s 
8 -S Debian  -N ./update-language > update-language.8
/bin/sh: 1: help2man: not found
make: *** [build-stamp] Error 127

... Adam


-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-3-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.55ubuntu2
ii  dpkg   1.17.25ubuntu1
ii  libpaper-utils 1.1.24+nmu2ubuntu3
ii  texlive-binaries   2014.20140926.35254-6build2
ii  ucf3.0030
ii  xdg-utils  1.1.0~rc1-2ubuntu11

Versions of packages texlive-base recommends:
pn  lmodern  

Versions of packages texlive-base suggests:
ii  evince [postscript-viewer]   3.16.1-0ubuntu1
ii  ghostscript [postscript-viewer]  9.15+dfsg-0ubuntu3
pn  perl-tk  
pn  xpdf-reader | pdf-viewer 

Versions of packages texlive-binaries depends on:
ii  dpkg  1.17.25ubuntu1
ii  install-info  5.2.0.dfsg.1-6
ii  libc6 2.21-0ubuntu4
ii  libfontconfig12.11.1-0ubuntu6
ii  libgcc1   1:5.1.1-12ubuntu1
ii  libgmp10  2:6.0.0+dfsg-6ubuntu1
ii  libgraphite2-31.2.4-3ubuntu1
ii  libgs99.15+dfsg-0ubuntu3
ii  libharfbuzz-icu0  0.9.40-3
ii  libharfbuzz0b 0.9.40-3
ii  libicu52  52.1-9
ii  libkpathsea6  2014.20140926.35254-6build2
ii  libmpfr4  3.1.3-1
ii  libpaper1 1.1.24+nmu2ubuntu3
ii  libpixman-1-0 0.32.6-3
ii  libpoppler52  0.33.0-0ubuntu1
ii  libpotrace0   1.12-1
ii  libptexenc1   2014.20140926.35254-6build2
ii  libstdc++65.1.1-12ubuntu1
ii  libsynctex1   2014.20140926.35254-6build2
ii  libx11-6  2:1.6.3-1ubuntu1
ii  libxaw7   2:1.0.12-2
ii  libxi62:1.7.4-1
ii  libxmu6   2:1.1.2-1
ii  libxpm4   1:3.5.11-1
ii  libxt61:1.1.4-1
ii  libzzip-0-13  0.13.62-3
ii  perl  5.20.2-6
ii  zlib1g1:1.2.8.dfsg-2ubuntu1

Versions of packages texlive-binaries recommends:
ii  python2.7.9-1
ii  ruby  1:2.1.0.4ubuntu1
ii  texlive-base  2014.20141024-2ubuntu1
ii  tk [wish] 8.6.0+6ubuntu3
diff -Nru tex-common-6.01/debian/control tex-common-6.01ubuntu1/debian/control
--- tex-common-6.01/debian/control	2015-06-24 23:41:50.0 -0600
+++ tex-common-6.01ubuntu1/debian/control	2015-06-26 21:22:54.0 -0600
@@ -4,7 +4,7 @@
 Maintainer: Debian TeX maintainers 
 Uploaders: Julian Gilbey , Frank Küster , Florent Rougon , Norbert Preining 
 Build-Depends: debhelper (>= 8.1.0~)
-Build-Depends-Indep: debiandoc-sgml
+Build-Depends-Indep: debiandoc-sgml, help2man
 Standards-Version: 3.9.6
 Vcs-Git: git://anonscm.debian.org/debian-tex/tex-common.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=debian-tex/tex-common.git

Bug#789743: FTBFS: lacking build-depends; patch attached

[Adam Conrad]

Package: scala-parser-combinators
Version: 1.0.3-2
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Added the missing build dependency on default-jdk.

This is fairly straightforward.  One can see the build failing here:

https://launchpad.net/ubuntu/+source/scala-parser-combinators/1.0.3-2

And succeeding with the attached patch here:

https://launchpad.net/ubuntu/+source/scala-parser-combinators/1.0.3-2ubuntu1

... Adam

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru scala-parser-combinators-1.0.3/debian/control scala-parser-combinators-1.0.3/debian/control
--- scala-parser-combinators-1.0.3/debian/control	2015-06-17 07:28:48.0 -0600
+++ scala-parser-combinators-1.0.3/debian/control	2015-06-23 18:55:06.0 -0600
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Java Maintainers 
 Uploaders: Emmanuel Bourg 
-Build-Depends: debhelper (>= 9), maven-repo-helper, scala (>= 2.11)
+Build-Depends: debhelper (>= 9), default-jdk, maven-repo-helper, scala (>= 2.11)
 Standards-Version: 3.9.6
 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-java/scala-parser-combinators.git
 Vcs-Git: git://anonscm.debian.org/pkg-java/scala-parser-combinators.git

Bug#749718: FTBFS on s390x (and others)

[Adam Conrad]

On Fri, May 30, 2014 at 06:15:59PM +0900, Norbert Preining wrote:
> > Ubuntu tried on arm64[1] and ppc64el[2], and the Debian tried on
> > ppc64[3], all failed the same way as the s390x and hppa failures:

Also, I cherry-picked your git commit, and it doesn't actually work
as advertised.  See below:

---
(base)adconrad@cthulhu:~/review/tex$ cat Makefile 
LUAJIT_FAIL_ARCHS="s390x hppa ppc64 ppc64el arm64"
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
ifneq (,$(filter $(DEB_HOST_ARCH), $(LUAJIT_FAIL_ARCHS)))
  DISABLE_JIT=--disable-luajittex
endif

foo:
echo $(DISABLE_JIT)
(base)adconrad@cthulhu:~/review/tex$ for i in s390x hppa ppc64 ppc64el arm64; 
do echo $i; DEB_HOST_ARCH=$i make; done
s390x
echo 

hppa
echo --disable-luajittex
--disable-luajittex
ppc64
echo --disable-luajittex
--disable-luajittex
ppc64el
echo --disable-luajittex
--disable-luajittex
arm64
echo 
---

If you change that to 'LUAJIT_FAIL_ARCHS=" s390x hppa ppc64 ppc64el arm64 "'
(note the leading and trailing space), then it catches all of the arches.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#749718: FTBFS on s390x (and others)

[Adam Conrad]

On Fri, May 30, 2014 at 06:10:00PM +0900, Norbert Preining wrote:
> On Fri, 30 May 2014, Adam Conrad wrote:
> > > +LUAJIT_FAIL_ARCHS="s390x hppa"
> > > 
> > > Looks like this should also include ppc64 and ppc64el, at least.
> > 
> > And also arm64 ...
> 
> Ahh, but for all of them the build succeed, right?
> 
> We have already tests in TeX Live source code and automatically
> disable luajittex for most archs ... only a few actually failed.
> 
> So guys, did you *try* to build the source code and it failed?

Ubuntu tried on arm64[1] and ppc64el[2], and the Debian tried on
ppc64[3], all failed the same way as the s390x and hppa failures:

[1] 
https://launchpad.net/ubuntu/+source/texlive-bin/2014.20140528.34243-1/+build/6053703
[2] 
https://launchpad.net/ubuntu/+source/texlive-bin/2014.20140528.34243-1/+build/6053707
[3] 
http://buildd.debian-ports.org/status/fetch.php?pkg=texlive-bin&arch=ppc64&ver=2014.20140522.34183-1&stamp=1400795747

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#749718: FTBFS on s390x (and others)

[Adam Conrad]

On Fri, May 30, 2014 at 06:07:27PM +0900, Norbert Preining wrote:
> On Fri, 30 May 2014, Adam Conrad wrote:
> > > Looks like this should also include ppc64 and ppc64el, at least.
> > 
> > And also arm64 ...
> 
> Hmmm, armel and armhf are fine?

armel and armhf should be fine, yes.  Though, as noted earlier in the
bug, it's pretty poor form to use embedded libraries (and runtimes!)
anyway, so is this a feature we really need?  Can it be built against
the system liblua/libluajit?

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#749718: FTBFS on s390x (and others)

[Adam Conrad]

> +LUAJIT_FAIL_ARCHS="s390x hppa"
> 
> Looks like this should also include ppc64 and ppc64el, at least.

And also arm64 ...

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745866: FileFd::Size failure on all big-endian architectures (patch attached)

[Adam Conrad]

On Sat, Apr 26, 2014 at 11:23:49AM +0200, David Kalnischkies wrote:
> 
> After a bit of talking on IRC, we agreed that both patches and than some
> should be applied. Beside that it hopefully still fixes the build
> (testers welcome to confirm), it also removes the dependency on binary
> math and endian flip grokking – and even reduces codesize. ;)

Tested on powerpc and confirmed to DTRT.  Cheers.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745866: FileFd::Size failure on all big-endian architectures

[Adam Conrad]

And, in case the explicit cast made you feel icky, this is a different
patch that also gets the job done, by keeping the 64-bit type, but
performing the byte swap correctly:

==
--- apt-1.0.2ubuntu1/apt-pkg/contrib/fileutl.cc 2014-04-25 05:49:56.0 
-0600
+++ apt-1.0.2ubuntu3/apt-pkg/contrib/fileutl.cc 2014-04-25 20:03:33.0 
-0600
@@ -1888,10 +1888,7 @@
}
 
 #ifdef WORDS_BIGENDIAN
-   uint32_t tmp_size = size;
-   uint8_t const * const p = (uint8_t const * const) &tmp_size;
-   tmp_size = (p[3] << 24) | (p[2] << 16) | (p[1] << 8) | p[0];
-   size = tmp_size;
+   size = le64toh(size);
 #endif
 
if (lseek(iFd, oldPos, SEEK_SET) < 0)
==

Use whichever appeals more, either should fix the issue. :)

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745866: FileFd::Size failure on all big-endian architectures (patch attached)

[Adam Conrad]

Package: apt
Version: 1.0.2
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu utopic ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * apt-pkg/contrib/fileutl.cc: When checking gzip filesizes, cast
size to uint32_t before setting it, so we don't end up playing
with the wrong half of a uint64_t on big-endian architectures.

This patch should be fairly self-explanatory for people who grok
binary math and endian flips.  Fixes the FTBFS on big-endian arches.

... Adam

-- System Information:
Debian Release: jessie/sid
  APT prefers utopic-updates
  APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 'utopic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru apt-1.0.2ubuntu1/apt-pkg/contrib/fileutl.cc apt-1.0.2ubuntu2/apt-pkg/contrib/fileutl.cc
--- apt-1.0.2ubuntu1/apt-pkg/contrib/fileutl.cc	2014-04-25 05:49:56.0 -0600
+++ apt-1.0.2ubuntu2/apt-pkg/contrib/fileutl.cc	2014-04-25 19:34:00.0 -0600
@@ -1880,7 +1880,7 @@
 	  FileFdErrno("lseek","Unable to seek to end of gzipped file");
 	  return 0;
}
-   size = 0;
+   uint32_t size = 0;
if (read(iFd, &size, 4) != 4)
{
 	  FileFdErrno("read","Unable to read original size of gzipped file");

Bug#735530: samhain: FTBFS on amd64 and kfreebsd

[Adam Conrad]

Package: samhain
Version: 3.1.0-5
Followup-For: Bug #735530
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Configure with disable-asm on amd64 targets to work around FTBFS.
  * Build-depend on autotools-dev to always update config.{sub,guess}

Obviously, upstream fixing their asm would be better than disabling it,
but this works around the FTBFS nicely.  Tacked on to this diff is also
updating build-deps to add autotools-dev so that builds on new arches
get config.{sub,guess} automatically without you needing to do a fresh
upload to update the diff.

... Adam

-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u samhain-3.1.0/debian/changelog samhain-3.1.0/debian/changelog
diff -u samhain-3.1.0/debian/control samhain-3.1.0/debian/control
--- samhain-3.1.0/debian/control
+++ samhain-3.1.0/debian/control
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Javier Fernández-Sanguino Peña 
-Build-Depends: debhelper (>= 4.1.16), autoconf, procps, libgmp3-dev, e2fslibs-dev, libprelude-dev, libauparse-dev [linux-any]
+Build-Depends: debhelper (>= 4.1.16), autoconf, procps, libgmp3-dev, e2fslibs-dev, libprelude-dev, libauparse-dev [linux-any], autotools-dev
 Standards-Version: 3.5.8
 Homepage: http://la-samhna.de/samhain/index.html
 
diff -u samhain-3.1.0/debian/rules samhain-3.1.0/debian/rules
--- samhain-3.1.0/debian/rules
+++ samhain-3.1.0/debian/rules
@@ -33,6 +33,10 @@
 endif
 endif
 
+ifeq (x86_64,$(DEB_HOST_GNU_CPU))
+DISABLE_ASM = --disable-asm
+endif
+
 build: build-stamp
 build-stamp:
 	dh_testdir
@@ -50,6 +54,7 @@
 		--with-state-dir=/var/state/samhain  \
 		--with-prelude \
 		$(DNMALLOC) \
+		$(DISABLE_ASM) \
 		--enable-network=no  \
 		--with-pid-file=/var/run/samhain/samhain.pid \
 		--with-log-file=/var/log/samhain/samhain.log 

Bug#724922: geda-gaf: FTBFS: dh_auto_test fork bombs (patch)

[Adam Conrad]

Package: geda-gaf
Version: 1:1.8.2-2
Followup-For: Bug #724922
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch


In Ubuntu, the attached patch was applied to achieve the following:

  * Switch to dh_autoreconf to update libtool macros for new ports.
  * Re-enable tests on all arches; autoreconf fixes the fork bomb.

So, I actually did this to add support for ppc64el but, as a happy
accident, I noticed that autoreconfing fixes whatever braindamage
the upstream makefiles had that was causing the fork bomb recursion
madness.  So, here's a twofer, extra arch support and an FTBFS fix.

And, before you ask, yes, you can replace autotools-dev with reconf
in this case, as automake-using projects update config.{sub,guess}
on autoreconf, so you can consider it a superset in those cases.

... Adam

-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru geda-gaf-1.8.2/debian/changelog geda-gaf-1.8.2/debian/changelog
diff -Nru geda-gaf-1.8.2/debian/control geda-gaf-1.8.2/debian/control
--- geda-gaf-1.8.2/debian/control	2013-10-17 17:19:16.0 -0600
+++ geda-gaf-1.8.2/debian/control	2014-03-24 21:36:32.0 -0600
@@ -4,7 +4,7 @@
 Maintainer: Debian Electronics Team 
 Uploaders: Peter Clifton , أحمد المحمودي (Ahmed El-Mahmoudy) , Hamish Moffatt , Bdale Garbee 
 Standards-Version: 3.9.4
-Build-Depends: debhelper (>= 9), libgtk2.0-dev (>= 2.16.0), guile-2.0-dev [!ia64 !hurd-i386], guile-1.8-dev [ia64 hurd-i386], libgd-dev, libxml-parser-perl, ghostscript, transfig, libstroke0-dev, groff, libglib2.0-dev, flex, intltool, autotools-dev
+Build-Depends: debhelper (>= 9), libgtk2.0-dev (>= 2.16.0), guile-2.0-dev [!ia64 !hurd-i386], guile-1.8-dev [ia64 hurd-i386], libgd-dev, libxml-parser-perl, ghostscript, transfig, libstroke0-dev, groff, libglib2.0-dev, flex, intltool, dh-autoreconf
 Homepage: http://geda.seul.org/
 Vcs-Git: git://anonscm.debian.org/pkg-electronics/geda-gaf.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-electronics/geda-gaf.git
diff -Nru geda-gaf-1.8.2/debian/rules geda-gaf-1.8.2/debian/rules
--- geda-gaf-1.8.2/debian/rules	2013-10-17 17:19:16.0 -0600
+++ geda-gaf-1.8.2/debian/rules	2014-03-24 20:47:51.0 -0600
@@ -4,7 +4,7 @@
 TEST_HOME=$(CURDIR)/tmp-home
 
 %:
-	dh $@ --with autotools_dev
+	dh $@ --with autoreconf
 
 override_dh_clean:
 	# gnetlist.orig is an upstream file that should not be removed:
@@ -18,12 +18,8 @@
 	 --disable-rpath LDFLAGS="$(LDFLAGS) -Wl,--as-needed"
 
 override_dh_auto_test:
-ifneq (${DEB_BUILD_ARCH},armel)
-  ifneq (${DEB_BUILD_ARCH},armhf)
 	mkdir -p $(TEST_HOME)
 	HOME=$(TEST_HOME) dh_auto_test
-  endif
-endif
 
 LIBPKG=libgeda42
 DEVPKG=libgeda-dev

Bug#724469: FTBFS on all big-endian architectures

[Adam Conrad]

On Sun, Mar 23, 2014 at 10:33:32AM +0100, intrigeri wrote:
> 
> I'd rather not drop s390x from the list of architectures this package
> is built for, but this RC bug has now been around for 6 months, and at
> some point I'll want to get rid of it.

Not fixing a bug isn't the way to get rid of it.  This isn't s390x
specific, it's incorrect code leading to failure on 64-bit BE arches,
of which there are several, it just happens that s390x is the only
officially-supported one.

I understand that you personally may not have the skills to fix it,
and need input from either a porter or upstream, but that doesn't mean
the bug magically doesn't exist if no one gives you a patch to fix it.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#724469: FTBFS on all big-endian architectures

[Adam Conrad]

On Sat, Mar 22, 2014 at 11:53:23AM +0100, intrigeri wrote:
> 
> AFAICT the latest patch proposed by upstream on February 9 [1] has
> been tested on mips only. My understanding is that upstream has been
> waiting for more test results since then. Can anyone please test this
> on other big-endian architectures?
> 
> It would good if we could at least fix this for the 32-bit ones.
> 
> [1] 
> https://rt.cpan.org/Ticket/Attachment/1324475/702426/0001-Fix-return-value-handling-on-big-endian-architecture.patch

Works fine for me on powerpc, but fails miserably on s390x:

t/00-basic-types.t  ok 
t/arg-checks.t  ok   
t/arrays.t  1/29 
#   Failed test at t/arrays.t line 14.
#  got: '0'
# expected: '6'
Out of memory!
# Looks like you planned 29 tests but ran 2.
# Looks like you failed 1 test of 2 run.
# Looks like your test exited with 1 just after 2.
t/arrays.t  Failed 28/29 subtests 
t/boxed.t . ok 
t/cairo-integration.t . ok   
t/callbacks.t . 1/25 
#   Failed test at t/callbacks.t line 14.
#  got: '6941192'
# expected: '23'

#   Failed test at t/callbacks.t line 16.
#  got: '894'
# expected: '23'

#   Failed test at t/callbacks.t line 17.
#  got: '894'
# expected: '23'

#   Failed test at t/callbacks.t line 18.
#  got: '-1071533088'
# expected: '46'

#   Failed test at t/callbacks.t line 22.
#  got: '0'
# expected: '23'

#   Failed test at t/callbacks.t line 26.
#  got: '-1071861040'
# expected: '23'
# Looks like you failed 6 tests of 25.
t/callbacks.t . Dubious, test returned 6 (wstat 1536, 0x600)
Failed 6/25 subtests 
t/closures.t .. ok   
t/constants.t . ok   
t/enums.t . Failed 3/4 subtests 
t/hashes.t  ok   
t/interface-implementation.t .. ok   
t/objects.t ... ok 
t/structs.t ... ok   
t/values.t  ok   
t/vfunc-chaining.t  ok 
t/vfunc-ref-counting.t  ok 

Test Summary Report
---
t/arrays.t  (Wstat: 9 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero wait status: 9
  Parse errors: Bad plan.  You planned 29 tests but ran 2.
t/callbacks.t   (Wstat: 1536 Tests: 25 Failed: 6)
  Failed tests:  3, 6, 9, 14, 19, 25
  Non-zero exit status: 6
t/enums.t   (Wstat: 11 Tests: 1 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 4 tests but ran 1.
Files=16, Tests=297, 222 wallclock secs ( 0.07 usr  0.03 sys + 11.27 cusr 39.60 
csys = 50.97 CPU)
Result: FAIL
Failed 3/16 test programs. 7/297 subtests failed.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#741200: libmysqlclient package version does NOT match the SONAME

[Adam Conrad]

Source: mysql-5.6
Version: 5.6.15-1~exp1
Severity: serious

With the upload of mysql-5.6, you bumped the client lib package name
from 18 to 18.1 and stopped shipping the .so.18 symlink, however this
is completely wrong.

The library SONAME is libmysqlclient.so.18, as it was in 5.5, the fact
that the version bumped from 5.5 to 5.6 is irrelevant.

This should still be libmysqlclient18, and should still ship the link.

Any attempt at making this co-installable with the mysql-5.5 version
of the library will ultimately fail, as they're the same SONAME, and
ldconfig will only generate a link to one, and ld.so will only be
able to resolve one.  Please undo the package rename madness.  Thanks.

... Adam



-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-16-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#739913: Bug#737906: transition: eglibc

[Adam Conrad]

reassign 739913 eglibc
kthxbye

On Sun, Feb 23, 2014 at 09:03:41PM +, Adam D. Barratt wrote:
> 
> One problem is libnih's FTBFS on i386 - #739913.

This looks like another incarnation of a binutils bug being tickled by
a glibc bug, that was discussed on launchpad[1] and upstream[2].  I'm
testing a simple patch to work around the issue now.

... Adam

[1] https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1266492
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=16159


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#737807: FTBFS on all big-endian architectures; patch attached

[Adam Conrad]

Package: libcmis
Version: 0.4.1-3
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/fix-endian-bool.diff: Fix int/bool confusion that
leads to the test suite failing on all big-endian architectures.

This should be fairly self-explanatory.  In that actual code, isOutOfMemory
is defined and used as a bool, but in the testsuite it's declared as an int.

On big-endian arches, int and bool aren't even remotely interchangeable, so
fixing the declaration in the testsuite (as this patch does) fixes the FTBFS.

This should be forwarded upstream too, obviously.

... Adam

-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-6-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru libcmis-0.4.1/debian/changelog libcmis-0.4.1/debian/changelog
diff -Nru libcmis-0.4.1/debian/control libcmis-0.4.1/debian/control
--- libcmis-0.4.1/debian/control	2014-02-05 08:53:57.0 -0700
+++ libcmis-0.4.1/debian/control	2014-02-05 19:18:48.0 -0700
@@ -1,7 +1,6 @@
 Source: libcmis
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Rene Engelhard 
+Maintainer: Rene Engelhard 
 Build-Depends: debhelper (>= 8.0.0), autotools-dev, libxml2-dev, libboost-dev, libboost-program-options-dev, libcurl4-gnutls-dev, libcppunit-dev, docbook-to-man, libboost-date-time-dev, dpkg-dev (>= 1.16.1), dh-autoreconf
 Standards-Version: 3.9.2
 Section: libs
diff -Nru libcmis-0.4.1/debian/patches/fix-endian-bool.diff libcmis-0.4.1/debian/patches/fix-endian-bool.diff
--- libcmis-0.4.1/debian/patches/fix-endian-bool.diff	1969-12-31 17:00:00.0 -0700
+++ libcmis-0.4.1/debian/patches/fix-endian-bool.diff	2014-02-05 18:47:05.0 -0700
@@ -0,0 +1,14 @@
+Description: Fix int/bool confusion on big-endian architectures.
+Author: Adam Conrad 
+
+--- libcmis-0.4.1.orig/qa/libcmis-c/test-document.cxx
 libcmis-0.4.1/qa/libcmis-c/test-document.cxx
+@@ -43,7 +43,7 @@
+ 
+ using namespace std;
+ 
+-extern int isOutOfMemory;
++extern bool isOutOfMemory;
+ 
+ namespace
+ {
diff -Nru libcmis-0.4.1/debian/patches/series libcmis-0.4.1/debian/patches/series
--- libcmis-0.4.1/debian/patches/series	2014-02-05 08:51:24.0 -0700
+++ libcmis-0.4.1/debian/patches/series	2014-02-05 19:15:06.0 -0700
@@ -1,3 +1,3 @@
 fix-run-tests-sh.diff
 fix-docbook-to-man-call.diff
-
+fix-endian-bool.diff

Bug#736097: libc6:amd64: libc6 2.17-97 rm'ing ld.so.cache at inopportune moment, can not upgrade

[Adam Conrad]

On Sun, Jan 19, 2014 at 06:55:49PM +0100, Robert Waldner wrote:
> 
> The problem is that as soon as ld.so.cache is gone, dpkg-deb stops working
> because it can't find libz.so.1 anymore. At the moment I don't have any
> idea on how to upgrade from stable (2.13-38) to testing (2.17-97). Any hints
> *greatly* appreciated.

Your analysis doesn't make much sense to me.  If libz.so.1 is on the
default search path (and it is, unless you've moved it), you don't
need ld.so.cache to exist to resolve it.  For things on the search
path, the cache only speeds up the lookup, it doesn't facilitate it.

If this weren't true, literally *nothing* would run, because most of
the world depends on finding libc.so.6 on path.

So, I'd recommend sorting out where your libz.so.1 has gone to, and
that should get you going again.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#719382: node-stringprep: FTBFS: /bin/sh: 1: node-waf: not found

[Adam Conrad]

Package: node-stringprep
Version: 0.1.5-1
Followup-For: Bug #719382
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Switch from node-waf to node-gyp to fix FTBFS (Closes: #719382)

I'm not a particularly node-friendly person, and have no ideal how
to test this, but this naive patch seems to end up building and
installing the right files, at any rate.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (500, 'saucy-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-0-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru node-stringprep-0.1.5/debian/changelog node-stringprep-0.1.5/debian/changelog
diff -Nru node-stringprep-0.1.5/debian/control node-stringprep-0.1.5/debian/control
--- node-stringprep-0.1.5/debian/control	2013-03-05 16:56:44.0 -0700
+++ node-stringprep-0.1.5/debian/control	2013-12-29 04:55:42.0 -0700
@@ -7,6 +7,7 @@
  debhelper,
  dh-buildinfo,
  nodejs-dev (>= 0.2.6),
+ node-gyp,
  libicu-dev
 Standards-Version: 3.9.4
 Homepage: https://github.com/astro/node-stringprep
diff -Nru node-stringprep-0.1.5/debian/rules node-stringprep-0.1.5/debian/rules
--- node-stringprep-0.1.5/debian/rules	2013-03-05 16:54:22.0 -0700
+++ node-stringprep-0.1.5/debian/rules	2013-12-29 04:51:12.0 -0700
@@ -22,7 +22,7 @@
 
 libpkgname = node-node-stringprep
 
-CDBS_BUILD_DEPENDS += , nodejs-dev (>= 0.2.6), libicu-dev
+CDBS_BUILD_DEPENDS += , nodejs-dev (>= 0.2.6), node-gyp, libicu-dev
 
 # suppress optional build-dependencies
 CDBS_BUILD_DEPENDS_rules_upstream-tarball =
@@ -35,13 +35,14 @@
 DEB_INSTALL_DOCS_$(libpkgname) += README.markdown
 
 configure/$(libpkgname)::
-	NODE_PATH=$(cdbs_curdestdir)/usr/lib/nodejs node-waf configure
+	NODE_PATH=$(cdbs_curdestdir)/usr/lib/nodejs node-gyp configure
 
 build/$(libpkgname)::
-	NODE_PATH=$(cdbs_curdestdir)/usr/lib/nodejs node-waf build
+	NODE_PATH=$(cdbs_curdestdir)/usr/lib/nodejs node-gyp build
 
 install/$(libpkgname)::
-	NODE_PATH=$(cdbs_curdestdir)/usr/lib/nodejs node-waf install
+	install -m 644 -D build/Release/node-stringprep.node \
+	  $(cdbs_curdestdir)/usr/lib/nodejs/node-stringprep.node
 
 # Node modules have an uncommon extension preventing autodetection by
 # dh_shlibdeps, so we do it manually

Bug#733118: Followup to #733118

[Adam Conrad]

Obviously, ignore the Maintainer/Orig-Maintainer change in debian/control,
that shouldn't have leaked into the debdiff.  Sorry for the noise.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#733118: inkscape: FTBFS with latest freetype, patch attached

[Adam Conrad]

Package: inkscape
Version: 0.48.4-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * 05-freetype-include.patch: Use freetype upstream's recommended include.

Freetype's include structure has moved around a bit and, according to
bug #731015, the only supported and stable API for freetype includes is
the one I've employed in this patch.  This should be suitable to send
upstream as well.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (500, 'saucy-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-0-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u inkscape-0.48.4/debian/changelog inkscape-0.48.4/debian/changelog
diff -u inkscape-0.48.4/debian/control inkscape-0.48.4/debian/control
--- inkscape-0.48.4/debian/control
+++ inkscape-0.48.4/debian/control
@@ -4,8 +4,7 @@
 Vcs-git: git://git.debian.org/git/collab-maint/inkscape.git
 Vcs-Browser: http://git.debian.org/?p=git/collab-maint/inkscape.git
 Homepage: http://www.inkscape.org/
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Wolfram Quester 
+Maintainer: Wolfram Quester 
 Uploaders: Matteo F. Vescovi 
 Build-Depends: autoconf,
automake,
diff -u inkscape-0.48.4/debian/patches/series inkscape-0.48.4/debian/patches/series
--- inkscape-0.48.4/debian/patches/series
+++ inkscape-0.48.4/debian/patches/series
@@ -5,0 +6 @@
+05-freetype-include.patch
only in patch2:
unchanged:
--- inkscape-0.48.4.orig/debian/patches/05-freetype-include.patch
+++ inkscape-0.48.4/debian/patches/05-freetype-include.patch
@@ -0,0 +1,15 @@
+Description: Use freetype upstream's recommended include.
+Author: Adam Conrad 
+
+--- inkscape-0.48.4~/src/libnrtype/FontFactory.h	2011-07-08 12:25:09.0 -0600
 inkscape-0.48.4/src/libnrtype/FontFactory.h	2013-12-25 15:20:26.134011106 -0700
+@@ -31,7 +31,8 @@
+ #include 
+ #else
+ #include 
+-#include 
++#include 
++#include FT_FREETYPE_H
+ #endif
+ 
+ namespace Glib

Bug#730899: razorqt: FTBFS: cp: cannot stat 'debian/tmp//usr/bin/razor-lightdm-greeter': No such file or directory

[Adam Conrad]

Package: razorqt
Version: 0.5.2-2
Followup-For: Bug #730899
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Add patch to look for lightdm-qt-3 in addition to versions 2 and 1.

This patch should be fairly self-explanatory.

... Adam


-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (500, 'saucy-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-13-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru razorqt-0.5.2/debian/changelog razorqt-0.5.2/debian/changelog
diff -Nru razorqt-0.5.2/debian/patches/lightdm3.patch razorqt-0.5.2/debian/patches/lightdm3.patch
--- razorqt-0.5.2/debian/patches/lightdm3.patch	1969-12-31 17:00:00.0 -0700
+++ razorqt-0.5.2/debian/patches/lightdm3.patch	2013-05-24 01:24:57.0 -0600
@@ -0,0 +1,26 @@
+Description: look for lightdm-qt-3 in addition to versions 2 and 1.
+Author: Adam Conrad 
+Forwarded: no
+Last-Update: 2013-05-24
+
+--- razorqt-0.5.2.orig/razorqt-lightdm-greeter/CMakeLists.txt
 razorqt-0.5.2/razorqt-lightdm-greeter/CMakeLists.txt
+@@ -24,11 +24,15 @@ include ( ${QT_USE_FILE} )
+ # check for new version
+ include(FindPkgConfig)
+ message(STATUS "Checking for lightdm-qt...")
+-pkg_check_modules(LIGHTDM_QT liblightdm-qt-2)
++pkg_check_modules(LIGHTDM_QT liblightdm-qt-3)
+ # or lightdm v1 if the version 2 is not found
+ if (NOT LIGHTDM_QT_FOUND)
+-message(STATUS "lightdm2 for Qt is not found. Trying to find v1")
+-pkg_check_modules(LIGHTDM_QT liblightdm-qt-1)
++message(STATUS "lightdm3 for Qt is not found. Trying to find v2")
++pkg_check_modules(LIGHTDM_QT liblightdm-qt-2)
++if (NOT LIGHTDM_QT_FOUND)
++message(STATUS "lightdm2 for Qt is not found. Trying to find v1")
++pkg_check_modules(LIGHTDM_QT liblightdm-qt-1)
++endif()
+ endif()
+ # decision for version. It needs to be separated as the cmake can
+ # be run more times. And the LIGHTDM_QT_FOUND is cached so it's
diff -Nru razorqt-0.5.2/debian/patches/series razorqt-0.5.2/debian/patches/series
--- razorqt-0.5.2/debian/patches/series	2013-03-30 09:25:03.0 -0600
+++ razorqt-0.5.2/debian/patches/series	2013-05-24 01:24:20.0 -0600
@@ -0,0 +1 @@
+lightdm3.patch

Bug#730308: x42-plugins: FTBFS: cc1: error: unrecognized command line option '-msse'

[Adam Conrad]

Package: x42-plugins
Version: 20131119-2
Followup-For: Bug #730308
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/01-remove-sse.patch: Remove SSE flags a bit harder.

The patch should be self-explanatory.  Cheers.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (500, 'saucy-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-13-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru x42-plugins-20131119/debian/changelog x42-plugins-20131119/debian/changelog
diff -Nru x42-plugins-20131119/debian/patches/01-remove-sse.patch x42-plugins-20131119/debian/patches/01-remove-sse.patch
--- x42-plugins-20131119/debian/patches/01-remove-sse.patch	2013-11-24 02:32:53.0 -0700
+++ x42-plugins-20131119/debian/patches/01-remove-sse.patch	2013-11-24 10:36:02.0 -0700
@@ -87,7 +87,7 @@
  #!/usr/bin/make -f
  
 -OPTIMIZATIONS ?= -msse -msse2 -mfpmath=sse -ffast-math -fomit-frame-pointer -O3 -fno-finite-math-only
-+OPTIMIZATIONS ?= -mfpmath=sse -ffast-math -fomit-frame-pointer -O3 -fno-finite-math-only
++OPTIMIZATIONS ?= -ffast-math -fomit-frame-pointer -O3 -fno-finite-math-only
  PREFIX ?= /usr/local
  CFLAGS ?= -g -Wall -Wno-unused-function
  LIBDIR ?= lib

Bug#728822: Acknowledgement (FTBFS on big-endian architectures, patches attached)

[Adam Conrad]

I completely forgot to fill in the dangling footnote in my original
bug report, but the commit that inspired my endian-detect patch that
should be replaced wholesale is:

https://code.google.com/p/orthanc/source/detail?r=900274ed996fb38d386b90f67267c0f422deeacc

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728822: FTBFS on big-endian architectures, patches attached

[Adam Conrad]

Package: orthanc
Version: 0.6.1-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * detect-endian.patch: Patch to correctly detect endianness of the
current host architecture, inspired by upstream's incomplete fix.
  * fix-endian-png.patch: Patch from upstream to fix PngWriter and
the associated tests on above detected big-endian architectures.

The second patch in the series is a straight backport from upstream
of their PngWriter and testsuite fix, and should be self-evident as
such.

The first patch was heavily inspired by upstream's fix[1] for endian
detection, except that it does it correctly for all arches, instead
of bizarrely assuming that only __powerpc__ is big-endian.  Please
forward this one to them as a more complete fix.

If upstream is concerned that  might not exist on Win32 (I
have no way of checking this, so don't know), the extra include could
be dropped, as  includes  on Linux anyway.  I just
prefer to be explicit in my includes when using features, as implicit
includes tend to bite you when linux or glibc upstream decide to move
things around. :)

... Adam Conrad

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12.0-1-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru orthanc-0.6.1/debian/changelog orthanc-0.6.1/debian/changelog
diff -Nru orthanc-0.6.1/debian/patches/detect-endian.patch orthanc-0.6.1/debian/patches/detect-endian.patch
--- orthanc-0.6.1/debian/patches/detect-endian.patch	1969-12-31 17:00:00.0 -0700
+++ orthanc-0.6.1/debian/patches/detect-endian.patch	2013-11-05 14:47:35.0 -0700
@@ -0,0 +1,29 @@
+Description: Detect correct endianness of the host machine
+Author: Adam Conrad 
+Forwarded: no
+
+--- orthanc-0.6.1.orig/UnitTests/main.cpp
 orthanc-0.6.1/UnitTests/main.cpp
+@@ -3,6 +3,7 @@
+ #include "gtest/gtest.h"
+ 
+ #include 
++#include 
+ 
+ #include "../Core/Compression/ZlibCompressor.h"
+ #include "../Core/DicomFormat/DicomTag.h"
+@@ -479,6 +480,14 @@ TEST(Toolbox, WriteFile)
+   ASSERT_THROW(Toolbox::ReadFile(u, path.c_str()), OrthancException);
+ }
+ 
++TEST(Toolbox, Endianness)
++{
++#if __BYTE_ORDER == __BIG_ENDIAN
++  ASSERT_EQ(Endianness_Big, Toolbox::DetectEndianness());
++#else // __LITTLE_ENDIAN
++  ASSERT_EQ(Endianness_Little, Toolbox::DetectEndianness());
++#endif
++}
+ 
+ int main(int argc, char **argv)
+ {
diff -Nru orthanc-0.6.1/debian/patches/fix-endian-png.patch orthanc-0.6.1/debian/patches/fix-endian-png.patch
--- orthanc-0.6.1/debian/patches/fix-endian-png.patch	1969-12-31 17:00:00.0 -0700
+++ orthanc-0.6.1/debian/patches/fix-endian-png.patch	2013-11-05 14:46:54.0 -0700
@@ -0,0 +1,75 @@
+Description: Fix PngWriter and associated test on big-endian arches
+Author: Adam Conrad 
+Origin: https://code.google.com/p/orthanc/source/detail?r=51892be15618cc934f099bf90c1180215d5778eb
+
+--- orthanc-0.6.1.orig/UnitTests/Png.cpp
 orthanc-0.6.1/UnitTests/Png.cpp
+@@ -3,6 +3,7 @@
+ #include 
+ #include "../Core/FileFormats/PngReader.h"
+ #include "../Core/FileFormats/PngWriter.h"
++#include "../Core/Toolbox.h"
+ 
+ TEST(PngWriter, ColorPattern)
+ {
+@@ -24,6 +25,11 @@ TEST(PngWriter, ColorPattern)
+   }
+ 
+   w.WriteToFile("ColorPattern.png", width, height, pitch, Orthanc::PixelFormat_RGB24, &image[0]);
++
++  std::string f, md5;
++  Orthanc::Toolbox::ReadFile(f, "ColorPattern.png");
++  Orthanc::Toolbox::ComputeMD5(md5, f);
++  ASSERT_EQ("604e785f53c99cae6ea4584870b2c41d", md5);
+ }
+ 
+ TEST(PngWriter, Gray8Pattern)
+@@ -44,6 +50,11 @@ TEST(PngWriter, Gray8Pattern)
+   }
+ 
+   w.WriteToFile("Gray8Pattern.png", width, height, pitch, Orthanc::PixelFormat_Grayscale8, &image[0]);
++
++  std::string f, md5;
++  Orthanc::Toolbox::ReadFile(f, "Gray8Pattern.png");
++  Orthanc::Toolbox::ComputeMD5(md5, f);
++  ASSERT_EQ("5a9b98bea3d0a6d983980cc38bfbcdb3", md5);
+ }
+ 
+ TEST(PngWriter, Gray16Pattern)
+@@ -66,6 +77,11 @@ TEST(PngWriter, Gray16Pattern)
+   }
+ 
+   w.WriteToFile("Gray16Pattern.png", width, height, pitch, Orthanc::PixelFormat_Grayscale16, &image[0]);
++
++  std::string f, md5;
++  Orthanc::Toolbox::ReadFile(f, "Gray16Pattern.png");
++  Orthanc::Toolbox::ComputeMD5(md5, f);
++  ASSERT_EQ("0785866a08bf0a02d2eeff87f658571c", md5);
+ }
+ 
+ TEST(PngWriter, EndToEnd)
+--- orthanc-0.6.1.orig/Core/FileFormats/PngWriter.cpp
 orthanc-0.6.1/Core/FileFormats/PngWriter.cpp
+@@ -174,15 +174,18 @@ namespace Orthan

Bug#728756: FTBFS on powerpc/ppc64, patch attached

[Adam Conrad]

Package: makedumpfile
Version: 1.5.4-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * 0003-powerpc-vmap_area_list.patch: Apply patch from RedHat to add
vmap_area_list definitions on powerpc and ppc64 to fix the FTBFS.

The patch itself should be fairly self-explanatory when compared to
the failed build logs.  Cheers.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12.0-1-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru makedumpfile-1.5.4/debian/changelog makedumpfile-1.5.4/debian/changelog
diff -Nru makedumpfile-1.5.4/debian/control makedumpfile-1.5.4/debian/control
--- makedumpfile-1.5.4/debian/control	2013-11-04 14:05:35.0 -0700
+++ makedumpfile-1.5.4/debian/control	2013-11-04 22:25:16.0 -0700
@@ -1,8 +1,7 @@
 Source: makedumpfile
 Section: devel
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: John Wright 
+Maintainer: John Wright 
 Uploaders: Louis Bouchard 
 Standards-Version: 3.8.2
 Build-Depends: debhelper (>= 7.0.50), libelf-dev, libz-dev, libdw-dev (>= 0.141-2ubuntu1), libbz2-dev
diff -Nru makedumpfile-1.5.4/debian/patches/0003-powerpc-vmap_area_list.patch makedumpfile-1.5.4/debian/patches/0003-powerpc-vmap_area_list.patch
--- makedumpfile-1.5.4/debian/patches/0003-powerpc-vmap_area_list.patch	1969-12-31 17:00:00.0 -0700
+++ makedumpfile-1.5.4/debian/patches/0003-powerpc-vmap_area_list.patch	2013-11-04 22:20:42.0 -0700
@@ -0,0 +1,43 @@
+From 150b58eb299066c65ef7713a93effc35c00be03a Mon Sep 17 00:00:00 2001
+Message-Id: <150b58eb299066c65ef7713a93effc35c00be03a.1374133991.git.bhe at redhat.com>
+From: Baoquan He 
+Date: Mon, 15 Jul 2013 20:37:14 +0800
+Subject: [PATCH] [PATCH] Add vmap_area_list definition for ppc/ppc64.
+
+vmap_area_list is added to get vmalloc_start for ppc/ppc64, but its
+definition is missing, now add them.
+
+Signed-off-by: Baoquan He 
+---
+ makedumpfile-1.5.4/arch/ppc.c   |2 +-
+ makedumpfile-1.5.4/arch/ppc64.c |2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/makedumpfile-1.5.4/arch/ppc.c b/makedumpfile-1.5.4/arch/ppc.c
+index a9b4812..a3e1a12 100644
+--- makedumpfile-1.5.4/arch/ppc.c
 makedumpfile-1.5.4/arch/ppc.c
+@@ -28,7 +28,7 @@
+ int
+ get_machdep_info_ppc(void)
+ {
+-	unsigned long vmlist, vmalloc_start;
++	unsigned long vmlist, vmap_area_list, vmalloc_start;
+ 
+ 	info->section_size_bits = _SECTION_SIZE_BITS;
+ 	info->max_physmem_bits  = _MAX_PHYSMEM_BITS;
+diff --git a/makedumpfile-1.5.4/arch/ppc64.c b/makedumpfile-1.5.4/arch/ppc64.c
+index c229ede..85144f6 100644
+--- makedumpfile-1.5.4/arch/ppc64.c
 makedumpfile-1.5.4/arch/ppc64.c
+@@ -49,7 +49,7 @@ set_ppc64_max_physmem_bits(void)
+ int
+ get_machdep_info_ppc64(void)
+ {
+-	unsigned long vmlist, vmalloc_start;
++	unsigned long vmlist, vmap_area_list, vmalloc_start;
+ 
+ 	info->section_size_bits = _SECTION_SIZE_BITS;
+ 	if (!set_ppc64_max_physmem_bits()) {
+-- 
+1.7.1
diff -Nru makedumpfile-1.5.4/debian/patches/series makedumpfile-1.5.4/debian/patches/series
--- makedumpfile-1.5.4/debian/patches/series	2013-07-30 03:23:52.0 -0600
+++ makedumpfile-1.5.4/debian/patches/series	2013-11-04 22:20:57.0 -0700
@@ -1,2 +1,3 @@
 0001-Remove-libebl-linkage.patch
 0002-Use-install-instead-of-cp-in-Makefile.patch
+0003-powerpc-vmap_area_list.patch

Bug#728650: [Debian-med-packaging] Bug#728650: FTBFS on PowerPC, patch attached.

[Adam Conrad]

On Mon, Nov 04, 2013 at 08:36:52AM +0900, Charles Plessy wrote:
> 
> Hmmer is a software for scientific computing.  Using it with AltiVec/VMX
> disabled on a recent PowerPC platform makes no sense from an economical
> point of view.

Sure, though previous versions had vmx disabled as well, that somehow just
didn't work out so well in the most recent upload without my patch.

> Also, if building with AltiVec/VMX is broken, it may be the symptom of a 
> bigger
> probem.  How do we know if it the program works at all even if it builds with
> AltiVec/VMX disabled ?  We have no test suite and no sign of users of the 
> hmmer
> Debian packages on PowerPC. 

I would be all for someone fixing the actual bug with building with AltiVec
enabled, though AltiVec isn't a baseline for Debian/powerpc, it could be
reasonably argued that certain packages can just warn in their description
that it's going to explode without it.  Runtime detection would be even
better, but hmmer doesn't seem to have any such fanciness currently.

> I would recommend to simply stop distributing it on PowerPC, and invest 
> further
> work only if we have a user asking for it.

Well, if you make that argument, you may as well stop building it on almost
all arches, as most use the generic C implementation.  I think there's value
in building on all arches, even if you think your target audience might not
care, in that porting to multiple arches keeps the code a bit more clean and
sane and generally portable, plus if someone comes along on ARM, installs it,
says "man, this is kinda crap", they may well be inclined to do a VFP or NEON
port and contribute it.  That's a lot less likely if you just shun arches
that don't have an optimised backend available.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728650: FTBFS on PowerPC, patch attached.

[Adam Conrad]

Package: hmmer
Version: 3.1b1-2
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Stop selecting vmx DP implementation on powerpc to resolve FTBFS.

I'm not sure how this ever worked before, since this debian/rules bit
reverses the logic of the patch in debian-changes-3.0-2.1, however it
builds fine here if I drop the bit from rules and revert to the dummy
implementation, as was used in previous uploads.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12.0-1-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru hmmer-3.1b1/debian/changelog hmmer-3.1b1/debian/changelog
diff -Nru hmmer-3.1b1/debian/rules hmmer-3.1b1/debian/rules
--- hmmer-3.1b1/debian/rules	2013-10-24 00:37:39.0 -0600
+++ hmmer-3.1b1/debian/rules	2013-11-03 11:50:15.0 -0700
@@ -11,11 +11,7 @@
 ifeq (amd64,$(ARCH))
 DEB_CONFIGURE_EXTRA_FLAGS := --enable-threads --enable-sse
  else
-ifeq (powerpc,$(ARCH))
-DEB_CONFIGURE_EXTRA_FLAGS := --enable-threads --enable-vmx
- else
 DEB_CONFIGURE_EXTRA_FLAGS := --enable-threads
- endif
 endif
 
 override_dh_auto_configure:

Bug#723156: NMU for libfolia FTBFS

[Adam Conrad]

I'm uploading an NMU for this bug with the following simple patch:


diff -Nru libfolia-0.10/debian/changelog libfolia-0.10/debian/changelog
--- libfolia-0.10/debian/changelog  2013-08-04 18:13:45.0 -0600
+++ libfolia-0.10/debian/changelog  2013-10-04 15:38:00.0 -0600
@@ -1,3 +1,9 @@
+libfolia (0.10-4.2) unstable; urgency=low
+
+  * Non-maintainer upload: Build-dep on libticcutils2-dev (closes: #723156)
+
+ -- Adam Conrad   Fri, 04 Oct 2013 15:36:59 -0600
+
 libfolia (0.10-4.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru libfolia-0.10/debian/control libfolia-0.10/debian/control
--- libfolia-0.10/debian/control2013-08-04 18:13:08.0 -0600
+++ libfolia-0.10/debian/control2013-10-04 15:36:55.0 -0600
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Debian Science Team 

 Uploaders: Joost van Baal-Ilić , Ko van der Sloot 

-Build-Depends: cdbs, debhelper (>= 7), pkg-config, libicu-dev, libxml2-dev, 
libticcutils-dev
+Build-Depends: cdbs, debhelper (>= 7), pkg-config, libicu-dev, libxml2-dev, 
libticcutils2-dev
 Standards-Version: 3.9.3
 Homepage: http://ilk.uvt.nl/
 Vcs-Svn: svn://svn.debian.org/svn/debian-science/packages/libfolia/trunk


... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#713366: [Pkg-openmpi-maintainers] Bug#713366: openmpi1.6: FTBFS: install: cannot change owner and permissions of 'debian/openmpi1.6-bin/DEBIAN': Operation not permitted

[Adam Conrad]

On Tue, Oct 01, 2013 at 09:49:56AM +0200, Sylvestre Ledru wrote:
> 
> However, openmpi1.6 is no longer maintained in Debian. We uploaded the
> 1.6 over the openmpi package (which already has most of the fixes).

Ahh, I hadn't noticed the transition ongoing.  Indeed, the soname/link
fixes are in there, however you might want to replace the inelegant
LD_LIBRARY_PATH fix of yours with my slightly saner dh_shlibdeps -lfoo
fix instead.  Yours overrides LD_LIBRARY_PATH in a way that means no
other wrappers get to play (which is why fakeroot broke until you put
it back on the path), so people with curious and weird custom build
setups will still run into issues there.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#713366: openmpi1.6: FTBFS: install: cannot change owner and permissions of 'debian/openmpi1.6-bin/DEBIAN': Operation not permitted

[Adam Conrad]

Package: openmpi1.6
Version: 1.6.4-2
Followup-For: Bug #713366
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Fix transposition of 1.3 to 3.1 that led to dangling symlinks and an
incorrect .so for libmpi_f90.so.1 in libopenmpi1.6 (Closes: #715097)
  * Call dh_shlibdeps with -lfoo to not break fakeroot (Closes: #713366)

Both parts of this patch should be fairly self-explanatory, I hope, and
it closes two of the three open bugs against openmpi1.6.  Cheers.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-8-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru openmpi1.6-1.6.4/debian/changelog openmpi1.6-1.6.4/debian/changelog
diff -Nru openmpi1.6-1.6.4/debian/libopenmpi1.6-dev.links openmpi1.6-1.6.4/debian/libopenmpi1.6-dev.links
--- openmpi1.6-1.6.4/debian/libopenmpi1.6-dev.links	2012-11-07 08:09:54.0 -0700
+++ openmpi1.6-1.6.4/debian/libopenmpi1.6-dev.links	2013-09-30 16:39:34.0 -0600
@@ -10,7 +10,7 @@
 usr/lib/libmca_common_sm.so.3	usr/lib/libmca_common_sm.so
 usr/lib/libmpi_cxx.so.1		usr/lib/libmpi_cxx.so
 usr/lib/libmpi_f77.so.1		usr/lib/libmpi_f77.so
-usr/lib/libmpi_f90.so.3		usr/lib/libmpi_f90.so
+usr/lib/libmpi_f90.so.1		usr/lib/libmpi_f90.so
 usr/lib/libompitrace.so.0	usr/lib/libompitrace.so
 usr/lib/libopen-pal.so.4	usr/lib/libopen-pal.so
 usr/lib/libopen-rte.so.4	usr/lib/libopen-rte.so
diff -Nru openmpi1.6-1.6.4/debian/libopenmpi1.6.links openmpi1.6-1.6.4/debian/libopenmpi1.6.links
--- openmpi1.6-1.6.4/debian/libopenmpi1.6.links	2013-04-11 08:23:00.0 -0600
+++ openmpi1.6-1.6.4/debian/libopenmpi1.6.links	2013-09-30 16:39:16.0 -0600
@@ -2,7 +2,7 @@
 usr/lib/openmpi/lib/libmca_common_sm.so.3.0.0   usr/lib/libmca_common_sm.so.3.0.0
 usr/lib/openmpi/lib/libmpi_cxx.so.1.0.1 usr/lib/libmpi_cxx.so.1.0.1
 usr/lib/openmpi/lib/libmpi_f77.so.1.0.6 usr/lib/libmpi_f77.so.1.0.6
-usr/lib/openmpi/lib/libmpi_f90.so.3.1.0 usr/lib/libmpi_f90.so.3.1.0
+usr/lib/openmpi/lib/libmpi_f90.so.1.3.0 usr/lib/libmpi_f90.so.1.3.0
 usr/lib/openmpi/lib/libmpi.so.1.0.7 usr/lib/libmpi.so.1.0.7
 usr/lib/openmpi/lib/libompitrace.so.0.0.0	usr/lib/libompitrace.so.0.0.0
 usr/lib/openmpi/lib/libopen-pal.so.4.0.4usr/lib/libopen-pal.so.4.0.4
@@ -11,7 +11,7 @@
 usr/lib/libmca_common_sm.so.3.0.0   usr/lib/libmca_common_sm.so.3
 usr/lib/libmpi_cxx.so.1.0.1 usr/lib/libmpi_cxx.so.1
 usr/lib/libmpi_f77.so.1.0.6 usr/lib/libmpi_f77.so.1
-usr/lib/libmpi_f90.so.3.1.0 usr/lib/libmpi_f90.so.3
+usr/lib/libmpi_f90.so.1.3.0 usr/lib/libmpi_f90.so.1
 usr/lib/libmpi.so.1.0.7 usr/lib/libmpi.so.1
 usr/lib/libompitrace.so.0.0.0			usr/lib/libompitrace.so.0
 usr/lib/libopen-pal.so.4.0.4usr/lib/libopen-pal.so.4
diff -Nru openmpi1.6-1.6.4/debian/rules openmpi1.6-1.6.4/debian/rules
--- openmpi1.6-1.6.4/debian/rules	2012-11-30 10:30:24.0 -0700
+++ openmpi1.6-1.6.4/debian/rules	2013-09-30 16:27:50.0 -0600
@@ -92,7 +92,7 @@
 	dh_installdocs --all AUTHORS NEWS README
 
 override_dh_shlibdeps:
-	LD_LIBRARY_PATH="$(CURDIR)/debian/tmp/usr/lib/openmpi/lib" dh_shlibdeps  -- --ignore-missing-info
+	dh_shlibdeps -l$(CURDIR)/debian/tmp/usr/lib/openmpi/lib -- --ignore-missing-info
 
 override_dh_strip:
 	dh_strip --dbg-package=libopenmpi1.6-dbg

Bug#719455: Needs updating for the latest vim in unstable

[Adam Conrad]

Package: vimhelp-de
Version: 7.3.101122-2
Severity: serious

vim in unstable has been updated to version 7.4, leaving vimhelp-de
uninstallable (and causing vimhelp-de to block migration of vim).  It
would be nice if vimhelp-de could be updated (or removed, if it's no
longer updated upstream and no one wants to adopt it), so vim can
move along to testing.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10.0-6-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#714535: netexpect: FTBFS with wireshark 1.10 (patch)

[Adam Conrad]

Package: netexpect
Version: 0.20-3
Followup-For: Bug #714535
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch

In Ubuntu, I've applied the following naive patch to port to the
wireshark 1.10 API.  It looks like the _set_unset calls can probably
just go away, as they're setting members that no longer exist.

As for the frame_data_{reset,destroy} mangling, I made a best-effort
guess as to which to use in which situation, but input from someone
more familiar with the source would probably not be a bad plan.

  * fix-libwireshark110-build.patch: Track wireshark 1.10 API (closes: #714535)

Thanks for considering the patch.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10.0-2-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru netexpect-0.20/debian/changelog netexpect-0.20/debian/changelog
diff -Nru netexpect-0.20/debian/patches/fix-libwireshark110-build.patch netexpect-0.20/debian/patches/fix-libwireshark110-build.patch
--- netexpect-0.20/debian/patches/fix-libwireshark110-build.patch	1969-12-31 17:00:00.0 -0700
+++ netexpect-0.20/debian/patches/fix-libwireshark110-build.patch	2013-07-05 13:08:32.0 -0600
@@ -0,0 +1,110 @@
+Description: Track API changes in wireshark 1.10
+Author: Adam Conrad 
+Bug-Debian: http://bugs.debian.org/714535
+Last-Update: 2013-07-05
+
+--- netexpect-0.20.orig/src/expect_network.c
 netexpect-0.20/src/expect_network.c
+@@ -167,7 +167,7 @@ process_packet(u_char *user, const struc
+ hd->passed_rfilter = pkt_dissect_tcl(hd->interp, bytes, &fdata, rfcode,
+ 	 ns_name, 1);
+ 
+-frame_data_cleanup(&fdata);
++frame_data_destroy(&fdata);
+ 
+ /*
+  * We rely on the current time in some operations (when reading packets
+--- netexpect-0.20.orig/src/tcl_packet.c
 netexpect-0.20/src/tcl_packet.c
+@@ -134,8 +134,6 @@ fill_in_framedata(frame_data *fdata, con
+ frame_data_init(fdata, 0 /* num */, &phdr, 0 /* offset */, 0 /* cum_bytes */);
+ 
+ nstime_set_unset(&fdata->rel_ts);
+-nstime_set_unset(&fdata->del_cap_ts);
+-nstime_set_unset(&fdata->del_dis_ts);
+ }
+ 
+ static
+@@ -381,7 +379,7 @@ update_string(Tcl_Obj *packet_obj)
+ packet_obj->length = len;
+ 
+ epan_dissect_free(edt);
+-frame_data_cleanup(&fdata);
++frame_data_destroy(&fdata);
+ }
+ 
+ static void
+@@ -505,7 +503,7 @@ tcl_packet_dissect(Tcl_Interp *interp, i
+ 
+ pkt_dissect_tcl(interp, packet->bytes.data, &fdata, NULL, ns_name, 1);
+ 
+-frame_data_cleanup(&fdata);
++frame_data_destroy(&fdata);
+ 
+ return TCL_OK;
+ }
+@@ -786,7 +784,7 @@ tcl_packet_show(Tcl_Interp *interp, int
+ 
+ pkt_dissect_show(packet->bytes.data, &fdata, verbose);
+ 
+-frame_data_cleanup(&fdata);
++frame_data_destroy(&fdata);
+ 
+ return TCL_OK;
+ }
+--- netexpect-0.20.orig/src/send_expect.c
 netexpect-0.20/src/send_expect.c
+@@ -273,8 +273,6 @@ fill_in_framedata(frame_data *fdata, con
+ frame_data_init(fdata, 0 /* num */, &phdr, 0 /* offset */, 0 /* cum_bytes */);
+ 
+ nstime_set_unset(&fdata->rel_ts);
+-nstime_set_unset(&fdata->del_cap_ts);
+-nstime_set_unset(&fdata->del_dis_ts);
+ }
+ 
+ /*
+@@ -317,7 +315,7 @@ build_and_hash(Tcl_Interp *interp, struc
+ 
+ 	packets[n].hash = pkt_hash(interp, packets[n].packet.data, &fdata);
+ 
+-	frame_data_cleanup(&fdata);
++	frame_data_destroy(&fdata);
+ 
+ #ifdef DEBUG
+ 	printf("sent pkt len = %u, packet data:\n", packets[n].packet.len);
+@@ -704,7 +702,7 @@ bypass_select:
+ 
+ 		hash = pkt_hash(interp, pkt_data, &rcvd_fdata);
+ 
+-		frame_data_cleanup(&rcvd_fdata);
++		frame_data_reset(&rcvd_fdata);
+ 
+ #ifdef DEBUG
+ 		printf("recv'ed pkt len = %u, packet data:\n", pkthdr.len);
+@@ -795,7 +793,7 @@ bypass_select:
+ 	sent_packets[j].packet.data,
+ 	&sent_fdata);
+ 		
+-		frame_data_cleanup(&sent_fdata);
++		frame_data_reset(&sent_fdata);
+ 
+ 		if (!isanswer)
+ 			/*
+@@ -1226,7 +1224,7 @@ NExp_SendExpectObjCmd(ClientData clientD
+ 
+ 		hash = pkt_hash(interp, pkt_data, &rcvd_fdata);
+ 
+-		frame_data_cleanup(&rcvd_fdata);
++		frame_data_reset(&rcvd_fdata);
+ 
+ #ifdef DEBUG
+ 		printf("recv'ed pkt len = %u, packet data:\n", pkthdr.len);
+@@ -1317,7 +1315,7 @@ NExp_SendExpectObjCmd(ClientData clientD
+ 	sent_packets[j].packet.data,
+ 	&sent_fdata);
+ 
+-		frame_data_cleanup(&sent_fdata);
++		frame_data_reset(&sent_fdata);
+ 
+ 		if (!isanswer)
+ 			/*
diff -Nru netexpect-0.20/debian/patches/series netexpect-0.20/debian/patches/series
--- netexpect-0.20/debian/patches/series	2012-06-13 16:25:29.0 -0600
+++ netexpect-0.20/debian/patches/series	2013-07-05 13:05:53.0 -0600
@@ -0,0 +1 @@
+fix-libwireshark110-build.patch

Bug#704718: pugixml: FTBFS on 32-bit architectures: symbols differ from expectations

[Adam Conrad]

Package: pugixml
Version: 1.2-1
Followup-For: Bug #704718
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Use regex patterns in symbols file to fix FTBFS on 32-bit arches.

This is much simpler than having symbols files for each arch (which
is overkill), or build-depending on pkgkde-tools for its symbol
mangling magic.  The intent of the patch should be self-explanatory.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9.0-3-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru pugixml-1.2/debian/changelog pugixml-1.2/debian/changelog
diff -Nru pugixml-1.2/debian/libpugixml1.symbols pugixml-1.2/debian/libpugixml1.symbols
--- pugixml-1.2/debian/libpugixml1.symbols	2013-01-12 10:55:32.0 -0700
+++ pugixml-1.2/debian/libpugixml1.symbols	2013-06-02 20:09:48.0 -0600
@@ -12,10 +12,10 @@
  _ZN4pugi11xpath_queryC2EPKcPNS_18xpath_variable_setE@Base 1.2
  _ZN4pugi11xpath_queryD1Ev@Base 1.2
  _ZN4pugi11xpath_queryD2Ev@Base 1.2
- _ZN4pugi12xml_document11load_bufferEPKvmjNS_12xml_encodingE@Base 1.2
- _ZN4pugi12xml_document16load_buffer_implEPvmjNS_12xml_encodingEbb@Base 1.2
- _ZN4pugi12xml_document19load_buffer_inplaceEPvmjNS_12xml_encodingE@Base 1.2
- _ZN4pugi12xml_document23load_buffer_inplace_ownEPvmjNS_12xml_encodingE@Base 1.2
+ (regex)"^_ZN4pugi12xml_document11load_bufferEPKv(m|j)jNS_12xml_encodingE@Base" 1.2
+ (regex)"^_ZN4pugi12xml_document16load_buffer_implEPv(m|j)jNS_12xml_encodingEbb@Base" 1.2
+ (regex)"^_ZN4pugi12xml_document19load_buffer_inplaceEPv(m|j)jNS_12xml_encodingE@Base" 1.2
+ (regex)"^_ZN4pugi12xml_document23load_buffer_inplace_ownEPv(m|j)jNS_12xml_encodingE@Base" 1.2
  _ZN4pugi12xml_document4loadEPKcj@Base 1.2
  _ZN4pugi12xml_document4loadERSijNS_12xml_encodingE@Base 1.2
  _ZN4pugi12xml_document4loadERSt13basic_istreamIwSt11char_traitsIwEEj@Base 1.2
@@ -68,7 +68,7 @@
  _ZN4pugi15xml_tree_walkerD0Ev@Base 1.2
  _ZN4pugi15xml_tree_walkerD1Ev@Base 1.2
  _ZN4pugi15xml_tree_walkerD2Ev@Base 1.2
- _ZN4pugi15xml_writer_file5writeEPKvm@Base 1.2
+ (regex)"^_ZN4pugi15xml_writer_file5writeEPKv(m|j)@Base" 1.2
  _ZN4pugi15xml_writer_fileC1EPv@Base 1.2
  _ZN4pugi15xml_writer_fileC2EPv@Base 1.2
  _ZN4pugi15xml_writer_fileD0Ev@Base 1.2
@@ -91,7 +91,7 @@
  _ZN4pugi17xml_node_iteratormmEv@Base 1.2
  _ZN4pugi17xml_node_iteratorppEi@Base 1.2
  _ZN4pugi17xml_node_iteratorppEv@Base 1.2
- _ZN4pugi17xml_writer_stream5writeEPKvm@Base 1.2
+ (regex)"^_ZN4pugi17xml_writer_stream5writeEPKv(m|j)@Base" 1.2
  _ZN4pugi17xml_writer_streamC1ERSo@Base 1.2
  _ZN4pugi17xml_writer_streamC1ERSt13basic_ostreamIwSt11char_traitsIwEE@Base 1.2
  _ZN4pugi17xml_writer_streamC2ERSo@Base 1.2
@@ -128,7 +128,7 @@
  _ZN4pugi23xml_named_node_iteratorppEi@Base 1.2
  _ZN4pugi23xml_named_node_iteratorppEv@Base 1.2
  _ZN4pugi30get_memory_allocation_functionEv@Base 1.2
- _ZN4pugi31set_memory_management_functionsEPFPvmEPFvS0_E@Base 1.2
+ (regex)"^_ZN4pugi31set_memory_management_functionsEPFPv(m|j)EPFvS0_E@Base" 1.2
  _ZN4pugi32get_memory_deallocation_functionEv@Base 1.2
  _ZN4pugi7as_utf8EPKw@Base 1.2
  _ZN4pugi7as_utf8ERKSbIwSt11char_traitsIwESaIwEE@Base 1.2
@@ -189,7 +189,7 @@
  _ZNK4pugi10xpath_nodentEv@Base 1.2
  _ZNK4pugi11xpath_query11return_typeEv@Base 1.2
  _ZNK4pugi11xpath_query15evaluate_numberERKNS_10xpath_nodeE@Base 1.2
- _ZNK4pugi11xpath_query15evaluate_stringEPcmRKNS_10xpath_nodeE@Base 1.2
+ (regex)"^_ZNK4pugi11xpath_query15evaluate_stringEPc(m|j)RKNS_10xpath_nodeE@Base" 1.2
  _ZNK4pugi11xpath_query15evaluate_stringERKNS_10xpath_nodeE@Base 1.2
  _ZNK4pugi11xpath_query16evaluate_booleanERKNS_10xpath_nodeE@Base 1.2
  _ZNK4pugi11xpath_query17evaluate_node_setERKNS_10xpath_nodeE@Base 1.2
@@ -229,7 +229,7 @@
  _ZNK4pugi14xpath_node_set5beginEv@Base 1.2
  _ZNK4pugi14xpath_node_set5emptyEv@Base 1.2
  _ZNK4pugi14xpath_node_set5firstEv@Base 1.2
- _ZNK4pugi14xpath_node_setixEm@Base 1.2
+ (regex)"^_ZNK4pugi14xpath_node_setixE(m|j)@Base" 1.2
  _ZNK4pugi14xpath_variable10get_numberEv@Base 1.2
  _ZNK4pugi14xpath_variable10get_stringEv@Base 1.2
  _ZNK4pugi14xpath_variable11get_booleanEv@Base 1.2

Bug#708342: glibc_2.14 and glibc_2.15 not found

[Adam Conrad]

On Wed, May 15, 2013 at 10:37:19AM +0200, Dávid Grochal wrote:
> Package: glibc-doc
> Severity: critical
> 
> glibc_2.14 and glibc_2.15 not found

I'm not sure, precisely, what this is a bug report about.  Could you
elaborate on what the problem is that you're seeing?

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#707185: Adding found version

[Adam Conrad]

found 707185 2.13-38
kthxbye

Not disputing the severity of this bug, and I'll look into it soon, but
it shouldn't block migration to testing, as it's not a new bug in the
packaging, based on other reports in earlier versions.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704206: teem: FTBFS[any-i386]: testsuite failures

[Adam Conrad]

Based on testsuite output on buildd.debian.org, it looks like you might
want the same fix for ia64 as I applied to PPC/s390.  Again, if the
fp-contract flag isn't supported, it might need to be -mno-fused-madd,
I'm not sure if that mapping was changed for all arches, or only PPC.

... Adam


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704206: teem: FTBFS[any-i386]: testsuite failures

[Adam Conrad]

Package: teem
Version: 1.11.0~svn5906-1
Followup-For: Bug #704206
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu raring ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Fix FTBFS on powerpc and s390 with -ffp-contract=off
  * Fix testsuite failure on any-i386 with -ffloat-store

These two different compiler flags end up fixing some FP rounding errors
unique to i386 and IBM platforms, respectively.  This is tested in Ubuntu
on i386 and powerpc and Works For Me.

It's possible that s390 doesn't support -ffp-contract=off, in which case
it would need -mno-fused-madd instead (which would have the same effect),
but I didn't have a chance to test this on an s390 machine.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru teem-1.11.0~svn5906/debian/changelog teem-1.11.0~svn5906/debian/changelog
diff -Nru teem-1.11.0~svn5906/debian/rules teem-1.11.0~svn5906/debian/rules
--- teem-1.11.0~svn5906/debian/rules	2013-01-09 09:08:48.0 -0700
+++ teem-1.11.0~svn5906/debian/rules	2013-04-21 09:55:03.0 -0600
@@ -13,6 +13,13 @@
 
 DEB_BUILD_PARALLEL := true
 
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386))
+  CFLAGS += -ffloat-store
+endif
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), powerpc ppc64 s390 s390x))
+  CFLAGS += -ffp-contract=off
+endif
+
 DEB_CMAKE_EXTRA_FLAGS = \
 -DCMAKE_INSTALL_PREFIX:PATH=/usr \
 -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo \

Bug#699132: Fix issues with non-arch-indep builds (like on the buildds)

[Adam Conrad]

Package: texmacs
Version: 1:1.0.7.16-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu raring ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * Make debian/fixsh operate on debian/texmacs instead of debian/tmp,
and move it to binary-post-install/texmacs:: to keep consistency
when not building arch-indep packages, as on the Dbeian buildds.
  * Remove maxima_filter in clean to fix FTBFS on on non-i386 arches.

So, there are three distinct bugs here, only two of which I address
with this patch:

1) When building without arch-indep (dpkg-buildpackage -B, instead of
   dpkg-buildpackage -b), debian/fixsh doesn't trigger.  The top
   changelog entry addresses that and fixes cross-arch consistency.

2) You're trying to ship an i386 binary on all arches, which causes
   an FTBFS (quite rightly so), the clean addition fixes that, BUT:

3) The i386 binary in question is a binary compiled from sources
   that no longer ship (the maxima_filter sources and Makefile were
   removed upstream, but they left the binary cruft in their tarball,
   it looks like).  Either you should repack your source as a dfsg
   orig tarball (as shipping a binary without source doesn't meet the
   DFSG), or you should talk your upstream into dropping the stray
   binary and re-releasing a 1.0.7.16.0 or something, so you can
   package that instead.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8.0-0-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u texmacs-1.0.7.16/debian/rules texmacs-1.0.7.16/debian/rules
--- texmacs-1.0.7.16/debian/rules
+++ texmacs-1.0.7.16/debian/rules
@@ -24,6 +24,7 @@
 	rm -rf TeXmacs/misc/pixmacs/.xvpics
 	rm -f config.log misc/admin/admin.makefile
 	rm -f packages/macos/Base.xcconfig
+	rm -f plugins/maxima/bin/maxima_filter
 
 binary-post-install/texmacs-common::
 	mv debian/texmacs-common/usr/share/texmacs/TeXmacs/misc/pixmaps debian/texmacs-common/usr/share/pixmaps/texmacs
@@ -49,3 +50,5 @@
+binary-post-install/texmacs::
+	sh ./debian/fixsh
+
 binary-predeb/texmacs-common::
 	chmod a+x debian/texmacs-common/usr/share/texmacs/TeXmacs/langs/encoding/*.awk
-	sh ./debian/fixsh
diff -u texmacs-1.0.7.16/debian/changelog texmacs-1.0.7.16/debian/changelog
diff -u texmacs-1.0.7.16/debian/fixsh texmacs-1.0.7.16/debian/fixsh
--- texmacs-1.0.7.16/debian/fixsh
+++ texmacs-1.0.7.16/debian/fixsh
@@ -2,7 +2,7 @@
 set -x
 
 # BIN are lists of ELF binaries and Perl/Python scripts so should be omitted.
-PLGIN=debian/tmp/usr/lib/texmacs/TeXmacs/bin
+PLGIN=debian/texmacs/usr/lib/texmacs/TeXmacs/bin
 BIN="maxima_filter realpath tm_axiom tm_graphviz tm_maple_5 tm_r tm_shell bbox_add.pl perl-tm_asy realpath.py tm_asy2 tm_mupad tm_python tm_sage"
 
 cd $PLGIN

Bug#698104: Patch to fix FTBFS on non-long-double ARM and MIPS

[Adam Conrad]

scription: Fix issues with non-long-double builds
+  * long_double_logic.patch: Fix ifdef logic around LONG_DOUBLE in
+goffice/math/go-cspline.c to fix FTBFS on ARM and MIPS arches.
+  * long_double_logic.patch: Also remove LONG_DOUBLE-only symbols
+from docs/reference/goffice-0.10.types and wrap their header
+declarations with __GTK_DOC_IGNORE__ magic to fix doc builds.
+Author: Adam Conrad 
+Forwarded: no
+
+Index: goffice-0.10.0/goffice/math/go-cspline.c
+===
+--- goffice-0.10.0.orig/goffice/math/go-cspline.c	2013-01-13 20:33:59.798064149 -0700
 goffice-0.10.0/goffice/math/go-cspline.c	2013-01-13 20:33:59.790064148 -0700
+@@ -228,7 +228,7 @@
+ }
+ 
+ GType
+-#ifdef LONG_DOUBLE
++#ifndef LONG_DOUBLE
+ go_cspline_get_type (void)
+ #else
+ go_csplinel_get_type (void)
+@@ -238,7 +238,7 @@
+ 
+ 	if (t == 0) {
+ 		t = g_boxed_type_register_static (
+-#ifdef LONG_DOUBLE
++#ifndef LONG_DOUBLE
+ 		 "GOCSpline",
+ #else
+ 		 "GOCSplinel",
+Index: goffice-0.10.0/docs/reference/goffice-0.10.types
+===
+--- goffice-0.10.0.orig/docs/reference/goffice-0.10.types	2013-01-13 20:33:59.798064149 -0700
 goffice-0.10.0/docs/reference/goffice-0.10.types	2013-01-13 20:33:59.794064148 -0700
+@@ -17,7 +17,6 @@
+ go_component_mime_dialog_get_type
+ go_conf_node_get_type
+ go_cspline_get_type
+-go_csplinel_get_type
+ go_data_get_type
+ go_data_matrix_get_type
+ go_data_matrix_val_get_type
+@@ -73,7 +72,6 @@
+ go_plugin_service_resource_get_type
+ go_plugin_service_simple_get_type
+ go_regression_stat_get_type
+-go_regression_statl_get_type
+ go_resource_type_get_type
+ go_rotation_sel_get_type
+ go_search_replace_get_type
+Index: goffice-0.10.0/goffice/math/go-cspline.h
+===
+--- goffice-0.10.0.orig/goffice/math/go-cspline.h	2012-08-21 20:02:40.0 -0600
 goffice-0.10.0/goffice/math/go-cspline.h	2013-01-13 20:35:06.166065200 -0700
+@@ -62,7 +62,9 @@
+ 	unsigned ref_count;
+ };
+ 
++#ifndef __GTK_DOC_IGNORE__
+ GType go_csplinel_get_type (void);
++#endif
+ GOCSplinel *go_cspline_initl (long double const *x, long double const *y, int n,
+  unsigned limits, long double a0, long double a1);
+ void go_cspline_destroyl (GOCSplinel *sp);
+Index: goffice-0.10.0/goffice/math/go-regression.h
+===
+--- goffice-0.10.0.orig/goffice/math/go-regression.h	2012-08-21 20:02:40.0 -0600
 goffice-0.10.0/goffice/math/go-regression.h	2013-01-13 20:36:22.238066405 -0700
+@@ -134,7 +134,9 @@
+ } go_regression_stat_tl;
+ #define GORegressionStatl go_regression_stat_tl
+ 
++#ifndef __GTK_DOC_IGNORE__
+ GTypego_regression_statl_get_type  (void);
++#endif
+ go_regression_stat_tl *go_regression_stat_newl	(void);
+ void 		go_regression_stat_destroyl	(go_regression_stat_tl *stat_);
+ 
diff -Nru goffice-0.10.0/debian/patches/series goffice-0.10.0/debian/patches/series
--- goffice-0.10.0/debian/patches/series	2012-12-19 05:10:40.0 -0700
+++ goffice-0.10.0/debian/patches/series	2013-01-13 16:28:03.0 -0700
@@ -0,0 +1 @@
+long_double_logic.patch

Bug#695814: FTBFS: need to switch libnode-uglify build-dep to node-uglify

[Adam Conrad]

Package: node-async
Version: 0.1.22-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu raring ubuntu-patch

This patch should be self-evident.  libnode-uglify was dropped from
unstable and, as such, node-async would now FTBFS if it was rebuilt
in a traditional buildd setup (where alternate build-depends are
ignored).

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.7.0-5-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru node-async-0.1.22/debian/changelog node-async-0.1.22/debian/changelog
diff -Nru node-async-0.1.22/debian/control node-async-0.1.22/debian/control
--- node-async-0.1.22/debian/control	2012-06-01 01:21:20.0 -0600
+++ node-async-0.1.22/debian/control	2012-12-12 16:46:13.0 -0700
@@ -6,7 +6,7 @@
 Build-Depends: cdbs,
  debhelper,
  dh-buildinfo,
- libnode-uglify | yui-compressor
+ node-uglify | yui-compressor
 Standards-Version: 3.9.3
 Homepage: https://github.com/caolan/async
 Vcs-Git: git://git.debian.org/git/collab-maint/node-async

Bug#694684: cityhash: Fix for FTBFS on PowerPC, ARM, and S/390

[Adam Conrad]

Package: cityhash
Version: 1.1.0-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu raring ubuntu-patch


In Ubuntu, I've worked around the FTBFS on arches with unsigned chars
with the following patch.  The correct solution would be to hunt down
everywhere in the source that incorrectly assumes char=uint, but this
works as a quick fix to make the testsuite pass again.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.7.0-4-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru cityhash-1.1.0/debian/changelog cityhash-1.1.0/debian/changelog
diff -Nru cityhash-1.1.0/debian/rules cityhash-1.1.0/debian/rules
--- cityhash-1.1.0/debian/rules	2012-11-19 06:06:16.0 -0700
+++ cityhash-1.1.0/debian/rules	2012-11-28 17:57:09.0 -0700
@@ -2,6 +2,9 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+# The source assumes signed chars, apply quick hack:
+export DEB_CXXFLAGS_MAINT_APPEND = -fsigned-char
+
 %:
 	dh $@ --with autotools-dev
 

Bug#693419: libltc: FTBFS on PowerPC due to misnamed member name in LTCFrame struct

[Adam Conrad]

Package: libltc
Version: 1.0.3-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu raring ubuntu-patch


The attached patch should be fairly self-evident, I hope.  This
fixes the FTBFS on PowerPC (and fixes a bug in general on all
big-endian arches, though some may be failing for other reasons
as well).

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 
'raring'), (500, 'quantal-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.5.0-18-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru libltc-1.0.3/debian/patches/big_endian_ftbfs.patch libltc-1.0.3/debian/patches/big_endian_ftbfs.patch
--- libltc-1.0.3/debian/patches/big_endian_ftbfs.patch	1969-12-31 17:00:00.0 -0700
+++ libltc-1.0.3/debian/patches/big_endian_ftbfs.patch	2012-11-16 02:06:16.0 -0700
@@ -0,0 +1,15 @@
+Description: Fix member name in big-endian version of LTCFrame
+Author: Adam Conrad 
+Forwarded: no
+
+--- libltc-1.0.3.orig/src/ltc.h
 libltc-1.0.3/src/ltc.h
+@@ -127,7 +127,7 @@ struct LTCFrame {
+ 	unsigned int frame_units:4;
+ 
+ 	unsigned int user2:4;
+-	unsigned int col_frm:1;
++	unsigned int col_frame:1;
+ 	unsigned int dfbit:1;
+ 	unsigned int frame_tens:2;
+ 
diff -Nru libltc-1.0.3/debian/patches/series libltc-1.0.3/debian/patches/series
--- libltc-1.0.3/debian/patches/series	1969-12-31 17:00:00.0 -0700
+++ libltc-1.0.3/debian/patches/series	2012-11-16 02:05:24.0 -0700
@@ -0,0 +1 @@
+big_endian_ftbfs.patch

Bug#685066: cain: FTBFS with the new dpkg-buildpackage on arch-only builds

[Adam Conrad]

Package: cain
Version: 1.9-5
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch


cain fails to build on arch-only builds (ie: dpkg-buildpackage -B) with
the new dpkg-buildpackage, leading to all buildd builds failing.  I've
uploaded the attached patch to Ubuntu, with the following changelog
entry, and I'd suggest the same fix for Debian:

  * debian/rules: postfix override_dh_install with -indep as it was
doing indep-specific mangling and failing on arch-only builds.


Thanks for considering the patch.

... Adam

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

Kernel: Linux 3.2.0-27-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru cain-1.9/debian/rules cain-1.9/debian/rules
--- cain-1.9/debian/rules	2012-08-10 06:09:14.0 -0600
+++ cain-1.9/debian/rules	2012-08-16 03:20:11.0 -0600
@@ -12,7 +12,7 @@
 %:
 	dh $@ --with python2
 
-override_dh_install:
+override_dh_install-indep:
 	dh_install
 	rm -rf debian/$(pkg)/usr/share/cain/help/* debian/$(pkg)/usr/share/cain/gui/help.htm*
 	cd help && zip ../debian/$(pkg)/usr/share/cain/help/cain.htb * -r -q -x *.htb *.htd

Bug#684528: elfutils: FTBFS with new dpkg-buildpackage due to build-arch split

[Adam Conrad]

Package: elfutils
Version: 0.153-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch


Due to a slight thinko (I assume), your build-arch/build-indep split
leads elfutils to FTBFS with the new dpkg-buildpackage, which calls
build-arch for arch-only builds.  I uploaded the attached patch to
Ubuntu, with the following changelog entry to resolve this:

  * Fix build-arch and build-indep targets to not require root.


I think this follows the spirit of what you were trying to achieve,
while making sure that the install target is only a dependency of
targets that require root (ie: the binary* targets).

... Adam


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

Kernel: Linux 3.2.0-27-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru elfutils-0.153/debian/rules elfutils-0.153/debian/rules
--- elfutils-0.153/debian/rules	2012-02-24 16:01:45.0 -0700
+++ elfutils-0.153/debian/rules	2012-08-10 13:16:08.0 -0600
@@ -87,12 +87,13 @@
 	rm debian/tmp/usr/include/elfutils/libebl.h
 
 # Build architecture-independent files here.
-build-indep: build install
-binary-indep: build-indep
+build-indep: build
+binary-indep: build-indep install
 # We have nothing to do.
 
 # Build architecture-dependent files here.
-build-arch: build install
+build-arch: build
+binary-arch: build-arch install
 	dh_testdir
 	dh_testroot
 	dh_installchangelogs ChangeLog
@@ -113,7 +114,6 @@
 	dh_md5sums
 	dh_builddeb
 
-binary-arch: build-arch
 binary: binary-indep binary-arch
 
 maint-unpatch:

Bug#682602: libnet-dns-perl_0.68-1 FTBFS: missing build-dep on netbase

[Adam Conrad]

Package: libnet-dns-perl
Version: 0.68-1
Severity: serious
Tags: patch

Okay, so I'm not going to bother including an actually diff/patch
for a 9-character addition to debian/control, but consider this a
verbal patch. :P

On several buildds (and it should have been on all of them), the
testsuite for libnet-dns-perl fails because (if you strace it), it's
trying to open /etc/protocols, which is shipped by netbase, which
isn't build-essential.

I can only guess at why it worked on some buildds, guesses ranging
from dirty chroots, to people using the (un)helpful sbuild/schroot
hooks that copy the base system's /etc/{services,protocols} into
the chroot before the build.

At any rate, build-dep on netbase, and that will clear your failures
in t/13-udp-trunc.t right up.

... Adam


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

Kernel: Linux 3.2.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libnet-dns-perl depends on:
ii  libc6   2.15-0ubuntu10
ii  libdigest-hmac-perl 1.03+dfsg-1
ii  libnet-ip-perl  1.25-3
ii  perl [libmime-base64-perl]  5.14.2-6ubuntu2
ii  perl-base [perlapi-5.14.2]  5.14.2-6ubuntu2

libnet-dns-perl recommends no packages.

Versions of packages libnet-dns-perl suggests:
pn  libio-socket-inet6-perl  

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#679180: FTBFS on arm*: SHLIB_LIBADD: No such file or directory

[Adam Conrad]

So, a few things about this bug.  It's almost certainly not a glibc
bug, but rather a bug in the bundled library that gets (ab)used to
handle POSIX extended regexes in non-UTF-8 locales.  The substing
failure doesn't show when either using PCRE and a C locale, or using
any combination of flags in a UTF-8 locale.

Another point worth noting is that it seems completely daft to use
a substring match to detect that you're on an architecture where
substring matching is broken.  My original patch that just forced
PCRE on all arches is sane enough, in that PCRE works well
everywhere and has a sane test suite to make sure that it the case.

That said, the reason I hadn't forwarded my patch to Debian yet was
because it's a hideous workaround and, obviously, the root cause
needs to be hunted down, as this only helps r-base's install routine,
but does nothing for applications that actually call into regex
routines in a C locale.

Anyhow, I think that having arch-specific testing and twiddling there
probably just makes things even less obvious and harder to track and
debug later, but that's just my opinion.  Your call, I suppose.

... Adam

PS: (FWIW, the original patch was mine, not Luca's, it seems to have
gotten mis/re-attributed along the way...)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#679180: FTBFS on arm*: SHLIB_LIBADD: No such file or directory

[Adam Conrad]

On Mon, Jul 16, 2012 at 08:27:50PM +, Adam Conrad wrote:
> PS: (FWIW, the original patch was mine, not Luca's, it seems to have
> gotten mis/re-attributed along the way...)

Disregard this bit, BTW.  Luca told me on IRC that we arrived at our
shockingly similar workarounds independently.

Anyhow.  More from said IRC discussion, while I was brain-dumping
at Luca:

< infinity> DktrKranz: If you feel like debugging further, I *suspect* 
the error either lies in the bundled tre (in src/extra/tre), 
or in the code in R itself that's calling it.
< infinity> DktrKranz: 20 to 1 odds say it's an alignment issue or 
something.
< infinity> DktrKranz: And, for added fun, the bundled tre is a forked 
version from upstream tre.  So, it could just be that it was 
subtly broken in the fork.
< infinity> DktrKranz: It still *could* be eglibc's fault, as we're also 
calling into eglibc to mangle wchars and such, but if wchar 
was fundamentally broken in eglibc on ARM, I think I'd have 
seen a lot more fallout.
< infinity> DktrKranz: So, it's probably either R mis-mangling types or 
doing dodgy pointer math, or tre doing similar.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#638068: initramfs-tools generates unbootable initrd.img on IA-64

[Adam Conrad]

I've committed a fix for #638068 to git.

It doesn't address the fact that klibc/sh appears to not be
"good enough" to boot ia64 (which is an entirely different
and, I assume, klibc bug), but it should improve the handling
enough to make it at least do as requested for both BUSYBOX=y
and BUSYBOX=n (which should fix ia64, as long as you use =y)

Can someone test out git head and let me know if this works
for you.  It looks "obviously correct" to me, but I can't
readily test it to make sure it DTRT.

... Adam



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#673304: libextractor: sponsorship for libpoppler transition

[Adam Conrad]

Hi there,

I've grabbed your current git master and tested it locally,
and would happily sponsor the upload to the archive.  Let
me know via email, or catch me on IRC (infinity) and tell
me if that's cool.

If I don't hear from you soon(ish), I'll probably just
sponsor your current git head anyway, to get this RC bug
cleared out. ;)

... Adam



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#663022: unicap: FTBFS: unicapgtk_device_property.c:199: undefined reference

[Adam Conrad]

At a quick glance at build logs here, the problem is that the package
is relinking in binary-arch, after the sed has happened.  This only
seems to be an issue when doing an arch-only build, arch+indep works
out just fine, as no relinking happens after the scrubbing.  Curious.

... Adam



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#670597: libc6: /lib/ld-linux.so.3 symlink not set

[Adam Conrad]

On Sun, Apr 29, 2012 at 04:13:17PM +0100, Steve McIntyre wrote:
> On Sun, Apr 29, 2012 at 04:57:03PM +0200, Philipp Kern wrote:
> >
> >However it would be nice if you could avoid breaking all our official
> >buildds in the process next time.  I.e. a notice *before* breaking the
> >ports' users would've been helpful, especially as that change wasn't
> >particularly time critical *for Debian*.
> 
> For now I've put in an extra /lib/ld-linux.so.3 symlink on the buildds
> so they can start working again immediately. Next, I'm scanning all
> the machines to verify exactly which packages need
> fixing/rebuilding/reinstalling. Shouldn't take too long.

To be fair, I had no way of knowing that the Debian buildds were running
binaries from debian-ports (or, more accurately, binaries built against
debian-ports by DSA).  The revelation was somewhat of a shock to me, as
I've had very little (ie: nothing) to do with the Debian armhf buildds.

Apologies for the breakage, but it seems like Steve has things well in
hand by now.

... Adam



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#669172: libc6: preinst fails in -28 and since then also in -27

[Adam Conrad]

The reason this fails in -27 as well as -28 is because it has
nothing to do with -28, it just got triggered for people by a
new eglibc upload, period.

The real bug here is that dpkg has decided that referring to
multi-arch:same packages without the :arch suffix is bad, wrong
and evil, and eglibc sprinkles "dpkg -L LIBC" and such all
over its maintainer scripts without adding an :arch qualifier.

I'll look at this tonight when I get off work and commit some
fixes, unless someone beats me to it.

... Adam



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#464118: rm -r broken: Function not implemented

[Adam Conrad]

On Fri, Feb 15, 2008 at 07:16:12PM -0500, Michael Stone wrote:
> Could you send an strace from one of the non-working systems? That might 
> be enough to figure out what's going wrong and whether it can be worked 
> around.

Attached.

... Adam

execve("/bin/rm", ["rm", "-rf", "foo/"], [/* 12 vars */]) = 0
brk(0)  = 0x8054000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7fd5000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)  = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=7012, ...}) = 0
mmap2(NULL, 7012, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fd3000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY)= 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260e\1"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1274092, ...}) = 0
mmap2(NULL, 1279600, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb7e9a000
mmap2(0xb7fcd000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x133) = 0xb7fcd000
mmap2(0xb7fd, 9840, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7fd
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7e99000
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e996b0, limit:1048575, 
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, 
useable:1}) = 0
mprotect(0xb7fcd000, 4096, PROT_READ)   = 0
munmap(0xb7fd3000, 7012)= 0
brk(0)  = 0x8054000
brk(0x8075000)  = 0x8075000
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
lstat64("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fstatat64(AT_FDCWD, "foo/", 0xbfdee29c, AT_SYMLINK_NOFOLLOW) = -1 ENOSYS 
(Function not implemented)
lstat64("foo/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
unlink("foo/")  = -1 EISDIR (Is a directory)
open("foo/", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fcntl64(3, F_GETFL) = 0x28800 (flags 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW)
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
getdents64(3, /* 3 entries */, 4096)= 72
open("/proc/self/fd/3/bar", 
O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW) = -1 ENOENT (No such file 
or directory)
fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/proc/self/fd", 0xbfdedff0) = -1 ENOENT (No such file or directory)
rmdir("/proc/self/fd/3/bar")= -1 ENOENT (No such file or directory)
fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/proc/self/fd", 0xbfdee050) = -1 ENOENT (No such file or directory)
write(2, "rm: ", 4rm: ) = 4
write(2, "cannot remove `foo/bar\'", 23cannot remove `foo/bar') = 23
write(2, ": Function not implemented", 26: Function not implemented) = 26
write(2, "\n", 1
)   = 1
getdents64(3, /* 0 entries */, 4096)= 0
fcntl64(3, F_GETFD) = 0x1 (flags FD_CLOEXEC)
close(3)= 0
close(0)= 0
close(1)= 0
close(2)= 0
exit_group(1)   = ?
Process 23930 detached

Bug#464118: rm -r broken: Function not implemented

[Adam Conrad]

What we were missing here was kernel build and/or version, it seems.

I vaguely remembered *not* seeing this on our hppa buildds and, on a hunch,
went checking kernel versions.  amd64, i386, powerpc, ia64, and sparc were
all running 2.6.15, lpia was running 2.6.17, and hppa is running the latest
2.6.22-14-hppa32 from gutsy.

On a hunch, I grabbed a buildd tarball and tried to reproduce this on my
laptop (also running 2.6.22-14 from gutsy, but on i386), and couldn't
reproduce it here locally either.

So, this seems to be restricted to either older kernels, or kernels with
a specific config.

... Adam




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#464118: rm -r broken: Function not implemented

[Adam Conrad]

On Fri, Feb 15, 2008 at 06:04:01PM -0500, Michael Stone wrote:
> 
> of course, I still can't reproduce it:
> 
> Am I missing something?

Damn.  I can tell you that I reproduced it on amd64, i386, powerpc, ia64,
and sparc, and that it was a bare hardy --variant=buildd chroot (more or
less) without /proc mounted.

There's nothing proprietary about our buildd chroots, so I could make a
tarball available to you if that would help.

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#464118: rm -r broken: Function not implemented

[Adam Conrad]

For what it's worth, the confusion in this bug log seems due to the
fact that people testing succesfully clearly have /proc mounted.

I spotted the same bug on the Ubuntu buildds today while mucking
around inside chroots without /proc mounted:

https://bugs.edge.launchpad.net/ubuntu/+source/coreutils/+bug/192239

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#393083: Hijacked website

[Adam Conrad]

Stephen Gran wrote:
> 
> Was this a joke?  Did I miss something here?

Yes.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#391387: [php-maint] Bug#391387: Yes, this is pretty bad

[Adam Conrad]

Steve Langasek wrote:
> On Fri, Oct 06, 2006 at 07:22:40PM -0400, Greg Taylor wrote:
>> I definitely wasn't expecting this. A fix would be great, and perhaps 
>> some more caution in the future with testing before pushing such a 
>> debilitating upgrade down to the many users out there :)
> 
> How did you even get your system into this state?  The libapache2-mod-php5
> depends on apache2-mpm-prefork, apache2-mpm-prefork 2.2.3-2 depends on
> apache2.2-common, and apache2.2-common conflicts with libapache2-mod-php5. 
> If you overrode the package relationships to force installation of
> incompatible packages, you get to keep both pieces.

The (<<) conflict is incorrect, since Sean uploaded a new php5 while
apache2 was in the NEW queue, that's how.  apache2's conflicts line will
need to be updated at the same time as php5 is updated for apache2.2.

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#366843: apache: same problem here...

[Adam Conrad]

Cristian Ionescu-Idbohrn wrote:
> Version: 1.3.34-3
> 
> | dpkg: error processing apache (--configure):
> |  subprocess post-installation script returned error exit status 10

This is already fixed in 1.3.34-4.

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#316321: revisiting the "reload target" issue

[Adam Conrad]

Pierre HABOUZIT wrote:
>   Ping apache2-common maintainers ?
>
>   is there any reason why that bug is rotting in a RC state for 4+
> monthes ?
>
>   I may perform an NMU soon.
>   
Yes, because I'm preparing a 2.0.58 upload which includes several
patches to the init scripts, not just this one, so uploading just for
this one bug would be reasonably pointless.

The RC bugs certainly matter for Etch's release (and will be fixed soon,
so in plenty of time), but they don't much matter for sid->etch
migration, since we're already up to date in Etch.

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#360574: FTBFS: patches/series includes deleted patches

[Adam Conrad]

# Didn't notice this had already been reported
severity 360126 serious
tags 360574 pending
merge 360126 360574
kthxbye



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#360574: FTBFS: patches/series includes deleted patches

[Adam Conrad]

Package: glibc
Severity: serious

As of recent changes in quilt (0.44-3), quilt now exits with an error
if patches/series contains patches that don't exist, which seems fair.

The glibc source has at least one such missing patch (perhaps more,
quilt was kind enough to stop for me on the first one it didn't find),
and is therefor now FTBFS on all arches in sid, and soon to be etch,
when quilt migrates in a day or two.

... Adam

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.4
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327139: apache-perl purge ate /etc/apache

[Adam Conrad]

Geoff Crompton wrote:
> 
> There is also /var/lib/dpkg/info/apache-perl.list, with the line
> "/etc/apache". Does dpkg use this file to remove stuff? Or is everything
> to be removed expressed in the apache-perl.*rm scritpts?

dpkg removes everything from .list files, *BUT*, it will never remove a
directory if it's either a) still owned by another package, or b) not empty.

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327139: apache-perl purge ate /etc/apache

[Adam Conrad]

Geoff Crompton wrote:
> 
> Do you have any recommendations on how to safely purge apache-perl? I
> thought it'd be good to have it documented in this bug report, for
> future people that might stumble across this.
> 
>  * manually edit files in /var/lib/dpkg/info to remove references to
> things belonging to apache, then purge

This one's probably your best bet.
/var/lib/dpkg/info/apache-perl.{prerm,postrm} may both be executed on
purge, depending on the current state of the package, and how those
scripts are written.  Dissecting them to remove whatever offending bits
they may have shouldn't be too hard.

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327139: apache-perl purge ate /etc/apache

[Adam Conrad]

Geoff Crompton wrote:
>
> ii  apache 1.3.33-6sarge1 versatile, high-performance HTTP server
> pc  apache-perl1.3.9-13.1-1.2 Versatile, high-performance HTTP

There's nothing I can do to fix the potato (!) version of apache-perl at
this point.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#358321: FTBFS: missing build-dep on cdbs

[Adam Conrad]

Package: ttf-freefont
Version: 20060126b-2
Severity: serious

Since the switch to using cdbs for this package, it no longer
builds from source, since you *cough* forgot the build-dep.

... Adam

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.4
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#346171: libstdc++6 loses changelog/copyright on upgrade

[Adam Conrad]

This comes from you doing your directory->symlink migration in preinst,
rather than postinst (to see an example of it being done correctly, see
openssh-server, or php4-mysql as examples).

If you migrate in preinst, you remove the directory, create the symlink,
THEN dpkg removes your package's files (dutifully following the symlink,
and removing the other package's changelog and copyright)

If you do it in postinst, this snafu doesn't occur, and the world goes
on happily able to read changelogs and licenses...

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#336645: [php-maint] Bug#336645: Bug 336645: PHP 4.4.1 Security Fixes

[Adam Conrad]

Nick Jenkins wrote:
> According to http://lwn.net/Articles/159103/ , it's looking like
> Debian is the last major distro without a fix for this. Could perhaps
> the recent Ubuntu updates ( http://lwn.net/Alerts/165505/ ), which
> were for PHP 4.3.8, be of use to Sarge?

Yes, I'm preparing updates for Debian matching those that I did for Ubuntu.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#335340: This still looks broken to me.

[Adam Conrad]

reopen 335340
kthxbye

This bug still looks to be there in the build logs for 2.9.7-1

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#336645: [php-maint] Bug#336645: More vulnerabilities

[Adam Conrad]

Moritz Muehlenhoff wrote:
> 
> * Fixed an issue with trailing slashes in allowed basedirs. They
>   were ignored by open_basedir checks, so that specified
>   basedirs were handled as prefixes and not as full directory
>   names. (there doesn't seem to be a CVE assignment yet)

This was assigned CAN-2005-3054, the patch was submitted upstream by me,
and it's been fixed in Sid.  The fix is committed to the sarge branch in
SVN, but as we don't tend to consider open_basedir/safe_mode bypasses as
critical security bugs, I'm rolling up all the current bugfixes and will
be preparing an upload for all of them at once.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#335438: libsvncpp-dev and libapr0-dev cannot be installed together

[Adam Conrad]

Matthias Klose wrote:
>
> Package: libsvncpp-dev,libapr0-dev
> Severity: serious
> 
> that means, that pysvn's build-deps cannot be installed
> anymore. Please coordinate, if these these packages should depend on
> libdb4.2-dev or libdb4.3-dev.

They should depend on libdb4.3-dev (and build against libdb4.3).  I'm
committing changes to pkg-subversion right now to fix up libsvn0 and
friends to switch over to db4.3... With any luck, we can rid our systems
of db4.2 sometime in the next 6 months. :/

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#334969: This is hardly "grave"

[Adam Conrad]

severity 334969 important
kthxbye

This bug is hardly "grave".  For starters, Debian doesn't even ship
"Auth-init.php", and a default Debian PEAR installation can run
"upgrade-all" just fine.

I imagine we (or you) will need to sort this with upstream eventually to
see where the blame really lies, if it's with PEAR for making
assumptions about what will be in certain directories, or if it's
auth-init for unceremoniously breaking PEAR by not respecting its
assumptions.

Either way, downgrading this to a non-RC severity, and it can be sorted
later.  The bug's probably always been there.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#322855: FTBFS: Syntax errors with freetds build-dep

[Adam Conrad]

I uploaded a fix to Ubuntu to get libgda2 building with the latest
freetds.  That (mixed up with Martin Pitt's changes to make it build
with the latest postgresql stuff), is included in our patch here:

http://people.ubuntu.com/~scott/patches/libgda2/libgda2_1.2.1-2ubuntu3.patch

Cheers,

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#330495: php3: FTBFS: Failed to satisfy Build-Depends: libsnmp5-dev

[Adam Conrad]

Steve Langasek wrote:
> 
> Adam, is it maybe time to go ahead and just remove php3 from the archive?
> melanie says it has no remaining reverse-deps or reverse-build-deps in
> testing/unstable.

I thought jvw had already requested/marked it for removal, but maybe
not.  Yes, the reason I was blatantly ignoring its RC bugs was
specifically because it was going to be removed, it's not like any of
them are HARD to fix.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#313615: License conflict makes binary undistributable

[Adam Conrad]

Hi, just a reminder on this bug.  Did you ever get around to talking to
upstream about this license conflict?  Note that, because apache almost
always links to libssl, they'll need a license exception for both Apache
and OpenSSL, as most people read things.  (I don't necessarily read it
that way, but better safe than sorry, I guess).

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327269: still problems

[Adam Conrad]

Andreas Jellinghaus wrote:
> btw, I tried --no-auth-cache and it
> does not help at all.
> 
> any other idea?

Can you test the packages at
http://people.debian.org/~adconrad/apache2-security/ for me?

They should fix /a/ bug with SSLVerifyClient and PROPFIND, but I can't
be positive if they'll fix YOUR bug without testing.

Thanks.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#329065: [php-maint] Bug#329065: php5-sybase: sybase_ct doesn't always return correct results from MS SQL

[Adam Conrad]

severity 329065 important
thanks

Johan Palmqvist wrote:
> Severity: grave
> Justification: causes non-serious data loss

How does this cause data loss and warrant a grave bug?

> sybase_ct doesn't always return correct results from MS SQL.
> mssql module seem to work in all cases but is not packaged.

Could you be more specific about what sorts of results it returns
incorrectly, what behaviour you're seeing, a test case to reproduce it?

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327269: apache2 security update breaks ssl+svn

[Adam Conrad]

Andreas Jellinghaus wrote:

>On Friday 09 September 2005 02:37, Adam Conrad wrote:
>  
>
>>I would like a tarball of your /etc/apache2/
>>
>if there is anything else I can do to help, please let me know.
>  
>

Meh.  Yeah, this is actually a neon or svn (not sure who) bug, where it
can't do renogotiations when requested, and our fix for the security
hole in apache2 removed a "feature" (that "feature" was the security
hole) you were relying on with your configs.  I need to set up a test
case here and see if there's a good way to do this, so it still works
how you want, without fixing neon/svn (which isn't really an option).

The bug that you were taking advantage of is that if you had
"SSLVerifyClient optional" in your VirtualHost, and "SSLVerifyClient
require" in a Location statement, the latter would never be honoured, so
I could actually get at your SVN repo by refusing to offer a client
cert, and Apache would give me write access.  Whoops.

We've fixed that, but in fixing that, obviously you've tripped on the
above issue.

Could you try, for curiosity's sake, setting "SSLVerifyClient none" in
the main VirtualHost, and keeping the rest the same, and seeing if that
makes a difference for you at all?  Over the weekend, I'll set up a test
SVN site and follow some codepaths around in mod_ssl and see if there's
still a way (short of you using seperate Vhosts for read access and
read/write access, which has been considered by many the "most secure"
option) to have apache behave the way you'd like it to.

... Adam



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327269: apache2 security update breaks ssl+svn

[Adam Conrad]

Andreas Jellinghaus wrote:

>Package: apache2
>Version: 2.0.54-5
>Severity: critical
>
>After upgrading 2.0.54-4 to 2.0.54-5 svn+ssl is broken:
>
>subversion client (e.g. checkout):
>svn: PROPFIND request failed on '/svn/test'
>svn: PROPFIND of '/svn/test': Could not read status line: SSL error: sslv3 
>alert unexpected message (https://www.opensc.org)
>
>apache error log:
>[Thu Sep 08 20:47:39 2005] [error] Re-negotiation handshake failed: Not 
>accepted by client!?
>
>downgrade to 2.0.54-4 and everything is fine again.
>
>debian gnu linux / sarge / kernel 2.6.11.11 vanilla, i386,
>apache2 on 80 and 443, ssl with self signed certificate,
>accepting a list of self signed certificates, svn repository
>needs those for write access only.
>
>more configuration and any detail you need available on request.
>  
>
I would like a tarball of your /etc/apache2/, if that's not too much
inconvenience.  I suspect a combination of a longstanding subversion bug
and a (mis)configuration of apache2 are biting you, and the recent
apache2 bugfix just exposed the issue.  I need to see how you have your
sites set up to confirm this, though.

... Adam




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327210: apache2: CAN-2005-2700

[Adam Conrad]

Juergen Kreileder wrote:
> Package: apache2
> Version: 2.0.54-4
> Severity: critical
> Tags: security, fixed-upstream
> 
> See http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2700

An update is already in the works for this.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327107: [php-maint] Bug#327107: php5-snmp: not installable in sid

[Adam Conrad]

Laurent Bonnaud wrote:
> Package: php5-snmp
> Version: 5.0.4-3
> Severity: grave
> Justification: renders package unusable
> 
> Hi,
> 
> php5-snmp needs to be recompiled with a newer libsnmp version:

No, net-snmp needs to be uploaded with an SOVERSION bump, THEN PHP needs
to be recompiled.  Recompiling against the currently broken library
won't be doing anyone any favours.  (for now, if you want php5-snmp,
install libsnmp5 from testing).

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#323366: [php-maint] Bug#323366: SECURITY: XML::RPC remote code injections (CAN-2005-2498)

[Adam Conrad]

Zoran Dzelajlija wrote:
> 
> FWIW, patches from Ubuntu might help:

I know, I did the Ubuntu patches.  I need to get the security team in
the loop to get my changes into Debian as well. :/

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#319497: php4: FTBFS (ia64+ppc64): new dpkg changed DEB_HOST_GNU_TYPE

[Adam Conrad]

tags 319497 pending
thanks

Andreas Jochens wrote:
> 
> checking for long... yes
> checking size of long... configure: error: cannot compute sizeof (long), 77
> See `config.log' for more details.
> make: *** [configure-apache-stamp] Error 1

Will be fixed in the next upload.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#318063: php4: PHP 4.4.0 may fix security bugs

[Adam Conrad]

Florian Weimer wrote:


Version 4.4.0 address some memory corruption bugs, apparently resulting
from fairly wide-spread errors in the implementation of reference
counting.  These bugs probably can be exploited by malicious PHP scripts
only, and not by specially crafted input to correctly written PHP
scripts.

These bugs will likely be addressed for stable by a change in the
security bug policy for stable.  Discussions with the security team are
ongoing; a detailed statement should be published soon.


We need a new security policy for something that *may* fix security 
bugs?  Neat.


... Adam



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#316173: apache2: Security issues in HTTP proxy responses with both Transfer-Encoding and Content-Length headers

[Adam Conrad]

Steve Kemp wrote:
>
> Can I be the first to say that I don't understand the nature of this
> issue?

The description sounds reasonably straightforward, though I'd classify
this as a vulnerability of pretty low importance, from a "will people be
exploited by this" viewpoint.

> Is this also present in 2.0.54 which is the latest stable release?
> There's no mention of it in the changelog there..

It looks like it's in 2.0.54, and there's a backport in SVN for the 2.0.55
release, but the backport looks more like a massive feature backport, not
just a small security patch, so I may look at if there's a way to fix this
a bit less intrusively.

Actually, it's worth nothing that we muck with Content-Length at another
point, thanks to a Debian-specific patch, so we may accidentally not be
vulnerable to this anyway.  I'll follow the code around a little later
today and see if that's the case.

... Adam




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]