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
Package: python-fabio
Version: 0.5.0+dfsg-2~bpo9+1
Severity: wishlist
Dear Maintainer,
It should be better to add -v after tuen run_tests in order to simplify
debugging.
thanks
-- System Information:
Debian Release: 9.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64
Hello Valentino,
I will have a look at this maybe this week-end.
thanks a lot for your contributions.
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
Just for info and as a work around, in stretch-backports there is the silx
package which can be used in order to explore the hdf5 files.
the command line is
silx view.
Cheers
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
This problem was due to this
python-fabio (0.5.0+dfsg-2) unstable; urgency=medium
* d/control
- python-qt4 -> python3-pyqt4-dbg (Closes: #876288)
Now that python-fabio was solved, it is ok to close this bug
thanks
Frederic
--
debian-science-maintainers mailing list
Hello
> Unfortunately it does not look that simple. OpenBLAS is optimized for z13, but
> our s390x port is supposed to support all the z systems (see [1]).
what about asking for a a z13-support package to the isa-support (source
package) maintainer.
This way it could be possible to upload an
> ah... right after I hit send it stroke me that you probably meant
> "uploaded to Debian" so nothing for me todo. Thanks Frederic-Emmanuel! ;)
Yes,enjoy your week-end :))
And numexpr was almost uploaded into unstable :))
--
debian-science-maintainers mailing list
Hello,
I uploaded numexpr.
Cheers
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Hello,
I need to work on the hkl library next week for my work.
I must backport this for jessie-backport. I think that I will use emacs instead
of emacs25/emacs24
Cheers
Fred
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
here the error message
~/Debian/nexus/bugs$ ./bug.py
Traceback (most recent call last):
File "./bug.py", line 15, in
f.flush()
File "/usr/lib/python2.7/dist-packages/nxs/napi.py", line 397, in flush
raise NeXusError, "Could not flush NeXus file %s"%(self.filename)
It seems that the fix is not enought
this test failed at the flush
import nxs
f = nxs.open("/tmp/foo.h5", "w5")
f.makegroup('entry', 'NXentry')
f.opengroup('entry')
f.makegroup('g', 'NXcollection')
f.opengroup('g', 'NXcollection')
f.makedata('d', 'float64', shape=(1,))
f.opendata('d')
> Ehm, yes. :)
so I just tested an upgrade from jessie to sid of tango-db and it works :)))
Now I have only one concern about the dump.
Since we had a failure with the dump when it ran as user, we discovered that
our procedures where wrong and necessitate the dbadmin grants in order to works.
Hello Paul
> Officially, no, because the documentation says: "If files exist in both
> data and scripts, they will both be executed in an unspecified order."
> However, the current behavior of dbconfig-common is to first run the
> script and then run the admin code and then run the user code. So
Hello Paul
> I really hope I can upload this weekend. I have code that I believe does
> what I want. I am in the process of testing it.
thanks a lot.
> [...]
> What I meant,
> instead of the mysql code that runs as user, run a script for the
> upgrade (they are run with database
same here after a binary upload my packages when thru the NEw process ?
BUt sardana is already into testing ??? and there is no new package at all
De : debian-science-maintainers
Hello
Is it normal ?
Source-only uploads to NEW are not allowed.
binary:python-sardana is NEW.
binary:python-sardana-doc is NEW.
The package is not NEW, but the previous source upload did not build.
So it seems thaht we can not do a new source upload if the previous one FTBFS.
Cheers
Hello Paul,
> Once I fixed 850190,
Do you think that you will fix this bug before next week in order to let me
enought time to fix tango and upload it.
> I believe that ought to work, although that is
> still a hack. I was thinking of doing the "DROP PROCEDURE IF EXISTS *"
> calls with the
Hello,
I discuss with the tango-db upstream and he found that
this one line fixed the problem, befrore doing the tango-db upgrade
UPDATE mysql.proc SET Definer='tango@localhost' where Db='tango';
Ideally it should be something like
UPDATE mysql.proc SET Definer='xxx' where Db='yyy';
where
Hello,
> I am suspecting that this commit may be related to the current behavior:
> https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git/commit/?id=acdb99d61abfff54630c4cfba6e4452357a83fb9
> I believe I implemented there that the drop of the database is performed
> with the user
Thanks to reynald
1) On Jessie
with the tango account
mysql> use tango;
mysql> show create procedure class_att_prop\G
I got "Create Procedure": NULL
But If I use the root account (mysqladmin)
CREATE DEFINER=`root`@`localhost` PROCEDURE `class_att_prop` (IN class_name
VARCHAR(255), INOUT
Hello, I would like to discuss about this bug [1]
I tryed to reproduce the scenary of piuparts in a virtual machine (gnome-box)
installed in 3 steps:
jessie base system
mysql-server (I need a working database)
tango-db (daemon)
It works ok, I have a running tango-db daemon (ps aux |
No i do not have access to my computer until 3 january
If you want to nmu go ahead
Cheers
De : Adrian Bunk [b...@stusta.de]
Envoyé : mercredi 21 décembre 2016 16:57
À : 811...@bugs.debian.org; Picca Frédéric-Emmanuel
Objet : Re: Bug#811973 closed by
Hello Andreas,
> In jessie, tango-db used mysql-server-5.5 (via mysql-server).
> The upgrade of tango-db was performed after mysql-server had been upgraded
> to mariadb-server-10.0 (via default-mysql-server) and was started again.
do you know if the mariadb-server was running during the upgrade
> In other words: if you want to use Qt you *need* a QApplication instance.
> That's Qt basics. Not using it is a bug.
I understand,
Nervertheless I think that the python binding should fail gracefully with an
exception instead of segfaulting...
Cheers
--
debian-science-maintainers mailing
Hello Dmitry
> The QFontDatabase method will definitely not work properly without a
> Q(Gui)Application instance.
thanks for this analyze.
so if I understand correctly, the problem is in the QFontDatabse method which
should raise an exception instead of segfaulting.
right ?
so I should clone
> From the original bug report (the only thing I had up to know):
I attached my backtrace in the bug report. this is why we are speaking about
different things;)
> Then if the gdb backtrace in the original bug report is to be trusted then
> you are indeed mixing Qt4 and Qt5. And you can expect
> Hi Picca! Please next time you reassign a bug also CC the maintainer/team that
> receives the bug, else we don't get this very text you wrote above :-)
sorry about that.
> No, this not seems to be a Qt bug, and even less a Qt5 bug, as the lib
> mentioned in the backtrace is from Qt4. By
Thanks, I forwarded the bug to the upstream
Do not hesitate to fill a bug report via reportbug
reportbug spyder
this way we will have all the necessary informations, version of all your
softwares etc...
https://github.com/spyder-ide/spyder/issues/3691
--
debian-science-maintainers mailing
The problem was in scipy,
#840264
Now it is fixed.
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
We are in the middle of the ipython transition and we are awaiting for the
ipykernel to b e uploaded.
I needed to uploade spyder in order to fix sardana for the ipython transition.
Cheers
Frederic
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
sardana 2.1.1-1~exp1 available into experimental is supporting python-qtconsole
and ipython5
so this is not a problem for the transition.
Cheers
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
> we are planning to transition ipython from version 2.4 to 5 [1]. This
> amounts to larger changes: ipython-notebook and ipython-qtconsole were
> moved to a separate project, Jupyter. Packages for ipython 5 and several
> Jupyter components are available in experimental (see [1]), however
>
Hello Andreas, what is strange is this
https://piuparts.debian.org/sid/state-successfully-tested.html#pymca-doc
Is there a problem with piuparts ?
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
Hello during the packaging I get this error message for the tests
==
ERROR: spyderlib.widgets.tests.test_array_builder
(unittest.loader.ModuleImportFailure)
--
uploaded
cheers
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Hello, I know that the current state of the spyder stack is quite unstable :((
Can you test this with the version available into unstable 2.3.8. And gives me
your feedback.
The problem is that spyder > 2.3.5 changed by default the PyQt API#1 -> #2 and
it broke a bunch of dependencies.
This is
Hello I do not know why this break, but nevertheless, I will reassign to
libstdc++in order to understand what is going on
* libstdc++6:i386 breaks python-guiqwt (<=2.3.1-1)
Please gcc guyes, can you tell me if a binNMU would be enought to solve this
problem.
Cheers
Frederic
--
thanks for the pacth :)
BUT python3-qt4 -> python3-pyqt4
I will upload spyder 2.3.7 today.
Thanks
Fred
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Hello Eugen,
Tes' when wheezy was released, Fabio was not available for python3.
I backported it to Jessie but I think that nothing prevent the backport to
wheezy.
Can test the backport on wheezy, then de will upload it into wheezy backported.
Cheers
Fred
Here also a discussion about the problem on the gcc mailing list
https://gcc.gnu.org/ml/gcc-help/2015-09/msg00057.html
It seems that a abi_tag attribut should be added in tango to the problematic
symbols in order to help gcc5 decide which ABI is expected.
ifdef _GLIBCXX_USE_CXX11_ABI
define
I started a thread about this on debian-python mailing list.
https://lists.debian.org/debian-python/2015/09/msg00028.html
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
:/usr/lib/i386-linux-gnu$ nm -D libtango.so.8.1.2 | grep ranges_type | c++filt
0045f258 D Tango::ranges_type2const::enu
00460dfc B Tango::ranges_type2const::str[abi:cxx11]
0045f280 D Tango::ranges_type2const::enu
00460fdc B Tango::ranges_type2const::str[abi:cxx11]
0045f27c D
Ok, with the new tango,I get another symbols problem
ImportError: /«PKGBUILDDIR»/build/lib.linux-i686-2.7/PyTango/_PyTango.so:
undefined symbol: _ZN5Tango17ranges_type2constIsE3strE
Tango::ranges_type2const::str
so once again a problem with a string ???
--
debian-science-maintainers mailing
ok, I just uploaded a tango package which fix the FTBFS with gcc5.
I also made a libstdc++6 transition for tango.
so now I think that after tango acceptation into unstable a simple binNMU
should fix this issue.
--
debian-science-maintainers mailing list
ok, when I unmangle the symbol, I get this
c++filt _ZN5Tango11DeviceProxy14get_corba_nameB5cxx11Eb
Tango::DeviceProxy::get_corba_name[abi:cxx11](bool)
so it seems that this FTBFS is about a cxx11 ABi change.
during this build the c++ code compile in pytango (boost python)is noo more
Hello Doko,
libtool: link: g++ -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -std=c++11 -D_REENTRANT -DOMNI_UNLOADABLE_STUBS -Wl,-z
-Wl,relro -o .libs/notifd2db notifd2db.o -L../../lib/cpp/server
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so
I am working on it with the upstream.
once fixed,I will upload a tango with the v5 extension. then I will ask for a
transition
right ?
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
any libstdc++6 follow-up transition is waived. you can just upload to
unstable.
ok, I will try to fix this issue next week.
thanks
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
Here I attach the unmangled symbols
clipper
Description: clipper
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Hello when I look here [1]
it seems that the Distribution is sid
Distribution: sid
but I expected to target the experimental distribution.
Changes:mmdb (2.0.1-1~exp1) experimental; urgency=medium
This is the first time, I used sbuild to generate the package instead of
pbuilder.
Ok,
I fixed the package, remove the GPL section, now the code is only LGPL.
use cme to add the default lpgl snipset.
I also made the -dbg pacakge multi-arch same.
thanks for considering accepting mmdb.
Cheers
Frederic
--
debian-science-maintainers mailing list
Yes, it will be renamed. In those build only Qt5 was tested
without renaming.
one of the revers dependencies of qglviwer force us to keep the qt4 version ?
$ apt-cache rdepends libqglviewer2
libqglviewer2
Reverse Depends:
python-yade
libyade
utopia-documents
octovis
liboctovis1.6
Is it ok if I do the copyright modification ?
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
Hello,
since we are close to the freeze and because your package add a new binary
package it will requiered to pass the new queue.
So it will no be possible to have python3 package for scoop into jessie.
nevertheless I propose to upload it targetting the experimental distribution
and reseve
I also took the liberty to bump the standards version and fix some of the
lintian pedentic errors. I am happy to share my changes with you guys if
you're interested
Hello, are you part of the debian-sceince team ?
if yes you can push your changes to the repository.
If not, just give me the
Yes, I am part of the DST. I did not know it was so straightforward.
This is the principle of team maintenance :)
What should i do regarding the changelog though ?
put your name in the changelog
Do i make it as spyder (2.3.1+dfsg-1) with distribution set to
UNRELEASED and file an RFS ?
Hello,
I have uploaded into unstable
mmdb, ssm, libccp4 and clipper.
so it is possible to work on the coot packaging for jessie.
cheers
Frederic
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
Hello andreas,
in beginning of February you injected an empty repository coot.git into
Debian Med team Git. I might have forgotten whether you did some
announcement about this but for the moment I see no point in keeping
any empty repository in our space. Moreover there is some existing
I don't think there is much that can reall be done to fix the
fundamental problem which is that system users and regular users have to
live in the same namespace causing a risk of conflicts.
There are two things I can see you could do to impreove the situation
with your package.
1: Fail
59 matches
Mail list logo
