Control: tags 958958 + patch
Control: tags 958958 + pending
Control: tags 962090 + patch
Control: tags 962090 + pending

Dear maintainer,

I've prepared an NMU for libtorrent-rasterbar (versioned as 1.2.5-1.1) 
and uploaded it to DELAYED/2. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru libtorrent-rasterbar-1.2.5/debian/changelog libtorrent-rasterbar-1.2.5/debian/changelog
--- libtorrent-rasterbar-1.2.5/debian/changelog	2020-03-10 02:41:03.000000000 +0200
+++ libtorrent-rasterbar-1.2.5/debian/changelog	2020-06-10 17:37:20.000000000 +0300
@@ -1,3 +1,12 @@
+libtorrent-rasterbar (1.2.5-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Link against libatomic on armel/mipsel/m68k/powerpc/sh4.
+    (Closes: #958958)
+  * Build depend on python, which reopens #936927 but closes: #962090.
+
+ -- Adrian Bunk <b...@debian.org>  Wed, 10 Jun 2020 17:37:20 +0300
+
 libtorrent-rasterbar (1.2.5-1) unstable; urgency=medium
 
   * New upstream release (Closes: #952447).
diff -Nru libtorrent-rasterbar-1.2.5/debian/control libtorrent-rasterbar-1.2.5/debian/control
--- libtorrent-rasterbar-1.2.5/debian/control	2020-03-10 02:30:54.000000000 +0200
+++ libtorrent-rasterbar-1.2.5/debian/control	2020-06-10 17:37:20.000000000 +0300
@@ -11,6 +11,7 @@
                libboost-random-dev,
                libssl-dev,
                pkg-config,
+               python,
                python3-docutils,
                python3-all-dev,
                python3-all-dbg,
diff -Nru libtorrent-rasterbar-1.2.5/debian/rules libtorrent-rasterbar-1.2.5/debian/rules
--- libtorrent-rasterbar-1.2.5/debian/rules	2020-03-10 02:39:23.000000000 +0200
+++ libtorrent-rasterbar-1.2.5/debian/rules	2020-06-10 17:37:16.000000000 +0300
@@ -5,6 +5,10 @@
 
 export DEB_LDFLAGS_MAINT_APPEND  = -Wl,--as-needed
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel m68k powerpc sh4))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic -Wl,--as-needed
+endif
+
 PYTHON3=$(shell py3versions -vr)
 ALLPY=$(PYTHON3) $(PYTHON3:%=%-dbg)
 

Reply via email to