Bug#897108: gitano FTBFS with pandoc 2.1.2

2018-04-30 Thread Daniel Silverstone
forward 897108 https://trello.com/c/CrnBZptB/275
thanks

On Sat, Apr 28, 2018 at 17:28:31 +0300, Adrian Bunk wrote:
> pandoc --standalone --toc --chapters -V documentclass:report -V 
> geometry:margin=1in -V graphics:true -V papersize:a4paper -H titling.tex -H 
> header.tex -o gitano-admin-doc.pdf 000.mdwn
> --chapters has been removed. Use --top-level-division=chapter instead.
> Try pandoc --help for more information.

This looks to be a non-backward-compatible change in behaviour between pandoc 
1.x and 2.x
and will require a change to the upstream build system.  There are a number of 
things which
must happen for 1.2 of Gitano and this has been added to them.

You can see the upstream tracking card at https://trello.com/c/CrnBZptB/275

Thanks,

Daniel.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



Bug#821892: Missing patch

2017-01-28 Thread Daniel Silverstone
Hi,

here's the missing patch, sorry, my email had a snafu.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
diff -Nru pycountry-1.8+ds1/debian/changelog pycountry-1.8+ds1/debian/changelog
--- pycountry-1.8+ds1/debian/changelog	2014-08-27 00:21:20.0 +0100
+++ pycountry-1.8+ds1/debian/changelog	2017-01-28 23:28:00.0 +
@@ -1,3 +1,10 @@
+pycountry (1.8+ds1-0.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 01-disable-failing-asserts.patch (Closes: #821892)
+
+ -- Daniel Silverstone <dsilv...@digital-scurf.org>  Sat, 28 Jan 2017 23:27:30 +
+
 pycountry (1.8+ds1-0.1) unstable; urgency=medium
 
   * New upstream release
diff -Nru pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch
--- pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch	1970-01-01 01:00:00.0 +0100
+++ pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch	2017-01-28 23:31:34.0 +
@@ -0,0 +1,52 @@
+Description: Disable failing asserts
+ iso-codes has long moved on beyond that which pycountry knows.
+ This means the count of countries, subdivisions, etc are out of
+ date.  Rather than risk an FTBFS when iso-codes moves on once more
+ simply comment out the specific asserts, leaving the rest of the
+ testing intact.
+Author: Daniel Silverstone <dsilv...@digital-scurf.org>
+Origin: other
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821892
+Forwarded: no
+Reviewed-by: Jonathan Wiltshire <j...@debian.org>
+Last-Update: 2017-02-28
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/pycountry/tests/test_general.py
 b/src/pycountry/tests/test_general.py
+@@ -25,7 +25,7 @@
+ 
+ 
+ def test_subdivisions_directly_accessible():
+-assert len(pycountry.subdivisions) == 4847
++#assert len(pycountry.subdivisions) == 4847
+ assert isinstance(list(pycountry.subdivisions)[0], pycountry.db.Data)
+ 
+ de_st = pycountry.subdivisions.get(code='DE-ST')
+@@ -51,7 +51,7 @@
+ 
+ 
+ def test_scripts():
+-assert len(pycountry.scripts) == 169
++#assert len(pycountry.scripts) == 169
+ assert isinstance(list(pycountry.scripts)[0], pycountry.db.Data)
+ 
+ latin = pycountry.scripts.get(name='Latin')
+@@ -61,7 +61,7 @@
+ 
+ 
+ def test_currencies():
+-assert len(pycountry.currencies) == 182
++#assert len(pycountry.currencies) == 182
+ assert isinstance(list(pycountry.currencies)[0], pycountry.db.Data)
+ 
+ argentine_peso = pycountry.currencies.get(letter='ARS')
+@@ -71,7 +71,7 @@
+ 
+ 
+ def test_languages():
+-assert len(pycountry.languages) == 487
++#assert len(pycountry.languages) == 487
+ assert isinstance(list(pycountry.languages)[0], pycountry.db.Data)
+ 
+ aragonese = pycountry.languages.get(alpha2='an')
diff -Nru pycountry-1.8+ds1/debian/patches/series pycountry-1.8+ds1/debian/patches/series
--- pycountry-1.8+ds1/debian/patches/series	2014-07-09 16:49:47.0 +0100
+++ pycountry-1.8+ds1/debian/patches/series	2017-01-28 23:26:49.0 +
@@ -1,2 +1,3 @@
 00-use_system_iso-codes.patch
 01-prevent_logger_warning.patch
+02-disable-failing-asserts.patch


Bug#821892: Fix patch - disables broken asserts

2017-01-28 Thread Daniel Silverstone
Hi,

I have prepared an NMU which disables the rogue asserts.  They make an
assumption on the size of the iso-codes databases which have moved on since
pycountry.  Rather than updating the numbers in the package which will fail the
next time iso-codes changes size again, simply disable the rogue asserts and
just let the rest of the test suite run.

I have uploaded this to Unstable.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



Bug#834746: NMU Fix for FTBFS

2017-01-28 Thread Daniel Silverstone
Control: tags -1 patch pending

Hi,

Attached is an NMU patch which corrects the problem in this bug.  This is
related to the fact that the test suite (and only the test suite) relies on
SSE2 for i386 (which should be no issue for the buildds).

I have uploaded this to unstable.

Thanks,

Daniel.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
diff -Nru jemalloc-3.6.0/debian/changelog jemalloc-3.6.0/debian/changelog
--- jemalloc-3.6.0/debian/changelog	2016-01-27 21:20:33.0 +
+++ jemalloc-3.6.0/debian/changelog	2017-01-28 17:21:21.0 +
@@ -1,3 +1,12 @@
+jemalloc (3.6.0-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add testflags.patch which adds a TESTFLAGS env var support when
+compiling tests.
+  * Add -msse4.1 to i386 TESTFLAGS (Closes: #834746)
+
+ -- Daniel Silverstone <dsilv...@digital-scurf.org>  Sat, 28 Jan 2017 17:21:21 +
+
 jemalloc (3.6.0-9) unstable; urgency=medium
 
   [ Balint Reczey ]
diff -Nru jemalloc-3.6.0/debian/patches/series jemalloc-3.6.0/debian/patches/series
--- jemalloc-3.6.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ jemalloc-3.6.0/debian/patches/series	2017-01-28 17:07:36.0 +
@@ -0,0 +1 @@
+testflags.patch
diff -Nru jemalloc-3.6.0/debian/patches/testflags.patch jemalloc-3.6.0/debian/patches/testflags.patch
--- jemalloc-3.6.0/debian/patches/testflags.patch	1970-01-01 01:00:00.0 +0100
+++ jemalloc-3.6.0/debian/patches/testflags.patch	2017-01-28 17:20:53.0 +
@@ -0,0 +1,31 @@
+Description: Add support for TESTFLAGS
+ Add support to Makefile.in to allow passing TESTFLAGS to give
+ extra CFLAGS to the compilation of test files.
+Author: Daniel Silverstone <dsilv...@digital-scurf.org>
+Origin: other
+Bug: 834746
+Forwarded: no
+Reviewed-by: Steve McIntyre <st...@einval.com>
+Last-Update: 2017-01-28
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Makefile.in
 b/Makefile.in
+@@ -207,7 +207,7 @@
+ $(C_UTIL_INTEGRATION_OBJS): $(objroot)src/%.integration.$(O): $(srcroot)src/%.c
+ $(C_TESTLIB_STRESS_OBJS): $(objroot)test/src/%.stress.$(O): $(srcroot)test/src/%.c
+ $(C_TESTLIB_STRESS_OBJS): CPPFLAGS += -DJEMALLOC_STRESS_TEST -DJEMALLOC_STRESS_TESTLIB
+-$(C_TESTLIB_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include
++$(C_TESTLIB_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include $(TESTFLAGS)
+ $(TESTS_UNIT_OBJS): CPPFLAGS += -DJEMALLOC_UNIT_TEST
+ $(TESTS_UNIT_AUX_OBJS): CPPFLAGS += -DJEMALLOC_UNIT_TEST
+ define make-unit-link-dep
+@@ -218,7 +218,7 @@
+ $(TESTS_INTEGRATION_OBJS): CPPFLAGS += -DJEMALLOC_INTEGRATION_TEST
+ $(TESTS_STRESS_OBJS): CPPFLAGS += -DJEMALLOC_STRESS_TEST
+ $(TESTS_OBJS): $(objroot)test/%.$(O): $(srcroot)test/%.c
+-$(TESTS_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include
++$(TESTS_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include $(TESTFLAGS)
+ ifneq ($(IMPORTLIB),$(SO))
+ $(C_OBJS): CPPFLAGS += -DDLLEXPORT
+ endif
diff -Nru jemalloc-3.6.0/debian/rules jemalloc-3.6.0/debian/rules
--- jemalloc-3.6.0/debian/rules	2016-01-27 21:16:22.0 +
+++ jemalloc-3.6.0/debian/rules	2017-01-28 17:21:21.0 +
@@ -27,6 +27,12 @@
   DEB_CPPFLAGS_MAINT_APPEND += -DPATH_MAX=8192
 endif
 
+ifeq ($(DEB_HOST_ARCH),i386)
+  # i386 needs -msse4.1 in order to be able to run the test suite
+  # and as far as we can tell, *ONLY* the test suite
+  TESTFLAGS += -msse4.1
+endif
+
 DEB_CFLAGS_MAINT_APPEND += -std=gnu99
 
 export DEB_CFLAGS_MAINT_APPEND DEB_CPPFLAGS_MAINT_APPEND
@@ -40,7 +46,7 @@
 ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
 export ASAN_OPTIONS = suppressions=$(CURDIR)/debian/asan-suppressions.txt
 override_dh_auto_test:
-	make check
+	make check "TESTFLAGS=$(TESTFLAGS)"
 endif
 
 override_dh_auto_install:


Bug#852044: Fix FTBFS

2017-01-28 Thread Daniel Silverstone
Control: tags 852044 + patch

Hi Enrico,

Attached is a patch which fixes this FTBFS.

I have uploaded this to unstable.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
diff -Nru lua-curl-0.3.0/debian/changelog lua-curl-0.3.0/debian/changelog
--- lua-curl-0.3.0/debian/changelog	2014-08-27 10:11:30.0 +0100
+++ lua-curl-0.3.0/debian/changelog	2017-01-28 14:09:19.0 +
@@ -1,3 +1,11 @@
+lua-curl (0.3.0-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * curl headers are now in the multiarch include form, use them.
+(Closes: #852044)
+
+ -- Daniel Silverstone <dsilv...@digital-scurf.org>  Sat, 28 Jan 2017 14:09:19 +
+
 lua-curl (0.3.0-9) unstable; urgency=medium
 
   * Fix FTBFS (Closes: #755338) 
diff -Nru lua-curl-0.3.0/debian/control lua-curl-0.3.0/debian/control
--- lua-curl-0.3.0/debian/control	2014-08-27 10:11:30.0 +0100
+++ lua-curl-0.3.0/debian/control	2017-01-28 14:03:48.0 +
@@ -2,7 +2,7 @@
 Section: interpreters
 Priority: optional
 Maintainer: Enrico Tassi <gareuselesi...@debian.org>
-Build-Depends: debhelper (>= 8.1.3), libcurl4-gnutls-dev (>= 7.15.0-2), dh-lua
+Build-Depends: debhelper (>= 8.1.3), libcurl4-gnutls-dev (>= 7.52.1-1~), dh-lua
 Standards-Version: 3.9.3
 Vcs-Svn: svn://svn.debian.org/pkg-lua/packages/lua-curl
 Vcs-Browser: http://svn.debian.org/viewsvn/pkg-lua/packages/lua-curl
diff -Nru lua-curl-0.3.0/debian/rules lua-curl-0.3.0/debian/rules
--- lua-curl-0.3.0/debian/rules	2014-08-27 10:11:30.0 +0100
+++ lua-curl-0.3.0/debian/rules	2017-01-28 13:57:15.0 +
@@ -8,5 +8,5 @@
 	dh_auto_clean
 
 override_dh_auto_configure:
-	$(MAKE) -f Makefile constants
+	$(MAKE) -f Makefile HEADER="/usr/include/$(shell dpkg-architecture -qDEB_HOST_MULTIARCH)/curl/curl.h" constants
 	dh_auto_configure


Bug#851803: Fix uploaded to DELAYED/5

2017-01-28 Thread Daniel Silverstone
Control: tag -1 pending

Hi,

I've uploaded the patch previously sent into DELAYED/5

Let me know if this should be expedited.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



Bug#851803: Bug fix for #851803

2017-01-28 Thread Daniel Silverstone
Attached is a quick fix for #851803

This is the quickest way to restore behaviour which was being used
before the update of /etc/debian_version ready for Stretch's release.

In the future, it'd be better to use --with-locfile=debian and adjust
the rules and install files to match the debian locations instead.
But this shouldn't be done until Stretch is out.

Thanks,

Daniel.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
diff -Nru ntp-4.2.8p9+dfsg/debian/changelog ntp-4.2.8p9+dfsg/debian/changelog
--- ntp-4.2.8p9+dfsg/debian/changelog	2016-11-21 19:09:17.0 +
+++ ntp-4.2.8p9+dfsg/debian/changelog	2017-01-28 11:58:18.0 +
@@ -1,3 +1,10 @@
+ntp (1:4.2.8p9+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Force program locations to use 'legacy' defaults (Closes: #851803)
+
+ -- Daniel Silverstone <dsilv...@digital-scurf.org>  Sat, 28 Jan 2017 11:58:18 +
+
 ntp (1:4.2.8p9+dfsg-2) unstable; urgency=medium
 
   * CVE-2016-0727: NTP statsdir cleanup cronjob insecure (Closes: #839998)
diff -Nru ntp-4.2.8p9+dfsg/debian/rules ntp-4.2.8p9+dfsg/debian/rules
--- ntp-4.2.8p9+dfsg/debian/rules	2016-05-19 19:53:43.0 +0100
+++ ntp-4.2.8p9+dfsg/debian/rules	2017-01-28 11:40:56.0 +
@@ -27,6 +27,7 @@
 		--disable-local-libopts \
 		--enable-ntp-signd \
 		--disable-dependency-tracking \
+		--with-locfile=legacy \
 		--with-openssl-libdir=/usr/lib/$(DEB_HOST_MULTIARCH)
 
 build: build-arch build-indep


Bug#837117: This bug is not found in 1.21-3

2016-10-12 Thread Daniel Silverstone
notfound 837117 1.21-3

Hi,

I spent some time today checking, and 1.21-3 's source doesn't differ
materially from the SHA presented by the reporter.  I can confirm that
the bug is definitely present in the version in Jessie, but unstable
is clear.

If I have some time, I'll look at what is necessary to fix the Jessie
package, but honestly, once 1.21-3 gets into testing it's probably best
to just request a backport if the reporter still cares.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



Bug#556939: libgfshare-bin: can produce broken shares containing foo.000

2009-11-18 Thread Daniel Silverstone
On Wed, Nov 18, 2009 at 03:36:37PM +0100, Florian Zumbiehl wrote:
 Why is it randomized anyhow? Just numbering shares from 1 would produce
 more reproducible results, thus making it more likely that problems
 specific to a certain use case would get noticed before it's too late.
 It probably would be easier to use for some purposes, too, if file names
 were easier to predict.

Randomised so that you can easily strip the numbers and place them
elsewhere and thereby make it harder to guess the share numbers.

 BTW, the command line parser is pretty much completely broken if you judge
 it by the error messages it produces even for completely valid values as
 per its own help output. In case you want to fix that, too ...

Back then I wasn't very good at cmdline parsers.  Patch welcome.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



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



Bug#556939: libgfshare-bin: can produce broken shares containing foo.000

2009-11-18 Thread Daniel Silverstone
On Wed, Nov 18, 2009 at 04:05:20PM +0100, Florian Zumbiehl wrote:
  Randomised so that you can easily strip the numbers and place them
  elsewhere and thereby make it harder to guess the share numbers.
 And that is good for what?

If you lose a number of shares equal-to-or-greater-than the number
required to reconstruct the share, it might arguably provide you with a
short period of time in which to revoke those keys.  I'd be quite happy
to receive a patch which offered an option of sequential vs. randomised
share numbers.

D.

(And no, I'm not claiming added security, just the potential of a little
more time to deal with the fact that your security is breached)

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



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



Bug#556939: libgfshare-bin: can produce broken shares containing foo.000

2009-11-18 Thread Daniel Silverstone
On Wed, Nov 18, 2009 at 02:00:25PM +, Simon McVittie wrote:
 The mathematics of Shamir secret sharing do not work correctly with x_i = 0,
 i.e. a component foo.000, so the library should reject any sharenrs array
 that contains 0, and the utilities should not produce such arrays. I'll
 prepare a patch this evening.
 Daniel, do you agree with this diagnosis?

Indeed, the zero-share is not useful since in theory it'd be the data
unchanged.

The software should reject zero-share instances, and not create them.

I'm happy for you to supply me with a bundle, or I can sort it out
myself, whichever you would prefer.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



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



Bug#527872: How to fix

2009-07-24 Thread Daniel Silverstone
tags 527872 + patch
thanks

Hi,

You can stop the exit-on-dbus-exit by adding:

dbus_connection_set_exit_on_disconnect(dbus_connection, FALSE);

to a_dbus_connect() in dbus.c

This has been tested and appears to work.

Dunno if awesome will then need some reconnect logic, but at least it'll
stop it exiting when dbus restarts.

D.


-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 2BC8 4016 2068 7895




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



Bug#527872: Diff for previous info

2009-07-24 Thread Daniel Silverstone
Attached is a diff which is an NMU. I can upload it if you're too busy
to take it.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 2BC8 4016 2068 7895
diff -u awesome-3.3.1/debian/changelog awesome-3.3.1/debian/changelog
--- awesome-3.3.1/debian/changelog
+++ awesome-3.3.1/debian/changelog
@@ -1,3 +1,10 @@
+awesome (3.3.1-1.1) unstable; urgency=low
+
+  * NMU to add dbus_connection_set_exit_on_disconnect to stop the bus
+disconnecting and causing awesome to die. (Closes: #527872)
+
+ -- Daniel Silverstone dsilv...@debian.org  Fri, 24 Jul 2009 15:42:14 +0200
+
 awesome (3.3.1-1) unstable; urgency=low
 
   * New upstream release
only in patch2:
unchanged:
--- awesome-3.3.1.orig/dbus.c
+++ awesome-3.3.1/dbus.c
@@ -502,7 +502,9 @@
 a_dbus_cleanup_bus(dbus_connection, dbusio);
 }
 }
-
+
+dbus_connection_set_exit_on_disconnect(dbus_connection, FALSE);
+
 return dbus_connection;
 }
 


signature.asc
Description: This is a digitally signed message part