Bug#853591: marked as done (openigtlink: ftbfs with GCC-7)

Your message dated Sat, 15 Apr 2017 03:49:00 + with message-id and subject line Bug#853591: fixed in openigtlink 1.11.0-2 has caused the Debian Bug report #853591, regarding openigtlink: ftbfs with GCC-7 to be marked as done. This means that you claim

Bug#860278: marked as done (openigtlink: please make the build reproducible)

Your message dated Sat, 15 Apr 2017 03:49:00 + with message-id and subject line Bug#860278: fixed in openigtlink 1.11.0-2 has caused the Debian Bug report #860278, regarding openigtlink: please make the build reproducible to be marked as done. This means

openigtlink_1.11.0-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Apr 2017 22:30:07 -0400 Source: openigtlink Binary: libopenigtlink-dev libopenigtlink1.11 libopenigtlink1.11-dbg openigtlink-doc openigtlink-examples Architecture: source amd64 all Version: 1.11.0-2

Processing of openigtlink_1.11.0-2_amd64.changes

openigtlink_1.11.0-2_amd64.changes uploaded successfully to localhost along with the files: openigtlink_1.11.0-2.dsc openigtlink_1.11.0-2.debian.tar.xz libopenigtlink-dev_1.11.0-2_amd64.deb libopenigtlink1.11-dbg_1.11.0-2_amd64.deb libopenigtlink1.11_1.11.0-2_amd64.deb

Re: sundials_2.7.0+dfsg-1~1_amd64.changes REJECTED

Dima Kogan writes: > OK. It's nowhere near done, but probably good enough for experimental. > Give me a few days. I just looked at it. There actually are some package names that are new in respect with the previous packages and that probably will change when we actually

h5py 2.7.0-1 MIGRATED to testing

FYI: The status of the h5py source package in Debian's testing distribution has changed. Previous version: 2.7.0~rc3-1 Current version: 2.7.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#810254:

Hi everyone, I did some work on this in the last few days and I got to something. As requested, it's all committed to the vtk6 repo (and also available from [1]). As far as I can tell, it's all in good order. I'm already running a bunch of applications against it with no nasty surprises so far.

eclib_20160720-2~bpo8+2_amd64.changes ACCEPTED into jessie-backports->backports-policy, jessie-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 13 Apr 2017 19:14:25 +0200 Source: eclib Binary: libec2 libec-dev eclib-tools Architecture: source amd64 Version: 20160720-2~bpo8+2 Distribution: jessie-backports Urgency: medium Maintainer: Debian Science

Kudos for packaging SageMath

Dear Debian Science Maintainers, Thanks for the enormous amount of hard work you have put in to get SageMath packages for Debian. Regards, Kapil Hari Paranjape Professor of Mathematics Indian Institute of Science Education and Research Mohali Sector 81, Ajitgarh Manauli PO 140306 Punjab --

Bug#860309: libceres1: Requires rebuild for Eigen 3.3.2

Package: libceres1 Version: 1.12.0+dfsg0-1 Severity: important libceres currently is not useable, at least not if the project in question uses CMake. The reason is to be found in cmake/CeresConfig.cmake.in: CMake Error at /usr/lib/cmake/ceres/CeresConfig.cmake:88 (message): Failed to find

Dear good day friend

Dear good day friend, Calvary Greetings in the name of the LORD Almighty and Our LORD JESUS CHRIST the giver of every good thing. Good day and compliments of the seasons, i know this letter will definitely come to you as a huge surprise, but I implore you to take the time to go through it

Any opinions about data files usually shipped with R packages (Was: r-cran-aer_1.2-5-1_amd64.changes REJECTED)

Hi ftpmasters, some years ago Jörg posted a way we should deal with data files in R packages[1]. I recently packaged r-cran-aer that contains 108 such data files in a data/* dir which each has its documentation inside dir man. For 100 of the data files names of data file and documentation are