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

2018-02-16 Thread Debian FTP Masters 
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.
binary:gazebo9 is NEW.
binary:libgazebo9 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 routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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

2018-02-16 Thread Debian FTP Masters 
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
  gazebo9-doc_9.0.0+dfsg5-1_all.deb
  gazebo9-plugin-base-dbgsym_9.0.0+dfsg5-1_amd64.deb
  gazebo9-plugin-base_9.0.0+dfsg5-1_amd64.deb
  gazebo9_9.0.0+dfsg5-1_amd64.deb
  gazebo_9.0.0+dfsg5-1_amd64.buildinfo
  libgazebo9-dbgsym_9.0.0+dfsg5-1_amd64.deb
  libgazebo9-dev_9.0.0+dfsg5-1_amd64.deb
  libgazebo9_9.0.0+dfsg5-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

pyfai 0.15.0+dfsg1-1 MIGRATED to testing

2018-02-16 Thread Debian testing watch 
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 will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

r-cran-mclust 5.4-1 MIGRATED to testing

2018-02-16 Thread Debian testing watch 
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 you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: hdfview 2.11 locks SWMR files

2018-02-16 Thread help 

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 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 files they loose their data.

Best regards,
Jan

- Original Message -
From: h...@hdfgroup.org
To: "Jan Kotanski" 
Cc: debian-science-maintainers@lists.alioth.debian.org
Sent: Friday, 16 February, 2018 16:49:46
Subject: 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 working on
resolving this issue for the release version of HDFView 3.0 due out later this
year (after HDF5-1.10.2).

As a workaround, we believe you should be able to use HDFView 3.0 (Beta) to open
the file if you select "File->Open Read-Only".

-Barbara


Barbara Jones, The HDF Group Helpdesk, h...@hdfgroup.org
Support Services:  https://www.hdfgroup.org/solutions/


On Fri, 16 Feb 2018, Jan Kotanski wrote:


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

   http://www.desy.de/~jkotan/swmr/swmr.h5

with:

   http://www.desy.de/~jkotan/swmr/writer2dattr.py

Normally, I can read it on stretch with:

   http://www.desy.de/~jkotan/swmr/reader2d.py


But after I run:

jkotan@stretch-jk:~/sources/lavue/nxstest$ hdfview swmr.h5

I get:

jkotan@stretch-jk:~/sources/lavue/nxstest$ python reader2d.py
Traceback (most recent call last):
 File "reader2d.py", line 4, in 
   f = h5py.File("swmr.h5", 'r', libver='latest', swmr=True)
 File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 271, in 
__init__
   fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
 File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 101, in 
make_fid
   fid = h5f.open(name, flags, fapl=fapl)
 File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2842)
 File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2800)
 File "h5py/h5f.pyx", line 78, in h5py.h5f.open 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/h5f.c:2127)
IOError: Unable to open file (File is not already open for swmr writing)


Thus, the hdfview breaks the file and the SWMR file is not more readable.


Is it possible to provide backports for the hdfview package with the version 
which fix the above problem
  (hope the newer version, e.g. 3.0.0 fix this problem)?


Best regards,
Jan



--



--

--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: hdfview 2.11 locks SWMR files

2018-02-16 Thread jan.kotanski 
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 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 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 files they loose their data.
>
> Best regards,
> Jan
>
> - Original Message -
> From: h...@hdfgroup.org
> To: "Jan Kotanski" 
> Cc: debian-science-maintainers@lists.alioth.debian.org
> Sent: Friday, 16 February, 2018 16:49:46
> Subject: 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 working on
> resolving this issue for the release version of HDFView 3.0 due out later this
> year (after HDF5-1.10.2).
>
> As a workaround, we believe you should be able to use HDFView 3.0 (Beta) to 
> open
> the file if you select "File->Open Read-Only".
>
> -Barbara
>
> 
> Barbara Jones, The HDF Group Helpdesk, h...@hdfgroup.org
> Support Services:  https://www.hdfgroup.org/solutions/
> 
>
> On Fri, 16 Feb 2018, Jan Kotanski wrote:
>
>> 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
>>
>>    http://www.desy.de/~jkotan/swmr/swmr.h5
>>
>> with:
>>
>>    http://www.desy.de/~jkotan/swmr/writer2dattr.py
>>
>> Normally, I can read it on stretch with:
>>
>>    http://www.desy.de/~jkotan/swmr/reader2d.py
>>
>>
>> But after I run:
>>
>> jkotan@stretch-jk:~/sources/lavue/nxstest$ hdfview swmr.h5
>>
>> I get:
>>
>> jkotan@stretch-jk:~/sources/lavue/nxstest$ python reader2d.py
>> Traceback (most recent call last):
>>  File "reader2d.py", line 4, in 
>>    f = h5py.File("swmr.h5", 'r', libver='latest', swmr=True)
>>  File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 271, in 
>>__init__
>>    fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
>>  File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 101, in 
>>make_fid
>>    fid = h5f.open(name, flags, fapl=fapl)
>>  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper 
>>(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2842)
>>  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper 
>>(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2800)
>>  File "h5py/h5f.pyx", line 78, in h5py.h5f.open 
>>(/build/h5py-b1xqNM/h5py-2.7.0/h5py/h5f.c:2127)
>> IOError: Unable to open file (File is not already open for swmr writing)
>>
>>
>> Thus, the hdfview breaks the file and the SWMR file is not more readable.
>>
>>
>> Is it possible to provide backports for the hdfview package with the version 
>> which fix the above problem
>>   (hope the newer version, e.g. 3.0.0 fix this problem)?
>>
>>
>> Best regards,
>> Jan
>>
>
> --
>

-- 
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: hdfview 2.11 locks SWMR files

2018-02-16 Thread Kotanski, Jan 
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 files they loose their data.

Best regards,
Jan  

- Original Message -
From: h...@hdfgroup.org
To: "Jan Kotanski" 
Cc: debian-science-maintainers@lists.alioth.debian.org
Sent: Friday, 16 February, 2018 16:49:46
Subject: 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 working on
resolving this issue for the release version of HDFView 3.0 due out later this
year (after HDF5-1.10.2).

As a workaround, we believe you should be able to use HDFView 3.0 (Beta) to 
open 
the file if you select "File->Open Read-Only".

-Barbara


Barbara Jones, The HDF Group Helpdesk, h...@hdfgroup.org
Support Services:  https://www.hdfgroup.org/solutions/


On Fri, 16 Feb 2018, Jan Kotanski wrote:

> 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
>
>http://www.desy.de/~jkotan/swmr/swmr.h5
>
> with:
>
>http://www.desy.de/~jkotan/swmr/writer2dattr.py
>
> Normally, I can read it on stretch with:
>
>http://www.desy.de/~jkotan/swmr/reader2d.py
>
>
> But after I run:
>
> jkotan@stretch-jk:~/sources/lavue/nxstest$ hdfview swmr.h5
>
> I get:
>
> jkotan@stretch-jk:~/sources/lavue/nxstest$ python reader2d.py
> Traceback (most recent call last):
>  File "reader2d.py", line 4, in 
>f = h5py.File("swmr.h5", 'r', libver='latest', swmr=True)
>  File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 271, in 
> __init__
>fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
>  File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 101, in 
> make_fid
>fid = h5f.open(name, flags, fapl=fapl)
>  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper 
> (/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2842)
>  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper 
> (/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2800)
>  File "h5py/h5f.pyx", line 78, in h5py.h5f.open 
> (/build/h5py-b1xqNM/h5py-2.7.0/h5py/h5f.c:2127)
> IOError: Unable to open file (File is not already open for swmr writing)
>
>
> Thus, the hdfview breaks the file and the SWMR file is not more readable.
>
>
> Is it possible to provide backports for the hdfview package with the version 
> which fix the above problem
>   (hope the newer version, e.g. 3.0.0 fix this problem)?
>
>
> Best regards,
> Jan
>

--

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: hdfview 2.11 locks SWMR files

2018-02-16 Thread help 


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 working on
resolving this issue for the release version of HDFView 3.0 due out later this
year (after HDF5-1.10.2).

As a workaround, we believe you should be able to use HDFView 3.0 (Beta) to open 
the file if you select "File->Open Read-Only".


-Barbara


Barbara Jones, The HDF Group Helpdesk, h...@hdfgroup.org
Support Services:  https://www.hdfgroup.org/solutions/


On Fri, 16 Feb 2018, Jan Kotanski wrote:


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

   http://www.desy.de/~jkotan/swmr/swmr.h5

with:

   http://www.desy.de/~jkotan/swmr/writer2dattr.py

Normally, I can read it on stretch with:

   http://www.desy.de/~jkotan/swmr/reader2d.py


But after I run:

jkotan@stretch-jk:~/sources/lavue/nxstest$ hdfview swmr.h5

I get:

jkotan@stretch-jk:~/sources/lavue/nxstest$ python reader2d.py
Traceback (most recent call last):
 File "reader2d.py", line 4, in 
   f = h5py.File("swmr.h5", 'r', libver='latest', swmr=True)
 File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 271, in 
__init__
   fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
 File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 101, in 
make_fid
   fid = h5f.open(name, flags, fapl=fapl)
 File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2842)
 File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2800)
 File "h5py/h5f.pyx", line 78, in h5py.h5f.open 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/h5f.c:2127)
IOError: Unable to open file (File is not already open for swmr writing)


Thus, the hdfview breaks the file and the SWMR file is not more readable.


Is it possible to provide backports for the hdfview package with the version 
which fix the above problem
  (hope the newer version, e.g. 3.0.0 fix this problem)?


Best regards,
Jan



--

--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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

2018-02-16 Thread Debian FTP Masters 


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: experimental
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Drew Parsons 
Description:
 dolfin-bin - Executable scripts for DOLFIN
 dolfin-doc - Documentation and demo programs for DOLFIN
 libdolfin-dev - Shared links and header files for DOLFIN
 libdolfin2017.2 - Shared libraries for DOLFIN
 python-dolfin - Python interface for DOLFIN (Python 2)
 python3-dolfin - Python interface for DOLFIN (Python 3)
Changes:
 dolfin (2017.2.0.post0-1exp2) experimental; urgency=medium
 .
   * reorganise debian/copyright: collect core DOLFIN files and
 contributors in one entry.
   * Remove -dbg packages from debian/control.
 Debug packages (-dbgsym) are built automatically.
Checksums-Sha1:
 44329f9b49a9fce158abe26802ef416b2f49e505 3524 dolfin_2017.2.0.post0-1exp2.dsc
 b17d6701357896aae7a54c926dcec62d0045c239 8159909 
dolfin_2017.2.0.post0.orig.tar.gz
 9ccec92fe918a2bc1adf5b08056db72043d22fc0 473 
dolfin_2017.2.0.post0.orig.tar.gz.asc
 9896ab33803db31b2342134757ca0c006ab48acd 16960 
dolfin_2017.2.0.post0-1exp2.debian.tar.xz
 287011559cf3afd2891f14dbb0526848d2b29012 46292 
dolfin-bin_2017.2.0.post0-1exp2_all.deb
 4bb6f063f07fc329f2c59d13c01f33aef0147778 2657384 
dolfin-doc_2017.2.0.post0-1exp2_all.deb
 a99f924455d08f91cb0a9ba69afa5f2d3a91e70e 16051 
dolfin_2017.2.0.post0-1exp2_amd64.buildinfo
 24b06546e59a8a9072f4b94512c3c9d7c290ea74 247092 
libdolfin-dev_2017.2.0.post0-1exp2_amd64.deb
 1ee32490dbc41161d163ed12d1187dcb97eef7d0 41411824 
libdolfin2017.2-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 6c492e6b9606cbf5482690b29861ae7f029ddfa7 1700940 
libdolfin2017.2_2017.2.0.post0-1exp2_amd64.deb
 2cd33671ecfb5de7018d5776ff60e9aee8ae144e 8945616 
python-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 9b8795c56cf42795f40f7296deb6b11e161ef238 1193832 
python-dolfin_2017.2.0.post0-1exp2_amd64.deb
 48c27e4db453348508f2af6ff719005625055ed7 8970752 
python3-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 5095910c1a79c4b3f03286e2976aa170f3002bbc 1196464 
python3-dolfin_2017.2.0.post0-1exp2_amd64.deb
Checksums-Sha256:
 be2f27cff8aa2395e5afc12191ed9840de5b1f0936c0c93a91ad2492c3f168f3 3524 
dolfin_2017.2.0.post0-1exp2.dsc
 d3c40cd8c1c882f517999c25ea4220adcd01dbb1d829406fce99b1fc40184c82 8159909 
dolfin_2017.2.0.post0.orig.tar.gz
 55b99e24089a28ed2bf5f5ccebc7e46410c2d4661c6c6b4ce735070884264f05 473 
dolfin_2017.2.0.post0.orig.tar.gz.asc
 964fed9901a052a36253029e7bcd8aee0dc9157263d7b429b429b3f27cd4a7e8 16960 
dolfin_2017.2.0.post0-1exp2.debian.tar.xz
 e5d2a6f88947cee350d5875e50a0282840ce678af563a1f72f077364c4ce787d 46292 
dolfin-bin_2017.2.0.post0-1exp2_all.deb
 2e55334d899c14b9881b955931a5b12ba49e53483e26e16298dc9c20c5f04930 2657384 
dolfin-doc_2017.2.0.post0-1exp2_all.deb
 6769a3ca5a631873d10e548cf6fcee57cb8561cf2fae1a0e7b16b08404f0abb9 16051 
dolfin_2017.2.0.post0-1exp2_amd64.buildinfo
 e247c9025b115669308849c6311d644509472e7056725ee0f8e1e9e5969ac0e5 247092 
libdolfin-dev_2017.2.0.post0-1exp2_amd64.deb
 4d41be67472ec627fa2ee33c606731b560749172bf02fe9dd2459aee15c4eecc 41411824 
libdolfin2017.2-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 801b75f5f33e492e10264f03d3f00f595852523f4c313c087acf9e35eaa49f7c 1700940 
libdolfin2017.2_2017.2.0.post0-1exp2_amd64.deb
 ca73337d1bf266abedbad74ebcef31780ad3745ad7ae8deba952abb7b722ea86 8945616 
python-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 846d286247c35f88e0e624a6edd294b2f4a266a54ce16b08ae7174eca7cbe6c6 1193832 
python-dolfin_2017.2.0.post0-1exp2_amd64.deb
 29ce4c52731ececcc1a6b514737363935e99a2e95a402d538c16c7784ae95fc3 8970752 
python3-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 dc44735d4fb8d73cddb9d91dfd6b4eec9f0844a03a066332701b4e951c07dcc5 1196464 
python3-dolfin_2017.2.0.post0-1exp2_amd64.deb
Files:
 ba6c18314aed0885c56db352d05f85f8 3524 math optional 
dolfin_2017.2.0.post0-1exp2.dsc
 84794a67844431e801a8875e19d60ef4 8159909 math optional 
dolfin_2017.2.0.post0.orig.tar.gz
 35e94bbcd3f84aceac02ce2f27bed1d7 473 math optional 
dolfin_2017.2.0.post0.orig.tar.gz.asc
 51141ee7d519994a8d36fadcef088ca5 16960 math optional 
dolfin_2017.2.0.post0-1exp2.debian.tar.xz
 0a4701ad2108ef3868cadb3b993f11da 46292 math optional 
dolfin-bin_2017.2.0.post0-1exp2_all.deb
 7d8a8056d4feddc3348769505070e871 2657384 doc optional 
dolfin-doc_2017.2.0.post0-1exp2_all.deb
 4d0cf55c8ae7af5ce334173f4b2b1336 16051 math optional 
dolfin_2017.2.0.post0-1exp2_amd64.buildinfo
 f1750ed6388a9697171b6ae2accd8bfb 247092 libdevel optional 
libdolfin-dev_2017.2.0.post0-1exp2_amd64.deb
 81ea50211d7c05a2cf85a9258bec9609 41411824 debug optional 
libdolfin2017.2-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 3e70c1d7758ee48be1f3038c11f5b1a0 1700940 libs optional

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

2018-02-16 Thread Drew Parsons 
-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
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Drew Parsons 
Description:
 dolfin-bin - Executable scripts for DOLFIN
 dolfin-doc - Documentation and demo programs for DOLFIN
 libdolfin-dev - Shared links and header files for DOLFIN
 libdolfin2017.2 - Shared libraries for DOLFIN
 python-dolfin - Python interface for DOLFIN (Python 2)
 python3-dolfin - Python interface for DOLFIN (Python 3)
Changes:
 dolfin (2017.2.0.post0-1exp2) experimental; urgency=medium
 .
   * reorganise debian/copyright: collect core DOLFIN files and
 contributors in one entry.
   * Remove -dbg packages from debian/control.
 Debug packages (-dbgsym) are built automatically.
Checksums-Sha1:
 44329f9b49a9fce158abe26802ef416b2f49e505 3524 dolfin_2017.2.0.post0-1exp2.dsc
 b17d6701357896aae7a54c926dcec62d0045c239 8159909 
dolfin_2017.2.0.post0.orig.tar.gz
 9ccec92fe918a2bc1adf5b08056db72043d22fc0 473 
dolfin_2017.2.0.post0.orig.tar.gz.asc
 9896ab33803db31b2342134757ca0c006ab48acd 16960 
dolfin_2017.2.0.post0-1exp2.debian.tar.xz
 287011559cf3afd2891f14dbb0526848d2b29012 46292 
dolfin-bin_2017.2.0.post0-1exp2_all.deb
 4bb6f063f07fc329f2c59d13c01f33aef0147778 2657384 
dolfin-doc_2017.2.0.post0-1exp2_all.deb
 a99f924455d08f91cb0a9ba69afa5f2d3a91e70e 16051 
dolfin_2017.2.0.post0-1exp2_amd64.buildinfo
 24b06546e59a8a9072f4b94512c3c9d7c290ea74 247092 
libdolfin-dev_2017.2.0.post0-1exp2_amd64.deb
 1ee32490dbc41161d163ed12d1187dcb97eef7d0 41411824 
libdolfin2017.2-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 6c492e6b9606cbf5482690b29861ae7f029ddfa7 1700940 
libdolfin2017.2_2017.2.0.post0-1exp2_amd64.deb
 2cd33671ecfb5de7018d5776ff60e9aee8ae144e 8945616 
python-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 9b8795c56cf42795f40f7296deb6b11e161ef238 1193832 
python-dolfin_2017.2.0.post0-1exp2_amd64.deb
 48c27e4db453348508f2af6ff719005625055ed7 8970752 
python3-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 5095910c1a79c4b3f03286e2976aa170f3002bbc 1196464 
python3-dolfin_2017.2.0.post0-1exp2_amd64.deb
Checksums-Sha256:
 be2f27cff8aa2395e5afc12191ed9840de5b1f0936c0c93a91ad2492c3f168f3 3524 
dolfin_2017.2.0.post0-1exp2.dsc
 d3c40cd8c1c882f517999c25ea4220adcd01dbb1d829406fce99b1fc40184c82 8159909 
dolfin_2017.2.0.post0.orig.tar.gz
 55b99e24089a28ed2bf5f5ccebc7e46410c2d4661c6c6b4ce735070884264f05 473 
dolfin_2017.2.0.post0.orig.tar.gz.asc
 964fed9901a052a36253029e7bcd8aee0dc9157263d7b429b429b3f27cd4a7e8 16960 
dolfin_2017.2.0.post0-1exp2.debian.tar.xz
 e5d2a6f88947cee350d5875e50a0282840ce678af563a1f72f077364c4ce787d 46292 
dolfin-bin_2017.2.0.post0-1exp2_all.deb
 2e55334d899c14b9881b955931a5b12ba49e53483e26e16298dc9c20c5f04930 2657384 
dolfin-doc_2017.2.0.post0-1exp2_all.deb
 6769a3ca5a631873d10e548cf6fcee57cb8561cf2fae1a0e7b16b08404f0abb9 16051 
dolfin_2017.2.0.post0-1exp2_amd64.buildinfo
 e247c9025b115669308849c6311d644509472e7056725ee0f8e1e9e5969ac0e5 247092 
libdolfin-dev_2017.2.0.post0-1exp2_amd64.deb
 4d41be67472ec627fa2ee33c606731b560749172bf02fe9dd2459aee15c4eecc 41411824 
libdolfin2017.2-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 801b75f5f33e492e10264f03d3f00f595852523f4c313c087acf9e35eaa49f7c 1700940 
libdolfin2017.2_2017.2.0.post0-1exp2_amd64.deb
 ca73337d1bf266abedbad74ebcef31780ad3745ad7ae8deba952abb7b722ea86 8945616 
python-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 846d286247c35f88e0e624a6edd294b2f4a266a54ce16b08ae7174eca7cbe6c6 1193832 
python-dolfin_2017.2.0.post0-1exp2_amd64.deb
 29ce4c52731ececcc1a6b514737363935e99a2e95a402d538c16c7784ae95fc3 8970752 
python3-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 dc44735d4fb8d73cddb9d91dfd6b4eec9f0844a03a066332701b4e951c07dcc5 1196464 
python3-dolfin_2017.2.0.post0-1exp2_amd64.deb
Files:
 ba6c18314aed0885c56db352d05f85f8 3524 math optional 
dolfin_2017.2.0.post0-1exp2.dsc
 84794a67844431e801a8875e19d60ef4 8159909 math optional 
dolfin_2017.2.0.post0.orig.tar.gz
 35e94bbcd3f84aceac02ce2f27bed1d7 473 math optional 
dolfin_2017.2.0.post0.orig.tar.gz.asc
 51141ee7d519994a8d36fadcef088ca5 16960 math optional 
dolfin_2017.2.0.post0-1exp2.debian.tar.xz
 0a4701ad2108ef3868cadb3b993f11da 46292 math optional 
dolfin-bin_2017.2.0.post0-1exp2_all.deb
 7d8a8056d4feddc3348769505070e871 2657384 doc optional 
dolfin-doc_2017.2.0.post0-1exp2_all.deb
 4d0cf55c8ae7af5ce334173f4b2b1336 16051 math optional 
dolfin_2017.2.0.post0-1exp2_amd64.buildinfo
 f1750ed6388a9697171b6ae2accd8bfb 247092 libdevel optional 
libdolfin-dev_2017.2.0.post0-1exp2_amd64.deb
 81ea50211d7c05a2cf85a9258bec9609 41411824 debug optional 
libdolfin2017.2-dbgsym_2017.2.0.post0-1exp2_amd64.deb
 3e70c1d7758ee48be1f3038c11f5b1a0 1700940 libs optional

dxf2gcode_20170925-1_amd64.changes ACCEPTED into unstable, unstable

2018-02-16 Thread Debian FTP Masters 


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 

Changed-By: Sebastian Kuzminsky 
Description:
 dxf2gcode  - prepares drawings of parts for automatic machine tools
Closes: 888298
Changes:
 dxf2gcode (20170925-1) unstable; urgency=medium
 .
   * Initial release.  (Closes: #888298)
Checksums-Sha1:
 07cb78c890ef61acca95352c8eac6cad4c8b8a83 2050 dxf2gcode_20170925-1.dsc
 7402fcfa3403b7d5b689d58daa622d0abe0d5941 396412 dxf2gcode_20170925.orig.tar.xz
 2b0404a11806277e1a60a725d2cbc00911d3653c 3800 
dxf2gcode_20170925-1.debian.tar.xz
 d69e2d060c31396316d2f3feffde6311e41acfdf 401816 dxf2gcode_20170925-1_all.deb
 7527bd49d1b3185c7b95acd66cb1144bd1fb221c 9712 
dxf2gcode_20170925-1_amd64.buildinfo
Checksums-Sha256:
 7783c12e5af1365fca84b993e9e5c58feb6638c42e5087ee7be570c1400859eb 2050 
dxf2gcode_20170925-1.dsc
 3ee4b99912bbd838c1b01cbbd48bff83cc1d06a1673391dd7747471670a2d684 396412 
dxf2gcode_20170925.orig.tar.xz
 c615c55c25414f5ab66b460f5eda91e1525a9153d43c06f79ac281382241611f 3800 
dxf2gcode_20170925-1.debian.tar.xz
 8b574a95cb23dcb72c11cf4cbfc315eef0ef0953801a99f3194effbd71987f41 401816 
dxf2gcode_20170925-1_all.deb
 ea413875d4a519f1ff2ebab964cd26d81ad585f1b9f5f8882000e2472ac05d17 9712 
dxf2gcode_20170925-1_amd64.buildinfo
Files:
 0f8cb71b35b57194f5e0c156e68752d0 2050 science optional dxf2gcode_20170925-1.dsc
 31310eb35a00b16f58fbf4645fa61dea 396412 science optional 
dxf2gcode_20170925.orig.tar.xz
 0b3062cd3978a22bfa942b1dc01e7f20 3800 science optional 
dxf2gcode_20170925-1.debian.tar.xz
 1662fdbcf261287b8c6348d1e1b9a646 401816 science optional 
dxf2gcode_20170925-1_all.deb
 14fa4ef1745efbfff7cc18e68a71f6c2 9712 science optional 
dxf2gcode_20170925-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlqEb4UACgkQLOzpNQ7O
vkrchg//Udbkr5FQlv09QWv5ctgfmVLz5OVHxfUcH/LOzh/J9LqPyof/IsX/mcRt
h6v2bd0ZU5GgxZ6wWNAR+gJkc8yc0SGi6ANwn9jTu44oG2SPAfa3TyAzNe3xxulc
4kk/JgsvCyu4psYXfeVLqd4UfAKsbRCO0uQ1ypE3hMk4ifr84hFLZkJWC1miTQla
CWJfHhQBFTSfE4yLanTw2q8bHhr9Bueh94qtJCYGbF4ahvKAKKgmBARGmih74hhB
Dp3JtqHh7Ia02vIeRwlH15ZcKIkhir8bcpo/H/BSHcqqvlXr7EEMVfiB6pFiWXyU
TXFCrXoXiR6rETBA7LHEQxGPFfLMMXwuuuadiJvVyZ4gqi0HhP9o1+nlKyxfxQoy
f2LLTRbtSDIIA+tBMPWvqtj0TVLhjvDQ3SND7eGIn8rC/om1vVcSS/+MwkKc0ihz
TAPqH3jUeKIjh+ro5VVdjFnz63vpMECDPzf1QOTqSXzRYKvjxuo+2preZ7TRlhPS
EfND6CR42zKP+tn51ITH0AgRUEfP97TkRV7XbhQqfI/k+NF5W1KuOlqQmIXTi8dS
0PmXIY+QRkDmkmRo0egFJTIcan7ce/wO3TRCJh71PKAm2lcwUjTJLLdi25dfauv6
n4IdQAK9WUB6dtfcHUzMDuwWi5VVV5GHhn/qgBFNTec2XOtjMmY=
=QcJI
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

RE:hdfview 2.11 locks SWMR files

2018-02-16 Thread PICCA Frederic-Emmanuel 
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
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

hdfview 2.11 locks SWMR files

2018-02-16 Thread Jan Kotanski 
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 

http://www.desy.de/~jkotan/swmr/swmr.h5

with:

http://www.desy.de/~jkotan/swmr/writer2dattr.py

Normally, I can read it on stretch with:

http://www.desy.de/~jkotan/swmr/reader2d.py


But after I run:

jkotan@stretch-jk:~/sources/lavue/nxstest$ hdfview swmr.h5

I get:

jkotan@stretch-jk:~/sources/lavue/nxstest$ python reader2d.py 
Traceback (most recent call last):
  File "reader2d.py", line 4, in 
f = h5py.File("swmr.h5", 'r', libver='latest', swmr=True)
  File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 271, in 
__init__
fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
  File "/usr/lib/python2.7/dist-packages/h5py/_hl/files.py", line 101, in 
make_fid
fid = h5f.open(name, flags, fapl=fapl)
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2842)
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/_objects.c:2800)
  File "h5py/h5f.pyx", line 78, in h5py.h5f.open 
(/build/h5py-b1xqNM/h5py-2.7.0/h5py/h5f.c:2127)
IOError: Unable to open file (File is not already open for swmr writing)


Thus, the hdfview breaks the file and the SWMR file is not more readable.


Is it possible to provide backports for the hdfview package with the version 
which fix the above problem
   (hope the newer version, e.g. 3.0.0 fix this problem)?


Best regards,
Jan

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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

2018-02-16 Thread Debian FTP Masters 
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 routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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

2018-02-16 Thread Debian FTP Masters 
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
  dolfin-doc_2017.2.0.post0-1exp2_all.deb
  dolfin_2017.2.0.post0-1exp2_amd64.buildinfo
  libdolfin-dev_2017.2.0.post0-1exp2_amd64.deb
  libdolfin2017.2-dbgsym_2017.2.0.post0-1exp2_amd64.deb
  libdolfin2017.2_2017.2.0.post0-1exp2_amd64.deb
  python-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
  python-dolfin_2017.2.0.post0-1exp2_amd64.deb
  python3-dolfin-dbgsym_2017.2.0.post0-1exp2_amd64.deb
  python3-dolfin_2017.2.0.post0-1exp2_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#890577: tkgate: please make the build reproducible

2018-02-16 Thread Chris Lamb 
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 reproducibly.

This is because it includes the output of `pwd` in the resulting
binary (which is useless/broken for an end-user, as well as being
a privacy leak of the builder).

Patch attached that sets TKGATE_SECONDARYHOME from TKGATE_HOMEDIR.
This is cleaner than removing the TKGATE_SECONDARYHOME mechanism
as the patch for _that_ would be:

  --- a/src/tkgate/tkgate.c 2018-02-16 07:56:06.421183383 +
  --- b/src/tkgate/tkgate.c 2018-02-16 08:27:09.286827217 +
  @@ -122,32 +122,29 @@
* 1) Directory specified by TKGATE_HOME environment variable
* 2) Current directory
* 3) Directory specified by TKGATE_HOMEDIR in config.h
  - * 4) Directory specified by TKGATE_SECONDARYHOME in config.h
*
* The #define value TKGATE_HOMEDIR is normally generated automatically by 
the
* configure script using TKGATE_HOMEDIRBASE as a prefix and tkgate-x.y 
(where
  - * x.y is the version number) the subdirectory.  The #define value 
TKGATE_SECONDARYHOME
  - * is normally set to the directory in which tkgate was configured/compiled.
  + * x.y is the version number) the subdirectory.
*

*/
   void findTkGateHome(char *homeDir)
   {
 char buf[STRMAX];
  -  char *trydirs[4];
  +  char *trydirs[3];
 int i;
   
 trydirs[0] = getenv("TKGATE_HOME");
 trydirs[1] = getcwd(buf,STRMAX);
 trydirs[2] = TKGATE_HOMEDIR;
  -  trydirs[3] = TKGATE_SECONDARYHOME;
   
  -  for (i = 0;i < 4;i++) {
  +  for (i = 0;i < 3;i++) {
   if (!trydirs[i]) continue;
   strcpy(homeDir,trydirs[i]);
   if (testHome(homeDir)) break;
 }
   
  -  if (i == 4) {
  +  if (i == 3) {
   printf("\n");
   printf("I could not locate the tkgate home directory.  I tried looking 
in:\n");
   if (trydirs[0]) printf("  %s  (environment variable)\n", trydirs[0]);


.. which is a little bizarre, not helped by the "magic numbers" used by
upstream :)


 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproduible-build.patch1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproduible-build.patch2018-02-16 08:20:36.644564932 
+
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2018-02-16
+
+--- tkgate-2.0~b10.orig/configure.ac
 tkgate-2.0~b10/configure.ac
+@@ -105,7 +105,7 @@ AH_BOTTOM([
+ # TkGate Installation Directories
+ #
+ currentDirectory=`pwd`
+-AC_DEFINE_UNQUOTED(TKGATE_SECONDARYHOME, "$currentDirectory", [Backup 
location for TkGate home directory])
++AC_DEFINE_UNQUOTED(TKGATE_SECONDARYHOME, TKGATE_HOMEDIR, [Backup location for 
TkGate home directory])
+ 
+ #
+ # Standard compiler checks
--- a/debian/patches/series 2018-02-16 07:56:06.417183359 +
--- b/debian/patches/series 2018-02-16 08:20:35.632559104 +
@@ -3,3 +3,4 @@
 hardening.patch
 remove-shebang-line.patch
 typos.patch
+reproduible-build.patch
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers