Bug#915823: marked as done (nmu: ossim_2.6.0-1)

2018-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 7 Dec 2018 07:49:37 +0100 with message-id <6f72a72f-bf95-20cf-d3a7-5b410ca3d...@xs4all.nl> and subject line Re: Bug#915823: Acknowledgement (nmu: ossim_2.6.0-1) has caused the Debian Bug report #915823, regarding nmu: ossim_2.6.0-1 to be marked as done. This means that you

Processed: block 913837 with 915207

2018-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 913837 with 915207 Bug #913837 [release.debian.org] transition: hdf5 913837 was blocked by: 915207 914493 913837 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #913837 to the same blocks previously set > thanks St

Bug#915823: nmu: ossim_2.6.0-1

2018-12-06 Thread Bas Couwenberg
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please rebuild ossim with the new geos in unstable: nmu ossim_2.6.0-1 . ANY . unstable . -m "Rebuild with libgeos++-dev (>= 3.7.1)" Kind Regards, Bas

Bug#915822: nmu: ossim_2.6.0-1

2018-12-06 Thread Bas Couwenberg
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please rebuild ossim with the new geos in unstable: nmu ossim_2.6.0-1 . ANY . unstable . -m "Rebuild with libgeos++-dev (>= 3.7.1)" Kind Regards, Bas

Bug#915811: nmu: pocl_1.1-7

2018-12-06 Thread Andreas Beckmann
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu pocl_1.1-7 . ANY . unstable . -m "Rebuild with latest gcc to collect symbol updates." These rebuilds will fail due to changed symbols ... which is a bit strange since the package was al

Bug#915790: transition: lm-sensors

2018-12-06 Thread Aurelien Jarno
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition A new version of lm-sensors has been released recently, which introduces a new ABI, but very limited API change (only some enums). This new upstream version notably adds support for the n

Re: Please dak copy-installer 20181206

2018-12-06 Thread Ansgar Burchardt
Cyril Brulebois writes: > FTPmasters, please sync the installer from sid to testing: > > dak copy-installer 20181206 Done. Thanks for your work on d-i :-) Ansgar

Processed: forcibly merging 858937 913959

2018-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 858937 913959 Bug #858937 {Done: Didier Raboud } [src:kde4libs] kde4libs: Please migrate to openssl1.1 in buster Bug #913959 [src:kde4libs] kde4libs: Build-Depends on libssl1.0-dev 871056 was blocked by: 859673 859542 859553 851087 859

Please dak copy-installer 20181206

2018-12-06 Thread Cyril Brulebois
Hi, FTPmasters, please sync the installer from sid to testing: dak copy-installer 20181206 Release team: FYI, I've urgented it. Thanks for your time. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -

Bug#915751: nmu: gr-limesdr_0.9~beta-1

2018-12-06 Thread Andreas Beckmann
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu gr-limesdr_0.9~beta-1 . amd64 . unstable . -m "Rebuild in a current sid environment." After some months in NEW, some dependencies are gone ... Andreas

Bug#915721: transition: opencv

2018-12-06 Thread Mo Zhou
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition opencv 3.4.4 introduced new features, bug fixes including CVE fixes. I'd like to request for a transition slot. The rebuild for all reverse build depends has been done locally, and here

Bug#915715: stretch-pu: package debian-security-support/2018.11.25~deb9u1

2018-12-06 Thread Holger Levsen
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to update debian-security-support in Stretch to the version in unstable, basically, modulo the changelog. I expect this should go in via a normal point update, though