gazebo_9.0.0+dfsg5-1_amd64.changes is NEW

binary:gazebo9 is NEW. binary:gazebo9-common is NEW. binary:gazebo9-doc is NEW. binary:gazebo9-plugin-base is NEW. binary:libgazebo9 is NEW. binary:libgazebo9-dev is NEW. binary:gazebo9-plugin-base is NEW. binary:gazebo9-common is NEW. binary:gazebo9-doc is NEW. binary:libgazebo9-dev is NEW.

Processing of gazebo_9.0.0+dfsg5-1_amd64.changes

gazebo_9.0.0+dfsg5-1_amd64.changes uploaded successfully to localhost along with the files: gazebo_9.0.0+dfsg5-1.dsc gazebo_9.0.0+dfsg5.orig.tar.gz gazebo_9.0.0+dfsg5-1.debian.tar.xz gazebo9-common_9.0.0+dfsg5-1_all.deb gazebo9-dbgsym_9.0.0+dfsg5-1_amd64.deb

pyfai 0.15.0+dfsg1-1 MIGRATED to testing

FYI: The status of the pyfai source package in Debian's testing distribution has changed. Previous version: 0.14.2+dfsg-6 Current version: 0.15.0+dfsg1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

r-cran-mclust 5.4-1 MIGRATED to testing

FYI: The status of the r-cran-mclust source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 5.4-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

Re: hdfview 2.11 locks SWMR files

Hi Jan, You can use the h5clear -s utility to remove the flag. I should have mentioned that! -Barbara On Fri, 16 Feb 2018, Kotanski, Jan wrote: Hi Barbara, Is there any way to rescue (i.e. unlock) the files broken by hdfview, e.g. a script which unlocks the file? If not we have to forbid

Re: hdfview 2.11 locks SWMR files

Hi Barbara, Ah ok. Thanks. Jan Oryginalna wiadomość Od: h...@hdfgroup.org Data: 16.02.2018 19:16 (GMT+01:00) Do: "Kotanski, Jan" DW: debian-science-maintainers@lists.alioth.debian.org Temat: Re: hdfview 2.11 locks SWMR files Hi Jan, You can use the

Re: hdfview 2.11 locks SWMR files

Hi Barbara, Is there any way to rescue (i.e. unlock) the files broken by hdfview, e.g. a script which unlocks the file? If not we have to forbid our user to use the hdfview (or do not use SWMR). They don't know a priori if the file was created with SWMR or not. And if they cannot unlock broken

Re: hdfview 2.11 locks SWMR files

Hi Jan, HDFView 2.11 is based on HDF5-1.8 with 32-bit object identifiers. SWMR is a new feature in HDF5-1.10 (which has 64-bit object identifiers). HDFView 3.0 (Beta) supports HDF5-1.10. However, even if you use it and select "File->Open", it gets a lock on the file and it modifies it. We are

dolfin_2017.2.0.post0-1exp2_amd64.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 16 Feb 2018 15:34:44 +0800 Source: dolfin Binary: libdolfin-dev libdolfin2017.2 python-dolfin python3-dolfin dolfin-doc dolfin-bin Architecture: source all amd64 Version: 2017.2.0.post0-1exp2 Distribution:

Accepted dolfin 2017.2.0.post0-1exp2 (source all amd64) into experimental, experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 16 Feb 2018 15:34:44 +0800 Source: dolfin Binary: libdolfin-dev libdolfin2017.2 python-dolfin python3-dolfin dolfin-doc dolfin-bin Architecture: source all amd64 Version: 2017.2.0.post0-1exp2 Distribution: experimental

dxf2gcode_20170925-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Feb 2018 18:15:51 +0100 Source: dxf2gcode Binary: dxf2gcode Architecture: source all Version: 20170925-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

RE:hdfview 2.11 locks SWMR files

Hello Jan, just as a work around, you can use the silx package which is available as a stretch-backports in order to explore your hdf5 file. cheers Frederic -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

hdfview 2.11 locks SWMR files

Dear HDFView Maintainers, I've just accounted problems in reading SWMR files with hdfview 2.11 on debian stretch. The hdfview 2.11 not only cannot read the SWMR files but it breaks them, i.e. set a lock inside the files, and the files are no more readable. For example I create a file

dolfin_2017.2.0.post0-1exp2_amd64.changes is NEW

binary:libdolfin2017.2 is NEW. binary:libdolfin2017.2 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are

Processing of dolfin_2017.2.0.post0-1exp2_amd64.changes

dolfin_2017.2.0.post0-1exp2_amd64.changes uploaded successfully to localhost along with the files: dolfin_2017.2.0.post0-1exp2.dsc dolfin_2017.2.0.post0.orig.tar.gz dolfin_2017.2.0.post0.orig.tar.gz.asc dolfin_2017.2.0.post0-1exp2.debian.tar.xz dolfin-bin_2017.2.0.post0-1exp2_all.deb

Bug#890577: tkgate: please make the build reproducible

Source: tkgate Version: 2.0~b10-5 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that tkgate could not be built