Package: python-pyside
Version: 1.2.1-4
Severity: normal
Dear Maintainer,
pip and easy_install fail to detect that PySide is already installed
from the debian repository
If a package depends on PySide, both easy_install and pip try to install
PySide regardless of it being already installed.
To
/sh linked to /bin/dash
Versions of packages libzmq3 depends on:
ii libc6 2.18-4
ii libgcc11:4.8.2-16
ii libpgm-5.1-0 5.1.118-1~dfsg-0.1
ii libstdc++6 4.8.2-16
ii multiarch-support 2.18-4
libzmq3 recommends no packages.
libzmq3 suggests no packages.
This makes me wonder if there shouldn't be a libzmq4 package for the 4.x
series while leaving the libzmq3 for the 3.x series.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
while nexus 4.3.2-svn1921-5 fixes the originally reported exception, the
fix seems not to be complete [1].
In order to trigger the still-existing regression, run the following
python code (which ideally should exit without errors):
```
import nxs
f = nxs.open("/tmp/foo.h5", "w5")
f.makegroup
python-sardana
patched package?
Cheers,
Carlos Pascual
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861736
[2] https://github.com/sardana-org/sardana/issues/460
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (1,
This is just to confirm that #834393 is now affecting Debian Stable.
Package: python-pint
Version: 0.7.2-3
Severity: wishlist
Dear Maintainer,
Upstream of pint already released 0.8.1
It includes some bug fixes that we (the upstream authors of python-taurus)
need for our latest version of Taurus to work.
Would you consider updating the python-pint package?
Note:
On Sunday, November 27, 2016 6:22:48 PM CET Dmitry Shachnev wrote:
> Such code should not be run on module *import* time, it should be run
> when the spyder code is first *used*.
I completely agree with this.
Also, I second the opinion that segfaults when using Qt code without a
QApplication is
ng "taurus"
package:
* Package name: taurus-pyqtgraph
Version : 0.1
Upstream Author : Carlos Pascual
* URL : https://github.com/taurus-org/taurus_pyqtgraph
* License : LGPL v3+
Section : python
It builds those binary packages:
python-taurus-py
No. It provides a module called taurus_pyqtgraph which in itself uses
taurus-defined entrypoints to plug into different parts of taurus . I've looked
at other packages providing plugins, and the current name seems the most
appropriate...
On February 6, 2019 9:20:54 PM GMT+01:00, PICCA Frederic-
Hi,
Just an update: the taurus-pyqtgrap package is now building successfully in
salsa:
https://salsa.debian.org/cpascual-guest/taurus-pyqtgraph
It is building two binary packages:
python-taurus-pyqtgraph
python3-taurus-pyqtgraph
All tests are passed except for piuparts which fails due to unav
Package: wnpp
Severity: wishlist
Owner: Carlos Pascual
* Package name: taurus-pyqtgraph
Version : 0.2.4
Upstream Author : Taurus Community
* URL : http://github.com/taurus-org/taurus_pyqtgraph
* License : LGPL-3+
Programming Lang: Python
Description
Hi, I fixed this in upstream:
https://github.com/hgrecco/pint/pull/630
Same here: my build of the taurus-pyqtgraph package is now working again in
sid.
Thanks!
Just adding that I checked and 0.10.0-1 is not affected.
Note this bug is affecting the to build the taurus-pyqtgraph package:
https://salsa.debian.org/science-team/taurus-pyqtgraph/-/jobs/362247
Package: silx
Version: 0.9.0+dfsg-3
Severity: important
Dear Maintainer,
Running `silx view` or `silx test` produces a crash straight away with the
following output:
```
~$ silx view
malloc_consolidate(): invalid chunk size
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name
e backtrace?
--
+----+
Carlos Pascual Izarra
Scientific Software Coordinator
Computing Division
ALBA Synchrotron [http://www.albasynchrotron.es]
Carrer de la Llum 2-26
E-08290 Cerdanyola del Valles (Barcelona), Spain
E-mail: cpasc...@cells.es
Phone:
On Friday, September 20, 2019 11:21:29 AM CEST PICCA Frederic-Emmanuel wrote:
> gdb -ex r --args python3 -m silx.app.view.main
Please find attached the output
--
++
Carlos Pascual Izarra
Scientific Software Coordinator
Computing Divis
Thanks for the investigation!
I can only add that the version of python3-qt5 available for stretch
(5.7+dfsg-5) was not affected by this.
all** for building taurus-pyqtgraph,
and this would add a lot of other dependencies for nothing
[1] https://salsa.debian.org/cpascual-guest/taurus-pyqtgraph/-/jobs/136769
--
+--------+
Carlos Pascual Izarra
Scientific Software Coordinato
On Wednesday, March 6, 2019 10:03:55 AM CET PICCA Frederic-Emmanuel wrote:
> I do not know how to do this transfer.
project settings -> General -> Advanced -> Transfer Project
> I am wondering if it is not necessary to open a tick to the salsa
> support[1] in order to move a repositor
I opened
t;
> Fred
I am fine with removing it, but just let me point that if it does not cause
harm to leave it there, it may facilitate the creation of backports to
stretch.
So let me know what you prefer.
Carlos
--
+------------+
Carlos Pascual Iza
>
> I think that it needs to be removed for Buster.
Fine. I'll remove it.
> I understand for the backports.
>
> do you know if a release is expected before the Debian freeze ?
I have no idea, but I don't expect it.
>
>
> Fred
--
+----
Hi Fred,
I made the required changes to the package sources in salsa.d.o
I hope they are ok.
Note that I did not use the -R option to gbp dch, so the fixed version
changelog is still marked as UNRELEASED
Also, I added my name to the Uploaders. I hope this is ok.
If not, feel free to revert my c
24 matches
Mail list logo