Source: node-ipydatagrid
Version: 1.4.0+~cs14.21.116-1
Severity: normal
Dear Maintainer,
A python module ipydatagrid is available in the sources.
Could you provide it ?
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Ar
Source: ipywidgets
Version: 8.1.5-6
Severity: normal
Dear Maintainer,
It would be great if the ipywidget package could become the source package of
the node-jupyter-widgets-xxx provider instead of the ipydatagrid.
at least
node-jupyter-widgets-base
node-jupyter-widgets-base-manager
node-jupyte
Package: vtk9
Version: 9.3.0+dfsg1-4
Severity: wishlist
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
I was trying to build paraview with the system vtk instead of the one embeded
into paraview.
but I end up with these errors.
CMake Error at CMakeLists.txt:562 (message):
Please reconfigure
Package: cambalache
Version: 0.94.1-2
Followup-For: Bug #1095742
Dear Maintainer,
$ cambalache pseudo-4.ui
Traceback (most recent call last):
File "/usr/bin/cambalache", line 42, in
from cambalache.app import CmbApplication
File "/usr/lib/python3/dist-packages/cambalache/__init__.py",
With the upload of the new zarr, the errors are now
=== short test summary info
FAILED xarray/tests/test_groupby.py::test_dask_da_groupby_quantile - Failed: ...
FAILED
xarray/tests/test_weighted.py::test_weighted_operations_keep_attr[False-Tr
Source: zarr
Severity: normal
Dear Maintainer,
I am wondering if the bug fix in zarr will not help with the xarray FTBFS[1].
In the changelog we see
What's Changed
fix: restore attrs del functionality by @ianhi in #2908
release: update release notes for 3.0.6 by @jhamman in #2923
and
Package: paraview
Version: 5.13.2+dfsg-3
Severity: important
Tags: ftbfs
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
while trying to rebuild paraview in a clean unstable chroot, I got at least
these erros:
cd
/build/reproducible-path/paraview-5.13.2+dfsg/build.python3.13/Wrapping/Python
Package: libboost-numpy1.83.0
Version: 1.83.0-4.1+b1
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
I am trying to fix the autopkgtest of cctbx but I end up with a segfault here
0 PyArray_GetCastingImpl (from=0x9fb020 , to=to@entry=0xe4dae0)
at ../numpy/_core/src/multiarra
Package: debci
Severity: normal
X-Debbugs-Cc: pi...@debian.org
Hello
I am trying to fix the autopkgtest of python-mp-api[1] .
It seems that the test are failling to a ban of our IP adresses.
183s ERRORS
183s ___
Package: silver-platter
Version: 0.5.44-1+b1
Severity: important
X-Debbugs-Cc: pi...@debian.org
Hello,
picca@cush:/tmp$ debian-svp new-upstream libobjcryst
Traceback (most recent call last):
File "/usr/bin/debian-svp", line 33, in
sys.exit(load_entry_point('silver-
':!/.gitignore' ':!*/.gitignore'
dgit:
dgit: ... debian/patches is missing; perhaps this is a patch queue branch?
picca@page:~/debian/science-team/hyperspy$ git diff
4f3547c9556f7313400bf895d6a00bce3b8e6ee5 HEAD -- :/ ':!debian' ':!/.gitignore'
':!
[17:20:31]: host page; command line: /usr/bin/autopkgtest
/home/picca/debian/science-team/pyfai_2025.01-1.dsc
/home/picca/debian/science-team/pyfai_2025.01-1_amd64.changes -- unshare
--release UNRELEASED --arch amd64
: failure: ['mmdebstrap', '--variant=apt',
'--skip
It seems that the pytest cache directory try to write under a read only
part of the system...
Testing with python3.13:
= test session starts
==
platform linux -- Python 3.13.2, pytest-8.3.4, pluggy-1.5.0 --
/usr/bin/python3.13
cachedir:
Package: silx
Version: 1.1.0+dfsg-5
Severity: important
Dear Maintainer,
The autopkgtests fail with this error message
477s File "/usr/lib/python3/dist-packages/_pytest/cacheprovider.py", line
184, in set
477s self._mkdir(path.parent)
477s File "/usr/lib/python3/dist-packages/_pytest/ca
thanks a lot, it is ok with this NMU, you can also commit to the git repositoy
if you want :).
https://salsa.debian.org/science-team/ifeffit
Cheers
Fred
Hello Andreas,
you can fill an RM request. I think also that I do not have any time for
this software which I do not use anymore myself... I switched to
haskell ;).
Cheers
Fred
Is it possible to make it binNMUable ?
Fred
- Le 14 Jan 25, à 13:20, Emilio Pozuelo Monfort po...@debian.org a écrit :
> Package: pyvkfft-cuda
> Version: 2024.1.4+ds1-4
> Severity: serious
>
> Hi,
>
> The ongoing python3.13 as python3 interpreter causes your package to be
> uninstallable,
for more details):
- hkl-0.1.0.2 (lib) (first run)
- hkl-0.1.0.2 (exe:binoculars-ng) (first run)
Preprocessing library for hkl-0.1.0.2..
Building library for hkl-0.1.0.2..
[18 of 36] Compiling Hkl.H5 ( src/Hkl/H5.hs,
/home/picca/src/repo.or.cz/hkl/binoculars-ng/dist-newstyle/build/x86_64
Hello Jose Luis,
is it possible to solve this bug in order to avoid a bunch of reverse
dependency removal.
thanks a lot
Frédéric-Emmanuel
Source: scipy
Severity: normal
X-Debbugs-Cc: pi...@debian.org
Hello,
I am working on package which require the ascent.dat in order to run its test.
/usr/lib/python3/dist-packages/scipy/datasets/_fetchers.py:71: in ascent
fname = fetch_data("ascent.dat")
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
graph...
Checking test dependency graph end
test 1
Start 1: clpeak_test_run
1: Test command:
/home/picca/tmp/clpeak-1.1.2/obj-x86_64-linux-gnu/clpeak
1: Working Directory: /home/picca/tmp/clpeak-1.1.2/obj-x86_64-linux-gnu
1: Test timeout computed to be: 1000
1:
1: Platform: AMD Accelerated
Le 2024-09-30 08:57, Cordell Bloor a écrit :
Hi Fred,
Hello
Thanks. Does this clpeak work for you? Or are you experiencing this
same bug?
I am the one who reported the bug, so yes I am affected by this same bug
;)
We could try reviewing the package lists of systems where it works and
wh
Hello,
In any case, it works on my machine. I cannot reproduce the bug, so it
will require more investigation to determine why you're encountering
this problem and I am not.
What kind of investigation ?. I can test a few things.
another point
It would be great if the rocm-opencl-icd packag
Package: python3-gemmi
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
While preparing the new version of dials, I discoverd that the gemmi dependency
was not automatically generated during the packaging process. Indeed,
python3-gemmi does not provide the necessary dist-info
Package: rocm-opencl-icd
Version: 5.7.1-5
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
I just installed rocm-opencl-icd and try to run the clpeak program.
But I get this error message
$ clpeak
: CommandLine Error: Option 'sanitizer-early-opt-ep' registered more than once!
- Le 17 Sep 24, à 20:02, Mechtilde Stehmann mechti...@debian.org a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: Mechtilde Stehmann
> X-Debbugs-Cc: debian-de...@lists.debian.org, mechti...@debian.org
>
> * Package name: webext-folder-account
> Version : 12.0
> Upstre
Package: bornagain
Version: 22~git20240726093306.cb41cc4+ds3-1
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
While trying to use bornagain, I got this error message
$ bornagain
bornagain: error while loading shared libraries: _libBornAgainGUI.so: cannot
open shared object
> That is true. I don't consider the bug to be the use of a temporary
> directory,
> but instead the embedding of build paths. I'll do some more investigation to
> try to figure out whether that can be resolved within the build toolchain.
thanks
> It appears my fix here is incomplete or inaccu
> The meson-python build generates and uses a temporary, randomized build
> directory path only when no build-dir setting is already configured. So we
> may
> be able to resolve this problem by choosing an appropriate static build-dir.
why not fixing meson-python directly. This way it is simp
If you are part of the Debian science just push to the repository.
It is easyer for me to revert from git, than to remember to check for MR :)
thanks a lot for these investigation.
it is very appreciable
Frederic
- Le 9 Aoû 24, à 13:18, James Addison via Debian-pan-maintainers
debian-p
Hello, I am the facet-analyser maintainer/upstream (support)
If fact the conflict comes from
facet-analyser -> libinsighttoolkit5-dev -> lib-vtk9-dev -> python3-vtk9
facet analyser which is a PV plugins depends also on paraview-dev.
facet-analyser -> paraview-dev -> conflict with python3-vt
the packaging of the next version is done here
https://salsa.debian.org/js-team/node-jupyterlab
in the branch merge-python-and-node
to build it
git clone -b merge-python-and-node
https://salsa.debian.org/js-team/node-jupyterlab
and
cd node-jupyterlab
gbp buildpackage --git-ignore-branch \
Running the upstream script I have this
$ bash ./ci_script.sh
+ set -o pipefail
+ export YARN_ENABLE_GLOBAL_CACHE=1
+ YARN_ENABLE_GLOBAL_CACHE=1
+ export YARN_ENABLE_INLINE_BUILDS=1
+ YARN_ENABLE_INLINE_BUILDS=1
+ [[ '' != nonode ]]
+ python -c 'from jupyterlab.commands import build_check; buil
Source: jupyterlab
Version: 4.0.11+ds1-2
Severity: normal
Dear Maintainer,
It would be great if we could run integration test with autopkgtests.
The upstream run test test using the attached file
-- System Information:
Debian Release: 12.6
APT prefers stable-updates
APT policy: (500, 'stab
ODULE_NOT_FOUND',
requireStack: []
}
Node.js v20.15.1
[I 2024-08-06 18:03:27.952 ServerApp] jupyterlab | extension was successfully
linked.
[I 2024-08-06 18:03:27.955 ServerApp] Writing Jupyter server cookie secret to
/home/picca/.local/share/jupyter/runtime/jupyter_cookie_secret
[I 202
Package: pkg-perl-tools
Version: 0.79
Severity: normal
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
When preparing one of my package, I did
orange-canvas-core$ dpt prepare
gbp pull
gbp:info: Fetching from default remote for each branch
gbp:info: Branch 'upstream' is already up to da
Source: cython
Version: 3.0.10+dfsg-5
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
while working on the pyfai packages, I got an FTBFS due to gcc-14.
like this
[34/91] cc -Isrc/pyFAI/ext/sparse_utils.cpython-312-x86_64-linux-gnu.so.p
-Isrc/pyFAI/ext -I../src/pyFAI/ext -I
Package: gourmand
Version: 1.1.0+really1.1.0~rc3-4
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
While trying the applciation I got this instead of a working application
$ gourmand
args = Namespace(db_url='', threads=False, gourmanddir='',
thread_debug_interval=5.0, thread
Package: coot
Version: 1.1.08+dfsg-3
Severity: normal
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
While using coot I found that it save it's states in these files
DEBUG:: saving state to filename 0-coot.state.py
State file 0-coot.state.py written.
State file 0-coot-history.py written.
State
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pyta...@packages.debian.org, pi...@debian.org
Control: affects -1 + src:pytango
User: ftp.debian@packages.debian.org
Usertags: remove
pytango's migration to testing is blocked by the lack of an s390x
build; this lack is due to the build be
Here the upstream point of view about the CVE.
https://github.com/epics-base/epics-base/issues/405
check with the security team, if their analyse is ok ?
Fred
I forgot to add that you start this script like this
Test-Command: xvfb-run -s "-screen 0 1024x768x24 -ac +extension GLX
+render -noreset" sh debian/tests/gui
Depends:
mesa-utils,
coot,
xauth,
xvfb,
Restrictions: allow-stderr
Package: coot
Version: 1.1.08+dfsg-2
Severity: important
X-Debbugs-Cc: pi...@debian.org
while trying to start coot, I get this error message.
$ coot
INFO:: built with GTK 4.12.5
pdd /usr/share/coot
WARNING:: Coot REFMAC dictionary override COOT_REFMAC_LIB_DIR
/usr/share/coot/lib failed to find
Here the diff between the epics version (debian patch unapplyed) and the
current 2.1.0 version of yajl (debian patch unapplyed).
not that simple...diff --git a/src/yajl.c b/src/yajl.c
index d477893..fdad3f6 100644
--- a/src/yajl.c
+++ b/src/yajl.c
@@ -1,5 +1,5 @@
/*
- * Copyright (c) 2007-2014,
following a different path...,
I added this in the rules file
-export POSIX_CFLAGS+=$(CFLAGS)
+export POSIX_CFLAGS+=$(CFLAGS) $(shell pkgconf --cflags yajl)
export POSIX_CFLAGS+=$(CPPFLAGS)
export POSIX_CPPFLAGS+=$(CPPFLAGS)
-export POSIX_LDFLAGS+=$(LDFLAGS)
+export POSIX_LDFLAGS+=$(LDFLAGS) $(sh
I am working on it at the upstream level
need a few more days.
Cheers
Fred
Hello Andreas,
I have another autopkgtest failure on armel with silx and pocl
The content of check_atomic32 is
def check_atomic32(device):
try:
ctx = pyopencl.Context(devices=[device])
except:
return False, f"Unable to create context on {device}"
else:
queue
Package: silx
Version: 2.0.1+dfsg-1
Severity: normal
X-Debbugs-Cc: pi...@debian.org
Hello, the armel autopkgtest fail with this error message
1016s autopkgtest [22:49:50]: test opencl: [---
1017s pocl warning: encountered incomplete implementation in
./lib/CL/clGetDeviceInfo.
bravo !!!
This is team works. :))
Cheers
Frederic
Here an analyse of the FTBFS
On the amd64, I have two failures dureing the test
Test Summary Report
---
testPVAServer.t(Wstat: 0 Tests: 0 Failed: 0)
Parse errors: No plan found in TAP output
Files=6, Tests=129, 1 wallclock secs ( 0.05 usr 0.01 sys + 0.09 cusr 0.06
csys
A workaround for now is to use this
POCL_WORK_GROUP_METHOD=cbs
Jerome is helping also here trying to understand the problem...
https://github.com/silx-kit/silx/issues/4073
POCL_WORK_GROUP_METHOD=cbs python3 test.py
make it works
$ POCL_WORK_GROUP_METHOD=cbs python3 test.py
[SubCFG] Form SubCFGs in bsort_all
[SubCFG] Form SubCFGs in bsort_horizontal
[SubCFG] Form SubCFGs in bsort_vertical
[SubCFG] Form SubCFGs in bsort_book
[SubCFG] Form SubCFGs in bsort_file
[SubC
With latest version (PAS OK)
$ dpkg -l | grep pocl
ii libpocl2-common5.0-2.1
all common files for the pocl library
ii libpocl2t64:amd64 5.0-2.1
amd64
Debian12 (OK)
$ dpkg -l | grep pocl
ii libpocl2:amd64 3.1-3+deb12u1
amd64Portable Computing Language library
ii libpocl2-common 3.1-3+deb12u1
all co
On Debian12 it works out of the box
$ POCL_DEBUG=1 python3 test.py
[2024-03-11 10:05:31.837738936]POCL: in fn pocl_install_sigfpe_handler at line
229:
| GENERAL | Installing SIGFPE handler...
[2024-03-11 10:05:31.868890390]POCL: in fn POclCreateCommandQueue at line 98:
| GENERAL | Crea
We already had the warning message
[2024-03-10 14:26:18.189651850]POCL: in fn void
appendToProgramBuildLog(cl_program, unsigned int, std::string&) at line 111:
| ERROR | warning:
/home/picca/.cache/pocl/kcache/tempfile_msXjLw.cl:861:14: AVX vector argument
of type '__priva
Here a log with POCL_DEBUG=all
picca@cush:/tmp$ python3 test.py
[2024-03-10 14:22:19.462191847]POCL: in fn pocl_install_sigfpe_handler at line
265:
| GENERAL | Installing SIGFPE handler...
[2024-03-10 14:22:19.475550217]POCL: in fn POclCreateCommandQueue at line 103:
| GENERAL
111:
| ERROR | warning:
/home/picca/.cache/pocl/kcache/tempfile_NcEztR.cl:861:14: AVX vector argument
of type '__private float8' (vector of 8 'float' values) without 'avx' enabled
changes the ABI
warning: /home/picca/.cache/pocl/kcache/tempfile_NcEztR.cl:893:14: AVX v
Here a small script which trigger the errorfrom silx.image import medianfilter
import numpy
IMG = numpy.arange(1.0).reshape(100, 100)
KERNEL = (1, 1)
res = medianfilter.medfilt2d(
image=IMG,
kernel_size=KERNEL,
engine="opencl",
)
===
platform linux -- Python 3.11.8, pytest-8.0.2, pluggy-1.4.0 -- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /home/picca/debian/science-team/pyvkfft
plugins: anyio-4.2.0, dials-data-2.4.0, xvfb-3.0.0
collected 2
Package: wnpp
Severity: wishlist
Owner: Picca Frédéric-Emmanuel
X-Debbugs-Cc: debian-de...@lists.debian.org,
debian-pan-maintain...@alioth-lists.debian.net, pi...@debian.org
* Package name: pynx
Version : 2023.1.2-1
Upstream Contact: fa...@esrf.fr
* URL : https
With the silx 2.0.0 version the failire is located in the OpenCL part
the backtrace is this one when running the median filter
# build the packag eintht echroot and enter into it once build
dgit --gbp sbuild --finished-build-commands '%SBUILD_SHELL'
run this command to obtain the backtrace...
Package: python3-sphinx
Version: 5.3.0-4
Severity: important
Dear Maintainer,
Hello,, while preparing the new silx package, I got this error message from
sphinx when calling this command line
# build man pages
pybuild --build -s custom -p $(PY3VER) --build-args="cd doc && env
P
Source: cglm
Severity: important
Dear Maintainer,
While working on my 'hkl' package I now have an FTBFS due to the 0.9.2 cglm
version
The error is
hkl-binoculars-geometry.c: In function
‘hkl_binoculars_parameter_transformation_get’:
hkl-binoculars-geometry.c:45:45: error: incompatible type
Package: devscripts
Version: 2.23.7
Severity: important
Dear Maintainer,
While reporting a bug against cglm, I tried build-rdeps but got this message...
$ build-rdeps cglm
Reverse Build-depends in experimental/main:
---
Use of uninitialized value $source
Package: tango-db
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
I upgraded a computer from bullseye to bookwork. tango-db was
installed with the bulleyes version before the upgrade.
The upgrade went fine, so I installed the tango-starter (bookworm
version).
BUT the tango-s
for dials it seems that the CI works with pandas 2.1 from experimental.
https://ci.debian.net/packages/d/dials/unstable/amd64/41962612/#S4
- Le 30 Jan 24, à 9:05, Rebecca N. Palmer rebecca_pal...@zoho.com a écrit :
> I intend to upload pandas 2.x to unstable soon. These packages have a
> p
Package: pyfai
Version: 2023.9.0-1
Severity: important
Dear Maintainer,
Could you apply this patch in order to avoid a segfault in pyFAI-calib2
https://github.com/silx-kit/pyFAI/pull/2064
it correspond to this bug report
https://github.com/silx-kit/pyFAI/issues/2047
Cheers
-- System Informa
Source: zfp
Severity: important
Dear Maintainer,
since the upload of zfp 1.0.1, the test of hdf5plugin are failing
look at here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059842
It seems to me that the zfp library should be recompile with the previous flag.
thanks
Frederic.
PS: Il
ok for me
- Le 4 Jan 24, à 13:19, Alexandre Detiste alexandre.deti...@gmail.com a
écrit :
> Le jeu. 4 janv. 2024 à 07:48, Andreas Tille a écrit :
>> > @Vincent: this one package "gtextfsm" is yours
>> > do you green light an upload ?
>>
>> If you ask me the package is team maintained and a
It seems to me that the FTBFS was not due to cython 3.x but related to this bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054716
now that this bug is solved, can you re run the build for bitshuffle ?
Frederic
Would you mind to migrate bitshuffle under the Debian-science umbrella.
this way I could fix the package (cython3, h5py, ...) issues and and
upload the latest version.
thanks for considering.
Frederic
Source: stdeb
Severity: important
X-Debbugs-Cc: pi...@debian.org
Hello,
while trying to use pupy-install, I got this error message
/tmp$ pypi-download at
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/stdeb/transport.py", line 62, in request
resp.raise_for_status()
A workaround is to set DEBOOTSTRAP_DIR
sudo DEBOOTSTRAP_DIR=/usr/share/debootstrap
sbuild-debian-developer-setup
-setup
info: L'utilisateur « picca » appartient déjà au groupe « sbuild ».
I: SUITE: unstable
I: TARGET: /srv/chroot/unstable-amd64-sbuild
I: MIRROR: http://localhost:3142/deb.debian.org/debian
I: Running debootstrap --arch=amd64 --variant=buildd --verbose
--include=fakeroot,build-essential,eatm
Package: linux-image-6.1.0-13-amd64
Version: 6.1.55-1
Severity: normal
Dear Maintainer,
I am preparing a virtual machine wher eI install the linux-headers-amd54
package.
But it failed with this error message
Setting up linux-image-6.1.0-13-amd64 (6.1.55-1) ...^M
I: /vmlinuz is now a symlink to
Package: python3-h5py
Version: 3.7.0-8
Followup-For: Bug #1051781
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
If I create a link
ln -s h5py._debian_h5py_serial-3.7.0.dist-info h5py-3.7.0.dist-info
under /usr/lib/python3/dist-packages
It solves my issue.
So my question is should the python
Package: libg3d-plugins
Version: 0.0.8-36
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
I am the maintainer of the hkl package.
When I use the ghkl librarry, I get this error message
(ghkl:1336510): LibG3D-WARNING **: 15:03:32.967: libg3d: plugins: failed to
load /usr/lib
Package: python3-h5py
Version: 3.7.0-8
Severity: important
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
I am thre maintainer of silx
This package depende of python3-h5py and contain entry points.
The build is ok, but once installed I get this error message when I try to
start the applicati
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: g...@packages.debian.org, pi...@debian.org
Control: affects -1 + src:genx
Hello, the new version of genx added test about the numba part. Currently the
numba package is in bad shape f
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: bornag...@packages.debian.org, pi...@debian.org
Control: affects -1 + src:bornagain
previously the unit test were not activated. So now we have a real picture of
what is working and w
Source: onednn
Severity: normal
Dear Maintainer,
I am reparing local backports of onednn on bookwork in order to backports
pytorch-cuda for my institut.
But it FTBFS due to missing symbols.
dpkg-gensymbols: warning: debian/libdnnl2/DEBIAN/symbols doesn't match
completely debian/libdnnl2.symbo
Hello, here you should find the informations.
platform: Debina unstable
python: ~$ python3
Python 3.11.5 (main, Aug 29 2023, 15:31:31) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
$ dpkg -l | grep wx
ii libwxbase3.2-1:amd64
Hello, I am preparing the packaging of genx 3.6.22.
When I try to quit the application I have this error message
CRITICAL: uncought python error
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/genx/gui/main_window.py", line 1418, in
eh_mb_quit
if event.CanVeto() and
Source: genx
Severity: normal
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
If I try to quite the application with the menu quit, I get this
CRITICAL: uncought python error
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/genx/gui/main_window.py", line 1418, in
eh_mb_
Package: lintian-brush
Version: 0.149
Severity: normal
File: /usr/bin/apply-multiarch-hints
Dear Maintainer,
I try to use the multiarch hints but I get this error message
Downloading new version of multi-arch hints.
Traceback (most recent call last):
File "/usr/bin/apply-multiarch-hints", line
Source: epics-base
Severity: important
Dear Maintainer,
please fix these FTBFS
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Ke
Package: lintian-brush
Version: 0.149
Severity: normal
Dear Maintainer,
I am preparing the new hyperspy package but when I try to run lintian-brush on
it, I get this message
$ lintian-brush
/home/picca/debian/science-team/hyperspy: Please commit pending changes and
remove unknown files
the old and new hyperspy is not compatible with imagio > 0.28.
I kindly opened a bug report about the situation at the upstream git repository.
I filled a bug report about the new upstream.
https://github.com/g1257/dmrgpp/issues/40
It is already fixed in the upstream git
https://github.com/g1257/dmrgpp/commit/528501e4a5814d4cbb80e2cf16ea407f9e012ee6
and a comment about this issue
https://github.com/g1257/dmrgpp/issues/38#issuecomment-1655740289
Source: dmrgpp
Version: 6.02-3
Severity: wishlist
Dear Maintainer,
A new version is available, could you package it
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-1-a
Source: pyqt6
Severity: normal
Dear Maintainer,
I would be great if we could have the documentation available in a dedicated
package.
there is a sphinx_qt_documentation extension which rely on intersphinx in order
to create link
about PyQt5/6 API. to produce some good documentation.
for now th
Hello,
I dicovered that upstream modifier yajl in order to support json5.
I am wondering if their modification could not be integrated in our yajl.
I fill a burg report about this idea here
https://github.com/epics-base/epics-base/issues/405
Tell me what is your opinion about this.
Cheers
Fre
Package: python3-mesonpy
Version: 0.12.0-2
Severity: normal
X-Debbugs-Cc: pi...@debian.org
Dear Maintainer,
I am packaging python-fabio and pyfai whcih use this new build system for
python extensions.
Now blhc complain that the compilation is not verbose.
So I need to add something like this to
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: python-fa...@packages.debian.org, pi...@debian.org
Control: affects -1 + src:python-fabio
thanks for considering
Frederic
> I am just the messenger here, if you disagree, please feel free to
> contact ftpmasters or lintian maintainers.
This was not a rant about this, I just wanted to understand what is going on :).
> Your package has been built successfully on (some) buildds, but then the
> binaries upload got rejec
I just check this date is in the upstream tar file
https://files.pythonhosted.org/packages/54/84/ea12e176489b35c4610625ce56aa2a1d91ab235b0caa71846317bfd1192f/pyfai-2023.5.0.tar.gz
ok, it seems that I generated an orig.tag.gz with this (Thu Jan 1 00:00:00
1970).
I can not remember which tool I used to generate this file.
gbp import-orig --uscan
or
deb-new-upstream
Nevertheless, why is it a serious bug ?
thanks
Frederic
thanks a lot
1 - 100 of 978 matches
Mail list logo
