Bug#885124: RM: pyresample [armhf] -- ROM; pandas dependency not available on armhf
Package: ftp.debian.org Severity: normal Please remove pyresample from armhf, the pandas dependencies (via xarray) are not available on armhf. Kind Regards, Bas
Bug#884967: opencv: FTBFS on various architectures
Source: opencv Version: 3.2.0+dfsg-4 Severity: serious Justification: makes the package in question unusable or mostly so Control: block 884504 by -1 Dear Maintainer, Your package FTBFS on various architectures, which is blocking the gdal transition (#884504). On most architectures the error is related to tesseract which was updated to 4.00~git2174-3b62badd-5 recently, triggering an uncoordinated transition. armel: cd /<>/opencv-3.2.0+dfsg/obj-arm-linux-gnueabi/modules/saliency && /usr/bin/c++ -DCVAPI_EXPORTS -D__OPENCV_BUILD=1 -isystem /<>/opencv-3.2.0+dfsg/obj-arm-linux-gnueabi -isystem /usr/include/gdal -isystem /usr/include/eigen3 -I/<>/opencv-3.2.0+dfsg/contrib/modules/saliency/include -I/<>/opencv-3.2.0+dfsg/contrib/modules/saliency/src -I/<>/opencv-3.2.0+dfsg/obj-arm-linux-gnueabi/modules/saliency -I/<>/opencv-3.2.0+dfsg/modules/core/include -I/<>/opencv-3.2.0+dfsg/modules/flann/include -I/<>/opencv-3.2.0+dfsg/modules/imgproc/include -I/<>/opencv-3.2.0+dfsg/modules/ml/include -I/<>/opencv-3.2.0+dfsg/modules/imgcodecs/include -I/<>/opencv-3.2.0+dfsg/modules/videoio/include -I/<>/opencv-3.2.0+dfsg/modules/highgui/include -I/<>/opencv-3.2.0+dfsg/modules/features2d/include -g -O2 -fdebug-prefix-map=/<>/opencv-3.2.0+dfsg=. -fstack-protector-strong -Wfo rmat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -fdiagnostics-show-option -pthread -fomit-frame-pointer -mfp16-format=ieee -ffunction-sections -fvisibility=hidden -fvisibility-inlines-hidden -Wno-overloaded-virtual -g -O2 -fdebug-prefix-map=/<>/opencv-3.2.0+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -fPIC -o CMakeFiles/opencv_saliency.dir/src/BING/CmShow.cpp.o -c /<>/opencv-3.2.0+dfsg/contrib/modules/saliency/src/BING/CmShow.cpp In file included from /usr/include/tesseract/ltrresultiterator.h:26:0, from /usr/include/tesseract/resultiterator.h:26, from /usr/include/tesseract/baseapi.h:31, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/precomp.hpp:51, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/erfilter.cpp:43: /usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; did you mean 'stdin'? static string UTF32ToUTF8(const std::vector& str32); ^~ stdin buildlog: https://buildd.debian.org/status/fetch.php?pkg=opencv=armel=3.2.0%2Bdfsg-4%2Bb1=1513664764=0 armhf: In file included from /usr/include/tesseract/ltrresultiterator.h:26:0, from /usr/include/tesseract/resultiterator.h:26, from /usr/include/tesseract/baseapi.h:31, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/precomp.hpp:51, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/erfilter.cpp:43: /usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; did you mean 'stdin'? static string UTF32ToUTF8(const std::vector& str32); ^~ stdin In file included from /usr/include/tesseract/ltrresultiterator.h:26:0, from /usr/include/tesseract/resultiterator.h:26, from /usr/include/tesseract/baseapi.h:31, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/precomp.hpp:51, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/ocr_beamsearch_decoder.cpp:43: /usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; did you mean 'stdin'? static string UTF32ToUTF8(const std::vector& str32); ^~ stdin buildlog: https://buildd.debian.org/status/fetch.php?pkg=opencv=armhf=3.2.0%2Bdfsg-4%2Bb1=1513722611=0 mips: In file included from /usr/include/tesseract/ltrresultiterator.h:26:0, from /usr/include/tesseract/resultiterator.h:26, from /usr/include/tesseract/baseapi.h:31, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/precomp.hpp:51, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/erfilter.cpp:43: /usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; did you mean 'stdin'? static string UTF32ToUTF8(const std::vector& str32); ^~ stdin In file included from /usr/include/tesseract/ltrresultiterator.h:26:0, from /usr/include/tesseract/resultiterator.h:26, from /usr/include/tesseract/baseapi.h:31, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/precomp.hpp:51, from /<>/opencv-3.2.0+dfsg/contrib/modules/text/src/ocr_beamsearch_decoder.cpp:43:
Bug#884537: RFA: jts -- JTS Topology Suite
Package: wnpp Severity: normal Due to the lack of Java expertise in the Debian GIS team, and all reverse dependencies of the jts package being maintained by the Debian Java Maintainers, I request the latter to adopt the jts package. The package description is: JTS is a java library which provides: * an implementation of the spatial data model defined in the OGC Simple Features Specification for SQL (SFS) * a complete, consistent, implementation of fundamental 2D spatial algorithms * an explicit precision model, with algorithms that gracefully handle situations that result in dimensional collapse * robust implementations of key computational geometric operations * I/O in Well-Known Text format Kind Regards, Bas
Bug#884504: transition: gdal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition For the Debian GIS team I'd like to transition to GDAL 2.2.3. Like the previous transition to GDAL 2.2.2 (#876561), there is no SONAME bump, only the virtual ABI package changed to account for the C++ symbol changes. All reverse dependencies rebuilt successfully with GDAL 2.2.3 from experimental as summarized below. libgdal-grass doesn't need a binNMU as the 2.2.3 version will be uploaded to unstable instead. liblas likewise doesn't need a binNMU, the version is experimental will be moved to unstable instead. Ben file: title = "gdal"; is_affected = .depends ~ "gdal-abi-2-2-2" | .depends ~ "gdal-abi-2-2-3"; is_good = .depends ~ "gdal-abi-2-2-3"; is_bad = .depends ~ "gdal-abi-2-2-2"; Transition: gdal libgdal20 (2.2.2+dfsg-2) -> libgdal20 (2.2.3+dfsg-1~exp1) gdal-abi-2-2-2 -> gdal-abi-2-2-3 The status of the most recent rebuilds is as follows. dans-gdal-scripts (0.24-1) OK fiona (1.7.10-1) OK gazebo (7.8.1+dfsg-3) OK gmt (5.4.2+dfsg-1) SKIP (no C++) imposm (2.6.0+ds-4) SKIP (no C++) libcitygml (2.0.7-1)OK liblas (1.8.1-5)OK libosmium (2.13.1-1) SKIP (no C++) mapcache(1.6.1-1)SKIP (no C++) mapnik (3.0.17+ds-1)OK mapproxy(1.11.0-1) SKIP (no C++) mapserver (7.0.7-1)SKIP (no C++) merkaartor (0.18.3+ds-2)OK mysql-workbench (6.3.8+dfsg-1) OK ncl (6.4.0-4)SKIP (no C++) node-srs(0.4.8+dfsg-3) OK octave-mapping (1.2.1-1)OK openorienteering-mapper (0.7.0-1)SKIP (no C++) openscenegraph (3.2.3+dfsg1-2) OK pdal(1.6.0-1)OK pgsql-ogr-fdw (1.0.5-2)SKIP (no C++) postgis (2.4.2+dfsg-3) SKIP (no C++) pprepair(0.0~20170614-dd91a21-1) OK prepair (0.7.1-1)OK python-django (1:1.11.7-1) SKIP (no C++) qlandkartegt(1.8.1+ds-8) OK qmapshack (1.9.1-1)OK rasterio(0.36.0-2) OK sumo(0.30.0+dfsg1-1) OK thuban (1.2.2-12) OK vtk6(6.3.0+dfsg1-11) OK xastir (2.0.8-3)SKIP (no C++) grass (7.2.2-1)SKIP (no C++) opencv (3.2.0+dfsg-4) OK openscenegraph-3.4 (3.4.1+dfsg1-2) OK osmcoastline(2.1.4-2)OK pktools (2.6.7.1+ds-1) OK pyosmium(2.13.0-1) SKIP (no C++) libgdal-grass (2.2.2-1 / 2.2.3-1~exp1) FTBFS / OK osgearth(2.8.0+dfsg-2) OK otb (6.2.0+dfsg-1) OK qgis(2.14.21+dfsg-1) OK saga(2.3.1+dfsg-3) OK Kind Regards, Bas
Bug#882681: mariadb-10.1: Missing mariadb-test package prevents testing migration
Source: mariadb-10.1 Version: 1:10.1.29-6 Severity: serious Justification: makes the package in question unusable or mostly so Control: affects -1 src:apr-util src:asterisk src:dovecot src:exim4 src:gammu src:gdal src:gnunet src:gnustep-sqlclient src:grass src:jabberd2 src:kamailio src:kdb src:kopanocore src:mailutils src:mysql-connector-c++ src:pike7.8 src:pmacct src:poco src:qtbase-opensource-src src:slurm-llnl src:sope src:vtk6 src:zabbix Dear Maintainer, The mariadb-10.1 packages no longer build the mariadb-test & mariadb-test-data packages, but the version in testing still does. This prevents britney from migrating the package to testing [0]: trying: mariadb-10.1 skipped: mariadb-10.1 (1827, 1009, 24) got: 71+0: a-10:i-32:a-3:a-3:a-3:m-3:m-7:m-3:p-3:s-4 * mips64el: mariadb-test Because mariadb-10.2 is not going to migrate to testing any time soon, the -test* packages need to be built by the mariadb-10.1 package again now that its version uses an epoch. [0] https://release.debian.org/britney/update_output.txt Kind Regards, Bas
Bug#882417: mariadb-10.1: FTBFS on arm64 (internal compiler error)
Source: mariadb-10.1 Version: 1:10.1.29-2 Severity: serious Justification: makes the package in question unusable or mostly so Control: affects -1 src:apr-util, src:asterisk, src:dovecot, src:exim4, src:gammu, src:gnunet, src:gnustep-sqlclient, src:grass, src:jabberd2, src:kamailio, src:kdb, src:kopanocore, src:mailutils, src:mysql-connector-c++, src:pike7.8, src:pmacct, src:poco, src:sope, src:vtk6, and src:zabbix Dear Maintainer, mariadb-10.1 (1:10.1.29-2) is looking much better than the previous uploads, but it still FTBFS on arm64 due to an internal compiler error: " /<>/storage/mroonga/vendor/groonga/lib/ts/ts_expr_node.c: In function 'grn_ts_op_not_equal_evaluate': /<>/storage/mroonga/vendor/groonga/lib/ts/ts_expr_node.c:3824:18: internal compiler error: in gen_vec_cmpv2dfv2di, at config/aarch64/aarch64-simd.md:2495 out_ptr[i] = grn_ts_op_ ## type ## _ ## kind(buf_ptrs[0][i],\ ~~~^~ buf_ptrs[1][i]);\ ~~~ /<>/storage/mroonga/vendor/groonga/lib/ts/ts_expr_node.c:3863:5: note: in expansion of macro 'GRN_TS_OP_CHK_EVALUATE_CASE' GRN_TS_OP_CHK_EVALUATE_CASE(type, FLOAT, float)\ ^~~ /<>/storage/mroonga/vendor/groonga/lib/ts/ts_expr_node.c:3893:3: note: in expansion of macro 'GRN_TS_OP_CHK_EVALUATE' GRN_TS_OP_CHK_EVALUATE(not_equal) ^~ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. " https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.1=arm64=1%3A10.1.29-2=1511344924=0 This build failure still prevents testing migration of mariadb-10.1 and its reverse dependencies. Kind Regards, Bas
Bug#881898: mariadb-10.1: Uploads rejected by dak, blocking testing migration of mariadb-10.1 and its reverse dependencies
Source: mariadb-10.1 Version: 10.1.28-2 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, The recent upload of mariadb-10.1 remains in Uploaded status on various architectures because as Mattia Rizzolo reported "the binary uploads got rejected by dak because they tried to upload binaries with a lower version than ones already installed (and built by mariadb-10.2)." Please fix these issues so mariadb-10.1 can finally migrate to testing and unblock the testing migration of its many reverse dependencies. Maintainers of reverse dependencies will be forced to remove the MySQL/MariaDB support in their packages if they want their packages to migrate to testing otherwise. This is not in the interest of our users. Kind Regards, Bas
Bug#880746: libmetadata-extractor-java: Manifest references xmpcore-debian.jar, but libxmpcore-java does not provide this file.
Source: libmetadata-extractor-java Version: 2.10.1-2 Severity: important Control: affects -1 src:gpsprune Dear Maintainer, As reported in the upstream GpsPrune issue [0], loading JPG files using libmetadata-extractor-java causes NoClassDefFoundError exceptions: Link: com/adobe/xmp/XMPException java.lang.NoClassDefFoundError: com/adobe/xmp/XMPException at com.drew.imaging.jpeg.JpegMetadataReader.(JpegMetadataReader.java:57) at com.drew.imaging.ImageMetadataReader.readMetadata(ImageMetadataReader.java:111) at com.drew.imaging.ImageMetadataReader.readMetadata(ImageMetadataReader.java:161) at tim.prune.jpeg.ExternalExifLibrary.getJpegData(ExternalExifLibrary.java:36) at tim.prune.jpeg.ExifGateway.getJpegData(ExifGateway.java:46) at tim.prune.load.JpegLoader.createPhoto(JpegLoader.java:227) at tim.prune.load.JpegLoader.processFile(JpegLoader.java:204) at tim.prune.load.JpegLoader.processFileList(JpegLoader.java:172) at tim.prune.load.JpegLoader.run(JpegLoader.java:127) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.ClassNotFoundException: com.adobe.xmp.XMPException at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) The GpsPrune upstream developer traced this issue down to an incorrect jar being referenced in the manifest of libmetdata-extractor-java: " I had a look at the jars, and the manifest of GpsPrune's jar correctly references the metadata-extractor.jar. However, the manifest of the metadata-extractor.jar refers to a file called "xmpcore-debian.jar" instead of "xmpcore.jar" as I would expect. " The xmpcore-debian.jar file is not provided by the libxmpcore-java package, only xmpcore.jar & xmpcore-5.1.2.jar. The attached patch uses jh_classpath from javahelper to fix the Class-Path in metadata-extractor.jar. Please consider applying this patch, or fix this issue in a different way. [0] https://github.com/activityworkshop/GpsPrune/issues/15 Kind Regards, Bas >From 70f18e987b094e2f562b68bb459aa7aca94f9b0c Mon Sep 17 00:00:00 2001 From: Bas Couwenberg <sebas...@xs4all.nl> Date: Sat, 4 Nov 2017 17:48:37 +0100 Subject: Use javahelper to fix the Class-Path for xmpcore.jar. --- debian/changelog| 7 +++ debian/control | 1 + debian/libmetadata-extractor-java.classpath | 1 + debian/rules| 4 4 files changed, 13 insertions(+) create mode 100644 debian/libmetadata-extractor-java.classpath diff --git a/debian/changelog b/debian/changelog index 4cd2d38..a87850d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +libmetadata-extractor-java (2.10.1-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Use javahelper to fix the Class-Path for xmpcore.jar. + + -- Bas Couwenberg <sebas...@debian.org> Sat, 04 Nov 2017 17:48:01 +0100 + libmetadata-extractor-java (2.10.1-2) unstable; urgency=medium * Team upload. diff --git a/debian/control b/debian/control index 06c4607..7dad3d2 100644 --- a/debian/control +++ b/debian/control @@ -6,6 +6,7 @@ Uploaders: Emmanuel Bourg <ebo...@apache.org> Build-Depends: debhelper (>= 10), default-jdk, default-jdk-doc, + javahelper, junit4, libxmpcore-java, libmaven-javadoc-plugin-java, diff --git a/debian/libmetadata-extractor-java.classpath b/debian/libmetadata-extractor-java.classpath new file mode 100644 index 000..10ba889 --- /dev/null +++ b/debian/libmetadata-extractor-java.classpath @@ -0,0 +1 @@ +usr/share/java/metadata-extractor.jar /usr/share/java/xmpcore.jar diff --git a/debian/rules b/debian/rules index fa23c8f..194f12c 100755 --- a/debian/rules +++ b/debian/rules @@ -3,5 +3,9 @@ %: dh $@ --buildsystem=maven +override_dh_install: + dh_install + jh_classpath -v + get-orig-source:: uscan --force-download --download-current-version -- 2.11.0
Bug#879544: netcdf transiton: ncl
On 2017-10-31 14:48, Alastair McKinstry wrote: "ncl" is involved in the current netcdf (and upcoming hdf5) transition(s). Its failed to build on mips64el (hardware issue on build machine?) but also on the kfreebsd, hurd, hppa archs: https://buildd.debian.org/status/package.php?p=ncl I've a fix for the kfreebsd, hurd FTBFS and also I think hppa (can't test). I've pushed it to git, but will hold off doing a release to unstable subject unless you think its ok, The netcdf package migrated to testing today, so the ncl package is no longer involved in ongoing transitions. Uploading to unstable should be okay. I uploaded netcdf4-python earlier today for example. Kind Regards, Bas
Bug#879637: mariadb-10.1: FTBFS on mips64el due to test failures
Source: mariadb-10.1 Version: 10.1.28-1 Severity: serious Justification: makes the package in question unusable or mostly so Control: affects -1 src:gdal Dear Maintainer, mariadb-10.1 (10.1.28-1) FTBFS on mips64el, and the missing binaries are blocking testing migration of mariadb-10.1 and its reverse dependencies. For the full build logs, see: https://buildd.debian.org/status/logs.php?arch=mips64el=mariadb-10.1=10.1.28-1 Please fix this ASAP or consider ignoring the test failure. Kind Regards, Bas
Bug#879544: transition: netcdf
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: block -1 by 878818 Control: forwarded -1 https://release.debian.org/transitions/html/auto-netcdf.html NetCDF 4.5.0 has been released and bumps the SOVERSION to 13 requiring a transition. The release candidates have been available in experimental for a while and the final release is there now. It built successfully on all release architectures, and also on hurd & kfreebsd after a fix to the symbols file. Only a single package failed to build, and not due to the changes in netcdf: ovito (2.9.0+dfsg1-2) FTBFS due to an unrelated issue: #878818 All other reverse dependencies rebuild successfully. Details of the rebuilds are included below. The automatically generated transition tracker is sufficient, the suggested ben file is included for completeness. Ben file: title = "netcdf"; is_affected = .depends ~ "libnetcdf11" | .depends ~ "libnetcdf13"; is_good = .depends ~ "libnetcdf13"; is_bad = .depends ~ "libnetcdf11"; Transition: netcdf libnetcdf11 (1:4.4.1.1-2) -> libnetcdf13 (1:4.5.0-1~exp1) The status of the most recent rebuilds is as follows. adios (1.12.0-4)OK cmor (3.2.7-2) OK dx (1:4.4.4-10) OK eccodes(2.5.0-2) OK exodusii (6.02.dfsg.1-8) OK ffmpeg (7:3.3.4-2) OK gdal (2.2.2+dfsg-2)OK grace (1:5.1.25-5) OK grads (3:2.1.1.b0-1)OK gri(2.12.26-1) OK grib-api (1.24.0-2)OK labplot(2.4.0-1) OK libminc(2.3.00-3.1) OK libpdl-netcdf-perl (4.20-5) OK nco(4.6.9-1) OK ncview (2.1.8+ds-1) OK netcdf-cxx (4.3.0+ds-4) OK netcdf-cxx-legacy (4.2-7) OK netcdf-fortran (4.4.4+ds-2) OK netcdf4-python (1.3.0-1) OK octave-netcdf (1.0.11-1)OK r-cran-ncdf4 (1.16-1) OK r-cran-rnetcdf (1.8-2-1) OK ruby-netcdf(0.7.2-1) OK v-sim (3.7.2-4) OK cdftools (3.0-2~exp1.1)OK etsf-io(1.0.4-1.1) OK ferret-vis (7.2-1) OK gmt(5.4.2+dfsg-1)OK gnudatalanguage(0.9.7-4) OK grass (7.2.2-1) OK magics++ (2.34.3-2)OK minc-tools (2.3.00+dfsg-1.1) OK ncl(6.4.0-4) OK oasis3 (3.mct+dfsg.121022-9) OK ovito (2.9.0+dfsg1-2) FTBFS (#878818) paraview (5.4.1+dfsg3-1) OK python-escript (5.0-4) OK vtk6 (6.3.0+dfsg1-10) OK cdo(1.9.1+dfsg.1-1) OK ifrit (4.1.2-5) OK metview(4.8.7-2) OK pyferret (7.2-1) OK Kind Regards, Bas
Bug#877863: RM: pgrouting [armel] -- ROM; Build dependency not available
Package: ftp.debian.org Severity: normal Please remove pgrouting on armel. The cgal build dependency is not available, and the missing binaries are blocking the postgis migration to testing. Kind Regards, Bas
Bug#876895: RM: nco [armhf] -- ROM; Missing build prevents testing migration
Package: ftp.debian.org Severity: normal Please remove nco from armhf, for over a week the build dependencies cannot be installed successfully and the missing build is preventing testing migration. Kind Regards, Bas
Bug#876562: gazebo: FTBFS after 'Built target gazebo_gui'
Source: gazebo Version: 7.8.1+dfsg-1 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, gazebo currently fails to build in unstable: cd /build/1st/gazebo-7.8.1+dfsg/obj-x86_64-linux-gnu/gazebo/gui && /usr/bin/cmake -E cmake_symlink_library libgazebo_gui.so.7.8.1 libgazebo_gui.so.7 libgazebo_gui.so make[3]: Leaving directory '/build/1st/gazebo-7.8.1+dfsg/obj-x86_64-linux-gnu' [ 88%] Built target gazebo_gui make[2]: Leaving directory '/build/1st/gazebo-7.8.1+dfsg/obj-x86_64-linux-gnu' Makefile:165: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/build/1st/gazebo-7.8.1+dfsg/obj-x86_64-linux-gnu' dh_auto_build: cd obj-x86_64-linux-gnu && make -j16 returned exit code 2 debian/rules:40: recipe for target 'build' failed make: *** [build] Error 2 The full build log is available at: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gazebo_7.8.1+dfsg-1.rbuild.log Kind Regards, Bas
Bug#876561: transition: gdal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition For the Debian GIS team I'd like to transition to GDAL 2.2.2. Like the previous transition to GDAL 2.2.1 (#866797), there is no SONAME bump, only the virtual ABI package changed to account for the C++ symbol changes. All reverse dependencies rebuilt successfully with GDAL 2.2.2 from experimental as summarized below, except gazebo. gazebo (7.8.1+dfsg-1) FTBFS for some unclear reason unrelated to gdal (it FTBFS with plain unstable too): [ 88%] Built target gazebo_gui make[2]: Leaving directory '/build/gazebo-7.8.1+dfsg/obj-x86_64-linux-gnu' Makefile:165: recipe for target 'all' failed libgdal-grass doesn't need a binNMU as the 2.2.2 version will be uploaded to unstable instead. liblas likewise doesn't need a binNMU, the version is experimental will be moved to unstable instead. A complication for the transition is the inability to build the gdal package on armhf, due to an issue with ca-certificates-java: Setting up ca-certificates-java (20170531+nmu1) ... Error: missing `server' JVM at `/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'. Please install or use the JRE or JDK that contains these missing components. But openjdk-8-jdk-headless cannot be installed because it depends on ca-certificates-java, see: https://buildd.debian.org/status/fetch.php?pkg=gdal=armhf=2.2.1%2Bdfsg-2%2Bb2=1505204615=0 Ben file: title = "gdal"; is_affected = .depends ~ "gdal-abi-2-2-1" | .depends ~ "gdal-abi-2-2-2"; is_good = .depends ~ "gdal-abi-2-2-2"; is_bad = .depends ~ "gdal-abi-2-2-1"; Kind Regards, Bas
Bug#876478: ben tracker --global-conf ignores settings
Package: ben Version: 0.7.4+b4 Severity: important Dear Maintainer, Since the upgrade to stretch my ben setup no longer works as before. The `ben tracker --global-conf /global.conf` commands don't use the cache file as configured in the global.conf file, and instead download the Sources & Packages files again (which were downloaded before using `ben download -c /global.conf`). The downloaded files also use the current working directory instead of the cache-dir configured in global.conf This makes it impossible to use multiple configurations for different transition trackers. Kind Regards, Bas -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ben depends on: ii bzip2 1.0.6-8.1 ii curl7.52.1-5 ii libben-ocaml [libben-ocaml-e1ii7] 0.7.4+b4 ii libc6 2.24-11+deb9u1 ii libjs-jquery3.1.1-2 ii libpcre32:8.39-3 ii libpq5 9.6.4-0+deb9u1 ii libtyxml-ocaml [libtyxml-ocaml-c63d2] 3.5.0-1 ii ocaml-base-nox [ocaml-base-nox-4.02.3] 4.02.3-9 Versions of packages ben recommends: ii dose-distcheck 5.0.1-8 ben suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /usr/share/ben/media/styles.css (from ben package)
Bug#876040: release.debian.org: Please age freexl (1.0.4-1), urgency was not set to high for security issues
Package: release.debian.org Severity: normal Please age freexl (1.0.4-1), it fixes two security issues, but the urgency was not set to high for the upload to unstable. Kind Regards, Bas
Bug#875811: postgresql-9.6-postgis-2.4-scripts: fails to upgrade from 'sid' - trying to overwrite /usr/share/postgresql/9.6/extension/address_standardizer.control
Control: tags -1 pending Thanks for reporting this issue. It has already been fixed in git by myon. The fix will be included in the next upload. Kind Regards, Bas
Bug#875690: Fixed in FreeXL 1.0.4
Control: tags -1 fixed-upstream Should be fixed in the new upstream release: https://groups.google.com/forum/m/#!topic/spatialite-users/Wpj62XSzcZY I'm not able to work on this until I return from VAC. Kind Regards, Bas
Bug#873711: ben: HTML trackers don't match release.debian.org due to typo in CSS
Source: ben Version: 0.7.4 Severity: normal Tags: patch Dear Maintainer, The HTML pages generated by ben in jessie & stretch doesn't match what's used on release.debian.org. The column layout is not applied because of a typo in the CSS which is not fixed in the package. The attached patch applies the typo fix making the HTML layout match that used on release.debian.org. Kind Regards, Bas >From 496b342c166b5a02e16e881a3b32d0d1df2a53db Mon Sep 17 00:00:00 2001 From: Bas Couwenberg <sebas...@xs4all.nl> Date: Wed, 30 Aug 2017 12:55:05 +0200 Subject: Fix column layout for transitions divs. --- media/styles.css | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/media/styles.css b/media/styles.css index 19f04c7..9f9eef7 100644 --- a/media/styles.css +++ b/media/styles.css @@ -1,4 +1,4 @@ -div.transition { +div.transitions { display: inline-block; vertical-align:text-top; margin: 2em; -- 2.11.0
Bug#873332: stretch-pu: package pyosmium/2.11.3-1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Upstream has released a new stable release of pyosmium fixing important bugs which I'd like to propose for inclusion in the next stable update. Kind Regards, Bas diff -Nru pyosmium-2.11.1/CHANGELOG.md pyosmium-2.11.3/CHANGELOG.md --- pyosmium-2.11.1/CHANGELOG.md2017-05-04 23:36:03.0 +0200 +++ pyosmium-2.11.3/CHANGELOG.md2017-08-20 11:18:52.0 +0200 @@ -12,6 +12,27 @@ ### Fixed +## [2.11.3] - 2017-08-20 + +### Added + +### Changed + +- updated to latest libosmium 2.11 bugfix release + +### Fixed + +- handler functions not called when using Reader instead of file + +## [2.11.2] - 2017-05-25 + +### Added + +### Changed + +### Fixed + +- handler functions not called when using replication service (#38) ## [2.11.1] - 2017-05-04 diff -Nru pyosmium-2.11.1/debian/changelog pyosmium-2.11.3/debian/changelog --- pyosmium-2.11.1/debian/changelog2017-05-05 09:51:21.0 +0200 +++ pyosmium-2.11.3/debian/changelog2017-08-26 15:10:04.0 +0200 @@ -1,3 +1,11 @@ +pyosmium (2.11.3-1) stretch; urgency=medium + + * New upstream bugfix release. +- handler functions not called when using replication service (#38) +- handler functions not called when using Reader instead of file + + -- Bas Couwenberg <sebas...@debian.org> Sat, 26 Aug 2017 15:10:04 +0200 + pyosmium (2.11.1-1) unstable; urgency=medium * New upstream bugfix release. diff -Nru pyosmium-2.11.1/lib/generic_handler.hpp pyosmium-2.11.3/lib/generic_handler.hpp --- pyosmium-2.11.1/lib/generic_handler.hpp 2017-05-04 23:36:03.0 +0200 +++ pyosmium-2.11.3/lib/generic_handler.hpp 2017-08-20 11:18:52.0 +0200 @@ -25,6 +25,7 @@ }; public: +virtual void apply_start() {}; // handler functions virtual void node(const osmium::Node&) const = 0; virtual void way(const osmium::Way&) const = 0; @@ -163,14 +164,7 @@ apply_object(osmium::io::File(cbuf, len, cfmt), locations, idx); } -private: -void apply_object(osmium::io::File file, bool locations, const std::string ) -{ -osmium::osm_entity_bits::type entities = osmium::osm_entity_bits::nothing; -BaseHandler::pre_handler handler = locations? -BaseHandler::location_handler -:BaseHandler::no_handler; - +void apply_start() override { m_callbacks = osmium::osm_entity_bits::nothing; if (hasfunc("node")) m_callbacks |= osmium::osm_entity_bits::node; @@ -182,6 +176,18 @@ m_callbacks |= osmium::osm_entity_bits::area; if (hasfunc("changeset")) m_callbacks |= osmium::osm_entity_bits::changeset; +} + + +private: +void apply_object(osmium::io::File file, bool locations, const std::string ) +{ +osmium::osm_entity_bits::type entities = osmium::osm_entity_bits::nothing; +BaseHandler::pre_handler handler = locations? +BaseHandler::location_handler +:BaseHandler::no_handler; + +apply_start(); if (m_callbacks & osmium::osm_entity_bits::area) { @@ -202,6 +208,7 @@ apply(file, entities, handler, idx); } + bool hasfunc(char const *name) { reference_existing_object::apply<SimpleHandlerWrap*>::type converter; PyObject* obj = converter( this ); diff -Nru pyosmium-2.11.1/lib/merged_input.hpp pyosmium-2.11.3/lib/merged_input.hpp --- pyosmium-2.11.1/lib/merged_input.hpp2017-05-04 23:36:03.0 +0200 +++ pyosmium-2.11.3/lib/merged_input.hpp2017-08-20 11:18:52.0 +0200 @@ -16,6 +16,7 @@ class MergeInputReader { public: void apply(BaseHandler& handler, bool simplify = true) { +handler.apply_start(); if (simplify) { objects.sort(osmium::object_order_type_id_reverse_version()); osmium::item_type prev_type = osmium::item_type::undefined; diff -Nru pyosmium-2.11.1/lib/osmium.cc pyosmium-2.11.3/lib/osmium.cc --- pyosmium-2.11.1/lib/osmium.cc 2017-05-04 23:36:03.0 +0200 +++ pyosmium-2.11.3/lib/osmium.cc 2017-08-20 11:18:52.0 +0200 @@ -13,11 +13,17 @@ osmium::apply(rd, h); } +template <> +void apply_reader_simple(osmium::io::Reader , BaseHandler ) { +h.apply_start(); +osmium::apply(rd, h); +} template void apply_reader_simple_with_location(osmium::io::Reader , osmium::handler::NodeLocationsForWays , BaseHandler ) { +h.apply_start(); osmium::apply(rd, l, h); } diff -Nru pyosmium-2.11.1/osmium/version.py pyosmium-2.11.3/osmium/version.py --- pyosmium-2.11.1/osmium/version.py 2017-05-04 23:36:03.0 +0200 ++
Bug#873330: stretch-pu: package libosmium/2.11.4-1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Upstream has releases a new stable release of libosmium fixing important bugs which I'd like to propose for inclusion in the next stable update. Kind Regards, Bas diff -Nru libosmium-2.11.3/CHANGELOG.md libosmium-2.11.4/CHANGELOG.md --- libosmium-2.11.3/CHANGELOG.md 2017-05-03 14:01:48.0 +0200 +++ libosmium-2.11.4/CHANGELOG.md 2017-08-15 15:41:10.0 +0200 @@ -8,6 +8,14 @@ ### Fixed +## [2.11.4] - 2017-08-15 + +### Fixed + +- Output coordinate with value of -2^31 correctly. +- Buffers larger than 2^32 bytes do now work. + + ## [2.11.3] - 2017-05-03 ### Fixed diff -Nru libosmium-2.11.3/CMakeLists.txt libosmium-2.11.4/CMakeLists.txt --- libosmium-2.11.3/CMakeLists.txt 2017-05-03 14:01:48.0 +0200 +++ libosmium-2.11.4/CMakeLists.txt 2017-08-15 15:41:10.0 +0200 @@ -25,7 +25,7 @@ set(LIBOSMIUM_VERSION_MAJOR 2) set(LIBOSMIUM_VERSION_MINOR 11) -set(LIBOSMIUM_VERSION_PATCH 3) +set(LIBOSMIUM_VERSION_PATCH 4) set(LIBOSMIUM_VERSION "${LIBOSMIUM_VERSION_MAJOR}.${LIBOSMIUM_VERSION_MINOR}.${LIBOSMIUM_VERSION_PATCH}") diff -Nru libosmium-2.11.3/debian/changelog libosmium-2.11.4/debian/changelog --- libosmium-2.11.3/debian/changelog 2017-05-03 18:44:44.0 +0200 +++ libosmium-2.11.4/debian/changelog 2017-08-26 15:05:22.0 +0200 @@ -1,3 +1,12 @@ +libosmium (2.11.4-1) stretch; urgency=medium + + * New upstream bugfix release. +- Output coordinate with value of -2^31 correctly. +- Buffers larger than 2^32 bytes do now work. + * Update branch in gbp.conf & Vcs-Git URL. + + -- Bas Couwenberg <sebas...@debian.org> Sat, 26 Aug 2017 15:05:22 +0200 + libosmium (2.11.3-1) unstable; urgency=medium * New upstream bugfix release. diff -Nru libosmium-2.11.3/debian/control libosmium-2.11.4/debian/control --- libosmium-2.11.3/debian/control 2017-05-03 18:37:13.0 +0200 +++ libosmium-2.11.4/debian/control 2017-08-26 15:03:43.0 +0200 @@ -19,7 +19,7 @@ zlib1g-dev Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/libosmium.git/ -Vcs-Git: https://anonscm.debian.org/git/pkg-grass/libosmium.git +Vcs-Git: https://anonscm.debian.org/git/pkg-grass/libosmium.git -b stretch Homepage: http://osmcode.org/libosmium/ Package: libosmium2-dev diff -Nru libosmium-2.11.3/debian/gbp.conf libosmium-2.11.4/debian/gbp.conf --- libosmium-2.11.3/debian/gbp.conf2017-05-03 18:37:13.0 +0200 +++ libosmium-2.11.4/debian/gbp.conf2017-08-26 15:03:36.0 +0200 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru libosmium-2.11.3/include/osmium/memory/item.hpp libosmium-2.11.4/include/osmium/memory/item.hpp --- libosmium-2.11.3/include/osmium/memory/item.hpp 2017-05-03 14:01:48.0 +0200 +++ libosmium-2.11.4/include/osmium/memory/item.hpp 2017-08-15 15:41:10.0 +0200 @@ -62,7 +62,8 @@ constexpr const item_size_type align_bytes = 8; inline constexpr std::size_t padded_length(std::size_t length) noexcept { -return (length + align_bytes - 1) & ~(align_bytes - 1); +return (length + static_cast(align_bytes) - 1) & + ~(static_cast(align_bytes) - 1); } /** diff -Nru libosmium-2.11.3/include/osmium/osm/location.hpp libosmium-2.11.4/include/osmium/osm/location.hpp --- libosmium-2.11.3/include/osmium/osm/location.hpp2017-05-03 14:01:48.0 +0200 +++ libosmium-2.11.4/include/osmium/osm/location.hpp2017-08-15 15:41:10.0 +0200 @@ -33,6 +33,7 @@ */ +#include #include #include #include @@ -198,6 +199,12 @@ // Convert integer as used by location for coordinates into a string. template inline T append_location_coordinate_to_string(T iterator, int32_t value) { +// need to special-case this, because later `value = -value` would overflow. +if (value == std::numeric_limits::min()) { +static const char minresult[] = "-214.7483648"; +return std::copy_n(minresult, sizeof(minresult) - 1, iterator); +} + // handle negative values if (value < 0) { *iterator++ = '-'; diff -Nru libosmium-2.11.3/include/osmium/version.hpp libosmium-2.11.4/include/osmium/version.hpp --- libosmium-2.11.3/include/osmium/version.hpp 2017-05-03 14:01:48.0 +0200 +++ libosmium-2.11.4/include/osmium/version.hpp 2017-08-15 15:41:10.0 +0200 @@ -35,8 +35,8 @@ #define LIBOSMIUM
Bug#871397: RM: doris -- ROM; RC buggy, dead upstream
Package: ftp.debian.org Severity: normal Please remove doris from the archive, it is RC buggy and dead upstream. Kind Regards, Bas
Bug#870812: RM: gosmore -- ROM; RC buggy, dead upstream
Package: ftp.debian.org Severity: normal Please remove gosmore from the archive, it is RC buggy and will remain so because it is also dead upstream. Kind Regards, Bas
Bug#870600: rabbitmq-server OCF resource agent does not support rabbitctl exit status 69 for nodedown
Source: rabbitmq-server Version: 3.6.6-1 Severity: important Dear Maintainer, The rabbitmq-server OCF resource agent stopped working correctly in stretch, it is unable to determine that the node is down due to rabbitctl changing the exit status. In jessie the `/usr/sbin/rabbitmqctl -n rabbit@localhost status` command returned exit status 2, in stretch it changes to exit status 69. This causes the OCF resource agent to fail with: ERROR: Unexpected return from rabbitmqctl -n rabbit@localhost status: 69 The attached patch updates the resource agent to handle exit status 60 the same as exit status 2, fixing the issue. Please consider applying the patch and resolve this issue with a proposed-update for stretch. Kind Regards, Bas -- System Information: Debian Release: 9.1 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff --git a/debian/changelog b/debian/changelog index ce6823c..e8acc29 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +rabbitmq-server (3.6.6-1+deb9u1) stretch; urgency=medium + + * Non-maintainer upload. + * Add patch to fix rabbitmq-server OCF resource agent. +`rabbitmqctl status` now uses exit status 69 when the node is down, +instead of 2 as before, both exit status 2 and 69 are now handled by +the OCF resource agent for the same case. + + -- Bas Couwenberg <sebas...@debian.org> Thu, 03 Aug 2017 10:05:11 +0200 + rabbitmq-server (3.6.6-1) unstable; urgency=medium [ Ondřej Nový ] diff --git a/debian/patches/ocf.patch b/debian/patches/ocf.patch new file mode 100644 index 000..f9b960e --- /dev/null +++ b/debian/patches/ocf.patch @@ -0,0 +1,14 @@ +Description: Also handle rabbitctl exit status 69 for nodedown. +Author: Bas Couwenberg <sebas...@debian.org> + +--- a/scripts/rabbitmq-server.ocf b/scripts/rabbitmq-server.ocf +@@ -256,7 +256,7 @@ rabbitmqctl_action() { + ocf_log debug "RabbitMQ server is running normally" + return $OCF_SUCCESS + ;; +-2) ++2|69) + ocf_log debug "RabbitMQ server is not running" + return $OCF_NOT_RUNNING + ;; diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..16260eb --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +ocf.patch
Bug#869888: otb FTBFS with cmake 3.9.0
Control: tags -1 pending Hi Adrian, Thanks for reporting this issue. A patch has been added in git and a new upload to unstable will follow shortly. Kind Regards, Bas
Bug#869679: [Pkg-nagios-devel] Bug#869679: icinga: /var/log/icinga/* not readable by www-data, preventing history viewing from web frontend
Control: tags -1 moreinfo Hi Christian, On 2017-07-25 17:09, root wrote: in the version of icinga in stretch, the icinca log files are created with permissions 600, user and group nagios:nagios or nagios:adm. This prevents the web frontend (which is run as www-data in case of apache2) from accessing it and displaying history for a service: "Log file "/var/log/icinga/icinga.log" invalid! No timestamp found within first 16 bytes! I have found not way of fixing this via additional group memberships. This was not the case in nagios as distributed with the previous release. I have several stretch systems (upgraded from jessie and earlier) running icinga, and they don't have this issue. On all those systems /var/log/icinga is owned by nagios:nagios with mode 644. In a clean stretch chroot the log file is indeed created with mod 600, but you should be able to change this with: chmod 644 /var/log/icinga.log This should be sufficient to let the webserver access the file. The logrotation performed by Icinga reuses the ownership and permissions of the existing logfile, so you should only need to do this once. Does this resolve your issue? Kind Regards, Bas
Bug#868850: gdal-bin: Almost all gdal commands (gdalinfo, ogr2ogr) terminate with "double free or corruption"
On 2017-07-19 11:22, Thomas Rohwer wrote: Correct, and tomorrow the new revision that has been built with libdap 3.19.0-1 will migrate to testing: https://qa.debian.org/excuses.php?package=gdal Ok, thanks for the information. I was not aware, that this is already fixed in unstable. You can thank the libdap maintainer for not coordinating his transitions. libdap 3.19.0-1 was accepted from the NEW queue during the gdal transition causing this issue. If libdap had been uploaded to experimental first and the transition coordinated, this issue would not have occurred. Kind Regards, Bas
Bug#868850: gdal-bin: Almost all gdal commands (gdalinfo, ogr2ogr) terminate with "double free or corruption"
Control: tags -1 pending On 2017-07-19 10:56, Thomas Rohwer wrote: It may be related to gdal linking to two versions of libdap (see above trace): Correct, and tomorrow the new revision that has been built with libdap 3.19.0-1 will migrate to testing: https://qa.debian.org/excuses.php?package=gdal Kind Regards, Bas
Bug#868759: gdal-bin: Segmentation fault with SQLite driver.
Control: tags -1 moreinfo Hi Andy, On 2017-07-18 12:13, Andy Wood wrote: Segmentation fault which probably appeared after gdal 2.2.1+dfsg-1 went into buster: $ ogr2ogr -t_srs EPSG:3857 -f "SQLite" -dsco SPATIALITE=YES \ test.sqlite test.xml Segmentation fault Can you provide a gdb stracktrace with the gdal-bin-dbgsym & libgdal20-dbgsym packages installed? Kind Regards, Bas
Bug#866797: Uncoordinated libdap transition
Alastair, Why do you keep uploading new upstream releases which trigger transition due to bumped SONAMEs to unstable, and thereby triggering uncoordinated transitions? When SONAMEs are bumped and library packages renamed the package should be uploaded to experimental and the transition coordinated with the Release Team. Please read the documentation and stick to that process: https://wiki.debian.org/Teams/ReleaseTeam/Transitions I'm very disappointed that you still haven't learned to coordinate transition with the Release Team, especially since your uncoordinated libdap transition conflicts with the ongoing gdal-2.2.1 transition. You need to contact the Release Team by filing the transition bugreport for libdap to coordinate the transition. Kind Regards, Bas
Bug#868130: stretch-pu: package geolinks/0.2.0-1+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu The incorrect dependencies for the python3-geolinks binary package reported in #867405 also affect the package in stretch. geolinks (0.2.0-2) has fixed the issue in testing & unstable, and the same fix is included in this proposed update for stretch. Kind Regards, Bas diff -Nru geolinks-0.2.0/debian/changelog geolinks-0.2.0/debian/changelog --- geolinks-0.2.0/debian/changelog 2015-09-14 22:19:29.0 +0200 +++ geolinks-0.2.0/debian/changelog 2017-07-12 11:28:48.0 +0200 @@ -1,3 +1,12 @@ +geolinks (0.2.0-1+deb9u1) stretch; urgency=medium + + * Team upload. + * Update branch in gbp.conf & Vcs-Git URL. + * Fix dependencies for Python 3 package. +(closes: #867405) + + -- Bas Couwenberg <sebas...@debian.org> Wed, 12 Jul 2017 11:28:48 +0200 + geolinks (0.2.0-1) unstable; urgency=medium [ Johan Van de Wauw ] diff -Nru geolinks-0.2.0/debian/control geolinks-0.2.0/debian/control --- geolinks-0.2.0/debian/control 2015-09-14 22:19:05.0 +0200 +++ geolinks-0.2.0/debian/control 2017-07-12 11:28:45.0 +0200 @@ -12,7 +12,7 @@ python3-all, Standards-Version: 3.9.6 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/geolinks.git -Vcs-Git: git://anonscm.debian.org/pkg-grass/geolinks.git +Vcs-Git: git://anonscm.debian.org/pkg-grass/geolinks.git -b stretch Homepage: https://pypi.python.org/pypi/geolinks X-Python-Version: >= 2.5 @@ -29,7 +29,7 @@ Package: python3-geolinks Architecture: all -Depends: ${python:Depends}, +Depends: ${python3:Depends}, ${misc:Depends} Description: Python 3 Library for using geospatial links (catalogue interoperablity) This package is a utility library to work with geospatial links. diff -Nru geolinks-0.2.0/debian/gbp.conf geolinks-0.2.0/debian/gbp.conf --- geolinks-0.2.0/debian/gbp.conf 2015-06-04 22:06:37.0 +0200 +++ geolinks-0.2.0/debian/gbp.conf 2017-07-12 11:28:17.0 +0200 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig
Bug#866575: libapache2-mod-wsgi-py3: Impossible depends when built with more then one supported python3 version
Package: libapache2-mod-wsgi-py3 Version: 4.5.11-1 Followup-For: Bug #866575 Dear Maintainer, The attached patch fixes this issue, but there are several other issues with the package that should be fixed in the next upload too. Kind Regards, Bas >From 4534ad18aaff225f87e7b3a33ec4ab3806e0f48b Mon Sep 17 00:00:00 2001 From: Bas Couwenberg <sebas...@debian.org> Date: Sat, 8 Jul 2017 12:34:58 +0200 Subject: Fix min/max Python 3 version determination for multiple versions. (closes: #866575) --- debian/changelog | 8 debian/rules | 4 ++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index b398340..90e6bcc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +mod-wsgi (4.5.11-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix min/max Python 3 version determination for multiple versions. +(closes: #866575) + + -- Bas Couwenberg <sebas...@debian.org> Sat, 08 Jul 2017 12:33:46 +0200 + mod-wsgi (4.5.11-1) unstable; urgency=medium * [8d515a5] Merge tag 'upstream/4.5.11' diff --git a/debian/rules b/debian/rules index d39b22d..d536d9e 100755 --- a/debian/rules +++ b/debian/rules @@ -9,8 +9,8 @@ PYMIN=$(shell echo $(PYVERS) | awk '{print $$1}') PYMAX=$(shell echo $(PYVERS) | LANG=C awk '{print $$NF+0.1}') PY3VERS=$(shell py3versions -vs) PY3DEFAULT=$(shell py3versions -dv) -PY3MIN=$(shell echo $(PY3VERS) | awk '{print $$1}') -PY3MAX=$(shell echo $(PY3VERS) | LANG=C awk '{print $$NF+0.1}') +PY3MIN=$(shell for VERSION in $(PY3VERS); do echo $$VERSION; done | sort | head -1) +PY3MAX=$(shell for VERSION in $(PY3VERS); do echo $$VERSION; done | sort | tail -1 | LANG=C awk '{print $$NF+0.1}') pkgdir = $(CURDIR)/debian/$(PACKAGE)$(if $(patsubst 3.%,,$(1)),,-py3) %: -- 2.11.0
Bug#867567: stretch-pu: package nagios-nrpe/3.0.1-3+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu To fix the incompatibility between NRPE 2.x and 3.x releases when SSL support is enabled, I'd like to propose the following update. There was a bug in the patch for reproducible builds which disabled the DH support causing SSL support without certificates configured not to work. This issue is discussed in the following upstream issue: https://github.com/NagiosEnterprises/nrpe/issues/113 Thanks to Johan Carlquist for reporting the fix. Because previous versions of NRPE in Debian and the package as built by other distributions uses SSL by default, the SSL support has been enabled by default in the Debian package again too. With these proposed changes users upgrading from jessie to stretch don't have to reconfigure their monitoring environment to disable SSL. Users that have already reconfigured their monitoring environment to disable SSL for NRPE can either leave it as-is, or re-enable the SSL support for NRPE too. Kind Regards, Bas diff -Nru nagios-nrpe-3.0.1/debian/changelog nagios-nrpe-3.0.1/debian/changelog --- nagios-nrpe-3.0.1/debian/changelog 2016-12-24 10:24:09.0 +0100 +++ nagios-nrpe-3.0.1/debian/changelog 2017-07-07 14:15:25.0 +0200 @@ -1,3 +1,13 @@ +nagios-nrpe (3.0.1-3+deb9u1) stretch; urgency=medium + + * Update branch in gbp.conf & Vcs-Git URL. + * Fix 11_reproducible_dh.h.patch to not leave USE_SSL_DH undefined. +Thanks to Johan Carlquist for pointing out this issue. + * Re-enable SSL support by default. +Compatibility with older versions has been fixed. + + -- Bas Couwenberg <sebas...@debian.org> Fri, 07 Jul 2017 14:15:25 +0200 + nagios-nrpe (3.0.1-3) unstable; urgency=medium * Add reload command to systemd service file. diff -Nru nagios-nrpe-3.0.1/debian/check_nrpe.cfg nagios-nrpe-3.0.1/debian/check_nrpe.cfg --- nagios-nrpe-3.0.1/debian/check_nrpe.cfg 2016-12-23 23:23:21.0 +0100 +++ nagios-nrpe-3.0.1/debian/check_nrpe.cfg 2017-07-07 14:13:19.0 +0200 @@ -1,11 +1,11 @@ -# this command runs a program $ARG1$ with no arguments and disables SSL support +# this command runs a program $ARG1$ with no arguments and enables SSL support define command { command_namecheck_nrpe - command_line/usr/lib/nagios/plugins/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ -n + command_line/usr/lib/nagios/plugins/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ } -# this command runs a program $ARG1$ with no arguments and enables SSL support +# this command runs a program $ARG1$ with no arguments and disables SSL support define command { - command_namecheck_nrpe_ssl - command_line/usr/lib/nagios/plugins/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ + command_namecheck_nrpe_nossl + command_line/usr/lib/nagios/plugins/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ -n } diff -Nru nagios-nrpe-3.0.1/debian/control nagios-nrpe-3.0.1/debian/control --- nagios-nrpe-3.0.1/debian/control2016-12-23 23:23:21.0 +0100 +++ nagios-nrpe-3.0.1/debian/control2017-07-07 14:13:11.0 +0200 @@ -11,7 +11,7 @@ openssl Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-nagios/pkg-nrpe.git -Vcs-Git: https://anonscm.debian.org/git/pkg-nagios/pkg-nrpe.git +Vcs-Git: https://anonscm.debian.org/git/pkg-nagios/pkg-nrpe.git -b stretch Homepage: https://github.com/NagiosEnterprises/nrpe Package: nagios-nrpe-server diff -Nru nagios-nrpe-3.0.1/debian/gbp.conf nagios-nrpe-3.0.1/debian/gbp.conf --- nagios-nrpe-3.0.1/debian/gbp.conf 2016-12-23 23:23:21.0 +0100 +++ nagios-nrpe-3.0.1/debian/gbp.conf 2017-07-07 14:13:11.0 +0200 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru nagios-nrpe-3.0.1/debian/nagios-nrpe-server.default nagios-nrpe-3.0.1/debian/nagios-nrpe-server.default --- nagios-nrpe-3.0.1/debian/nagios-nrpe-server.default 2016-12-23 23:23:21.0 +0100 +++ nagios-nrpe-3.0.1/debian/nagios-nrpe-server.default 2017-07-07 14:13:19.0 +0200 @@ -5,9 +5,7 @@ # nrpe daemon. # # The -n option disables SSL support. -# Don't remove this option before configuring SSL in /etc/nagios/nrpe.cfg! -# See /usr/share/doc/nagios-nrpe-server/README.SSL.md.gz for instructions. -NRPE_OPTS="-n" +#NRPE_OPTS="-n" # NICENESS is if you want to run the server at a different nice() priority. # (only used by the init script) diff -Nru nagios-nrpe-3.0.1/debian/NEWS nagios-nrpe-3.0.1/debian/NEWS --- nagios-nrpe-3.0.1/debian/NEWS 2016-12-23 23:23:21.0 +0100 +++ nagios-nrpe-3.0.1/debian/NEWS
Bug#867405: python3-geolinks: missing python3 dependency
Control: tags -1 pending Hi Adrian, On 2017-07-06 15:43, Adrian Bunk wrote: Due to a cut'n'paste error the python3 dependency is missing. Thanks for reporting this issue, it has been fixed in git and a new upload to unstable will follow shortly. Kind Regards, Bas
Bug#866797: transition: gdal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition For the Debian GIS team I'd like to transition to GDAL 2.2.1. Like the previous transition to GDAL 2.1.2 (#842288), there is no SONAME bump, only the virtual ABI package changed to account for the C++ symbol changes. All reverse dependencies rebuilt successfully with GDAL 2.2.1 from experimental as summarized below, except rasterio & vtk6. rasterio cannot be built yet because python-numpy hasn't been built with Python 3.6 yet as part of the python3-defaults transition (#866335). rasterio built successfully with Python 3.5 and GDAL 2.2.1~rc1, so this will likely be resolved with the rebuild of python-numpy. vtk6 FTBFS due to missing build dependencies: texlive-math-extra. The recent texlive-extra source packages no longer build with binary package. Dropping the build dependency was sufficient to build vtk6 successfully with GDAL 2.2.1. The patch has been submitted in #866723. A new revision of qgis has been uploaded to unstable which includes the changes from 2.14.16 (currently in NEW) for GDAL 2.2 support, which allow the package the build successfully with GDAL 2.2.1 too. libgdal-grass doesn't need a binNMU as the 2.2.1 version will be uploaded to unstable instead. liblas likewise doesn't need a binNMU, the version is experimental will be moved to unstable instead. Please also binNMU mapnik in experimental as part of the transition. Ben file: title = "gdal"; is_affected = .depends ~ "gdal-abi-2-1-2" | .depends ~ "gdal-abi-2-2-1"; is_good = .depends ~ "gdal-abi-2-2-1"; is_bad = .depends ~ "gdal-abi-2-1-2"; Transition: gdal libgdal20 (2.1.2+dfsg-5) -> libgdal20 (2.2.1+dfsg-1~exp1) gdal-abi-2-1-2 -> gdal-abi-2-2-1 The status of the most recent rebuilds is as follows. dans-gdal-scripts (0.24-1) OK fiona (1.7.8-1) OK gazebo (7.5.0+dfsg-1) OK gmt(5.4.2+dfsg-1) SKIP (no C++) imposm (2.6.0+ds-4) SKIP (no C++) libcitygml (2.0.4-1) OK liblas (1.8.1-3 / 1.8.1-4~exp5) OK / OK libosmium (2.12.2-2) SKIP (no C++) mapcache (1.6.0-2) SKIP (no C++) mapnik (3.0.12+ds-3 / 3.0.15+ds-1~exp1) OK / OK mapproxy (1.10.2-2) SKIP (no C++) mapserver (7.0.6-2) SKIP (no C++) merkaartor (0.18.3+ds-2) OK mysql-workbench(6.3.8+dfsg-1) OK ncl(6.3.0-13) SKIP (no C++) node-srs (0.4.8+dfsg-3) OK octave-mapping (1.2.1-1) OK openscenegraph (3.2.3+dfsg1-2)OK pdal (1.5.0-3) OK pgsql-ogr-fdw (1.0.2-2) SKIP (no C++) postgis(2.3.2+dfsg-2) SKIP (no C++) pprepair (0.0~20160321-87ffae5-1) OK prepair(0.7-6)OK python-django (1:1.11.2-2) SKIP (no C++) qlandkartegt (1.8.1+ds-7) OK qmapshack (1.8.1-1) OK rasterio (0.36.0-2) FTBFS saga (2.3.1+dfsg-3) OK sumo (0.28.0+dfsg1-1) OK thuban (1.2.2-12) OK vtk6 (6.3.0+dfsg1-5)OK (#866723) xastir (2.0.8-2) SKIP (no C++) grass (7.2.1-2) SKIP (no C++) openscenegraph-3.4 (3.4.0+dfsg1-4)OK osmcoastline (2.1.4-2) OK otb(6.0.0+dfsg-2) OK pktools(2.6.7.1+ds-1) OK pyosmium (2.12.3-2) SKIP (no C++) libgdal-grass (2.1.2-6 / 2.2.1-1~exp1) FTBFS / OK osgearth (2.8.0+dfsg-1) OK qgis (2.14.15+dfsg-2 / 2.14.16+dfsg-1~exp1) OK [+] / OK Kind Regards, Bas
Bug#866759: stretch-pu: package protozero/1.5.1-1+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu protozero 1.5.1 in stretch contains a serious bug that was fixed in 1.5.2. The fix has been cherry-picked and I'd like to upload this proposed-update. >From the changelog and patch description: " This fixes a rather embarrassing bug in the equality operator of the data_view class. The equality operator is actually never used in the protozero code itself, but users of protozero might use it. This is a serious bug that could lead to buffer overrun type problems. " The issue was pointed out by the upstream author in: https://lists.debian.org/debian-gis/2017/07/msg0.html Kind Regards, Bas diff -Nru protozero-1.5.1/debian/changelog protozero-1.5.1/debian/changelog --- protozero-1.5.1/debian/changelog2017-01-14 11:19:51.0 +0100 +++ protozero-1.5.1/debian/changelog2017-07-01 15:59:15.0 +0200 @@ -1,3 +1,14 @@ +protozero (1.5.1-1+deb9u1) stretch; urgency=medium + + * Update branch in gbp.conf & Vcs-Git URL. + * Include upstream patch to fix data_view equality operator. +This fixes a rather embarrassing bug in the equality operator of the +data_view class. The equality operator is actually never used in the +protozero code itself, but users of protozero might use it. This is a +serious bug that could lead to buffer overrun type problems. + + -- Bas Couwenberg <sebas...@debian.org> Sat, 01 Jul 2017 15:59:15 +0200 + protozero (1.5.1-1) unstable; urgency=medium * New upstream release. diff -Nru protozero-1.5.1/debian/control protozero-1.5.1/debian/control --- protozero-1.5.1/debian/control 2017-01-12 15:17:23.0 +0100 +++ protozero-1.5.1/debian/control 2017-07-01 15:59:12.0 +0200 @@ -11,7 +11,7 @@ pkg-config Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/protozero.git/ -Vcs-Git: https://anonscm.debian.org/git/pkg-grass/protozero.git +Vcs-Git: https://anonscm.debian.org/git/pkg-grass/protozero.git -b stretch Homepage: https://github.com/mapbox/protozero Package: libprotozero-dev diff -Nru protozero-1.5.1/debian/gbp.conf protozero-1.5.1/debian/gbp.conf --- protozero-1.5.1/debian/gbp.conf 2017-01-12 15:17:23.0 +0100 +++ protozero-1.5.1/debian/gbp.conf 2017-07-01 15:59:12.0 +0200 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru protozero-1.5.1/debian/patches/0001-Bugfix-in-data_view-equality-operator.patch protozero-1.5.1/debian/patches/0001-Bugfix-in-data_view-equality-operator.patch --- protozero-1.5.1/debian/patches/0001-Bugfix-in-data_view-equality-operator.patch 1970-01-01 01:00:00.0 +0100 +++ protozero-1.5.1/debian/patches/0001-Bugfix-in-data_view-equality-operator.patch 2017-07-01 15:59:15.0 +0200 @@ -0,0 +1,63 @@ +Description: Bugfix in data_view equality operator. + This fixes a rather embarrassing bug in the equality operator of the + data_view class. The equality operator is actually never used in the + protozero code itself, but users of protozero might use it. This is a + serious bug that could lead to buffer overrun type problems. +Author: Jochen Topf <joc...@topf.org> +Origin: https://github.com/mapbox/protozero/commit/3d998ed0864f0db1d876d72a2658e5bdff9a0474 + +--- a/include/protozero/types.hpp b/include/protozero/types.hpp +@@ -16,6 +16,7 @@ documentation. + * @brief Contains the declaration of low-level types used in the pbf format. + */ + ++#include + #include + #include + #include +@@ -178,7 +179,7 @@ inline void swap(data_view& lhs, data_vi + * @param rhs Second object. + */ + inline bool operator==(const data_view& lhs, const data_view& rhs) noexcept { +-return lhs.size() == rhs.size() && !std::strcmp(lhs.data(), rhs.data()); ++return lhs.size() == rhs.size() && std::equal(lhs.data(), lhs.data() + lhs.size(), rhs.data()); + } + + /** +--- a/test/t/data_view/test_cases.cpp b/test/t/data_view/test_cases.cpp +@@ -64,20 +64,32 @@ TEST_CASE("comparing data_views") { + protozero::data_view v2{"bar"}; + protozero::data_view v3{"foox"}; + protozero::data_view v4{"foo"}; ++protozero::data_view v5{"fooo", 3}; ++protozero::data_view v6{"f\0o", 3}; ++protozero::data_view v7{"f\0obar", 3}; + + REQUIRE_FALSE(v1 == v2); + REQUIRE_FALSE(v1 == v3); + REQUIRE(v1 == v4); ++REQUIRE(v1 == v5); ++REQUIRE_FALSE(v1 == v6); ++REQUIRE_FALSE(v1 == v7); + REQUIRE_FALSE(v2 == v3); + REQUIRE_F
Bug#866723: vtk6: FTBFS due to texlive-math-extra no longer existing
Source: vtk6 Version: 6.3.0+dfsg1-5 Severity: serious Tags: patch Justification: makes the package in question unusable or mostly so Dear Maintainer, While preparing the transition to GDAL 2.2.1, your package failed to build due to unsatisfied build dependencies: Depends: texlive-math-extra which is a virtual package and is not provided by any available package The recent revisions of texlive-extra no longer provide this binary package. Dropping the build dependency was sufficient to build vtk6 successfully again. Please apply the attached patch to drop the dependency. Kind Regards, Bas --- vtk6-6.3.0+dfsg1/debian/control 2017-05-09 22:38:24.0 +0200 +++ vtk6-6.3.0+dfsg1/debian/control 2017-07-01 00:52:50.0 +0200 @@ -71,7 +71,6 @@ zlib1g-dev Build-Depends-Indep: doxygen-latex, texlive-binaries, - texlive-math-extra, graphviz, ghostscript, gnuplot-nox
Bug#866035: RM: osmcoastline [mips] -- ROM; Build dependency not available, blocks testing migration.
Package: ftp.debian.org Severity: normal Please remove osmcoastline from mips. The missing pandoc build dependency is blocking testing migration. Kind Regards, Bas
Bug#866034: RM: osmium-tool [mips] -- ROM; Build dependency not available, blocks testing migration.
Package: ftp.debian.org Severity: normal Please remove osmium-tool from mips. The missing pandoc build dependency is blocking testing migration. Kind Regards, Bas
Bug#866036: RM: osgearth [armel] -- ROM; Build dependency not available, blocks testing migration.
Package: ftp.debian.org Severity: normal Please remove osgearth from armel. The missing openscenegraph-3.4 build dependency is blocking testing migration. Kind Regards, Bas
Bug#865212: stretch-pu: package qgis/2.14.11+dfsg-3+deb9u1
Control: tags -1 - moreinfo On 2017-06-26 12:38, Cyril Brulebois wrote: Control: tag -1 - confirmed + moreinfo Cyril Brulebois(2017-06-26): Control: tag -1 confirmed … Looks good to me, feel free to upload. On second thought, the situation with openscenegraph [1] is going to lead to version constraint violation on point release day AFAIUI, if we accept this update in stretch. The osgearth packages in stretch depends on openscenegraph, the osgearth packages in buster/unstable depend on openscenegraph-3.4. The recent qgis upload to experimental (currently in NEW) disabled the osgearth & openscenegraph build dependencies because osgearth 2.8 with Qt5 is not (yet) supported by the QGIS globe plugin. In the meanwhile, I'm adjusting tags for this stretch-pu requests, so that other release team members aren't tempted to accept the package you uploaded, until we get a FTBFS (or BD-Uninstallable) fix. I see no reason to not accept the stretch-pu. The issue with qgis and osgearth 2.8 / openscenegraph-3.4 only affects unstable. Once the qgis 2.14.16 passes the NEW queue and is moved to unstable, that issue is resolved too. Kind Regards, Bas
Bug#865212: stretch-pu: package qgis/2.14.11+dfsg-3+deb9u1
Hi Mattia, On 2017-06-26 12:11, Mattia Rizzolo wrote: On Mon, Jun 26, 2017 at 07:32:35AM +0200, Sebastiaan Couwenberg wrote: Right, I did that initially but dch complained that it wasn't a recognised distribution and the DevRef also doesn't mention the use of codenames. Looks like bugs need to be filed for those two. No need. devref: https://bugs.debian.org/865367 (but I swear I remember seeing another one in the past) devscripts: right, just done in git. Thanks. Your devscripts change can probably close #789587. Kind Regards, Bas
Bug#865684: josm-plugins: Obsolete, causes issues with user installed plugins
Source: josm-plugins Version: 0.0.svn33112+ds-1 Severity: serious Tags: upstream Justification: makes the package unsuitable for release josm-plugins will be removed from Debian because it doesn't play well with user installed plugins. See: https://josm.openstreetmap.de/ticket/7483 RM bugs have been filed to remove the package from unstable & experimental: https://bugs.debian.org/864976 (unstable) https://bugs.debian.org/864975 (experimental) This RC bugs serves to get josm-plugins removed from testing to allow josm (>= 0.0.svn12275+dfsg-1) to migrate to testing.
Bug#865414: otb: fails to locate OpenCV 3.1 on non-x86
Control: forwarded -1 https://bugs.orfeo-toolbox.org/view.php?id=1419 Hi Mattia. On 2017-06-21 11:09, Mattia Rizzolo wrote: Trying to rebuild otb with OpenCV 3.1 (as found in experimental) fails on non-x86 due to cmake not locating it. I'm aware of this issue, and it has been fixed upstream more generically than with my patch. Although they still set the PATH_SUFFIXES, see: https://git.orfeo-toolbox.org/otb.git/commitdiff/f0541d761ee69f3300d0cdfd3c869140bec29c2d You very much need not tell cmake where to find libraries as long as they in a standard path, therefore the attached patch is quite enough to do the trick. Please remove the opencv-i386.patch and replace it with the attached one. Severity is important because we would like to proceed with the transition soonish, at which point this will be a blocker. OTB can only be built on i386 & amd64 because ITK4 is only available there, otb is not a blocker for the OpenCV transition because it builds everywhere where it built before. It doesn't look like insighttoolkit4 in experimental has included the changes from Ubuntu to support more than amd64 & i386, so we don't have to handle other architectures in OTB yet. I consider applying your patch as it's a more correct fix for the OpenCV issue, but it's not strictly required. Kind Regards, Bas
Bug#865403: [Pkg-nagios-devel] Bug#865403: monitoring-plugins-basic: check_ntp fails with stretch version of ntpd
On 2017-06-21 08:42, Christoph Biedl wrote: Bas Couwenberg wrote... On 2017-06-21 08:18, Christoph Biedl wrote: > LANG=C /usr/lib/nagios/plugins/check_ntp -4 -H $server -w 0.5 -c 0.8 check_ntp has been deprecated for many years now, you should be using check_ntp_time & check_ntp_peer instead. Does the issue also occur with those? Quick check, just replacing check_ntp with one these: * check_ntp_peer sends a NTPv2 package, no reply from the server. * check_ntp_time: Same as with check_ntp, works with a jessie ntpd, fails with a stretch ntpd. This is from a stretch system: $ /usr/lib/nagios/plugins/check_ntp_peer -H localhost -v 3 candidate peers available synchronization source found Getting offset, jitter and stratum for peer d53 parsing offset from peer d53: 0.000473 NTP OK: Offset 0.000473 secs|offset=0.000473s;60.00;120.00; Does your /etc/ntp.conf include the IP for your monitoring system to allow it to interrogate the ntp server more closely? Kind Regards, Bas
Bug#865403: [Pkg-nagios-devel] Bug#865403: monitoring-plugins-basic: check_ntp fails with stretch version of ntpd
On 2017-06-21 08:18, Christoph Biedl wrote: LANG=C /usr/lib/nagios/plugins/check_ntp -4 -H $server -w 0.5 -c 0.8 check_ntp has been deprecated for many years now, you should be using check_ntp_time & check_ntp_peer instead. Does the issue also occur with those? Kind Regards, Bas
Bug#865212: stretch-pu: package qgis/2.14.11+dfsg-3+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu As reported in #864695, the qgis packages cause the jessie to stretch upgrade to fail due to missing Breaks/Replaces for qgis_customwidgets.py that moved from python-qgis to python-qgis-common. The proposed update adds the versioned Breaks/Replaces to fix this issue. Kind Regards, Bas diff -Nru qgis-2.14.11+dfsg/debian/changelog qgis-2.14.11+dfsg/debian/changelog --- qgis-2.14.11+dfsg/debian/changelog 2017-03-21 12:49:51.0 +0100 +++ qgis-2.14.11+dfsg/debian/changelog 2017-06-19 20:51:12.0 +0200 @@ -1,3 +1,10 @@ +qgis (2.14.11+dfsg-3+deb9u1) stable; urgency=medium + + * Add Breaks/Replaces to python-qgis-common for qgis_customwidgets.py move. +(closes: #864695) + + -- Bas Couwenberg <sebas...@debian.org> Mon, 19 Jun 2017 20:51:12 +0200 + qgis (2.14.11+dfsg-3) unstable; urgency=medium * Add patch to fix GRASS 7.2 support in processing. diff -Nru qgis-2.14.11+dfsg/debian/control qgis-2.14.11+dfsg/debian/control --- qgis-2.14.11+dfsg/debian/control2017-03-21 12:49:51.0 +0100 +++ qgis-2.14.11+dfsg/debian/control2017-06-19 20:48:27.0 +0200 @@ -379,6 +379,8 @@ libqgis-customwidgets (>= ${source:Version}), ${python:Depends}, ${misc:Depends} +Breaks: python-qgis (<< 2.6.0) +Replaces: python-qgis (<< 2.6.0) Description: Python bindings to QGIS - architecture-independent files QGIS is a Geographic Information System (GIS) which manages, analyzes and display databases of geographic information.
Bug#864976: RM: josm-plugins -- ROM; Obsolete, causes issues with user installed plugins
Package: ftp.debian.org Severity: normal Please remove the josm-plugins package from the archive. It causes issues with user installed plugins. See: https://josm.openstreetmap.de/ticket/7483 Kind Regards, Bas
Bug#864975: RM: josm-plugins/experimental -- ROM; Obsolete, causes issues with user installed plugins
Package: ftp.debian.org Severity: normal Please remove the josm-plugins package from the archive. It causes issues with user installed plugins. See: https://josm.openstreetmap.de/ticket/7483 Kind Regards, Bas
Bug#864712: release-notes: Document possible QGIS upgrade failure
Package: release-notes Severity: normal Tags: patch Dear Maintainer, The jessie to stretch upgrade may fail due to a file conflict in the QGIS packages as reported in #864695. Because the fix cannot be included in stretch r0, the issue should be documented in the release notes. Please consider the attached patch. Kind Regards, Bas Index: en/issues.dbk === --- en/issues.dbk (revision 11636) +++ en/issues.dbk (working copy) @@ -905,6 +905,16 @@ do this transition. + +QGIS upgrade may fail + + The upgrade of the + python-qgis-common + package may fail due to a file conflict. To prevent the upgrade + failure remove the qgis packages before the upgrade and reinstall + them afterwards. + +
Bug#864571: ITP: mapbox-wagyu -- Wagyu Geometry Processing Library
Package: wnpp Severity: wishlist Owner: Bas Couwenberg <sebas...@debian.org> * Package name: mapbox-wagyu Version : 0.4.2 Upstream Author : Mapbox (https://github.com/mapbox/wagyu/issues) * URL : https://github.com/mapbox/wagyu * License : BSL-1.0 Programming Lang: C++ Description : Wagyu Geometry Processing Library Wagyu is a general library for the following basic geometric operations: - Union - Intersection - Difference - XOR The output geometry from each of these operations is guaranteed to be valid and simple as per the OGC. This package is required for the recent upstream releases of mapnik-vector-tile, and will be maintained in the Debian GIS team alongside mapnik-vector-tile.
Bug#864570: ITP: mapbox-geometry -- Generic C++ interfaces for geometry types, collections, and features
Package: wnpp Severity: wishlist Owner: Bas Couwenberg <sebas...@debian.org> * Package name: mapbox-geometry Version : 0.9.1 Upstream Author : Mapbox (https://github.com/mapbox/geometry.hpp/issues) * URL : https://github.com/mapbox/geometry.hpp * License : ISC Programming Lang: C++ Description : Generic C++ interfaces for geometry types, collections, and features geometry.hpp provides header-only, generic C++ interfaces for geometry types, geometry collections, and features. These types are designed to be easy to parse and serialize to GeoJSON. They should also be a robust and high performance container for data processing and conversion. This package is required for the recent upstream releases of mapnik-vector-tile, and will be maintained in the Debian GIS team alongside mapnik-vector-tile.
Bug#863797: Bug#863797: monitoring-plugins-basic: unable to use check_disk inside /var/tmp
On 2017-06-01 10:11, Emmanuel DECAEN wrote: Le 01/06/2017 à 07:21, Sebastiaan Couwenberg a écrit : notfound 863797 nagios-nrpe/3.0.1-3 thanks On 05/31/2017 11:05 PM, Emmanuel DECAEN wrote: And what does nagios-nrpe-server log on the system where the check_disk command you claim fails? May 31 22:46:45 server nrpe[31037]: Running command: /usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /var/tmp/mysql May 31 22:46:45 server nrpe[31037]: Command completed with return code 2 and output: DISK CRITICAL - /var/tmp/mysql is not accessible: No such file or directory May 31 22:46:45 server nrpe[31037]: Return Code: 2, Output: DISK CRITICAL - /var/tmp/mysql is not accessible: No such file or directory I think the problem is related to this "private" mount in nagios-nrpe-server (extract from /proc/xx/mountinfo): 121 113 8:5 /tmp/systemd-private-b35c254c031041979d3126e02a0c5c51-nagios-nrpe-server.service-MbLbk1/tmp /var/tmp rw,relatime shared:66 master:28 - ext4 /dev/sda5 rw,data=ordered The systemd configuration uses PrivateTmp=true, you can override it by adding a snippet: /etc/systemd/system/nagios-nrpe-server.service.d/local.conf With the following content: [Service] PrivateTmp=false See systemd.exec(5) for details about PrivateTmp. Thanks for the details. You have a non-standard setup, hence you need to customize the configuration. This is not a bug in nagios-nrpe, so I'm closing this issue. I disagree. Having a configuration using standard check_disk on any directory can't be considered as "a non-standard setup" (and especially when it was working correctly in Debian 8) Your check_disk command is not standard, on Debian systems /var/tmp/mysql is not a standard directory. /var/tmp and its subdirectories are either part of the / slice or a separate /var slice. Maybe, I'm missing something but there was no "PrivateTmp=true" in Debian 8 nagios-nrpe-server. From what I see, using "PrivateTmp=true" in nagios-nrpe-server is a *change in behavior from Debian 8 to Debian 9*. NRPE 2.15 in jessie didn't support systemd, NRPE 3.0 in stretch does. It is a change in behavior, but not a bug. I think, you can't indicate "not found" on this bug report as it can be easily reproduced, with a standard check_disk configuration. It's not a bug, so I removed the affected version. Don't you think the package upgrade should warn user about this change when migrating from Debian 8 to Debian 9 ? No. Standard setups don't have a separate /var/tmp/mysql partition, and will have /var/tmp as part of the root file system or separate /var. check_disk via NRPE works as expected on those systems. You have a non-standard setup where you explicitly want to monitor a non-standard subdirectory of /var/tmp and so you need to customize your monitoring to work with your non-standard setup. On one of my systems I have a separate /tmp and /var and there check_disk works just fine via NRPE 3.x with PrivateTmp=true. Kind Regards, Bas
Bug#863864: [Pkg-nagios-devel] Bug#863864: release-notes: Document that nagios is not in stretch and how to switch to icinga (if that is possible)
On 2017-06-01 08:51, Johannes Ranke wrote: I assume that switching to icinga is possible, but I am missing a hint in the release notes. Will icinga use nagios configuration files? Icinga 1.x uses the same configuration syntax as Nagios 3.x, so switching from Nagios 3 to Icinga 1 should be as simple as copying the configuration files to the appropriate directory (/etc/icinga/objects). Icinga 2.x uses a different configuration syntax and migratie to it from Nagios 3.x is more involved. Kind Regards, Bas
Bug#863797: [Pkg-nagios-devel] Bug#863797: Bug#863797: monitoring-plugins-basic: unable to use check_disk inside /var/tmp
On 2017-05-31 16:52, Jan Wagner wrote: Am 31.05.17 um 12:06 schrieb Emmanuel DECAEN: In nrpe, system wide /var/tmp is no more reachable $ grep "/var/tmp" /proc/11489/mountinfo 115 113 254:2 / /var/tmp/mysql rw,noatime,nodiratime shared:65 master:32- xfs /dev/mapper/v1-tmp rw,attr2,inode64,noquota 121 113 8:5 /tmp/systemd-private-b35c254c031041979d3126e02a0c5c51-nagios-nrpe-server.service-7xjqpw/tmp /var/tmp rw,relatime shared:66 master:28 - ext4 /dev/sda5 rw,data=ordered As you traced the problem yourself to nrpe, you might want to reassign the bug to nagios-nrpe-plugin with appropriate version? If NRPE cannot execute the checkcommand that implies that the nagios user doesn't have the required permissions. The given checkcommand is not part of the default configuration: /usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /var/tmp/mysql Which suggests that this is a configuration issue to be resolved by the administrator of the system. (e.g use sudo to execute the plugin as a users with the required permissions). Kind Regards, Bas
Bug#861905: unblock: pyosmium/2.11.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pyosmium Upstream has only fixed bugs for this release in line with the freeze policy. unblock pyosmium/2.11.1-1 Kind Regards, Bas diff -Nru pyosmium-2.11.0/CHANGELOG.md pyosmium-2.11.1/CHANGELOG.md --- pyosmium-2.11.0/CHANGELOG.md2017-01-15 15:39:17.0 +0100 +++ pyosmium-2.11.1/CHANGELOG.md2017-05-04 23:36:03.0 +0200 @@ -13,6 +13,19 @@ ### Fixed +## [2.11.1] - 2017-05-04 + +### Added + +### Changed + +### Fixed + +- prevent unnecessary calls to callbacks +- correctly throw KeyError in taglist accessor +- fix output type of index.map_types() function +- don't overgrow writer buffers over requested size + ## [2.11.0] - 2017-01-15 ### Changed @@ -123,7 +136,8 @@ - Exception not caught in test. -[unreleased]: https://github.com/osmcode/pyosmium/compare/v2.11.0...HEAD +[unreleased]: https://github.com/osmcode/pyosmium/compare/v2.11.1...HEAD +[2.11.1]: https://github.com/osmcode/pyosmium/compare/v2.11.0...v2.11.1 [2.11.0]: https://github.com/osmcode/pyosmium/compare/v2.10.2...v2.11.0 [2.10.2]: https://github.com/osmcode/pyosmium/compare/v2.9.0...v2.10.2 [2.9.0]: https://github.com/osmcode/pyosmium/compare/v2.8.0...v2.9.0 diff -Nru pyosmium-2.11.0/debian/changelog pyosmium-2.11.1/debian/changelog --- pyosmium-2.11.0/debian/changelog2017-01-17 18:45:04.0 +0100 +++ pyosmium-2.11.1/debian/changelog2017-05-05 09:51:21.0 +0200 @@ -1,3 +1,15 @@ +pyosmium (2.11.1-1) unstable; urgency=medium + + * New upstream bugfix release. +- Prevent unnecessary calls to callbacks +- Correctly throw KeyError in taglist accessor +- Fix output type of index.map_types() function +- Don't overgrow writer buffers over requested size + * Update branch in gbp.conf & Vcs-Git URL. + * Limit watch file to 2.11.x releases. + + -- Bas Couwenberg <sebas...@debian.org> Fri, 05 May 2017 09:51:21 +0200 + pyosmium (2.11.0-1) unstable; urgency=medium * Move from experimental to unstable. diff -Nru pyosmium-2.11.0/debian/control pyosmium-2.11.1/debian/control --- pyosmium-2.11.0/debian/control 2017-01-15 21:46:51.0 +0100 +++ pyosmium-2.11.1/debian/control 2017-05-05 09:48:33.0 +0200 @@ -23,7 +23,7 @@ zlib1g-dev Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/pyosmium.git/ -Vcs-Git: https://anonscm.debian.org/git/pkg-grass/pyosmium.git +Vcs-Git: https://anonscm.debian.org/git/pkg-grass/pyosmium.git -b stretch Homepage: http://osmcode.org/pyosmium/ Package: python-pyosmium diff -Nru pyosmium-2.11.0/debian/gbp.conf pyosmium-2.11.1/debian/gbp.conf --- pyosmium-2.11.0/debian/gbp.conf 2016-11-27 10:29:05.0 +0100 +++ pyosmium-2.11.1/debian/gbp.conf 2017-05-05 09:48:33.0 +0200 @@ -2,11 +2,11 @@ # The default name for the upstream branch is "upstream". # Change it if the name is different (for instance, "master"). -upstream-branch = upstream +upstream-branch = upstream-2.11 # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru pyosmium-2.11.0/debian/watch pyosmium-2.11.1/debian/watch --- pyosmium-2.11.0/debian/watch2016-10-26 21:36:51.0 +0200 +++ pyosmium-2.11.1/debian/watch2017-05-05 09:48:33.0 +0200 @@ -4,4 +4,4 @@ uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\ filenamemangle=s/(?:.*\/)?(?:rel|v|pyosmium)[\-\_]?(\d[\d\-\.]+)\.(tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))/pyosmium-$1.$2/ \ https://github.com/osmcode/pyosmium/releases \ -(?:.*/)?(?:rel|v|pyosmium)[\-\_]?(\d[\d\-\.]+)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) +(?:.*/)?(?:rel|v|pyosmium)[\-\_]?(2\.11\.\d[\d\-\.]*)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) diff -Nru pyosmium-2.11.0/lib/generic_handler.hpp pyosmium-2.11.1/lib/generic_handler.hpp --- pyosmium-2.11.0/lib/generic_handler.hpp 2017-01-15 15:39:17.0 +0100 +++ pyosmium-2.11.1/lib/generic_handler.hpp 2017-05-04 23:36:03.0 +0200 @@ -104,45 +104,46 @@ struct SimpleHandlerWrap: BaseHandler, wrapper { void node(const osmium::Node& node) const { -if (override f = this->get_override("node")) -f(boost::ref(node)); -} +if (!(m_callbacks & osmium::osm_entity_bits::node)) +return; -void default_node(const osmium::Node&) const { +if (override f = this->get_override("node")) { +f(boost::ref(node)); +} } void way(const osmium::Way& way) const { +if (!(m_callbacks & osmium:
Bug#861880: unblock: icinga/1.13.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package icinga It fixes the upgrade issue reported in #861077, by dropping the constraints only if they exist, and supporting both the old and new names. unblock icinga/1.13.4-2 Kind Regards, Bas diff -Nru icinga-1.13.4/debian/changelog icinga-1.13.4/debian/changelog --- icinga-1.13.4/debian/changelog 2016-12-23 10:05:44.0 +0100 +++ icinga-1.13.4/debian/changelog 2017-05-05 08:57:03.0 +0200 @@ -1,3 +1,11 @@ +icinga (1.13.4-2) unstable; urgency=medium + + * Team upload. + * Add patch to fix database upgrade to 1.13.0. +(closes: #861077) + + -- Bas Couwenberg <sebas...@debian.org> Fri, 05 May 2017 08:57:03 +0200 + icinga (1.13.4-1) unstable; urgency=high * Team upload. diff -Nru icinga-1.13.4/debian/patches/pgsql-upgrade-1.13.0.patch icinga-1.13.4/debian/patches/pgsql-upgrade-1.13.0.patch --- icinga-1.13.4/debian/patches/pgsql-upgrade-1.13.0.patch 1970-01-01 01:00:00.0 +0100 +++ icinga-1.13.4/debian/patches/pgsql-upgrade-1.13.0.patch 2017-05-03 12:47:00.0 +0200 @@ -0,0 +1,24 @@ +Description: Fix database upgrade to 1.13.0. + error encountered processing /usr/share/dbconfig-common/data/icinga-idoutils/upgrade/pgsql/1.13.0: + ERROR: constraint "uq_servicedependencies" of relation "icinga_servicedependencies" does not exist +Author: Bas Couwenberg <sebas...@debian.org> +Bug-Debian: https://bugs.debian.org/861077 +Forwarded: https://github.com/Icinga/icinga-core/pull/1595 +Applied-Upstream: https://github.com/Icinga/icinga-core/commit/d6ed8875b124205cf61b3a2aad59ec46292e7ff7 + +--- a/module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.13.0.sql b/module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.13.0.sql +@@ -11,8 +11,11 @@ + -- #7765 drop unique constraint + -- - + +-ALTER TABLE icinga_servicedependencies DROP CONSTRAINT uq_servicedependencies; +-ALTER TABLE icinga_hostdependencies DROP CONSTRAINT uq_hostdependencies; ++ALTER TABLE icinga_servicedependencies DROP CONSTRAINT IF EXISTS icinga_servicedependencies_instance_id_key; ++ALTER TABLE icinga_hostdependencies DROP CONSTRAINT IF EXISTS icinga_hostdependencies_instance_id_key; ++ ++ALTER TABLE icinga_servicedependencies DROP CONSTRAINT IF EXISTS UQ_servicedependencies; ++ALTER TABLE icinga_hostdependencies DROP CONSTRAINT IF EXISTS UQ_hostdependencies; + + CREATE INDEX idx_servicedependencies ON icinga_servicedependencies(instance_id,config_type,service_object_id,dependent_service_object_id,dependency_type,inherits_parent,fail_on_ok,fail_on_warning,fail_on_unknown,fail_on_critical); + CREATE INDEX idx_hostdependencies ON icinga_hostdependencies(instance_id,config_type,host_object_id,dependent_host_object_id,dependency_type,inherits_parent,fail_on_up,fail_on_down,fail_on_unreachable); diff -Nru icinga-1.13.4/debian/patches/series icinga-1.13.4/debian/patches/series --- icinga-1.13.4/debian/patches/series 2016-12-20 18:56:51.0 +0100 +++ icinga-1.13.4/debian/patches/series 2017-05-02 22:13:46.0 +0200 @@ -7,3 +7,4 @@ 99_CVE-2015-8010.patch spelling-errors.patch 53_jquery-ui.patch +pgsql-upgrade-1.13.0.patch
Bug#861788: unblock: libosmium/2.11.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libosmium Upstream has only fixed bugs for this release in line with the freeze policy. (include/attach the debdiff against the package in testing) unblock libosmium/2.11.3-1 Kind Regards, Bas diff -Nru libosmium-2.11.1/CHANGELOG.md libosmium-2.11.3/CHANGELOG.md --- libosmium-2.11.1/CHANGELOG.md 2017-03-07 13:54:48.0 +0100 +++ libosmium-2.11.3/CHANGELOG.md 2017-05-03 14:01:48.0 +0200 @@ -8,6 +8,24 @@ ### Fixed +## [2.11.3] - 2017-05-03 + +### Fixed + +- Two bugs in area assembler affecting very complex multipolygons and + multipolygons with overlapping or nearly overlapping lines. +- Invalid use of iterators leading to undefined behaviour in area assembler + code. +- Read OPL file correctly even if trailing newline in file is missing. + + +## [2.11.2] - 2017-04-10 + +### Fixed + +- Use minimum size of 64 bytes for buffers. This fixes an infinite loop + when buffer size is zero. + ## [2.11.1] - 2017-03-07 @@ -531,7 +549,9 @@ Doxygen (up to version 1.8.8). This version contains a workaround to fix this. -[unreleased]: https://github.com/osmcode/libosmium/compare/v2.11.1...HEAD +[unreleased]: https://github.com/osmcode/libosmium/compare/v2.11.3...HEAD +[2.11.3]: https://github.com/osmcode/libosmium/compare/v2.11.2...v2.11.3 +[2.11.2]: https://github.com/osmcode/libosmium/compare/v2.11.1...v2.11.2 [2.11.1]: https://github.com/osmcode/libosmium/compare/v2.11.0...v2.11.1 [2.11.0]: https://github.com/osmcode/libosmium/compare/v2.10.3...v2.11.0 [2.10.3]: https://github.com/osmcode/libosmium/compare/v2.10.2...v2.10.3 diff -Nru libosmium-2.11.1/CMakeLists.txt libosmium-2.11.3/CMakeLists.txt --- libosmium-2.11.1/CMakeLists.txt 2017-03-07 13:54:48.0 +0100 +++ libosmium-2.11.3/CMakeLists.txt 2017-05-03 14:01:48.0 +0200 @@ -25,7 +25,7 @@ set(LIBOSMIUM_VERSION_MAJOR 2) set(LIBOSMIUM_VERSION_MINOR 11) -set(LIBOSMIUM_VERSION_PATCH 1) +set(LIBOSMIUM_VERSION_PATCH 3) set(LIBOSMIUM_VERSION "${LIBOSMIUM_VERSION_MAJOR}.${LIBOSMIUM_VERSION_MINOR}.${LIBOSMIUM_VERSION_PATCH}") diff -Nru libosmium-2.11.1/debian/changelog libosmium-2.11.3/debian/changelog --- libosmium-2.11.1/debian/changelog 2017-03-07 18:31:00.0 +0100 +++ libosmium-2.11.3/debian/changelog 2017-05-03 18:44:44.0 +0200 @@ -1,3 +1,17 @@ +libosmium (2.11.3-1) unstable; urgency=medium + + * New upstream bugfix release. +- Use minimum size of 64 bytes for buffers. This fixes an infinite + loop when buffer size is zero. +- Two bugs in area assembler affecting very complex multipolygons and + multipolygons with overlapping or nearly overlapping lines. +- Invalid use of iterators leading to undefined behaviour in area + assembler code. +- Read OPL file correctly even if trailing newline in file is missing. + * Update watch file to limit results to 2.11.x releases. + + -- Bas Couwenberg <sebas...@debian.org> Wed, 03 May 2017 18:44:44 +0200 + libosmium (2.11.1-1) unstable; urgency=medium * New upstream bugfix release. diff -Nru libosmium-2.11.1/debian/watch libosmium-2.11.3/debian/watch --- libosmium-2.11.1/debian/watch 2017-03-07 18:23:24.0 +0100 +++ libosmium-2.11.3/debian/watch 2017-05-03 18:38:25.0 +0200 @@ -4,4 +4,4 @@ uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/;s/RC/rc/,\ filenamemangle=s/(?:.*\/)?(?:rel|v|libosmium)[\-\_]?(\d[\d\-\.]+)\.(tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))/libosmium-$1.$2/ \ https://github.com/osmcode/libosmium/releases \ -(?:.*/)?(?:rel|v|libosmium)[\-\_]?(\d[\d\-\.]+)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) +(?:.*/)?(?:rel|v|libosmium)[\-\_]?(2\.11\.\d[\d\-\.]*)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) diff -Nru libosmium-2.11.1/include/osmium/area/assembler.hpp libosmium-2.11.3/include/osmium/area/assembler.hpp --- libosmium-2.11.1/include/osmium/area/assembler.hpp 2017-03-07 13:54:48.0 +0100 +++ libosmium-2.11.3/include/osmium/area/assembler.hpp 2017-05-03 14:01:48.0 +0200 @@ -474,17 +474,17 @@ class rings_stack_element { -int32_t m_y; +double m_y; detail::ProtoRing* m_ring_ptr; public: -rings_stack_element(int32_t y, detail::ProtoRing* ring_ptr) : +rings_stack_element(double y, detail::ProtoRing* ring_ptr) : m_y(y), m_ring_ptr(ring_ptr) { } -int32_t y() const noexcept { +double y() const noexcept { return m_y; } @@ -504,7 +504,7 @@ return m_y < rhs.m_y; } -}; // class ring_stack_element +}; // class rings_stack_element using rings_stack = std::
Bug#861353: unblock: libhdf4/4.2.12-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libhdf4 It fixes the upgrade issue reported in #861303. unblock libhdf4/4.2.12-3 Kind Regards, Bas diff -Nru libhdf4-4.2.12/debian/changelog libhdf4-4.2.12/debian/changelog --- libhdf4-4.2.12/debian/changelog 2017-04-03 14:28:06.0 +0200 +++ libhdf4-4.2.12/debian/changelog 2017-04-27 12:42:18.0 +0200 @@ -1,3 +1,12 @@ +libhdf4 (4.2.12-3) unstable; urgency=medium + + * Team upload. + * Fix symlink to directory conversion that happened in squeeze. +(closes: #861303) + * Update spelling-errors.patch to fix 'conversion' typo. + + -- Bas Couwenberg <sebas...@debian.org> Thu, 27 Apr 2017 12:42:18 +0200 + libhdf4 (4.2.12-2) unstable; urgency=medium * Team upload. diff -Nru libhdf4-4.2.12/debian/control libhdf4-4.2.12/debian/control --- libhdf4-4.2.12/debian/control 2016-07-01 18:49:14.0 +0200 +++ libhdf4-4.2.12/debian/control 2017-04-27 11:53:33.0 +0200 @@ -148,6 +148,7 @@ Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} +Pre-Depends: ${misc:Pre-Depends} Description: Hierarchical Data Format library -- runtime package HDF is a multi-object file format for storing and transferring graphical and numerical data mainly used in scientific computing. HDF diff -Nru libhdf4-4.2.12/debian/control.in libhdf4-4.2.12/debian/control.in --- libhdf4-4.2.12/debian/control.in2016-07-01 18:27:07.0 +0200 +++ libhdf4-4.2.12/debian/control.in2017-04-27 11:53:23.0 +0200 @@ -148,6 +148,7 @@ Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} +Pre-Depends: ${misc:Pre-Depends} Description: Hierarchical Data Format library -- runtime package HDF is a multi-object file format for storing and transferring graphical and numerical data mainly used in scientific computing. HDF diff -Nru libhdf4-4.2.12/debian/hdf4-tools.maintscript libhdf4-4.2.12/debian/hdf4-tools.maintscript --- libhdf4-4.2.12/debian/hdf4-tools.maintscript1970-01-01 01:00:00.0 +0100 +++ libhdf4-4.2.12/debian/hdf4-tools.maintscript2017-04-27 11:52:31.0 +0200 @@ -0,0 +1 @@ +symlink_to_dir /usr/share/doc/hdf4-tools libhdf4g 4.2.12-3~ diff -Nru libhdf4-4.2.12/debian/patches/spelling-errors.patch libhdf4-4.2.12/debian/patches/spelling-errors.patch --- libhdf4-4.2.12/debian/patches/spelling-errors.patch 2016-06-30 21:00:12.0 +0200 +++ libhdf4-4.2.12/debian/patches/spelling-errors.patch 2017-04-27 12:41:32.0 +0200 @@ -8,6 +8,7 @@ inadvertantly -> inadvertently syncronize-> synchronize existant -> existent + converion -> conversion Author: Bas Couwenberg <sebas...@debian.org> --- a/hdf/util/gif2hdf.c @@ -478,3 +479,14 @@ num_errs++; } +--- a/hdf/util/hdf8to24.c b/hdf/util/hdf8to24.c +@@ -266,7 +266,7 @@ main(int argc, char *argv[]) + } /* end if */ + } /* end if */ + else +-printf("No palette associated with image, using default grey scale converion\n"); ++printf("No palette associated with image, using default grey scale conversion\n"); + + if (DFR8getimage(argv[file], img_buf, xdim, ydim, (ispal ? pal_buf : NULL)) == FAIL) + {
Bug#861077: icinga-idoutils: fails to upgrade squeeze -> wheezy -> jessie -> stretch
Source: icinga Followup-For: Bug #861077 Control: tags -1 patch Dear Maintainer, It's probably sufficient to fix the case of the constraints as per the attached patch. I've haven't tested this (yet), as I don't know who to reproduce the issue with piuparts. Andreas, how can the upgrade test you performed be reproduced by others using piuparts? Kind Regards, Bas diff --git a/module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.13.0.sql b/module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.13.0.sql index d0c9a92..ab5608a 100644 --- a/module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.13.0.sql +++ b/module/idoutils/db/pgsql/upgrade/pgsql-upgrade-1.13.0.sql @@ -11,8 +11,8 @@ -- #7765 drop unique constraint -- - -ALTER TABLE icinga_servicedependencies DROP CONSTRAINT uq_servicedependencies; -ALTER TABLE icinga_hostdependencies DROP CONSTRAINT uq_hostdependencies; +ALTER TABLE icinga_servicedependencies DROP CONSTRAINT UQ_servicedependencies; +ALTER TABLE icinga_hostdependencies DROP CONSTRAINT UQ_hostdependencies; CREATE INDEX idx_servicedependencies ON icinga_servicedependencies(instance_id,config_type,service_object_id,dependent_service_object_id,dependency_type,inherits_parent,fail_on_ok,fail_on_warning,fail_on_unknown,fail_on_critical); CREATE INDEX idx_hostdependencies ON icinga_hostdependencies(instance_id,config_type,host_object_id,dependent_host_object_id,dependency_type,inherits_parent,fail_on_up,fail_on_down,fail_on_unreachable);
Bug#860802: [Pkg-nagios-devel] Bug#860802: nagios-nrpe-server: nrpe daemon doesn't log client IP address
Control: tags -1 upstream Control: forwarded -1 https://github.com/NagiosEnterprises/nrpe/issues/115 Hi Ralf, Since this is an upstream issue, I've forwarded your request upstream. On 2017-04-20 12:07, Ralf G. R. Bergs wrote: I'm seeing scans from hosts on the internet like follows: Due to NRPEs security track record you should really put the NRPE services behind a firewall and only allow connections from your Nagios/Icinga server(s), i.e. the allowed_hosts. Kind Regards, Bas
Bug#860773: unblock: pysal/1.13.0-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pysal It "fixes" #860694 by ignoring test failure on i386 where it's normally not built (the source only builds arch:all packages). unblock pysal/1.13.0-4 Kind Regards, Bas diff -Nru pysal-1.13.0/debian/changelog pysal-1.13.0/debian/changelog --- pysal-1.13.0/debian/changelog 2017-01-28 12:38:13.0 +0100 +++ pysal-1.13.0/debian/changelog 2017-04-19 11:19:27.0 +0200 @@ -1,3 +1,11 @@ +pysal (1.13.0-4) unstable; urgency=medium + + * Team upload. + * Ignore test failures on i386, package not normally built there. +(closes: #860694) + + -- Bas Couwenberg <sebas...@debian.org> Wed, 19 Apr 2017 11:19:27 +0200 + pysal (1.13.0-3) unstable; urgency=medium * Team upload. diff -Nru pysal-1.13.0/debian/rules pysal-1.13.0/debian/rules --- pysal-1.13.0/debian/rules 2017-01-28 12:36:16.0 +0100 +++ pysal-1.13.0/debian/rules 2017-04-19 11:18:38.0 +0200 @@ -1,6 +1,8 @@ #!/usr/bin/make -f # -*- makefile -*- +DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH) + export PYBUILD_NAME=pysal export PYBUILD_TEST_NOSE=1 export PYBUILD_TEST_ARGS=--exclude test_DistanceBand_arc --exclude-dir=pysal/contrib --exclude-dir pysal/network @@ -8,6 +10,14 @@ %: dh $@ --with python2,python3 --buildsystem pybuild +override_dh_auto_test: +# Ignore test failures on problematic architectures only +ifneq (,$(findstring $(DEB_BUILD_ARCH),"i386")) + dh_auto_test || echo "Ignoring test failures" +else + dh_auto_test +endif + override_dh_python2: dh_python2 -ppython-pysal dh_numpy -ppython-pysal
Bug#860772: unblock: python-geopandas/0.2.1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-geopandas It "fixes" #860621 by ignoring test failure on i386 where it's normally not built (the source only builds arch:all packages) unblock python-geopandas/0.2.1-3 Kind Regards, Bas diff -Nru python-geopandas-0.2.1/debian/changelog python-geopandas-0.2.1/debian/changelog --- python-geopandas-0.2.1/debian/changelog 2017-01-02 19:37:48.0 +0100 +++ python-geopandas-0.2.1/debian/changelog 2017-04-19 10:28:22.0 +0200 @@ -1,3 +1,11 @@ +python-geopandas (0.2.1-3) unstable; urgency=medium + + * Team upload. + * Ignore test failures on i386, package not normally built there. +(closes: #860621) + + -- Bas Couwenberg <sebas...@debian.org> Wed, 19 Apr 2017 10:28:22 +0200 + python-geopandas (0.2.1-2) unstable; urgency=medium * Team upload. diff -Nru python-geopandas-0.2.1/debian/rules python-geopandas-0.2.1/debian/rules --- python-geopandas-0.2.1/debian/rules 2017-01-02 19:35:41.0 +0100 +++ python-geopandas-0.2.1/debian/rules 2017-04-19 10:09:47.0 +0200 @@ -1,5 +1,7 @@ #!/usr/bin/make -f +DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH) + export PYBUILD_NAME=geopandas %: @@ -16,8 +18,16 @@ override_dh_auto_test: # Disable geocode tests as these require online access cp -v debian/nybb_*.zip examples/ + +# Ignore test failures on problematic architectures only +ifneq (,$(findstring $(DEB_BUILD_ARCH),"i386")) + PYBUILD_SYSTEM=custom \ + PYBUILD_TEST_ARGS="TRAVIS=1 nosetests -v -e test_geocode.py" dh_auto_test || echo "Ignoring test failures" +else PYBUILD_SYSTEM=custom \ PYBUILD_TEST_ARGS="TRAVIS=1 nosetests -v -e test_geocode.py" dh_auto_test +endif + rm -f examples/nybb_*.zip override_dh_auto_install:
Bug#860694: pysal: FTBFS on i386: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
Control: severity -1 important Hi Lucas, Like python-geopandas, pysal only builds arch:all packages and is normally not built on i386 machines, so I've downgraded the severity. I'll ignore the test failures on i386 to close this issue. Kind Regards, Bas
Bug#860621: python-geopandas: FTBFS on i386: Test failures
Control: severity -1 important Hi Lucas, This package only builds arch:all packages and is not normally built on i386 machines, so I'm downgrading the severity. I'll update the package to ignore test failures on i386 to close this issue. Kind Regards, Bas
Bug#860299: unblock: osm2pgsql/0.92.0+ds-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package osm2pgsql It fixes two important issues reported to me by one of the developers one was also reported in #860273. unblock osm2pgsql/0.92.0+ds-2 Kind Regards, Bas diff -Nru osm2pgsql-0.92.0+ds/debian/changelog osm2pgsql-0.92.0+ds/debian/changelog --- osm2pgsql-0.92.0+ds/debian/changelog2016-12-16 11:34:24.0 +0100 +++ osm2pgsql-0.92.0+ds/debian/changelog2017-04-13 23:00:11.0 +0200 @@ -1,3 +1,18 @@ +osm2pgsql (0.92.0+ds-2) unstable; urgency=medium + + * Add upstream patches from 0.92.x branch to fix two important issues: +- Ignore relations with more than 32k members. + There is a hard restriction in the pgsql middle tables, where + relation members are indexed using a smallint. To remain + consistent, drop all relations which exceed this size. + https://github.com/openstreetmap/osm2pgsql/issues/713 +- Use the same logic for queuing pending ways with multi and pgsql. + Fixes ways disappearing from the output table. + https://github.com/openstreetmap/osm2pgsql/issues/735 +(closes: #860273) + + -- Bas Couwenberg <sebas...@debian.org> Thu, 13 Apr 2017 23:00:11 +0200 + osm2pgsql (0.92.0+ds-1) unstable; urgency=medium * New upstream release. diff -Nru osm2pgsql-0.92.0+ds/debian/patches/0001-ignore-relations-with-more-than-32k-members.patch osm2pgsql-0.92.0+ds/debian/patches/0001-ignore-relations-with-more-than-32k-members.patch --- osm2pgsql-0.92.0+ds/debian/patches/0001-ignore-relations-with-more-than-32k-members.patch 1970-01-01 01:00:00.0 +0100 +++ osm2pgsql-0.92.0+ds/debian/patches/0001-ignore-relations-with-more-than-32k-members.patch 2017-04-13 22:55:58.0 +0200 @@ -0,0 +1,20 @@ +Description: ignore relations with more than 32k members + There is a hard restriction in the pgsql middle tables, where + relation members are indexed using a smallint. To remain + consistent, drop all relations which exceed this size. +Author: Sarah Hoffmann <lon...@denofr.de> +Origin: https://github.com/openstreetmap/osm2pgsql/commit/ec9c84edbcbd0dafab6d6c30290083e75c023890 +Bug: https://github.com/openstreetmap/osm2pgsql/issues/713 + +--- a/parse-osmium.cpp b/parse-osmium.cpp +@@ -176,6 +176,9 @@ void parse_osmium_t::relation(osmium::Re + if (rel.deleted()) { + m_data->relation_delete(rel.id()); + } else { ++if (rel.members().size() > 32767) { ++return; ++} + convert_tags(rel); + convert_members(rel.members()); + if (m_append) { diff -Nru osm2pgsql-0.92.0+ds/debian/patches/0001-Use-the-same-logic-for-queuing-pending-ways-with-mul.patch osm2pgsql-0.92.0+ds/debian/patches/0001-Use-the-same-logic-for-queuing-pending-ways-with-mul.patch --- osm2pgsql-0.92.0+ds/debian/patches/0001-Use-the-same-logic-for-queuing-pending-ways-with-mul.patch 1970-01-01 01:00:00.0 +0100 +++ osm2pgsql-0.92.0+ds/debian/patches/0001-Use-the-same-logic-for-queuing-pending-ways-with-mul.patch 2017-04-13 23:00:11.0 +0200 @@ -0,0 +1,27 @@ +Description: Use the same logic for queuing pending ways with multi and pgsql + Fixes ways disappearing from the output table. +Author: Paul Norman <penor...@mac.com> +Origin: https://github.com/openstreetmap/osm2pgsql/commit/8ffe16e67da43fd531a5e73b10d31465324f4a91 +Bug: https://github.com/openstreetmap/osm2pgsql/issues/735 +Bug-Debian: https://bugs.debian.org/860273 + +--- a/output-multi.cpp b/output-multi.cpp +@@ -92,7 +92,7 @@ void output_multi_t::enqueue_ways(pendin + } + + //make sure to get this one as well and move to the next +-if(popped == id) { ++if (popped > id) { + if (!ways_done_tracker->is_marked(popped) && id_tracker::is_valid(popped)) { + job_queue.push(pending_job_t(popped, output_id)); + added++; +@@ -143,7 +143,7 @@ void output_multi_t::enqueue_relations(p + } + + //make sure to get this one as well and move to the next +-if(popped == id) { ++if (popped > id) { + if(id_tracker::is_valid(popped)) { + job_queue.push(pending_job_t(popped, output_id)); + added++; diff -Nru osm2pgsql-0.92.0+ds/debian/patches/series osm2pgsql-0.92.0+ds/debian/patches/series --- osm2pgsql-0.92.0+ds/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ osm2pgsql-0.92.0+ds/debian/patches/series 2017-04-13 22:55:55.0 +0200 @@ -0,0 +1,2 @@ +0001-ignore-relations-with-more-than-32k-members.patch +0001-Use-the-same-logic-for-queuing-pending-ways-with-mul.patch
Bug#859984: unblock: gdal/2.1.2+dfsg-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gdal It fixes the upgrade issue reported in #859918 by adding Breaks on libgdal1h. unblock gdal/2.1.2+dfsg-5 Kind Regards, Bas diff -Nru gdal-2.1.2+dfsg/debian/changelog gdal-2.1.2+dfsg/debian/changelog --- gdal-2.1.2+dfsg/debian/changelog2017-04-02 23:35:22.0 +0200 +++ gdal-2.1.2+dfsg/debian/changelog2017-04-09 13:22:29.0 +0200 @@ -1,3 +1,10 @@ +gdal (2.1.2+dfsg-5) unstable; urgency=medium + + * Mark libgdal20 as breaking libgdal1h to fix upgrades. +(closes: #859918) + + -- Bas Couwenberg <sebas...@debian.org> Sun, 09 Apr 2017 13:22:29 +0200 + gdal (2.1.2+dfsg-4) unstable; urgency=medium * Enable PIE hardening flags. diff -Nru gdal-2.1.2+dfsg/debian/control gdal-2.1.2+dfsg/debian/control --- gdal-2.1.2+dfsg/debian/control 2017-04-02 22:41:06.0 +0200 +++ gdal-2.1.2+dfsg/debian/control 2017-04-09 13:20:47.0 +0200 @@ -69,6 +69,7 @@ Depends: ${shlibs:Depends}, ${misc:Depends} Recommends: proj-bin +Breaks: libgdal1h (<< 2.0) Provides: gdal-abi-2-1-2 Description: Geospatial Data Abstraction Library GDAL is a translator library for raster geospatial data formats.
Bug#859501: unblock: netcdf/1:4.4.1.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package netcdf It fixes #859430 by enabling the PIE hardening buildflags. unblock netcdf/1:4.4.1.1-2 Kind Regards, Bas diff -Nru netcdf-4.4.1.1/debian/changelog netcdf-4.4.1.1/debian/changelog --- netcdf-4.4.1.1/debian/changelog 2016-11-22 07:24:16.0 +0100 +++ netcdf-4.4.1.1/debian/changelog 2017-04-04 08:09:19.0 +0200 @@ -1,3 +1,11 @@ +netcdf (1:4.4.1.1-2) unstable; urgency=medium + + * Enable PIE hardening buildflags. +(closes: #859430) + * Drop unused lintian overrides for hardening-no-pie. + + -- Bas Couwenberg <sebas...@debian.org> Tue, 04 Apr 2017 08:09:19 +0200 + netcdf (1:4.4.1.1-1) unstable; urgency=medium * New upstream release. diff -Nru netcdf-4.4.1.1/debian/netcdf-bin.lintian-overrides netcdf-4.4.1.1/debian/netcdf-bin.lintian-overrides --- netcdf-4.4.1.1/debian/netcdf-bin.lintian-overrides 2016-08-28 15:45:53.0 +0200 +++ netcdf-4.4.1.1/debian/netcdf-bin.lintian-overrides 1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -# PIE breaks the build -netcdf-bin: hardening-no-pie * diff -Nru netcdf-4.4.1.1/debian/rules netcdf-4.4.1.1/debian/rules --- netcdf-4.4.1.1/debian/rules 2016-08-28 15:45:53.0 +0200 +++ netcdf-4.4.1.1/debian/rules 2017-04-04 08:08:33.0 +0200 @@ -2,9 +2,8 @@ #export DH_VERBOSE=1 -# Enable hardening build flags, except: -# pie: causes build failure -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +# Enable hardening build flags +export DEB_BUILD_MAINT_OPTIONS=hardening=+all DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
Bug#859466: unblock: mapnik/3.0.12+ds-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mapnik It fixes #859424 by enabling the PIE hardening buildflags. unblock mapnik/3.0.12+ds-3 Kind Regards, Bas diff -Nru mapnik-3.0.12+ds/debian/changelog mapnik-3.0.12+ds/debian/changelog --- mapnik-3.0.12+ds/debian/changelog 2016-11-05 14:15:44.0 +0100 +++ mapnik-3.0.12+ds/debian/changelog 2017-04-03 14:47:38.0 +0200 @@ -1,3 +1,11 @@ +mapnik (3.0.12+ds-3) unstable; urgency=medium + + * Update branch in gbp.conf & Vcs-Git URL. + * Enable PIE hardening buildflags. +(closes: #859424) + + -- Bas Couwenberg <sebas...@debian.org> Mon, 03 Apr 2017 14:47:38 +0200 + mapnik (3.0.12+ds-2) unstable; urgency=medium * Add patch to fix 'dependencies' typo. diff -Nru mapnik-3.0.12+ds/debian/control mapnik-3.0.12+ds/debian/control --- mapnik-3.0.12+ds/debian/control 2016-10-30 12:18:51.0 +0100 +++ mapnik-3.0.12+ds/debian/control 2017-04-03 14:45:40.0 +0200 @@ -33,7 +33,7 @@ zlib1g-dev Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/mapnik.git -Vcs-Git: https://anonscm.debian.org/git/pkg-grass/mapnik.git +Vcs-Git: https://anonscm.debian.org/git/pkg-grass/mapnik.git -b stretch Homepage: http://www.mapnik.org/ Package: libmapnik3.0 diff -Nru mapnik-3.0.12+ds/debian/gbp.conf mapnik-3.0.12+ds/debian/gbp.conf --- mapnik-3.0.12+ds/debian/gbp.conf2016-10-15 20:08:15.0 +0200 +++ mapnik-3.0.12+ds/debian/gbp.conf2017-04-03 14:45:48.0 +0200 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru mapnik-3.0.12+ds/debian/rules mapnik-3.0.12+ds/debian/rules --- mapnik-3.0.12+ds/debian/rules 2016-11-05 14:13:46.0 +0100 +++ mapnik-3.0.12+ds/debian/rules 2017-04-03 14:46:26.0 +0200 @@ -4,9 +4,8 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 -# Enable hardening build flags, except: -# pie: causes python-mapnik build failure -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +# Enable hardening build flags +export DEB_BUILD_MAINT_OPTIONS=hardening=+all NJOBS := -j1 ifneq (,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
Bug#859464: unblock: libhdf4/4.2.12-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libhdf4 It fixes #859413 by enabling the PIE hardening buildflags. unblock libhdf4/4.2.12-2 Kind Regards, Bas diff -Nru libhdf4-4.2.12/debian/changelog libhdf4-4.2.12/debian/changelog --- libhdf4-4.2.12/debian/changelog 2016-07-06 17:35:44.0 +0200 +++ libhdf4-4.2.12/debian/changelog 2017-04-03 14:28:06.0 +0200 @@ -1,3 +1,12 @@ +libhdf4 (4.2.12-2) unstable; urgency=medium + + * Team upload. + * Enable PIE hardening flags. +(closes: #859413) + * Drop unused lintian overrides for hardening-no-pie. + + -- Bas Couwenberg <sebas...@debian.org> Mon, 03 Apr 2017 14:28:06 +0200 + libhdf4 (4.2.12-1) unstable; urgency=medium * Team upload. diff -Nru libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides --- libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides 2016-05-20 18:11:05.0 +0200 +++ libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides 1970-01-01 01:00:00.0 +0100 @@ -1,3 +0,0 @@ -# PIE breaks the build -hdf4-tools: hardening-no-pie * - diff -Nru libhdf4-4.2.12/debian/rules libhdf4-4.2.12/debian/rules --- libhdf4-4.2.12/debian/rules 2016-06-30 23:28:39.0 +0200 +++ libhdf4-4.2.12/debian/rules 2017-04-03 14:26:02.0 +0200 @@ -6,7 +6,7 @@ # # Enable hardening build flags -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS=hardening=+all DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) @@ -24,9 +24,9 @@ CXX := g++ LIBS := -ljpeg -lz -lm -CFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie dpkg-buildflags --get CFLAGS) -CFLAGS += $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie dpkg-buildflags --get CPPFLAGS) -LDFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie dpkg-buildflags --get LDFLAGS) +CFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get CFLAGS) +CFLAGS += $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get CPPFLAGS) +LDFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get LDFLAGS) ifneq (,$(findstring verbose,$(DEB_BUILD_OPTIONS))) DH_VERBOSE=1
Bug#859465: unblock: ogdi-dfsg/3.2.0+ds-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ogdi-dfsg It fixes #859433 by enabling the PIE hardening buildflags. unblock ogdi-dfsg/3.2.0+ds-2 Kind Regards, Bas diff -Nru ogdi-dfsg-3.2.0+ds/debian/changelog ogdi-dfsg-3.2.0+ds/debian/changelog --- ogdi-dfsg-3.2.0+ds/debian/changelog 2016-07-19 15:58:59.0 +0200 +++ ogdi-dfsg-3.2.0+ds/debian/changelog 2017-04-03 15:36:52.0 +0200 @@ -1,3 +1,12 @@ +ogdi-dfsg (3.2.0+ds-2) unstable; urgency=medium + + * Team upload. + * Enable PIE hardening buildflags. +(closes: #859433) + * Drop unused lintian overrides for hardening-no-pie. + + -- Bas Couwenberg <sebas...@debian.org> Mon, 03 Apr 2017 15:36:52 +0200 + ogdi-dfsg (3.2.0+ds-1) unstable; urgency=medium * Team upload. diff -Nru ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides --- ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides2016-07-19 15:19:14.0 +0200 +++ ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides1970-01-01 01:00:00.0 +0100 @@ -1,3 +0,0 @@ -# PIE breaks the build -ogdi-bin: hardening-no-pie * - diff -Nru ogdi-dfsg-3.2.0+ds/debian/rules ogdi-dfsg-3.2.0+ds/debian/rules --- ogdi-dfsg-3.2.0+ds/debian/rules 2016-07-19 15:48:19.0 +0200 +++ ogdi-dfsg-3.2.0+ds/debian/rules 2017-04-03 15:36:52.0 +0200 @@ -5,7 +5,7 @@ #export DH_VERBOSE=1 # Enable hardening build flags -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS=hardening=+all export TOPDIR=$(CURDIR) export CFG=debug
Bug#859392: unblock: gdal/2.1.2+dfsg-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gdal It fixes #859368 by enabling PIE. unblock gdal/2.1.2+dfsg-4 Kind Regards, Bas diff -Nru gdal-2.1.2+dfsg/debian/changelog gdal-2.1.2+dfsg/debian/changelog --- gdal-2.1.2+dfsg/debian/changelog2017-02-02 20:15:59.0 +0100 +++ gdal-2.1.2+dfsg/debian/changelog2017-04-02 23:35:22.0 +0200 @@ -1,3 +1,11 @@ +gdal (2.1.2+dfsg-4) unstable; urgency=medium + + * Enable PIE hardening flags. +(closes: #859368) + * Drop unused hardening-no-pie lintian override. + + -- Bas Couwenberg <sebas...@debian.org> Sun, 02 Apr 2017 23:35:22 +0200 + gdal (2.1.2+dfsg-3) unstable; urgency=medium * Add upstream patch to fix _gdal_array ImportError with Python 3. diff -Nru gdal-2.1.2+dfsg/debian/gdal-bin.lintian-overrides gdal-2.1.2+dfsg/debian/gdal-bin.lintian-overrides --- gdal-2.1.2+dfsg/debian/gdal-bin.lintian-overrides 2017-01-20 10:15:35.0 +0100 +++ gdal-2.1.2+dfsg/debian/gdal-bin.lintian-overrides 2017-04-02 22:42:59.0 +0200 @@ -7,6 +7,3 @@ # in pre-1.10 versions distributed in experimental. Just for safety. gdal-bin: package-relation-with-self breaks: gdal-bin (<< 1.10.0-0~) -# PIE breaks the Python bindings -gdal-bin: hardening-no-pie * - diff -Nru gdal-2.1.2+dfsg/debian/rules gdal-2.1.2+dfsg/debian/rules --- gdal-2.1.2+dfsg/debian/rules2017-02-02 20:14:10.0 +0100 +++ gdal-2.1.2+dfsg/debian/rules2017-04-02 22:41:34.0 +0200 @@ -9,7 +9,7 @@ #export DH_VERBOSE=1 # Enable hardening build flags -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS=hardening=+all UPSTREAM_VERSION = $(shell dpkg-parsechangelog | sed -ne 's/^Version: \(.*\)-.*/\1/p' | sed -e 's/\+.*//; s/^[0-9]://')
Bug#859394: unblock: libgdal-grass/2.1.2-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libgdal-grass It enables PIE to as done for gdal (#859368) & grass (#859372) to keep the family in sync. unblock libgdal-grass/2.1.2-5 Kind Regards, Bas diff -Nru libgdal-grass-2.1.2/debian/changelog libgdal-grass-2.1.2/debian/changelog --- libgdal-grass-2.1.2/debian/changelog2017-01-17 01:50:21.0 +0100 +++ libgdal-grass-2.1.2/debian/changelog2017-04-02 23:43:22.0 +0200 @@ -1,3 +1,9 @@ +libgdal-grass (2.1.2-5) unstable; urgency=medium + + * Enable PIE hardening flags. + + -- Bas Couwenberg <sebas...@debian.org> Sun, 02 Apr 2017 23:43:22 +0200 + libgdal-grass (2.1.2-4) unstable; urgency=medium * Add patch to link GRASS 7.2 libraries. diff -Nru libgdal-grass-2.1.2/debian/patches/grass72.patch libgdal-grass-2.1.2/debian/patches/grass72.patch --- libgdal-grass-2.1.2/debian/patches/grass72.patch2017-01-17 01:50:11.0 +0100 +++ libgdal-grass-2.1.2/debian/patches/grass72.patch2017-04-02 23:42:35.0 +0200 @@ -1,6 +1,7 @@ Description: Add libraries for GRASS 7.2. Author: Bas Couwenberg <sebas...@debian.org> Forwarded: https://trac.osgeo.org/gdal/ticket/6785 +Applied-Upstream: http://trac.osgeo.org/gdal/changeset/37161 --- a/configure.in +++ b/configure.in diff -Nru libgdal-grass-2.1.2/debian/rules libgdal-grass-2.1.2/debian/rules --- libgdal-grass-2.1.2/debian/rules2016-10-28 16:20:25.0 +0200 +++ libgdal-grass-2.1.2/debian/rules2017-04-02 23:42:50.0 +0200 @@ -5,7 +5,7 @@ #export DH_VERBOSE=1 # Enable hardening build flags -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS=hardening=+all PKGNAME=$(shell grep Package: debian/control.in | head -1 | cut -d' ' -f2) GRASS=grass$(subst .,,$(shell pkg-config --modversion grass | cut -d. -f1,2))
Bug#859393: unblock: grass/7.2.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package grass It fixes 859372 by enabling PIE. unblock grass/7.2.0-2 Kind Regards, Bas diff -Nru grass-7.2.0/debian/changelog grass-7.2.0/debian/changelog --- grass-7.2.0/debian/changelog2016-12-28 19:05:08.0 +0100 +++ grass-7.2.0/debian/changelog2017-04-02 23:38:40.0 +0200 @@ -1,3 +1,11 @@ +grass (7.2.0-2) unstable; urgency=medium + + * Enable PIE hardening flags. +(closes: #859372) + * Drop unused lintian overrides for hardening-no-pie. + + -- Bas Couwenberg <sebas...@debian.org> Sun, 02 Apr 2017 23:38:40 +0200 + grass (7.2.0-1) unstable; urgency=medium * New upstream release. diff -Nru grass-7.2.0/debian/grass-core.lintian-overrides grass-7.2.0/debian/grass-core.lintian-overrides --- grass-7.2.0/debian/grass-core.lintian-overrides 2016-12-28 18:10:58.0 +0100 +++ grass-7.2.0/debian/grass-core.lintian-overrides 2017-04-02 23:38:05.0 +0200 @@ -44,6 +44,3 @@ grass-core: extra-license-file usr/lib/grass*/etc/license grass-core: extra-license-file usr/share/doc/grass-core/COPYING -# PIE breaks the build -grass-core: hardening-no-pie * - diff -Nru grass-7.2.0/debian/grass-dev.lintian-overrides grass-7.2.0/debian/grass-dev.lintian-overrides --- grass-7.2.0/debian/grass-dev.lintian-overrides 2016-12-01 20:04:08.0 +0100 +++ grass-7.2.0/debian/grass-dev.lintian-overrides 1970-01-01 01:00:00.0 +0100 @@ -1,3 +0,0 @@ -# PIE breaks the build -grass-dev: hardening-no-pie * - diff -Nru grass-7.2.0/debian/patches/hicolor-icons.patch grass-7.2.0/debian/patches/hicolor-icons.patch --- grass-7.2.0/debian/patches/hicolor-icons.patch 2016-12-28 19:04:36.0 +0100 +++ grass-7.2.0/debian/patches/hicolor-icons.patch 2017-01-17 00:33:11.0 +0100 @@ -2,6 +2,7 @@ grass.desktop uses Icon=grass not Icon=grass71. Author: Bas Couwenberg <sebas...@debian.org> Forwarded: https://trac.osgeo.org/grass/ticket/3233 +Applied-Upstream: https://trac.osgeo.org/grass/changeset/70166 --- a/gui/icons/Makefile +++ b/gui/icons/Makefile diff -Nru grass-7.2.0/debian/rules grass-7.2.0/debian/rules --- grass-7.2.0/debian/rules2016-12-28 18:53:46.0 +0100 +++ grass-7.2.0/debian/rules2017-04-02 23:36:12.0 +0200 @@ -3,9 +3,8 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 -# Enable hardening build flags, except: -# pie: causes build failure -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +# Enable hardening build flags +export DEB_BUILD_MAINT_OPTIONS=hardening=+all VERSION=$(shell echo `head -2 $(CURDIR)/include/VERSION` | sed -e 's/ //') ABI=$(shell echo `head -3 $(CURDIR)/include/VERSION` | sed -e 's/ //g' -e 's/RC/-/')
Bug#858391: unblock: qgis/2.14.11+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package qgis It fixes the integration with GRASS 7.2 in the Processing plugin. (#858251) unblock qgis/2.14.11+dfsg-3 Kind Regards, Bas diff -Nru qgis-2.14.11+dfsg/debian/changelog qgis-2.14.11+dfsg/debian/changelog --- qgis-2.14.11+dfsg/debian/changelog 2017-02-13 18:43:07.0 +0100 +++ qgis-2.14.11+dfsg/debian/changelog 2017-03-21 12:49:51.0 +0100 @@ -1,3 +1,11 @@ +qgis (2.14.11+dfsg-3) unstable; urgency=medium + + * Add patch to fix GRASS 7.2 support in processing. +(closes: #858251) + * Update branch in gbp.conf & Vcs-Git URL. + + -- Bas Couwenberg <sebas...@debian.org> Tue, 21 Mar 2017 12:49:51 +0100 + qgis (2.14.11+dfsg-2) unstable; urgency=medium * Add Breaks/Replaces on python-qt4 for QtWebKit. diff -Nru qgis-2.14.11+dfsg/debian/control qgis-2.14.11+dfsg/debian/control --- qgis-2.14.11+dfsg/debian/control2017-02-13 18:37:20.0 +0100 +++ qgis-2.14.11+dfsg/debian/control2017-03-21 12:49:51.0 +0100 @@ -68,7 +68,7 @@ qgis-dev Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/qgis.git -Vcs-Git: https://anonscm.debian.org/git/pkg-grass/qgis.git +Vcs-Git: https://anonscm.debian.org/git/pkg-grass/qgis.git -b stretch Homepage: https://qgis.org/ X-Python-Version: >= 2.7, << 2.8 diff -Nru qgis-2.14.11+dfsg/debian/gbp.conf qgis-2.14.11+dfsg/debian/gbp.conf --- qgis-2.14.11+dfsg/debian/gbp.conf 2017-01-25 10:22:19.0 +0100 +++ qgis-2.14.11+dfsg/debian/gbp.conf 2017-03-21 12:49:51.0 +0100 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru qgis-2.14.11+dfsg/debian/patches/grass72.patch qgis-2.14.11+dfsg/debian/patches/grass72.patch --- qgis-2.14.11+dfsg/debian/patches/grass72.patch 1970-01-01 01:00:00.0 +0100 +++ qgis-2.14.11+dfsg/debian/patches/grass72.patch 2017-03-21 12:48:03.0 +0100 @@ -0,0 +1,41 @@ +Description: Add support for GRASS 7.2. +Author: Bas Couwenberg <sebas...@debian.org> +Bug-Debian: https://bugs.debian.org/858251 + +--- a/python/plugins/processing/algs/grass7/Grass7AlgorithmProvider.py b/python/plugins/processing/algs/grass7/Grass7AlgorithmProvider.py +@@ -100,7 +100,7 @@ class Grass7AlgorithmProvider(AlgorithmP + return self.tr('GRASS GIS 7 commands') + + def getName(self): +-return 'grass70' ++return 'grass72' + + def getIcon(self): + return QIcon(os.path.join(pluginPath, 'images', 'grass.svg')) +--- a/python/plugins/processing/algs/grass7/Grass7Utils.py b/python/plugins/processing/algs/grass7/Grass7Utils.py +@@ -77,7 +77,7 @@ class Grass7Utils: + def getGrassVersion(): + # FIXME: I do not know if this should be removed or let the user enter it + # or something like that... This is just a temporary thing +-return '7.0.0' ++return '7.2.0' + + @staticmethod + def grassPath(): +@@ -251,7 +251,7 @@ class Grass7Utils: + command = Grass7Utils.grassPath() + os.sep + 'grass.sh ' \ + + Grass7Utils.grassMapsetFolder() + '/PERMANENT' + else: +-command = 'grass70 ' + Grass7Utils.grassMapsetFolder() \ ++command = 'grass ' + Grass7Utils.grassMapsetFolder() \ + + '/PERMANENT' + + return command, env +@@ -417,4 +417,4 @@ class Grass7Utils: + helpPath = os.path.abspath(path) + break + +-return helpPath if helpPath is not None else 'http://grass.osgeo.org/grass70/manuals/' ++return helpPath if helpPath is not None else 'http://grass.osgeo.org/grass72/manuals/' diff -Nru qgis-2.14.11+dfsg/debian/patches/series qgis-2.14.11+dfsg/debian/patches/series --- qgis-2.14.11+dfsg/debian/patches/series 2017-02-13 18:42:44.0 +0100 +++ qgis-2.14.11+dfsg/debian/patches/series 2017-03-21 12:48:03.0 +0100 @@ -8,3 +8,4 @@ qtermwidget-hurd.patch qt4-without-qtwebkit.patch columns-typo.patch +grass72.patch
Bug#858251: qgis: no access to grass7 algorithms from toolbox
Control: tags -1 pending On 2017-03-21 11:17, Moritz Lennert wrote: However, I think I found the culprit: [...] Changing line 254 to 'grass' and the other two to '7.2.0' and 'grass72' respectively makes GRASS7 processing work for me. Thanks for these pointers, I've added patch with these changes to fix the GRASS 7.2.0 support. New uploads to experimental and unstable with the patch included will follow soon. Kind Regards, Bas
Bug#858218: unblock: openlayers/2.13.1+ds2-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package openlayers. It drops the -doc package which required libjs-jquery-mobile, see the discussion in #734101. unblock openlayers/2.13.1+ds2-4 Kind Regards, Bas diff -Nru openlayers-2.13.1+ds2/debian/changelog openlayers-2.13.1+ds2/debian/changelog --- openlayers-2.13.1+ds2/debian/changelog 2016-05-06 19:03:55.0 +0200 +++ openlayers-2.13.1+ds2/debian/changelog 2017-03-19 21:21:01.0 +0100 @@ -1,3 +1,10 @@ +openlayers (2.13.1+ds2-4) unstable; urgency=medium + + * Drop libjs-openlayers-doc binary package. +See: #734101 (libjs-jquery-mobile not working) + + -- Bas Couwenberg <sebas...@debian.org> Sun, 19 Mar 2017 21:21:01 +0100 + openlayers (2.13.1+ds2-3) unstable; urgency=medium * Update Vcs-Git URL to use HTTPS. diff -Nru openlayers-2.13.1+ds2/debian/control openlayers-2.13.1+ds2/debian/control --- openlayers-2.13.1+ds2/debian/control2016-05-06 19:02:20.0 +0200 +++ openlayers-2.13.1+ds2/debian/control2017-03-19 21:02:41.0 +0100 @@ -6,8 +6,7 @@ Priority: extra Build-Depends: debhelper (>= 9), python -Build-Depends-Indep: node-uglify, - naturaldocs +Build-Depends-Indep: node-uglify Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/openlayers.git Vcs-Git: https://anonscm.debian.org/git/pkg-grass/openlayers.git @@ -25,21 +24,3 @@ geographic applications, similar to the Google Maps and MSN Virtual Earth APIs. -Package: libjs-openlayers-doc -Architecture: all -Section: doc -Depends: libjs-bootstrap, - libjs-jquery, - libjs-jquery-mobile, - ${misc:Depends} -Recommends: libjs-openlayers -Description: documentation for OpenLayers - OpenLayers is a pure JavaScript library for displaying map data in - most modern web browsers, with no server-side dependencies. - . - OpenLayers implements a JavaScript API for building rich web-based - geographic applications, similar to the Google Maps and MSN Virtual - Earth APIs. - . - This package contains documentation and examples of OpenLayers. - diff -Nru openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.doc-base openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.doc-base --- openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.doc-base 2014-12-26 01:41:51.0 +0100 +++ openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.doc-base 1970-01-01 01:00:00.0 +0100 @@ -1,10 +0,0 @@ -Document: openlayers -Title: OpenLayers Documentation -Author: OpenLayers Contributors -Abstract: This manual describes what OpenLayers is - and how it can be used. -Section: Programming/Javascript - -Format: HTML -Index: /usr/share/doc/libjs-openlayers-doc/html/index.html -Files: /usr/share/doc/libjs-openlayers-doc/html/* diff -Nru openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.examples openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.examples --- openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.examples 2014-12-26 01:41:51.0 +0100 +++ openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.examples 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -examples/* diff -Nru openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.install openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.install --- openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.install 2015-03-20 15:05:28.0 +0100 +++ openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.install 1970-01-01 01:00:00.0 +0100 @@ -1,3 +0,0 @@ -gendoc/*/usr/share/doc/libjs-openlayers-doc/html/ -lib/Firebug//usr/share/doc/libjs-openlayers-doc/examples/ -notes/ /usr/share/doc/libjs-openlayers-doc/ diff -Nru openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.links openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.links --- openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.links 2015-12-22 18:09:13.0 +0100 +++ openlayers-2.13.1+ds2/debian/libjs-openlayers-doc.links 1970-01-01 01:00:00.0 +0100 @@ -1,4 +0,0 @@ -usr/share/javascript/bootstrap usr/share/doc/libjs-openlayers-doc/examples/bootstrap -usr/share/javascript/jquery usr/share/doc/libjs-openlayers-doc/examples/jquery -usr/share/javascript/jquery-mobile usr/share/doc/libjs-openlayers-doc/examples/jquery-mobile -usr/share/javascript/openlayers usr/share/doc/libjs-openlayers-doc/examples/openlayers diff -Nru openlayers-2.13.1+ds2/debian/rules openlayers-2.13.1+ds2/debian/rules --- openlayers-2.13.1+ds2/debian/rules 2015-12-22 16:56:07.0 +0100 +++ openlayers-2.13.1+ds2/debian/rules 2017-03-19 21:19:40.0 +0100 @@ -28,22 +28,12 @@ cd build && ./build.py tests.cfg OpenLayers.tests.js uglifyjs -o build/OpenLayers.tests.min.js build/OpenLayers.tests.js - mkdir gendoc - naturaldocs -i lib/ -o HTML gendoc/ -p doc_config/ -s Default OL - -overr
Bug#857180: unblock: libosmium/2.11.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libosmium Upstream has only fixed bugs for this release in line with the freeze policy. unblock libosmium/2.11.1-1 diff -Nru libosmium-2.11.0/CHANGELOG.md libosmium-2.11.1/CHANGELOG.md --- libosmium-2.11.0/CHANGELOG.md 2017-01-14 11:50:34.0 +0100 +++ libosmium-2.11.1/CHANGELOG.md 2017-03-07 13:54:48.0 +0100 @@ -6,12 +6,18 @@ ## [unreleased] - -### Added +### Fixed -### Changed + +## [2.11.1] - 2017-03-07 ### Fixed +- Terminate called on full non-auto-growing buffer. (Issue #189.) +- When file formats were used that were not compiled into the binary, it + terminated instead of throwing. (Issue #197.) +- The `Filter::count()` method didn't compile at all. + ## [2.11.0] - 2017-01-14 @@ -525,7 +531,9 @@ Doxygen (up to version 1.8.8). This version contains a workaround to fix this. -[unreleased]: https://github.com/osmcode/libosmium/compare/v2.10.3...HEAD +[unreleased]: https://github.com/osmcode/libosmium/compare/v2.11.1...HEAD +[2.11.1]: https://github.com/osmcode/libosmium/compare/v2.11.0...v2.11.1 +[2.11.0]: https://github.com/osmcode/libosmium/compare/v2.10.3...v2.11.0 [2.10.3]: https://github.com/osmcode/libosmium/compare/v2.10.2...v2.10.3 [2.10.2]: https://github.com/osmcode/libosmium/compare/v2.10.1...v2.10.2 [2.10.1]: https://github.com/osmcode/libosmium/compare/v2.10.0...v2.10.1 diff -Nru libosmium-2.11.0/CMakeLists.txt libosmium-2.11.1/CMakeLists.txt --- libosmium-2.11.0/CMakeLists.txt 2017-01-14 11:50:34.0 +0100 +++ libosmium-2.11.1/CMakeLists.txt 2017-03-07 13:54:48.0 +0100 @@ -25,7 +25,7 @@ set(LIBOSMIUM_VERSION_MAJOR 2) set(LIBOSMIUM_VERSION_MINOR 11) -set(LIBOSMIUM_VERSION_PATCH 0) +set(LIBOSMIUM_VERSION_PATCH 1) set(LIBOSMIUM_VERSION "${LIBOSMIUM_VERSION_MAJOR}.${LIBOSMIUM_VERSION_MINOR}.${LIBOSMIUM_VERSION_PATCH}") diff -Nru libosmium-2.11.0/debian/changelog libosmium-2.11.1/debian/changelog --- libosmium-2.11.0/debian/changelog 2017-01-17 18:29:43.0 +0100 +++ libosmium-2.11.1/debian/changelog 2017-03-07 18:31:00.0 +0100 @@ -1,3 +1,17 @@ +libosmium (2.11.1-1) unstable; urgency=medium + + * New upstream bugfix release. +- Fix the Filter::count() method. +- Bugfix: Terminate called on full buffer. + See: https://github.com/osmcode/libosmium/issues/189 +- Add test for not correctly handled unsupported_file_format_error. + See: https://github.com/osmcode/libosmium/issues/197 +- Bugfix: Call get_creator_function() in main thread. + See: https://github.com/osmcode/libosmium/issues/197 + * Update gbp.conf to use upstream-2.11 branch. + + -- Bas Couwenberg <sebas...@debian.org> Tue, 07 Mar 2017 18:31:00 +0100 + libosmium (2.11.0-1) unstable; urgency=medium * Move from experimental to unstable. diff -Nru libosmium-2.11.0/debian/gbp.conf libosmium-2.11.1/debian/gbp.conf --- libosmium-2.11.0/debian/gbp.conf2016-11-26 10:23:21.0 +0100 +++ libosmium-2.11.1/debian/gbp.conf2017-03-07 18:31:00.0 +0100 @@ -2,7 +2,7 @@ # The default name for the upstream branch is "upstream". # Change it if the name is different (for instance, "master"). -upstream-branch = upstream +upstream-branch = upstream-2.11 # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). diff -Nru libosmium-2.11.0/include/osmium/builder/builder.hpp libosmium-2.11.1/include/osmium/builder/builder.hpp --- libosmium-2.11.0/include/osmium/builder/builder.hpp 2017-01-14 11:50:34.0 +0100 +++ libosmium-2.11.1/include/osmium/builder/builder.hpp 2017-03-07 13:54:48.0 +0100 @@ -168,6 +168,20 @@ } /** + * Append data to buffer and append an additional \0. + * + * @param data Pointer to data. + * @param length Length of data in bytes. + * @returns The number of bytes appended (length + 1). + */ +osmium::memory::item_size_type append_with_zero(const char* data, const osmium::memory::item_size_type length) { +unsigned char* target = reserve_space(length + 1); +std::copy_n(reinterpret_cast(data), length, target); +target[length] = '\0'; +return length + 1; +} + +/** * Append \0-terminated string to buffer. * * @param str \0-terminated string. @@ -180,9 +194,11 @@ /** * Append '\0' to the buffer. * + * @deprecated Use append_with_zero() instead. + * * @returns The number of bytes appended (always 1). */ -osmium::memory::item_size_type append_zero() { +
Bug#856472: gdal-bin: SrcDataSource ODBC Segmentation fault
On 2017-03-02 12:38, Andy G Wood wrote: Can you also provide a minimal test case to reproduce the issue on a system which doesn't have your ODBC data source configured? The system which exhibits the problem is using an Oracle 11g ODBC driver (testing this outside of gdal shows no problems). The following builds a test case with sqlite, but unfortunately this works fine! The sqlite test case also works fine for me, and based on your stacktrace it looks like an issue in the Oracle libsqora library, not GDAL. Maybe you can update the Oracle library? Kind Regards, Bas
Bug#856472: gdal-bin: SrcDataSource ODBC Segmentation fault
Hi Andy, On 2017-03-02 12:38, Andy G Wood wrote: Can you install the gdal-bin-dbgsym & libgdal20-dbgsym packages an run the ogrinfo command via gdb to get a backtrace? There does not appear to be an amd64 architecture version of these packages, so I am a bit stuck with this? The automatic debug packages are available in separate repositories which you need to add to your /etc/apt/sources.list, see: https://wiki.debian.org/DebugPackage For stretch the sources.list entry would be: deb http://debug.mirrors.debian.org/debian-debug/ stretch-debug main contrib non-free Can you also provide a minimal test case to reproduce the issue on a system which doesn't have your ODBC data source configured? The system which exhibits the problem is using an Oracle 11g ODBC driver (testing this outside of gdal shows no problems). The following builds a test case with sqlite, but unfortunately this works fine! Thanks for the repro, I'll give it a go after I get back from $DAYJOB later today. Kind Regards, Bas
Bug#855170: unblock: mapserver/7.0.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mapserver The attached debdiff contains two patches. The first fixes a DoS and was reported to me privately by Landry Breuil. The second is not strictly required for unstable, it fixes a FTBFS issue with PHP 5. It is required for the OSGeo-Live derivative which uses the source package maintained in Debian. unblock mapserver/7.0.4-2 Kind Regards, Bas diff -Nru mapserver-7.0.4/debian/changelog mapserver-7.0.4/debian/changelog --- mapserver-7.0.4/debian/changelog2017-01-16 19:38:29.0 +0100 +++ mapserver-7.0.4/debian/changelog2017-02-14 18:29:54.0 +0100 @@ -1,3 +1,11 @@ +mapserver (7.0.4-2) unstable; urgency=medium + + * Add patch to use include paths from php-config. + * Add patch by Landry Breuil to fix memory corruption/double-free +when LAYERS parameter is specified multiple times. + + -- Bas Couwenberg <sebas...@debian.org> Tue, 14 Feb 2017 18:29:54 +0100 + mapserver (7.0.4-1) unstable; urgency=high * New upstream release. diff -Nru mapserver-7.0.4/debian/patches/0001-Declare-nLayerOrder-where-it-s-used.-5387.patch mapserver-7.0.4/debian/patches/0001-Declare-nLayerOrder-where-it-s-used.-5387.patch --- mapserver-7.0.4/debian/patches/0001-Declare-nLayerOrder-where-it-s-used.-5387.patch 1970-01-01 01:00:00.0 +0100 +++ mapserver-7.0.4/debian/patches/0001-Declare-nLayerOrder-where-it-s-used.-5387.patch 2017-02-14 18:23:46.0 +0100 @@ -0,0 +1,25 @@ +Description: Declare nLayerOrder where it's used. + If LAYERS is specified multiple times in the query string, nLayerOrder isnt + reset to 0, and this leads to memory corruption/double-free's upon exit. +Author: Landry Breuil <bre...@craig.fr> +Origin: https://github.com/mapserver/mapserver/commit/132695864b27bb6fced9a866f35365f445889a00 +Bug: https://github.com/mapserver/mapserver/issues/5387 + +--- a/mapwms.c b/mapwms.c +@@ -791,7 +791,6 @@ int msWMSLoadGetMapParams(mapObj *map, i + const char *wms_request, owsRequestObj *ows_request) + { + int i, adjust_extent = MS_FALSE, nonsquare_enabled = MS_FALSE; +- int nLayerOrder = 0; + int transparent = MS_NOOVERRIDE; + int bbox_pixel_is_point = MS_FALSE; + outputFormatObj *format = NULL; +@@ -870,6 +869,7 @@ int msWMSLoadGetMapParams(mapObj *map, i + + if (strcasecmp(names[i], "LAYERS") == 0) { + int j, k, iLayer, *layerOrder; ++ int nLayerOrder = 0; + char ***nestedGroups = NULL; + int *numNestedGroups = NULL; + int *isUsedInNestedGroup = NULL; diff -Nru mapserver-7.0.4/debian/patches/php-mapscript.patch mapserver-7.0.4/debian/patches/php-mapscript.patch --- mapserver-7.0.4/debian/patches/php-mapscript.patch 1970-01-01 01:00:00.0 +0100 +++ mapserver-7.0.4/debian/patches/php-mapscript.patch 2017-02-14 18:24:48.0 +0100 @@ -0,0 +1,18 @@ +Description: Use include paths from php-config when include path not found. +Author: Bas Couwenberg <sebas...@debian.org> +Forwarded: https://github.com/mapserver/mapserver/pull/5370 +Applied-Upstream: https://github.com/mapserver/mapserver/commit/37a70fff4ab54f12619833414cb1995643f7a10d + +--- a/cmake/FindPHP5.cmake b/cmake/FindPHP5.cmake +@@ -86,6 +86,10 @@ IF(PHP5_CONFIG_EXECUTABLE) + + MESSAGE(STATUS ${PHP5_MAIN_INCLUDE_DIR}) + ++ IF(NOT PHP5_INCLUDE_PATH) ++set(PHP5_INCLUDE_PATH ${PHP5_INCLUDES}) ++ ENDIF(NOT PHP5_INCLUDE_PATH) ++ + IF(PHP5_VERSION LESS 5) + MESSAGE(FATAL_ERROR "PHP version is not 5 or later") + ENDIF(PHP5_VERSION LESS 5) diff -Nru mapserver-7.0.4/debian/patches/series mapserver-7.0.4/debian/patches/series --- mapserver-7.0.4/debian/patches/series 2017-01-07 11:15:20.0 +0100 +++ mapserver-7.0.4/debian/patches/series 2017-02-14 18:23:42.0 +0100 @@ -2,3 +2,5 @@ perl-mapscript-install.patch ruby-mapscript-install.patch java-hardening.patch +php-mapscript.patch +0001-Declare-nLayerOrder-where-it-s-used.-5387.patch
Bug#855084: unblock: qgis/2.14.11+dfsg-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package qgis It fixes possible upgrade issues reported in #855048 by adding Breaks/Replaces. unblock qgis/2.14.11+dfsg-2 Kind Regards, Bas diff -Nru qgis-2.14.11+dfsg/debian/changelog qgis-2.14.11+dfsg/debian/changelog --- qgis-2.14.11+dfsg/debian/changelog 2017-01-14 09:39:46.0 +0100 +++ qgis-2.14.11+dfsg/debian/changelog 2017-02-13 18:43:07.0 +0100 @@ -1,3 +1,10 @@ +qgis (2.14.11+dfsg-2) unstable; urgency=medium + + * Add Breaks/Replaces on python-qt4 for QtWebKit. +(closes: #855048) + + -- Bas Couwenberg <sebas...@debian.org> Mon, 13 Feb 2017 18:43:07 +0100 + qgis (2.14.11+dfsg-1) unstable; urgency=medium * Update symbols for other architectures. diff -Nru qgis-2.14.11+dfsg/debian/control qgis-2.14.11+dfsg/debian/control --- qgis-2.14.11+dfsg/debian/control2017-01-13 14:22:35.0 +0100 +++ qgis-2.14.11+dfsg/debian/control2017-02-13 18:37:20.0 +0100 @@ -360,7 +360,9 @@ ${misc:Depends}, ${sip:Depends} Recommends: liblwgeom-dev +Breaks: python-qt4 (<< 4.11.4+dfsg-2) Provides: ${python:Provides} +Replaces: python-qt4 (<< 4.11.4+dfsg-2) Description: Python bindings to QGIS QGIS is a Geographic Information System (GIS) which manages, analyzes and display databases of geographic information.
Bug#855048: qgis: Ships an unsupported copy of QtWebkit in public Python path without any transition
Control: severity -1 important On 2017-02-13 15:57, Raphaël Hertzog wrote: python-qt4 dropped support for QtWebkit it's because it was not possible to provide security support for it (cf #784514). You disabled that support in response to that bug. But later you decided to re-enable it using an embedded copy, the net result is that python-qgis is now shipping files that used to be shipped by python-qt4: /usr/lib/python2.7/dist-packages/PyQt4/QtWebKit.x86_64-linux-gnu.so Yes, because QGIS without QtWebKit loses most plugins and other functionality demanded by users. There are two problems: 1/ the upgrade is not safe, you can have conflicts with python-qt4 if python-qgis is upgraded before python-qt4 (even more likely in Kali where we kept QtWebkit a while longer in python-qt4) Adding Breaks/Replaces is no problem. 2/ if QtWebkit cannot be suppported in python-qt4, it also cannot be supported in python-qgis It doesn't have to be supported to be included. IMO you should disable that embedded copy usage or at least get a prior ack from the security team. NAK, the QtWebKit support stays as it's in the interest of our users. Upstream added the QtWebKit support for Python because the C++ package (qtwebkit) is still available and only the in development 3.x branch of QGIS has support for Qt5. The debian-security-support package already warns about no security support for qtwebkit so that doesn't change anything wrt QtWebKit support in QGIS. Kind Regards, Bas
Bug#854028: unblock: svgsalamander/1.1.1+dfsg-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package svgsalamander It contains a patch by Vincent Privat to fix CVE-2017-5617 (#853134). unblock svgsalamander/1.1.1+dfsg-2 Kind Regards, Bas diff -Nru svgsalamander-1.1.1+dfsg/debian/changelog svgsalamander-1.1.1+dfsg/debian/changelog --- svgsalamander-1.1.1+dfsg/debian/changelog 2016-08-22 08:31:39.0 +0200 +++ svgsalamander-1.1.1+dfsg/debian/changelog 2017-02-03 08:39:45.0 +0100 @@ -1,3 +1,11 @@ +svgsalamander (1.1.1+dfsg-2) unstable; urgency=medium + + * Team upload. + * Add patch by Vincent Privat to fix CVE-2017-5617 (SSRF). +(closes: #853134) + + -- Bas Couwenberg <sebas...@debian.org> Fri, 03 Feb 2017 08:39:45 +0100 + svgsalamander (1.1.1+dfsg-1) unstable; urgency=medium * Team upload. diff -Nru svgsalamander-1.1.1+dfsg/debian/patches/0007-CVE-2017-5617-Allow-only-data-scheme.patch svgsalamander-1.1.1+dfsg/debian/patches/0007-CVE-2017-5617-Allow-only-data-scheme.patch --- svgsalamander-1.1.1+dfsg/debian/patches/0007-CVE-2017-5617-Allow-only-data-scheme.patch 1970-01-01 01:00:00.0 +0100 +++ svgsalamander-1.1.1+dfsg/debian/patches/0007-CVE-2017-5617-Allow-only-data-scheme.patch 2017-02-02 07:34:34.0 +0100 @@ -0,0 +1,109 @@ +Description: Fix CVE-2017-5617: svgSalamander SSRF (Server-Side Request Forgery) + See: http://www.openwall.com/lists/oss-security/2017/01/27/3 +Author: Vincent Privat +Origin: https://josm.openstreetmap.de/changeset/11526/josm +Bug: https://github.com/blackears/svgSalamander/issues/11 +Bug-Debian: https://bugs.debian.org/853134 + +--- a/svg-core/src/main/java/com/kitfox/svg/ImageSVG.java b/svg-core/src/main/java/com/kitfox/svg/ImageSVG.java +@@ -112,21 +112,10 @@ public class ImageSVG extends Renderable + if (getPres(sty.setName("xlink:href"))) + { + URI src = sty.getURIValue(getXMLBase()); ++// CVE-2017-5617: Allow only data scheme + if ("data".equals(src.getScheme())) + { + imageSrc = new URL(null, src.toASCIIString(), new Handler()); +-} else +-{ +-try +-{ +-imageSrc = src.toURL(); +-} catch (Exception e) +-{ +- Logger.getLogger(SVGConst.SVG_LOGGER).log(Level.WARNING, +-"Could not parse xlink:href " + src, e); +-//e.printStackTrace(); +-imageSrc = null; +-} + } + } + } catch (Exception e) +@@ -134,32 +123,33 @@ public class ImageSVG extends Renderable + throw new SVGException(e); + } + +-diagram.getUniverse().registerImage(imageSrc); +- +-//Set widths if not set +-BufferedImage img = diagram.getUniverse().getImage(imageSrc); +-if (img == null) ++if (imageSrc != null) + { +-xform = new AffineTransform(); +-bounds = new Rectangle2D.Float(); +-return; +-} ++diagram.getUniverse().registerImage(imageSrc); + +-if (width == 0) +-{ +-width = img.getWidth(); +-} +-if (height == 0) +-{ +-height = img.getHeight(); +-} ++//Set widths if not set ++BufferedImage img = diagram.getUniverse().getImage(imageSrc); ++if (img == null) ++{ ++xform = new AffineTransform(); ++bounds = new Rectangle2D.Float(); ++return; ++} + +-//Determine image xform +-xform = new AffineTransform(); +-//xform.setToScale(this.width / img.getWidth(), this.height / img.getHeight()); +-//xform.translate(this.x, this.y); +-xform.translate(this.x, this.y); +-xform.scale(this.width / img.getWidth(), this.height / img.getHeight()); ++if (width == 0) ++{ ++width = img.getWidth(); ++} ++if (height == 0) ++{ ++height = img.getHeight(); ++} ++ ++//Determine image xform ++xform = new AffineTransform(); ++xform.translate(this.x, this.y); ++xform.scale(this.width / img.getWidth(), this.height / img.getHeight()); ++} + + bounds = new Rectangle2D.Float(this.x, this.y, this.width, this.height); + } +@@ -328,16 +318,14 @@ public class ImageSVG extends Renderable + { + URI src = sty.getURIValue(getXMLBase()); + +-URL newVal; ++URL newVal = null; ++// CVE-2017-5617: Allow only data scheme +
Bug#854023: unblock: gdal/2.1.2+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gdal The only change is the fix for #853900 _gdal_array ImportError with Python 3. unblock gdal/2.1.2+dfsg-3 Kind Regards, Bas diff -Nru gdal-2.1.2+dfsg/debian/changelog gdal-2.1.2+dfsg/debian/changelog --- gdal-2.1.2+dfsg/debian/changelog2016-11-09 18:38:03.0 +0100 +++ gdal-2.1.2+dfsg/debian/changelog2017-02-02 20:15:59.0 +0100 @@ -1,3 +1,10 @@ +gdal (2.1.2+dfsg-3) unstable; urgency=medium + + * Add upstream patch to fix _gdal_array ImportError with Python 3. +(closes: #853900) + + -- Bas Couwenberg <sebas...@debian.org> Thu, 02 Feb 2017 20:15:59 +0100 + gdal (2.1.2+dfsg-2) unstable; urgency=medium * Add upstream patch to fix crash on URLs that are not DODS servers. diff -Nru gdal-2.1.2+dfsg/debian/patches/python3-import-gdal_array.patch gdal-2.1.2+dfsg/debian/patches/python3-import-gdal_array.patch --- gdal-2.1.2+dfsg/debian/patches/python3-import-gdal_array.patch 1970-01-01 01:00:00.0 +0100 +++ gdal-2.1.2+dfsg/debian/patches/python3-import-gdal_array.patch 2017-02-02 20:14:31.0 +0100 @@ -0,0 +1,28 @@ +Description: Python bindings: fix 'import osgeo.gdal_array' with python3 and SWIG 3.0.10 +Author: Even Rouault +Origin: https://trac.osgeo.org/gdal/changeset/37277 +Bug: https://trac.osgeo.org/gdal/ticket/6801 +Bug-Debian: https://bugs.debian.org/853900 + +--- a/swig/include/gdal_array.i b/swig/include/gdal_array.i +@@ -994,7 +994,7 @@ retStringAndCPLFree* GetArrayFilename(Py + + %pythoncode %{ + import numpy +-import _gdal_array ++from . import _gdal_array + + import gdalconst + import gdal +--- a/swig/python/osgeo/gdal_array.py b/swig/python/osgeo/gdal_array.py +@@ -145,7 +145,7 @@ def RATValuesIONumPyRead(*args, **kwargs + return _gdal_array.RATValuesIONumPyRead(*args, **kwargs) + RATValuesIONumPyRead = _gdal_array.RATValuesIONumPyRead + import numpy +-import _gdal_array ++from . import _gdal_array + + import gdalconst + import gdal diff -Nru gdal-2.1.2+dfsg/debian/patches/series gdal-2.1.2+dfsg/debian/patches/series --- gdal-2.1.2+dfsg/debian/patches/series 2016-11-09 18:31:25.0 +0100 +++ gdal-2.1.2+dfsg/debian/patches/series 2017-02-02 20:15:40.0 +0100 @@ -11,3 +11,4 @@ sort-files-in-static-library.patch spelling-errors.patch svn-r36175-DODS-fix-crash-on-URL-that-are-not-DODS-servers.patch +python3-import-gdal_array.patch
Bug#853134: CVE-2017-5617: svgSalamander
On 2017-02-01 09:35, Bas Couwenberg wrote: Including the JOSM developers (josm-...@openstreetmap.org) is also a good idea, they (and Vincent Privat in particular) have contributed patches to svgSalamander recently. I'll report the issue in the JOSM Trac since it also affects the embedded copy in their upstream SVN repo. JOSM issue: https://josm.openstreetmap.de/ticket/14319 Kind Regards, Bas
Bug#853134: CVE-2017-5617: svgSalamander
Hi Felix, On 2017-02-01 09:13, Felix Natter wrote: there is a security vulnerability in svgSalamander: https://github.com/blackears/svgSalamander/issues/11 I've been following that issue since it popped up on by DMD TODO list. The problem occurs when including raster/svg images via . The reporter says "How to fix - any schemes apart from data in the xlink:href attribute should be disallowed" The fix for svgSalamander is probably to patch the code which handles xlink:href and return NULL for any value that doesn't start with "data:", or something along those lines. --> I am not aware of svgSalamander properties (the only other toggle I can think of is java system properties), so can we _disable_ other schemes? I don't think that breaks SVG renderding in Freeplane, how about josm / other applications? I don't know if it will break JOSM, but I suspect it won't. We'll have to test it with the patched svgsalamander when it's available. http://stackoverflow.com/questions/6249664/does-svg-support-embedding-of-bitmap-images --> data: schema seems provides a way for including base64 encoded raster/svg images inline in an SVG. --> Can we discuss how to fix this? Sure, ideally upstream is included in that discussion. Or shall we wait until Mark (the upstream author) fixes this (might take a month)? Or at least ping him for a solution? Pinging him is a good idea, upstream needs to be involved in resolving this issue. Including the JOSM developers (josm-...@openstreetmap.org) is also a good idea, they (and Vincent Privat in particular) have contributed patches to svgSalamander recently. I'll report the issue in the JOSM Trac since it also affects the embedded copy in their upstream SVN repo. Kind Regards, Bas
Bug#848634: python-cartopy: FTBFS on *i386: test_lambert_azimuthal_equal_area fails
On 2017-01-31 11:57, Ghislain Vaillant wrote: Reassigning this bug to src:proj, following Aaron's investigation. On Thu, 26 Jan 2017 11:34:40 -0500 u...@debian.org (Aaron M. Ucko) wrote: Ghislain Vaillantwrites: > So, you think it would help to request src:proj to be build with > -ffloat-store then? Yes; testing in a personal chroot confirms that adjusting its build settings is both necessary and sufficient. (I don't recommend turning this flag on blindly.) I'm not sure if this is desirable in proj, I think PROJ.4 is among "most programs" for which "the excess precision does only good". It's probably better to make test_lambert_azimuthal_equal_area less strict. The impact of this change in proj affects many reverse dependencies and users due to its central role in the geospatial ecosystem. I'll need to discuss this with PROJ.4 upstream before I can consider incorporating the suggested change in the proj package. If you need to fix the test_lambert_azimuthal_equal_area failure for python-cartopy to be included in stretch, you'll need to handle this in the that package since the discussion with upstream won't reach a conclusion before the hard freeze next Sunday (when many of us will be at FOSDEM). Kind Regards, Bas
Bug#853047: unblock: pysal/1.13.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pysal It contains an upstream patch to fix #848783 (FTBFS with NumPy 1.12), instead of just ignoring the test failure. unblock pysal/1.13.0-3 Kind Regards, Bas diff -Nru pysal-1.13.0/debian/changelog pysal-1.13.0/debian/changelog --- pysal-1.13.0/debian/changelog 2016-12-19 22:45:24.0 +0100 +++ pysal-1.13.0/debian/changelog 2017-01-28 12:38:13.0 +0100 @@ -1,3 +1,12 @@ +pysal (1.13.0-3) unstable; urgency=medium + + * Team upload. + * Add upstream patch to fix FTBFS with NumPy 1.12. +(closes: #848783) + * Don't ignore test failures, numpy compatibility has been fixed. + + -- Bas Couwenberg <sebas...@debian.org> Sat, 28 Jan 2017 12:38:13 +0100 + pysal (1.13.0-2) unstable; urgency=medium * Team upload. diff -Nru pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch --- pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch 1970-01-01 01:00:00.0 +0100 +++ pysal-1.13.0/debian/patches/fix-for-numpy-bump-induced-breakage.patch 2017-01-28 12:36:03.0 +0100 @@ -0,0 +1,346 @@ +Description: Fix for numpy bump induced breakage. + - casting index to int + - casting to ints + - fix for numpy bump (casting and reshape behavior) +Author: Serge Rey <sjs...@gmail.com> +Bug: https://github.com/pysal/pysal/issues/896 +Bug-Debian: https://bugs.debian.org/848783 + +--- a/pysal/esda/smoothing.py b/pysal/esda/smoothing.py +@@ -555,11 +555,11 @@ def assuncao_rate(e, b): + class _Smoother(object): + """ + This is a helper class that implements things that all smoothers should do. +-Right now, the only thing that we need to propagate is the by_col function. ++Right now, the only thing that we need to propagate is the by_col function. + + TBQH, most of these smoothers should be functions, not classes (aside from + maybe headbanging triples), since they're literally only inits + one +-attribute. ++attribute. + """ + def __init__(self): + pass +@@ -567,7 +567,7 @@ class _Smoother(object): + @classmethod + def by_col(cls, df, e,b, inplace=False, **kwargs): + """ +-Compute smoothing by columns in a dataframe. ++Compute smoothing by columns in a dataframe. + + Parameters + --- +@@ -582,15 +582,15 @@ class _Smoother(object): + inplace : bool +a flag denoting whether to output a copy of `df` with the +relevant smoothed columns appended, or to append the columns +- directly to `df` itself. ++ directly to `df` itself. + **kwargs: optional keyword arguments +optional keyword options that are passed directly to the +- smoother. ++ smoother. + + Returns + - + a copy of `df` containing the columns. Or, if `inplace`, this returns +-None, but implicitly adds columns to `df`. ++None, but implicitly adds columns to `df`. + """ + if not inplace: + new = df.copy() +@@ -718,13 +718,13 @@ class Empirical_Bayes(_Smoother): + class _Spatial_Smoother(_Smoother): + """ + This is a helper class that implements things that all the things that +-spatial smoothers should do. ++spatial smoothers should do. + . +-Right now, the only thing that we need to propagate is the by_col function. ++Right now, the only thing that we need to propagate is the by_col function. + + TBQH, most of these smoothers should be functions, not classes (aside from + maybe headbanging triples), since they're literally only inits + one +-attribute. ++attribute. + """ + def __init__(self): + pass +@@ -732,7 +732,7 @@ class _Spatial_Smoother(_Smoother): + @classmethod + def by_col(cls, df, e,b, w=None, inplace=False, **kwargs): + """ +-Compute smoothing by columns in a dataframe. ++Compute smoothing by columns in a dataframe. + + Parameters + --- +@@ -748,19 +748,19 @@ class _Spatial_Smoother(_Smoother): +the spatial weights object or objects to use with the +event-population pairs. If not provided and a weights object +is in the dataframe's metadata, that weights object will be +- used. ++ used. + inplace : bool +a flag denoting whether to output a copy of `df` with the +relevant smoothed columns appended, or to append the columns +- di
Bug#852932: unblock: libmodule-corelist-perl/5.20170120-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock/age package libmodule-corelist-perl to allow perl and mapserver to migrate to testing. mapserver (7.0.4-1) fixes CVE-2017-5522 and was aged via #851781. unblock libmodule-corelist-perl/5.20170120-1 Kind Regards, Bas
Bug#851781: unblock: mapserver/7.0.4-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mapserver, it fixes CVE-2017-5522. unblock mapserver/7.0.4-1 Aging it should be sufficient too. Kind Regards, Bas
Bug#850848: RM: pgrouting [mips mips64el mipsel] -- ROM; unsatisfiable Depends on mips* (outdated postgis packages)
Package: ftp.debian.org Severity: normal Please remove pgrouting from mips*, the latest builds picked up outdated postgis dependencies which should have been removed (#847756). Kind Regards, Bas
Bug#850593: RM: openstreetmap-map-icons -- ROM; obsolete, OSM SVN icons now maintained within JOSM
Package: ftp.debian.org Severity: normal Please remove the openstreetmap-map-icons packages from the archive, the map-icons from the OpenStreetMap SVN have been integrated into JOSM. The josm package no longer depends on openstreetmap-map-icons packages, and no other packages use the openstreetmap-map-icons packages either. Kind Regards, Bas
Bug#849910: RM: gmt-tutorial -- ROM; RC buggy, obsoleted by gmt-doc
Package: ftp.debian.org Severity: normal Please remove the gmt-tutorial package from the archive. It is unmaintained, RC buggy, and obsoleted by gmt-doc. Kind Regards, Bas
Bug#849323: icinga: FTBFS with -Wl,-Bsymbolic-functions
Source: icinga Version: 1.13.4-1 Severity: normal Tags: patch Dear Maintainer, icinga (1.13.4-1) FTBFS on Ubuntu because they include -Wl,-Bsymbolic-functions in LDFLAGS. [0] The attached patch strips -Wl,-Bsymbolic-functions from LDFLAGS which should resolve this issue. [0] https://launchpadlibrarian.net/299806145/buildlog_ubuntu-zesty-amd64.icinga_1.13.4-1_BUILDING.txt.gz Kind Regards, Bas >From 78c328f4a09bb6982417a4eeefb1fdc50ec08cc9 Mon Sep 17 00:00:00 2001 From: Bas Couwenberg <sebas...@xs4all.nl> Date: Sun, 25 Dec 2016 14:49:44 +0100 Subject: Strip -Bsymbolic-functions from LDFLAGS, causes FTBFS on Ubuntu. --- debian/changelog | 6 ++ debian/rules | 2 ++ 2 files changed, 8 insertions(+) diff --git a/debian/changelog b/debian/changelog index 10a3edf..2f36682 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +icinga (1.13.4-2) UNRELEASED; urgency=medium + + * Strip -Bsymbolic-functions from LDFLAGS, causes FTBFS on Ubuntu. + + -- Bas Couwenberg <sebas...@debian.org> Sun, 25 Dec 2016 14:49:10 +0100 + icinga (1.13.4-1) unstable; urgency=high * Team upload. diff --git a/debian/rules b/debian/rules index ce5d1af..f974e88 100755 --- a/debian/rules +++ b/debian/rules @@ -6,6 +6,8 @@ # Enable hardening build flags export DEB_BUILD_MAINT_OPTIONS=hardening=+all +export DEB_LDFLAGS_STRIP="-Wl,-Bsymbolic-functions" + export AUTOHEADER=true b := $(shell pwd)/debian -- 2.1.4
Bug#849283: ITP: php-geos -- GEOS bindings for PHP
Package: wnpp Severity: wishlist Owner: Bas Couwenberg <sebas...@debian.org> * Package name: php-geos Version : 1.0.0 Upstream Author : GEOS Developers <geos-de...@lists.osgeo.org> * URL : https://git.osgeo.org/gogs/geos/php-geos/ * License : Expat Programming Lang: PHP & C Description : GEOS bindings for PHP GEOS provides a spatial object model and fundamental geometric functions. It implements the geometry model defined in the OpenGIS Consortium Simple Features Specification for SQL. This package contains the PHP bindings for GEOS. The package will be maintained within the Debian GIS team along with GEOS.
Bug#849200: nagios-images: Outdated packaging
Source: nagios-images Version: 0.8 Severity: normal Tags: patch Dear Maintainer, The packaging for nagios-images is outdated as reported by lintian. An ancient Standards-Version is used, and an extra-license-file false positive is not addressed. The package also installs symlinks for nagios3 which has been removed from unstable. The attached patches resolve this issue. Kind Regards, Bas >From b55b14fc2910e73afefcf6b6a835a296479499ca Mon Sep 17 00:00:00 2001 From: Bas Couwenberg <sebas...@xs4all.nl> Date: Fri, 23 Dec 2016 15:07:45 +0100 Subject: Update Vcs-* URLs for move to git. --- debian/changelog | 1 + debian/control | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index 881be09..02b0bbb 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,6 +2,7 @@ nagios-images (0.9) UNRELEASED; urgency=medium * Team upload. * Restructure control file with cme. + * Update Vcs-* URLs for move to git. -- Bas Couwenberg <sebas...@debian.org> Fri, 23 Dec 2016 15:06:34 +0100 diff --git a/debian/control b/debian/control index 2b1a4eb..511961c 100644 --- a/debian/control +++ b/debian/control @@ -6,8 +6,8 @@ Section: net Priority: optional Build-Depends: debhelper (>= 9) Standards-Version: 3.9.4 -Vcs-Browser: http://anonscm.debian.org/viewvc/pkg-nagios/nagios-images/ -Vcs-Svn: svn://anonscm.debian.org/pkg-nagios/nagios-images/trunk/ +Vcs-Browser: https://anonscm.debian.org/cgit/pkg-nagios/pkg-nagios-images.git +Vcs-Svn: https://anonscm.debian.org/git/pkg-nagios/pkg-nagios-images.git Package: nagios-images Architecture: all -- 2.1.4 >From cef9fb3b739c506e1a0b043b42016deb46c60cdd Mon Sep 17 00:00:00 2001 From: Bas Couwenberg <sebas...@xs4all.nl> Date: Fri, 23 Dec 2016 15:13:16 +0100 Subject: Update copyright file using copyright-format 1.0. --- debian/changelog | 1 + debian/copyright | 56 2 files changed, 29 insertions(+), 28 deletions(-) diff --git a/debian/changelog b/debian/changelog index c94259e..eb3d9df 100644 --- a/debian/changelog +++ b/debian/changelog @@ -4,6 +4,7 @@ nagios-images (0.9) UNRELEASED; urgency=medium * Restructure control file with cme. * Update Vcs-* URLs for move to git. * Enable parallel builds. + * Update copyright file using copyright-format 1.0. -- Bas Couwenberg <sebas...@debian.org> Fri, 23 Dec 2016 15:06:34 +0100 diff --git a/debian/copyright b/debian/copyright index a4f2a2b..4b640ee 100644 --- a/debian/copyright +++ b/debian/copyright @@ -1,30 +1,30 @@ -Format-Specification: http://wiki.debian.org/Proposals/CopyrightFormat?action=recall=196 -Packaged-By: Debian Nagios Maintainer Group <pkg-nagios-de...@lists.alioth.debian.org> -Packaged-Date: Thu, 6 Oct 2005 19:12:42 +0200 -Upstream-Source: ftp://ftp.debian.org/dists/unstable/main/source/ +Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Upstream-Contact: Debian Nagios Maintainer Group <pkg-nagios-de...@lists.alioth.debian.org> +Source: https://anonscm.debian.org/cgit/pkg-nagios/pkg-nagios-images.git -Copyright (C) 2005 Debian Nagios Maintainer Group -Copyright Bernhard Albler <balb...@nts.at> -Copyright Cook Garry <gwc...@mactec.com> -Copyright Didier LIROULET <didier.lirou...@tiscali.fr> -Copyright Brad Werschler <bwersch...@sjsd.net> -Copyright Altinity <http://www.altinity.com/nagiosdownloads> +Files: * +Copyright: 2005, Debian Nagios Maintainer Group + Bernhard Albler <balb...@nts.at> + Cook Garry <gwc...@mactec.com> + Didier LIROULET <didier.lirou...@tiscali.fr> + Brad Werschler <bwersch...@sjsd.net> + Altinity <http://www.altinity.com/nagiosdownloads> +License: GPL-2+ -License: - - 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 2 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 package; if not, write to the Free Software - Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - -On Debian systems, the complete text of the GNU General -Public License can be found in `/usr/share/common-licenses/GPL'. +License: GPL-2+ + 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 2 of the License, or + (at your option) a
Bug#849188: libmonitoring-livestatus-perl: VCS repository listed in the package does not exist
Source: libmonitoring-livestatus-perl Version: 0.74-1 Severity: normal Dear Maintainer, The VCS repository listed in the package does not exist on ALioth: git://git.debian.org/pkg-nagios/pkg-libmonitoring-livestatus-perl.git Please create the repository and push your local changes to Alioth. Kind Regards, Bas
Bug#848688: [Pkg-nagios-devel] Bug#848688: 848688 / ftbfs on mips should be RC, no?
On 2016-12-20 12:07, Holger Levsen wrote: shouldnt this bug be severity:serious? Not being able to build on mips* is a regression, so this is a blocker for getting icinga2 back into testing… To get icinga2 back into testing I suggest to file RM bugreports for icinga2 on the problematic arm* & mips* architectures, and downgrade the severity of the FTBFS bugreports to important. Unless icinga2 is actually used on those architectures. Kind Regards, Bas