> 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,
Here the answer of the taurus upstream (he forgot to CC the the bts)
Carlos Pascual [cpasc...@cells.es]
Hi Fred and Jonathan,
First of all, sorry for the late reply (I hope it is still relevant). I am
currently out of office and with limited email access. If you require
further info, plea
so here the question
> That's where you come in. You're the maintainer and the expert in this
> package. Are 251 and 221 that common and important that the other
> changes are worth less testing than usual?
Yes I know about the package, I trust also the upstream when they did that they
did all t
Done :)
thanks for your work.
Fred
uploaded.
thanks a lot
Fred
Uploaded
thanks for your work
Frederic
uploaded.
thanks for your work :)
De : Sean Whitton [spwhit...@spwhitton.name]
Envoyé : mercredi 13 janvier 2016 04:19
À : sub...@bugs.debian.org
Objet : Bug#810870: RFS: propellor/2.15.3-1 -- property-based host
configuration management in haskell
Packag
accepted :)
Hello Ghislain,
I am wondering it this python-qtawesome package should not be replace by the
already available one [1]
python-xstatic-font-awesome.
It would be great if we could convince the spyder upstream to use the
python-xstatic system instead of embeding third party solutions.
Cheers
Fr
> I don't know enough about the python-qtawesome package to tell whether
> python-xstatic-font-awesome is equivalent functionality-wise.
Me too :)
> I don't expect it to be an easy pitch to ask the Spyder team to
> rethink their dependency chain just for the sake of re-usability.
> Unless you ha
Hello,
Here a test.hs file which show starnge behaviour when using the tab key
Go to the open [ and hit tab
before
packages :: [Package]
packages =
[
-- hardware
"firmware-linux-nonfree"
]
after
packages :: [Package]
packag[
-- hardware
"firmware-li
In fact I would change the title :)
for
indentation problem with
I do not know if the new version solve this problem.
Fred
Hello Ghislain.
I see only one problem you did not repackage the source with a +dfsg in order
to remove the font files.
If you let the files inside the source package you need to add the copyright
information of these files.
the best is to repackge using the Files-Excludes in the copyright fil
Hello Ghislain
>* The -common package contains 2 fonts, one of which is not available
> for Debian (elusive-iconfont, SIL OFL 1.1). The other one (fontawesome)
> is symlinked from its corresponding package.
in that case can you create a real fonts package in order to be consistant with
all o
> The Spyder Development Team is not upstream of this font actually. So I
> don't think creating a font package from this source package is the
> right solution, is it?
No you are right
I looked at the elusive content
/tmp$ unzip elusive-icons-2.0.0.zip
Archive: elusive-icons-2.0.0.zip
crea
done.
thanks for your contribution :))
De : Sean Whitton [spwhit...@spwhitton.name]
Envoyé : dimanche 3 janvier 2016 18:28
À : sub...@bugs.debian.org
Objet : Bug#809747: RFS: propellor/2.15.1-1 -- property-based host
configuration management in haskell
P
done :)
Thanks
Fred
De : Sean Whitton [spwhit...@spwhitton.name]
Envoyé : lundi 4 janvier 2016 13:58
À : sub...@bugs.debian.org
Objet : Bug#809826: RFS: propellor/2.15.2-1 -- property-based host
configuration management in haskell
Package: sponsorship-re
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
Thanks to Picca Frederic-Emmanuel (Closes: #793789)
* d/control: cme fix, wrap and sort, update descriptions.
* Add examples to doc package.
* Move documentation generation to arch-indep targets.
* Add autopkgtest testsuite.
* Simplify clean target.
Best regards,
Ghislain Vaillant
Hello Sean
> git changed its behaviour, but there was a fix added to DotDir.hs some
> time ago. What version are you upgrading from? Please look in
> DotDir.hs in your repo for the string
my local.propellor repository contained the 3.2.3 version.
Then I upgrade my unstable machine with the late
setupUpstreamMaster :: String -> IO ()
setupUpstreamMaster newref = do
changeWorkingDirectory =<< dotPropellor
go =<< catchMaybeIO getoldrev
where
go Nothing = warnoutofdate False
go (Just oldref) = do
let tmprepo = ".git/propellordisttmp"
> Okay. I think that this is a bug, but I don't know how to reproduce it
> yet.
> Do you have an upstream remote pointing to Joey's repository?
[remote "upstream"]
url = /usr/src/propellor/propellor.git
fetch = +refs/heads/*:refs/remotes/upstream/*
> Please run propellor with PR
I did a
git merge -Xtheirs upstream/master --allow-unrelated-hitories
this wipeout my config-simple.hs.
So I ammended the merge in order to restore config.hs and fix it with the new
propellor.
I hope that next timeit will work without all this mess ;)
Cheers
Fred
Hello,
One difficulty I have with sbuild is to deal with http proxy.
During the chroot creation, it goes well because I have on my system the apt
proxy setup but
at the end of the installation, there is an upgrade of the chroot and it failed
with a timeout because there is no proxy setup in the
Hello guyes,
look at here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873921
:((
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 op
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
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 o
Yes I work on this with the upstream :))
So don't worry I will tell you when it is ok.
Cheers
Fred
I Uploaded tango 9.2.5~rc3+dfsg1-1into Debian unstable.
I think that once migrated into testing it will be ok toclose this bug.
Thanks
Fred
> 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.
W
Hello Ghislain.
do you know if this version is compatible with the reverse dependencies already
in Debian ?
python-qtpy
Reverse Depends:
python-spyder
python-ginga
python-qtawesome
python-glue
We are close from the freeze and I do not want to end up with a bunch of autorm
packages due
I am on it :)
Cheers
De : Ghislain Vaillant [ghisv...@gmail.com]
Envoyé : mercredi 25 janvier 2017 19:00
À : sub...@bugs.debian.org
Objet : Bug#852626: RFS: h5py/2.7.0~rc3-1 [RC]
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking
to late ;)
De : PICCA Frederic-Emmanuel
Envoyé : mercredi 25 janvier 2017 19:10
À : Ghislain Vaillant; 852...@bugs.debian.org; sub...@bugs.debian.org
Objet : Bug#852626: RFS: h5py/2.7.0~rc3-1 [RC]
I am on it :)
Cheers
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 Pic
once uploaded I need also to upload from experimental
spyder (3.x) in order to fix the current spyder 2.x which is broken in unstable.
Frédéric
Re-Hello, In order to upload a sardana compatible with ipython5, it need to
also upload pytango9 -> tango transition.
Cheers
Frédéric
python-qtconsole Source uploaded :)
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
The problem was in scipy,
#840264
Now it is fixed.
Hello,
Is it possible to upload ipykernel in order to allow qtconsole to compile ?
Thanks
Frederic
> 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 looking
> 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
Hello Luca
> This is very unfortunate, but as explained on the mailing list, this
> behaviour was an unintentional internal side effect. I didn't quite
> realise it was there, and so most other devs.
I understand, I just wanted to point that the synchrotron community invest a
lot of efforts in o
Hello,
I just opened a bug for tango
https://github.com/tango-controls/cppTango/issues/312
what is the deadline where we can take the decision to upload or not zeromq
4.2.0 into Debian testing ?
This will let also some time in order to check if this 4.2.0 do not have other
size effect of dep
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
> 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
Hello, somenews about this issue ?
Cheers
Fred
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 adm
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 administrator
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 y
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 | gr
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 re
> I am not sure that I follow what you are doing, but if you need the code
> to be run with the dbadmin privileges, you should put the code in:
>/usr/share/dbconfig-common/data/PACKAGE/upgrade-dbadmin/DBTYPE/VERSION
> instead of in:
>/usr/share/dbconfig-common/data/PACKAGE/upgrade/DBTYPE/VE
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 privi
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 xxx
> 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
> jupyter
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
Hello, here the guy who packages python-qtconsole
This package provide
ipython-qtconsole
ipython3-qtconsole
jupyter-qtconsole
python-qtconsole
python-qtconsole-doc
python3-qtconsole
where
ipython(3)-qtconsole are transitionnal packages in order to install
python(3)-qtcon
Hello Sean,
in flycheck-doc, you put this
+Depends: www-browser, elpa-flycheck (= ${source:Version})
+Suggests: elpa-flycheck
why this dependency to elpa-flycheck ?
Hello Andreas, what is strange is this
https://piuparts.debian.org/sid/state-successfully-tested.html#pymca-doc
Is there a problem with piuparts ?
Hello Sean
diff --git a/debian/control b/debian/control
index 9194b6c..21a524d 100644
--- a/debian/control
+++ b/debian/control
@@ -43,7 +43,7 @@ Depends: ${misc:Depends}, ${shlibs:Depends},
libghc-stm-dev,
libghc-text-dev,
libghc-concurrent-output-dev,
- git,
+
> It means you need git 2.9 on the system you run `propellor --spin`, but
> it shouldn't break anything on the host you are trying to configure.
Yes, but usually, I prepare my configuration on the targetted machine. (a
jessie machine)
So if I can not run propello on jessie I will be really sad ;
> So you're installing the .deb from stretch on your jessie machine?
Yes exactly I rebuild the propellor on my jessie machines.
> I suggest that you install the /usr/bin/propellor wrapper from the
> jessie repos, and then use a more recent ~/.propellor. E.g.:
>cd ~/.propellor
>git remo
Hello during the packaging I get this error message for the tests
==
ERROR: spyderlib.widgets.tests.test_array_builder
(unittest.loader.ModuleImportFailure)
--
I
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...
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
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 \
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
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
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
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,
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
I am working on it at the upstream level
need a few more days.
Cheers
Fred
Hello Anton, I try to checkout paraview in order to add the -dev dependencies
but I have this message
$ git clone https://salsa.debian.org/science-team/paraview
Clonage dans 'paraview'...
remote: Enumerating objects: 175624, done.
remote: Counting objects: 100% (78929/78929), done.
remote: Compre
Hello François,
thanks a lot, I removed the NMU number and release a -2 package. (uploaded)
thanks for your contribution to Debian.
Fred
in order to debug this, I started gdb
set a breakpoint in init_module_scitbx_linalg_ext
then a catch throw and I end up with this backtrace
Catchpoint 2 (exception thrown), 0x770a90a1 in __cxxabiv1::__cxa_throw
(obj=0xb542e0, tinfo=0x772d8200 , dest=0x772c1290
) at
../../../..
There is a fix from the upstream around enum.
https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013
Fix enum_type_object type on Python 3.11
The enum_type_object type inherits from PyLong_Type which is not tracked
by the GC. Instances doesn't have to be tracked by
Hello Anton, I have just pushed a few dependencies in the -dev package in the
salsa repo
I did not updated the changelog.
Cheers
Fred
If I remove the pylint package, no more error...
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
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
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
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
> 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
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
In order to reproduce the bug,
install python3-silx 2.0.0+dfsg-1
python3-pytest-xvfb pocl-opencl-icd
then
$ pytest --pyargs silx.image.test.test_medianfilter -v
===
test session starts
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",
)
It seems that here is an error here
[2024-03-10 14:22:19.550588408]POCL: in fn int
pocl_llvm_build_program(cl_program, unsigned int, cl_uint, _cl_program* const*,
const char**, int) at line 420:
| LLVM | all build options: -Dcl_khr_int64
-DPOCL_DEVICE_ADDRESS_BITS=64 -D__USE_CLANG_OPENC
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 | Create
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 '__private float8' (vec
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
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
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
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
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
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
bravo !!!
This is team works. :))
Cheers
Frederic
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
101 - 200 of 340 matches
Mail list logo
