Bug#1027941: O: keras-preprocessing -- data preprocessing module for the Keras deep learning framework
Package: wnpp Severity: normal X-Debbugs-Cc: keras-preprocess...@packages.debian.org Control: affects -1 + src:keras-preprocessing I intend to orphan the keras-preprocessing package, as it is no longer maintained upstream as an independent software from tensorflow, and the base package keras is now giving errors with the latest version of numpy that I cannot resolve. The package description is: Keras is a Python library for machine learning based on deep (multi- layered) artificial neural networks (DNN), which follows a minimalistic and modular design with a focus on fast experimentation. . Features of DNNs like neural layers, cost functions, optimizers, initialization schemes, activation functions and regularization schemes are available in Keras a standalone modules which can be plugged together as wanted to create sequence models or more complex architectures. Keras supports convolutions neural networks (CNN, used for image recognition resp. classification) and recurrent neural networks (RNN, suitable for sequence analysis like in natural language processing). . It runs as an abstraction layer on the top of Theano (math expression compiler) by default, which makes it possible to accelerate the computations by using (GP)GPU devices. Alternatively, Keras could run on Google's TensorFlow (not yet available in Debian). . Keras Preprocessing is the data preprocessing and data augmentation module of the Keras deep learning library. It provides utilities for working with image data, text data, and sequence data.
Bug#1027940: O: keras-applications -- popular models and pre-trained weights for the Keras deep learning framework
Package: wnpp Severity: normal X-Debbugs-Cc: keras-applicati...@packages.debian.org Control: affects -1 + src:keras-applications I intend to orphan the keras-applications package, as the upstream package is no longer maintained as an independent software from tensorflow, and its base package keras now has errors with the latest version of numpy that I cannot resolve. The package description is: Keras is a Python library for machine learning based on deep (multi- layered) artificial neural networks (DNN), which follows a minimalistic and modular design with a focus on fast experimentation. . Features of DNNs like neural layers, cost functions, optimizers, initialization schemes, activation functions and regularization schemes are available in Keras a standalone modules which can be plugged together as wanted to create sequence models or more complex architectures. Keras supports convolutions neural networks (CNN, used for image recognition resp. classification) and recurrent neural networks (RNN, suitable for sequence analysis like in natural language processing). . It runs as an abstraction layer on the top of Theano (math expression compiler) by default, which makes it possible to accelerate the computations by using (GP)GPU devices. Alternatively, Keras could run on Google's TensorFlow (not yet available in Debian). . Keras Applications is the applications module of the Keras deep learning library. It provides model definitions and pre-trained weights for a number of popular architectures, such as VGG16, ResNet50, Xception, MobileNet, and more.
Bug#1027938: O: keras -- deep learning framework running on Theano or TensorFlow
Package: wnpp Severity: normal X-Debbugs-Cc: ke...@packages.debian.org Control: affects -1 + src:keras I intend to orphan the keras package, as it is no longer updated as an independent package outside of tensorflow, and the last independent problem now has difficult to resolve errors with the latest version of numpy. The package description is: Keras is a Python library for machine learning based on deep (multi- layered) artificial neural networks (DNN), which follows a minimalistic and modular design with a focus on fast experimentation. . Features of DNNs like neural layers, cost functions, optimizers, initialization schemes, activation functions and regularization schemes are available in Keras a standalone modules which can be plugged together as wanted to create sequence models or more complex architectures. Keras supports convolutions neural networks (CNN, used for image recognition resp. classification) and recurrent neural networks (RNN, suitable for sequence analysis like in natural language processing). . It runs as an abstraction layer on the top of Theano (math expression compiler) by default, which makes it possible to accelerate the computations by using (GP)GPU devices. Alternatively, Keras could run on Google's TensorFlow (not yet available in Debian).
Bug#1020544: siconos: FTBFS on s390x: Cholesky solve kNM_test failed
On Fri, Sep 23, 2022 at 5:33 AM Aron Xu wrote: > Package: siconos > Version: 4.4.0+dfsg-1 > Severity: important > > The new version FTBFS on s390x in test suite 23, relevant log entry: > > > Cholesky solve preserving matrix > > Cholesky solve kNM_test: ./numerics/src/tools/NumericsMatrix.c:3023: > NM_csc: > Assertion `A->matrix2->csc->m == A->size0 && "inconsistent size > > Full build log is > > https://buildd.debian.org/status/fetch.php?pkg=siconos&arch=s390x&ver=4.4.0%2Bdfsg-1&stamp=1663797112&raw=0 > > Regards, > Aron > > Thanks for this bug report. I was able to reproduce the problem under qemu, and it is unclear to me whether the problem is actually a missing step in dense-to-sparse conversion, or simply a problematic assert after. It seems to be an issue showing up only on this architecture, because the numerical results of the test are slightly different, but this is possibly revealing a logical error in how dense to sparse is working or how the results are checked. Therefore, I have reported it upstream [0] and will try to include a patch in a package update if/when we are able to determine what is going on here. [0] https://github.com/siconos/siconos/issues/467 regards, Steve
Bug#1016600: siconos: vtk[6,7] removal
On Thu, Sep 1, 2022 at 10:56 PM Adrian Bunk wrote: > > On Wed, Aug 03, 2022 at 10:42:08PM +0200, Sebastian Ramacher wrote: > > Source: siconos > > Version: 4.3.1+dfsg-2 > > Severity: serious > > X-Debbugs-Cc: sramac...@debian.org > > Tags: sid bookworm > > Control: block 1016597 by -1 > > User: gl...@debian.org > > Usertags: vtk6_vtk7_removal > > > > Based on #1013156 and similar bugs: > > > > Dear maintainer, > > > > Debian archive has now three major versions of the VTK (The > > Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions > > (vtk6 and vtk7) are not supported by upstream and the package itself > > is not easy for the mainance. > > > > We aim to drop old and deprecated version vtk6 and vtk7 packages before > > the freeze of the Debian 12 Bookworm. Your package depends on vtk6 or > > vtk7. Thus we ask you to migrate it to the latest vtk9 package. > > Two observations regarding the usage of VTK in siconos: > > There is WITH_VTK in siconos that does not seem to build with VTK 9, > but it's anyway not enabled. > > The only current usage of VTK is python3-vtk7 in siconos-mechanics-tools. > This might need upstrream fixes like > https://github.com/siconos/siconos/pull/437 > > > Cheers Thank you Adrian. I have an update to the package for a newer upstream version that has been under construction for a while, but I haven't been available until recently to work on it more. I'll try to get this done soon. Steve
Bug#986515: siconos: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test "ARGS=-E 'COLLECTION|collection|python_test_lcp|dr_iso1|ContactTest'" ARGS\+=-j1 returned exit code 2
I was unable to reproduce this issue. The build was successful for me locally and on Debian Salsa server. The salsa build log can be found here: https://salsa.debian.org/science-team/siconos/-/jobs/1562650/raw My local build log is attached from running dpkg-buildpackage. regards, Stephen Sinclair On Wed, Apr 7, 2021 at 9:01 AM Lucas Nussbaum wrote: > > Source: siconos > Version: 4.3.1+dfsg-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20210406 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in bullseye, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > > Running tests... > > /usr/bin/ctest --force-new-ctest-process -E > > 'COLLECTION|collection|python_test_lcp|dr_iso1|ContactTest' -j1 > > Test project /<>/obj-x86_64-linux-gnu > > Start 1: DLSODES-test > > 1/95 Test #1: DLSODES-test Passed > > 0.01 sec > > Start 2: DLSODAR-test > > 2/95 Test #2: DLSODAR-test Passed > > 0.01 sec > > Start 3: DLSODI-test > > 3/95 Test #3: DLSODI-test . Passed > > 0.02 sec > > Start 4: DLSODPK-test > > 4/95 Test #4: DLSODPK-test Passed > > 0.12 sec > > Start 5: DLSODA-test > > 5/95 Test #5: DLSODA-test . Passed > > 0.01 sec > > Start 6: DLSODE-test > > 6/95 Test #6: DLSODE-test . Passed > > 0.01 sec > > Start 7: DLSODIS-test > > 7/95 Test #7: DLSODIS-test Passed > > 0.01 sec > > Start 8: DLSODKR-test > > 8/95 Test #8: DLSODKR-test Passed > > 0.03 sec > > Start 9: DLSOIBT-test > > 9/95 Test #9: DLSOIBT-test Passed > > 0.04 sec > > Start 10: odepacktest10 > > 10/95 Test #10: odepacktest10 ... Passed > > 0.00 sec > > Start 11: dr1_radau5 > > 11/95 Test #11: dr1_radau5 .. Passed > > 0.01 sec > > Start 12: dr2_radau5 > > 12/95 Test #12: dr2_radau5 .. Passed > > 0.01 sec > > Start 13: dr_radau > > 13/95 Test #13: dr_radau Passed > > 0.00 sec > > Start 14: dr_radaup > > 14/95 Test #14: dr_radaup ... Passed > > 0.01 sec > > Start 15: dr_rodas > > 15/95 Test #15: dr_rodas Passed > > 0.00 sec > > Start 16: dr_seulex > > 16/95 Test #16: dr_seulex ... Passed > > 0.00 sec > > Start 17: test_op3x3 > > 17/95 Test #17: test_op3x3 .. Passed > > 0.26 sec > > Start 18: test_timers_interf > > 18/95 Test #18: test_timers_interf .. Passed > > 0.01 sec > > Start 19: test_blas_lapack > > 19/95 Test #19: test_blas_lapack Passed > > 0.01 sec > > Start 20: test_pinv > > 20/95 Test #20: test_pinv ... Passed > > 0.02 sec > > Start 21: tools_projection > > 21/95 Test #21: tools_projection Passed > > 0.01 sec > > Start 22: NumericsArrays > > 22/95 Test #22: NumericsArrays .. Passed > > 0.01 sec > > Start 23: NM_test > > 23/95 Test #23: NM_test . Passed > > 0.17 sec > > Start 24: tools_test_JordanAlgebra > > 24/95 Test #24: tools_test_JordanAlgebra Passed > > 0.01 sec > > Start 25: NM_MUMPS_test > > 25/95 Test #25: NM_MUMPS_test ... Passed > > 0.01 sec > > Start 26: SBM_test > > 26/95 Test #26: SBM_test Passed > > 0.02 sec > > Start 27: SBCM_to_SBM > > 27/95 Test #27: SBCM_to_SBM . Passed > > 0.01 sec > > Start 28: SparseMatrix_test > > 28/95 Test #28: SparseMatrix_test ... Passed > >
Bug#975099: O: lasagne -- deep learning library build on the top of Theano
Package: wnpp Severity: normal Version: 0.1+git20160728.8b66737-2 Package has bugs that cannot be easily solved and upstream is unresponsive. Its main dependency Theano is still in Debian but upstream is EOL, so it is unlikely upstream will continue maintenance.
Bug#972394: likely cause: Python.h not found because of version mismatch 3.8 vs 3.9
On Wed, Oct 21, 2020 at 10:39 AM Adrian Bunk wrote: > > Control: retitle -1 siconos FTBFS with more than one supported python3 version > > On Mon, Oct 19, 2020 at 11:38:42PM +0200, Markus Koschany wrote: > > > > I built siconos in a clean chroot environment. The recent rebuild of > > siconos also shows build failures > > > > https://buildd.debian.org/status/package.php?p=siconos > > > > I don't think it's specific to my environment. > > You need something like python3-dev -> python3-all-dev in the build > dependencies. I can confirm that making this change allows the package to build. However, some Python-related tests in autopkgtest fail when trying to import the Siconos python modules, so something still needs to be fixed. I will investigate. As for this change, however, is it the correct one to make? Or should I wait for more information in #972551? > The next problem is what it builds - it then builds for the highest > version only, not for the default version. Can I ask how you determined this? It is not surprising that something could be wrong, as the CMake configuration is very complicated in this package. However, the configure step includes the line, -DPYTHON_EXECUTABLE=$(shell which python3)" which should specify the path to the default Python interpreter. Is there a better way to determine this path? > This bug could be solved by either adjusting the build dependencies > and the build to build for all supported python3 versions, or by fixing > whatever in the build system does not use the default version. I would prefer the latter as the package is already quite complicated and does not play well with multiple pythons. regards, Steve
Bug#963621: RFS: keras/2.3.1+dfsg-2 [RC] -- deep learning framework running on Theano or TensorFlow
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "keras" * Package name: keras Version : 2.3.1+dfsg-2 Upstream Author : François Chollet * URL : https://keras.io/ * License : Expat * Vcs : https://salsa.debian.org/science-team/keras Section : science It builds those binary packages: python3-keras - deep learning framework running on Theano or TensorFlow To access further information about this package, please visit the following URL: https://mentors.debian.net/package/keras Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/keras/keras_2.3.1+dfsg-2.dsc Changes since the last upload: * debian/patches: + fix test regression for python3-h5py 2.10.0-8. (Closes: #963426) The package will not be updated to Keras release 2.4.0 due to end-of-life. In the future Keras will be included in TensorFlow, which is not yet available in Debian; when it is, this package will be removed, but until then this package remains the principle way to include Keras in Debian. Please read: https://github.com/keras-team/keras/releases/tag/2.4.0 This update fixes a small problem with a test due to updates to python3-h5py. Regards, -- Stephen Sinclair
Bug#962441: RFS: siconos/4.3.0+dfsg-1 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
The problem turned out to be a real bug (null dereference) that only occurred occasionally due to poor testing procedures (test includes some randomization in the code path). The bug has been patched and a separate RFS for fclib has been filed, #962684. regards, Steve On Mon, Jun 8, 2020 at 6:09 PM Stephen Sinclair wrote: > > Hi Adam, > > Thanks for taking a look. > > On Mon, Jun 8, 2020 at 5:29 PM Adam Borowski wrote: > > > > On Mon, Jun 08, 2020 at 07:37:26AM +0200, Stephen Sinclair wrote: > > > * Package name: siconos > > >Version : 4.3.0+dfsg-1 > > > > But > > > > > Testing this package requires fclib 3.1.0+dfsg-1, which also needs > > > sponsorship. It can be found here: > > > > > > https://mentors.debian.net/package/fclib > > > > so thats actually two RFSes in one. And there are problems with fclib. > > I'm not sure what the right protocol is in this case, to be honest. > Should I have issued two RFSes or done this one differently? > > > > Changes since the last upload: > > > > > >* New upstream version. (Closes: #962219) (Closes: #961735) > > >* Add dependencies libboost-timer-dev, libboost-chrono-dev. > > >* Depend on openblas and lapacke instead of atlas. > > >* Require fclib 3.1.0 > > >* Update location of install paths. > > >* Enable WITH_GENERATION, now required for serialization. > > >* Install new siconos_export_raw_data tool. > > >* Fix cmake import targets to allow independent packages. > > >* Update patches for new upstream version. > > >* Add a flag for gfortran to avoid a regression in GCC-10. > > > (Closes: #957794) > > >* Remove unused build rule for swig3.0 symlink. > > >* Remove non-existent files from debian/copyright. > > >* Rewrite patch descriptions using gbp pq. > > >* Fix a Python warning about using 'is' with a literal. > > > > It looked ok on my box, and passed both all automated and manual review I've > > done. But, it fails on some of official buildds: at least on amd64 arm64 > > x32. > > > > I seem unable to reproduce the FTBFS locally -- in 15 tries on amd64, 1 on > > arm64, all passed. > > > > Thus, you'd need to investigate and fix that one in fclib first. > > I'm very confused about the error on buildd because I have indeed > built the package many times with a fresh debootstrap without such a > segfault. I will investigate and try to reproduce. > > I did my best to avoid problems but it seems I have missed something, > I'd like to understand the difference between buildd and my own > configuration to avoid this happening in the future. > > By the way Siconos due to its nature has been quite hard to get > working on any architecture other than amd64 unfortunately. Is there > a way to mark the package as amd64-only? > In the meantime I try to find solutions for other architectures but it > is slow going. > > > It'd be good if you filed a separate RFS for that. Let's leave this one > > for siconos 4.3.0+dfsg-1 > > Okay that sounds like a reasonable approach given this problem. > > regards, > Steve
Bug#962684: RFS: fclib/3.1.0+dfsg-2 -- read and write problems from the Friction Contact Library (library)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "fclib" * Package name: fclib Version : 3.1.0+dfsg-2 Upstream Author : fclib-proj...@lists.gforge.inria.fr * URL : https://frictionalcontactlibrary.github.io/ * License : Apache-2.0 * Vcs : https://salsa.debian.org/science-team/fclib Section : science It builds those binary packages: libfclib0 - read and write problems from the Friction Contact Library (library) libfclib-dev - read and write problems from the Friction Contact Library (headers) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fclib Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fclib/fclib_3.1.0+dfsg-2.dsc Changes since the last upload: * Patch wrong argument to cs_transpose which leads to segfault. (Closes: #927761) The previous upload, 3.1.0+dfsg-1, failed on buildd and this patch fixes the problem. This package is required for siconos 4.3.0+dfsg-1, uploaded in parallel, with RFS #962441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962441 Regards, -- Stephen Sinclair
Bug#962441: RFS: siconos/4.3.0+dfsg-1 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
Hi Adam, Thanks for taking a look. On Mon, Jun 8, 2020 at 5:29 PM Adam Borowski wrote: > > On Mon, Jun 08, 2020 at 07:37:26AM +0200, Stephen Sinclair wrote: > > * Package name: siconos > >Version : 4.3.0+dfsg-1 > > But > > > Testing this package requires fclib 3.1.0+dfsg-1, which also needs > > sponsorship. It can be found here: > > > > https://mentors.debian.net/package/fclib > > so thats actually two RFSes in one. And there are problems with fclib. I'm not sure what the right protocol is in this case, to be honest. Should I have issued two RFSes or done this one differently? > > Changes since the last upload: > > > >* New upstream version. (Closes: #962219) (Closes: #961735) > >* Add dependencies libboost-timer-dev, libboost-chrono-dev. > >* Depend on openblas and lapacke instead of atlas. > >* Require fclib 3.1.0 > >* Update location of install paths. > >* Enable WITH_GENERATION, now required for serialization. > >* Install new siconos_export_raw_data tool. > >* Fix cmake import targets to allow independent packages. > >* Update patches for new upstream version. > >* Add a flag for gfortran to avoid a regression in GCC-10. > > (Closes: #957794) > >* Remove unused build rule for swig3.0 symlink. > >* Remove non-existent files from debian/copyright. > >* Rewrite patch descriptions using gbp pq. > >* Fix a Python warning about using 'is' with a literal. > > It looked ok on my box, and passed both all automated and manual review I've > done. But, it fails on some of official buildds: at least on amd64 arm64 > x32. > > I seem unable to reproduce the FTBFS locally -- in 15 tries on amd64, 1 on > arm64, all passed. > > Thus, you'd need to investigate and fix that one in fclib first. I'm very confused about the error on buildd because I have indeed built the package many times with a fresh debootstrap without such a segfault. I will investigate and try to reproduce. I did my best to avoid problems but it seems I have missed something, I'd like to understand the difference between buildd and my own configuration to avoid this happening in the future. By the way Siconos due to its nature has been quite hard to get working on any architecture other than amd64 unfortunately. Is there a way to mark the package as amd64-only? In the meantime I try to find solutions for other architectures but it is slow going. > It'd be good if you filed a separate RFS for that. Let's leave this one > for siconos 4.3.0+dfsg-1 Okay that sounds like a reasonable approach given this problem. regards, Steve
Bug#962441: RFS: siconos/4.3.0+dfsg-1 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "siconos" * Package name: siconos Version : 4.3.0+dfsg-1 Upstream Author : siconos-t...@lists.gforge.inria.fr * URL : https://nonsmooth.gricad-pages.univ-grenoble-alpes.fr/siconos/index.html * License : Apache-2.0 * Vcs : https://salsa.debian.org/science-team/siconos Section : science It builds those binary packages: siconos - modeling and simulation of nonsmooth dynamical systems (simulation runner tool) siconos-mechanics-tools - modeling and simulation of nonsmooth dynamical systems (mechanics tools) libsiconos-numerics6 - modeling and simulation of nonsmooth dynamical systems (numerics lib) libsiconos-numerics-dev - modeling and simulation of nonsmooth dynamical systems (numerics dev) libsiconos-kernel6 - modeling and simulation of nonsmooth dynamical systems (kernel lib) libsiconos-kernel-dev - modeling and simulation of nonsmooth dynamical systems (kernel dev) libsiconos-control6 - modeling and simulation of nonsmooth dynamical systems (control lib) libsiconos-control-dev - modeling and simulation of nonsmooth dynamical systems (control dev) libsiconos-mechanics6 - modeling and simulation of nonsmooth dynamical systems (mechanics lib) libsiconos-mechanics-dev - modeling and simulation of nonsmooth dynamical systems (mechanics dev) libsiconos-io6 - modeling and simulation of nonsmooth dynamical systems (io lib) libsiconos-io-dev - modeling and simulation of nonsmooth dynamical systems (io dev) python3-siconos - modeling and simulation of nonsmooth dynamical systems (python3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/siconos Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/siconos/siconos_4.3.0+dfsg-1.dsc Testing this package requires fclib 3.1.0+dfsg-1, which also needs sponsorship. It can be found here: https://mentors.debian.net/package/fclib and can get downloading with dget using: dget -x https://mentors.debian.net/debian/pool/main/s/fclib/fclib_3.1.0+dfsg-1.dsc Changes since the last upload: * New upstream version. (Closes: #962219) (Closes: #961735) * Add dependencies libboost-timer-dev, libboost-chrono-dev. * Depend on openblas and lapacke instead of atlas. * Require fclib 3.1.0 * Update location of install paths. * Enable WITH_GENERATION, now required for serialization. * Install new siconos_export_raw_data tool. * Fix cmake import targets to allow independent packages. * Update patches for new upstream version. * Add a flag for gfortran to avoid a regression in GCC-10. (Closes: #957794) * Remove unused build rule for swig3.0 symlink. * Remove non-existent files from debian/copyright. * Rewrite patch descriptions using gbp pq. * Fix a Python warning about using 'is' with a literal. Regards, -- Stephen Sinclair
Bug#961735: siconos: FTBFS with mumps 5.3.1
Okay I'll take a look, there is actually a new version of Siconos that I have almost finished packaging so I will test against experimental. regards, Steve On Thu, May 28, 2020 at 4:15 PM Sebastian Ramacher wrote: > > Source: siconos > Version: 4.2.0+git20181026.0ee5349+dfsg.2-3 > Severity: important > Tags: ftbfs sid bullseye > Control: block 961053 by -1 > > A test rebuild of siconos for the upcoming mumps transition (the new > package is available in experimental) failed: > | The following tests FAILED: > |19 - python_test_fclib, (SEGFAULT) > | 345 - FC3D_sparse_test (SEGFAULT) > | 364 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_CONSTANT_FC3D_Example1_SBM > (SEGFAULT) > | 365 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_RESIDUAL_BALANCING_FC3D_Example1_SBM > (SEGFAULT) > | 366 - > fc3d__NSN_AC_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_FC3D_Example1_SBM > (SEGFAULT) > | 367 - > fc3d__NSN_AC_TEST_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_FC3D_Example1_SBM > (SEGFAULT) > | 368 - fc3d__NSN_AC_Tol_1e-3_Max_1000_inTol_0_inMax_0_FC3D_Example1_SBM > (SEGFAULT) > | 369 - > fc3d__NSN_AC_TEST_Tol_1e-3_Max_1000_inTol_0_inMax_0_FC3D_Example1_SBM > (SEGFAULT) > | 370 - fc3d__NSN_FB_Tol_1e-3_Max_1000_inTol_0_inMax_0_FC3D_Example1_SBM > (SEGFAULT) > | 371 - fc3d__NSN_NM_Tol_1e-3_Max_1000_inTol_0_inMax_0_FC3D_Example1_SBM > (SEGFAULT) > | 403 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_CONSTANT_Capsules-i100-1090 > (SEGFAULT) > | 404 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_RESIDUAL_BALANCING_Capsules-i100-1090 > (SEGFAULT) > | 405 - > fc3d__NSN_AC_TEST_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_Capsules-i100-1090 > (SEGFAULT) > | 406 - fc3d__NSN_AC_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-1090 > (SEGFAULT) > | 407 - > fc3d__NSN_AC_TEST_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-1090 > (SEGFAULT) > | 408 - fc3d__NSN_FB_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-1090 > (SEGFAULT) > | 409 - fc3d__NSN_NM_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-1090 > (SEGFAULT) > | 415 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_CONSTANT_Capsules-i100-889 > (SEGFAULT) > | 416 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_RESIDUAL_BALANCING_Capsules-i100-889 > (SEGFAULT) > | 417 - > fc3d__NSN_AC_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_Capsules-i100-889 > (SEGFAULT) > | 418 - > fc3d__NSN_AC_TEST_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_Capsules-i100-889 > (SEGFAULT) > | 419 - fc3d__NSN_AC_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-889 > (SEGFAULT) > | 420 - > fc3d__NSN_AC_TEST_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-889 > (SEGFAULT) > | 421 - fc3d__NSN_FB_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-889 > (SEGFAULT) > | 422 - fc3d__NSN_NM_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i100-889 > (SEGFAULT) > | 428 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_CONSTANT_Capsules-i101-404 > (SEGFAULT) > | 429 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_RESIDUAL_BALANCING_Capsules-i101-404 > (SEGFAULT) > | 430 - > fc3d__NSN_AC_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_Capsules-i101-404 > (SEGFAULT) > | 431 - fc3d__NSN_AC_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i101-404 > (SEGFAULT) > | 432 - fc3d__NSN_FB_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i101-404 > (SEGFAULT) > | 433 - fc3d__NSN_NM_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i101-404 > (SEGFAULT) > | 439 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_CONSTANT_Capsules-i103-990 > (SEGFAULT) > | 440 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_RESIDUAL_BALANCING_Capsules-i103-990 > (SEGFAULT) > | 441 - > fc3d__NSN_AC_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_Capsules-i103-990 > (SEGFAULT) > | 442 - > fc3d__NSN_AC_TEST_Tol_1e-5_Max_1000_inTol_0_inMax_0_IPARAM_1_Capsules-i103-990 > (SEGFAULT) > | 443 - fc3d__NSN_AC_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i103-990 > (SEGFAULT) > | 444 - > fc3d__NSN_AC_TEST_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i103-990 > (SEGFAULT) > | 445 - fc3d__NSN_FB_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i103-990 > (SEGFAULT) > | 446 - fc3d__NSN_NM_Tol_1e-3_Max_1000_inTol_0_inMax_0_Capsules-i103-990 > (SEGFAULT) > | 452 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_CONSTANT_Capsules-i122-1617 > (SEGFAULT) > | 453 - > fc3d__ADMM_Tol_1e-5_Max_1_inTol_0_inMax_0_IPARAM_SICONOS_FRICTION_3D_ADMM_RHO_STRATEGY_RESIDUAL_BALANCI
Bug#959647: lasagne: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
I am confused. This bug is filed against 0.1+git20200419.5d3c63c+ds-1, which contains a patch for this exact problem, but the build logs indicate that the previous version, 0.1+git20181019.a61b76f-2, is being built. Steve
Bug#959137: lasagne: (autopkgtest) needs update for new version of numpy: 'numpy.float64' object cannot be interpreted as an integer
The package has been updated in salsa and is awaiting sponsorship. regards, Steve On Wed, Apr 29, 2020 at 9:48 PM Paul Gevers wrote: > > Source: lasagne > Version: 0.1+git20181019.a61b76f-2 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org, nu...@packages.debian.org > Tags: sid bullseye > User: debian...@lists.debian.org > Usertags: needs-update > Control: affects -1 src:numpy > > Dear maintainer(s), > > With a recent upload of numpy the autopkgtest of lasagne fails in > testing when that autopkgtest is run with the binary packages of numpy > from unstable. It passes when run with only packages from testing. In > tabular form: > >passfail > numpy from testing1:1.18.3-1 > lasagnefrom testing0.1+git20181019.a61b76f-2 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration of numpy to testing > [1]. Of course, numpy shouldn't just break your autopkgtest (or even > worse, your package), but it seems to me that the change in numpy was > intended and your package needs to update to the new situation. > > If this is a real problem in your package (and not only in your > autopkgtest), the right binary package(s) from numpy should really add a > versioned Breaks on the unfixed version of (one of your) package(s). > Note: the Breaks is nice even if the issue is only in the autopkgtest as > it helps the migration software to figure out the right versions to > combine in the tests. > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=numpy > > https://ci.debian.net/data/autopkgtest/testing/amd64/l/lasagne/5197094/log.gz > > === FAILURES > === > > TestTPSTransformLayer.test_transform_thin_plate_spline_variable_input _ > > start = -1, stop = 1, num = 4.0, endpoint = True, retstep = False, dtype > = None > axis = 0 > > @array_function_dispatch(_linspace_dispatcher) > def linspace(start, stop, num=50, endpoint=True, retstep=False, > dtype=None, > axis=0): > """ > Return evenly spaced numbers over a specified interval. > > Returns `num` evenly spaced samples, calculated over the > interval [`start`, `stop`]. > > The endpoint of the interval can optionally be excluded. > > .. versionchanged:: 1.16.0 > Non-scalar `start` and `stop` are now supported. > > Parameters > -- > start : array_like > The starting value of the sequence. > stop : array_like > The end value of the sequence, unless `endpoint` is set to > False. > In that case, the sequence consists of all but the last of > ``num + 1`` > evenly spaced samples, so that `stop` is excluded. Note > that the step > size changes when `endpoint` is False. > num : int, optional > Number of samples to generate. Default is 50. Must be > non-negative. > endpoint : bool, optional > If True, `stop` is the last sample. Otherwise, it is not > included. > Default is True. > retstep : bool, optional > If True, return (`samples`, `step`), where `step` is the spacing > between samples. > dtype : dtype, optional > The type of the output array. If `dtype` is not given, > infer the data > type from the other input arguments. > > .. versionadded:: 1.9.0 > > axis : int, optional > The axis in the result to store the samples. Relevant only > if start > or stop are array-like. By default (0), the samples will be > along a > new axis inserted at the beginning. Use -1 to get an axis at > the end. > > .. versionadded:: 1.16.0 > > Returns > --- > samples : ndarray > There are `num` equally spaced samples in the closed interval > ``[start, stop]`` or the half-open interval ``[start, stop)`` > (depending on whether `endpoint` is True or False). > step : float, optional > Only returned if `retstep` is True > > Size of spacing between samples. > > > See Also > > arange : Similar to `linspace`, but uses a step size (instead of the > number of samples). > geomspace : Similar to `linspace`, but with numbers spaced > evenly on a log > scale (a geometric progression). > logspace : Similar to `geomspace`, but with the end points > specified as >logarithms. > > Examples > > >>> n
Bug#954857: RFS: siconos/4.2.0+git20181026.0ee5349+dfsg.2-3 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
The package has been updated on mentors. regards, Steve On Thu, Mar 26, 2020 at 9:57 PM Stephen Sinclair wrote: > > Hello Adam, > > Thank you for looking at the package. > I believe I have fixed the problem now and updated master on salsa. > I am trying to re-upload to mentors but no acknowledgement yet after > waiting the whole day, I will try again tomorrow. > > I have now to taught my system to run autopkgtest automatically after > sbuild, so hopefully won't make the same mistake again. > > Incidentally, in the interim I have been informed by upstream that a > new version is coming soon so I will be updating the package probably > again next week, but it would be good to get this fix in anyways since > I don't know exactly how long that will be. > > regards, > Steve > > > On Thu, Mar 26, 2020 at 3:03 AM Adam Borowski wrote: > > > > On Tue, Mar 24, 2020 at 03:17:31PM +0100, Stephen Sinclair wrote: > > > * Package name: siconos > > >Version : 4.2.0+git20181026.0ee5349+dfsg.2-3 > > > > > Changes since the last upload: > > > > > >* Patch to remove bad cc options. > > >* Patch to find python3.8 config. > > >* Depend on swig instead of swig3.0. > > >* Backport support for swig4.0. (Closes: #952601) > > >* Removed a failing numerics test. > > >* debian/rules: Remove use of ccache. (Closes: #945613 #954497) > > >* Require Python 3.8. > > > > Hi! > > I'm afraid that while the package builds, it fails tests: > > > > autopkgtest [02:57:15]: summary > > kernel-dev PASS > > numerics-tests FAIL non-zero exit status 2 > > kernel-tests FAIL non-zero exit status 2 > > control-testsFAIL non-zero exit status 2 > > kernel-tests-python PASS > > control-tests-python PASS > > mechanics-tests FAIL non-zero exit status 2 > > mechanics-tests-python PASS > > mechanics-tools PASS > > > > Full log attached. > > > > > > Meow! > > -- > > ⢀⣴⠾⠻⢶⣦⠀ > > ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. > > ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi > > ⠈⠳⣄
Bug#954857: RFS: siconos/4.2.0+git20181026.0ee5349+dfsg.2-3 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
Hello Adam, Thank you for looking at the package. I believe I have fixed the problem now and updated master on salsa. I am trying to re-upload to mentors but no acknowledgement yet after waiting the whole day, I will try again tomorrow. I have now to taught my system to run autopkgtest automatically after sbuild, so hopefully won't make the same mistake again. Incidentally, in the interim I have been informed by upstream that a new version is coming soon so I will be updating the package probably again next week, but it would be good to get this fix in anyways since I don't know exactly how long that will be. regards, Steve On Thu, Mar 26, 2020 at 3:03 AM Adam Borowski wrote: > > On Tue, Mar 24, 2020 at 03:17:31PM +0100, Stephen Sinclair wrote: > > * Package name: siconos > >Version : 4.2.0+git20181026.0ee5349+dfsg.2-3 > > > Changes since the last upload: > > > >* Patch to remove bad cc options. > >* Patch to find python3.8 config. > >* Depend on swig instead of swig3.0. > >* Backport support for swig4.0. (Closes: #952601) > >* Removed a failing numerics test. > >* debian/rules: Remove use of ccache. (Closes: #945613 #954497) > >* Require Python 3.8. > > Hi! > I'm afraid that while the package builds, it fails tests: > > autopkgtest [02:57:15]: summary > kernel-dev PASS > numerics-tests FAIL non-zero exit status 2 > kernel-tests FAIL non-zero exit status 2 > control-testsFAIL non-zero exit status 2 > kernel-tests-python PASS > control-tests-python PASS > mechanics-tests FAIL non-zero exit status 2 > mechanics-tests-python PASS > mechanics-tools PASS > > Full log attached. > > > Meow! > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. > ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi > ⠈⠳⣄
Bug#954857: RFS: siconos/4.2.0+git20181026.0ee5349+dfsg.2-3 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "siconos" * Package name: siconos Version : 4.2.0+git20181026.0ee5349+dfsg.2-3 Upstream Author : siconos-t...@lists.gforge.inria.fr * URL : https://nonsmooth.gricad-pages.univ-grenoble-alpes.fr/siconos/index.html * License : Apache-2.0 * Vcs : https://salsa.debian.org/science-team/siconos Section : science It builds those binary packages: siconos - modeling and simulation of nonsmooth dynamical systems (simulation runner tool) siconos-mechanics-tools - modeling and simulation of nonsmooth dynamical systems (mechanics tools) libsiconos-numerics6 - modeling and simulation of nonsmooth dynamical systems (numerics lib) libsiconos-numerics-dev - modeling and simulation of nonsmooth dynamical systems (numerics dev) libsiconos-kernel6 - modeling and simulation of nonsmooth dynamical systems (kernel lib) libsiconos-kernel-dev - modeling and simulation of nonsmooth dynamical systems (kernel dev) libsiconos-control6 - modeling and simulation of nonsmooth dynamical systems (control lib) libsiconos-control-dev - modeling and simulation of nonsmooth dynamical systems (control dev) libsiconos-mechanics6 - modeling and simulation of nonsmooth dynamical systems (mechanics lib) libsiconos-mechanics-dev - modeling and simulation of nonsmooth dynamical systems (mechanics dev) libsiconos-io6 - modeling and simulation of nonsmooth dynamical systems (io lib) libsiconos-io-dev - modeling and simulation of nonsmooth dynamical systems (io dev) python3-siconos - modeling and simulation of nonsmooth dynamical systems (python3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/siconos Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/siconos/siconos_4.2.0+git20181026.0ee5349+dfsg.2-3.dsc Changes since the last upload: * Patch to remove bad cc options. * Patch to find python3.8 config. * Depend on swig instead of swig3.0. * Backport support for swig4.0. (Closes: #952601) * Removed a failing numerics test. * debian/rules: Remove use of ccache. (Closes: #945613 #954497) * Require Python 3.8. Regards, -- Stephen Sinclair
Bug#954737: RFS: keras-preprocessing/1.1.0+ds-1 -- data preprocessing module for the Keras deep learning framework
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "keras-preprocessing". The package is schedule to be autoremoved tomorrow without this update. * Package name: keras-preprocessing Version : 1.1.0+ds-1 Upstream Author : François Chollet * URL : http://keras.io/ * License : Expat * Vcs : https://salsa.debian.org/science-team/keras-preprocessing Section : science It builds those binary packages: python3-keras-preprocessing - data preprocessing module for the Keras deep learning framework To access further information about this package, please visit the following URL: https://mentors.debian.net/package/keras-preprocessing Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/keras-preprocessing/keras-preprocessing_1.1.0+ds-1.dsc Changes since the last upload: * New upstream version 1.1.0. * debian/watch: + add dversionmangle for +ds suffix. * debian/control: + update standard version to 4.5.0 (no changes). Regards, -- Stephen Sinclair
Bug#954740: RFS: keras/2.3.1+dfsg-1 [RC] -- deep learning framework running on Theano or TensorFlow
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "keras". The package is schedule to be autoremoved tomorrow without this update. * Package name: keras Version : 2.3.1+dfsg-1 Upstream Author : François Chollet * URL : http://keras.io/ * License : Expat * Vcs : https://salsa.debian.org/science-team/keras Section : science It builds those binary packages: python3-keras - deep learning framework running on Theano or TensorFlow To access further information about this package, please visit the following URL: https://mentors.debian.net/package/keras Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/keras/keras_2.3.1+dfsg-1.dsc Changes since the last upload: [ Stephen Sinclair ] * New upstream version 2.3.1. * debian/watch: + add dversionmangle for +dfsg suffix. * debian/control: + update standards to 4.5.0 (no changes). + add build-dep on python3-flaky. + remove package keras-doc. + update required python version to 3.8. * debian/patches: + refresh patches for new version. + add a tolerance for an activations test. (Closes: #952163) * debian/rules: + ignore two tests requiring unpackaged dependencies. Regards, -- Stephen Sinclair
Bug#954738: RFS: keras-applications/1.0.8+ds-1 -- popular models and pre-trained weights for the Keras deep learning framework
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "keras-applications". The package is scheduled to be autoremoved tomorrow without this update. * Package name: keras-applications Version : 1.0.8+ds-1 Upstream Author : François Chollet * URL : http://keras.io/ * License : Expat * Vcs : https://salsa.debian.org/science-team/keras-applications Section : science It builds those binary packages: python3-keras-applications - popular models and pre-trained weights for the Keras deep learning framework To access further information about this package, please visit the following URL: https://mentors.debian.net/package/keras-applications Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/keras-applications/keras-applications_1.0.8+ds-1.dsc Changes since the last upload: * New upstream version 1.0.8. * debian/watch: + add dversionmangle for +ds suffix. * debian/control: + update to standards 4.5.0 (no changes). Regards, -- Stephen Sinclair
Bug#951254: RFS: siconos/4.2.0+git20181026.0ee5349+dfsg.2-2 -- simulation of nonsmooth dynamical systems
Package: sponsorship-requests Severity: important Tags: patch Dear mentors, I am looking for a sponsor for my package "siconos" * Package name: siconos Version : 4.2.0+git20181026.0ee5349+dfsg.2-2 Upstream Author : Siconos Team * URL : http://siconos.gforge.inria.fr * License : Apache * Vcs : https://salsa.debian.org/science-team/siconos Section : science This update fixes some broken tests that block its current build, and closes one bug. It builds these binary packages: siconos - compilation and run tools siconos-mechanics-tools - run tools for mechanics simulations libsiconos-numerics6 - numerics library libsiconos-numerics-dev - numerics dev libsiconos-kernel6 - kernel library libsiconos-kernel-dev - kernel dev libsiconos-control6 - control library libsiconos-control-dev - control dev libsiconos-mechanics6 - mechanics library libsiconos-mechanics-dev - mechanics dev libsiconos-io6 - io library libsiconos-io-dev - io dev python3-siconos - python wrappers To access further information about this package, please visit the following URL: https://mentors.debian.net/package/siconos Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/siconos/siconos_4.2.0+git20181026.0ee5349+dfsg.2-2.dsc Changes since the last upload: [ Stephen Sinclair ] * Patch to fix ref filename for test SMCTest::SMCLsodar. * Add TwistingTest::test_ExplicitTwisting_Lsodar to list of broken tests. * Remove compiler paths and flags in installed CMakeLists.txt. (Closes: #940194) * Update to standards version 4.5.0, no changes necessary. * Update to debhelper compat 12, no changes necessary. * d/copyright: Add Upstream-Contact field. Regards, Steve -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-74-generic (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect
Bug#940194: siconos: /usr/bin/siconos broken due to invalid CMAKE_CXX_COMPILER
Package: siconos Version: 4.2.0+git20181026.0ee5349+dfsg.2-1 Severity: important Dear Maintainer, When running the /usr/bin/siconos script, the process fails at the cmake step due to an invalid CMAKE_CXX_COMPILER and CMAKE_C_COMPILER. For example, the autopkgtest numerics-tests fails on ci.debian.net with the error: make[2]: /build/siconos-4.2.0+git20181026.0ee5349+dfsg.2/obj-x86_64-linux- gnu/cc: Command not found Siconos can be used without this script but it would be helpful to have it fixed. -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic'), (100, 'bionic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-62-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#916355: cython: References to non-existent members of PyThreadState in Python 3.7
Package: cython
Version: 0.28.4-1
Severity: grave
Tags: upstream patch
Justification: renders package unusable
Dear Maintainer,
While building and testing an update to lasagne, I got the following
error, which I have tracked down to cython.
```
E Exception: ('The following error happened while compiling the node',
forall_inplace,cpu,scan_fn}(Elemwise{sub,no_inplace}.0,
Subtensor{int64:int64:int64}.0, IncSubtensor{InplaceSet;:int64:}.0,
Join.0), '\n', 'Compilation failed (return status=1):
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:
In function ‘void __Pyx__ExceptionSave(PyThreadState*, PyObject**,
PyObject**,
PyObject**)’:.
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12749:21:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_type’; did you mean ‘curexc_type’?. *type = tstate->exc_type;.
^~~~.
curexc_type.
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12750:22:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_value’; did you mean ‘curexc_value’?. *value =
tstate->exc_value;. ^.
curexc_value.
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12751:19:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_traceback’; did you mean ‘curexc_traceback’?. *tb =
tstate->exc_traceback;. ^.
curexc_traceback.
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:
In function ‘void __Pyx__ExceptionReset(PyThreadState*, PyObject*,
PyObject*,
PyObject*)’:.
/<>/lasagne-0.1+git20181019.a61b76f/.pybuild/compiledir_Linux-4.15--generic-x86_64-with-debian-buster-sid--3.7.2rc1-64/scan_perform/mod.cpp:12758:24:
error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named
‘exc_type’; did you mean ‘curexc_type’?. tmp_type =
tstate->exc_type;. ^~~~.
```
Lasagne uses theano, which run-time compiles Python extensions using
cython. When used with python 3.7, cython generates code containing
references to members of PyThreadState that do not exist. This seems
to be related to an upstream bug which has been fixed:
https://github.com/cython/cython/issues/1955
Therefore, I recommend upgrading the cython package to the latest
release which is only a couple of weeks old. I have provided a merge
request for this update here:
https://salsa.debian.org/python-team/applications/cython/merge_requests/2
regards,
Steve
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-42-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Versions of packages cython depends on:
ii libc6 2.28-2
ii python 2.7.15-3
Versions of packages cython recommends:
ii gcc 4:8.2.0-2
ii python-dev 2.7.15-3
Versions of packages cython suggests:
pn cython-doc
-- no debconf information
Bug#915656: ITP: siconos -- modeling and simulation of nonsmooth dynamical systems
Package: wnpp Severity: wishlist Owner: Stephen Sinclair * Package name: siconos Version : 4.2.0+git20181026.0ee5349 Upstream Author : Siconos development team * URL : http://siconos.gforge.inria.fr * License : Apache Programming Lang: C, C++, Python Description : modeling and simulation of nonsmooth dynamical systems Siconos is an open-source scientific software primarily targeted at modeling and simulating nonsmooth dynamical systems in C++ and in Python: * Mechanical systems (rigid or solid) with unilateral contact and Coulomb friction and impact (nonsmooth mechanics, contact dynamics, multibody systems dynamics or granular materials). * Switched Electrical Circuit such as electrical circuits with ideal and piecewise linear components: power converter, rectifier, Phase-Locked Loop (PLL) or Analog-to-Digital converter. * Sliding mode control systems. * Biology (Gene regulatory network). Other applications are found in Systems and Control (hybrid systems, differential inclusions, optimal control with state constraints), Optimization (Complementarity systems and Variational inequalities), Fluid Mechanics, and Computer Graphics. I propose this package for maintenance under the Debian Science team, of which I am a guest member, and I plan to continue maintaining this package for the foreseeable future.
Bug#896348: affects package development, any news?
I am working on a docs package that requires this sphinxcontrib youtube module, and it fails to import. Any news on fixing this? It appears the package is out of date with upstream, as the docs compile fine if I install this using pip. thanks, Steve
Bug#902391: ITP: keras-applications -- popular models and pre-trained weights for the Keras deep learning framework
Package: wnpp Severity: wishlist Owner: Stephen Sinclair * Package name: keras-applications Version : 1.0.2 Upstream Author : Francois Chollet * URL : http://keras.io/ * License : Expat Programming Lang: Python Description : popular models and pre-trained weights for the Keras deep learning framework Keras is a Python library for machine learning based on deep (multi- layered) artificial neural networks (DNN), which follows a minimalistic and modular design with a focus on fast experimentation. Features of DNNs like neural layers, cost functions, optimizers, initialization schemes, activation functions and regularization schemes are available in Keras a standalone modules which can be plugged together as wanted to create sequence models or more complex architectures. Keras supports convolutions neural networks (CNN, used for image recognition resp. classification) and recurrent neural networks (RNN, suitable for sequence analysis like in natural language processing). It runs as an abstraction layer on the top of Theano (math expression compiler) by default, which makes it possible to accelerate the computations by using (GP)GPU devices. Alternatively, Keras could run on Google's TensorFlow (not yet available in Debian). Keras Applications is the applications module of the Keras deep learning library. It provides model definitions and pre-trained weights for a number of popular archictures, such as VGG16, ResNet50, Xception, MobileNet, and more. This new package is to be a dependency of an updated keras package, following upstream's splitting of keras-applications to its own Python module.
Bug#902390: ITP: keras-preprocessing -- data preprocessing module for the Keras deep learning framework
Package: wnpp Severity: wishlist Owner: Stephen Sinclair * Package name: keras-preprocessing Version : 1.0.1 Upstream Author : Francois Chollet * URL : http://keras.io/ * License : Expat Programming Lang: Python Description : data preprocessing module for the Keras deep learning framework Keras is a Python library for machine learning based on deep (multi- layered) artificial neural networks (DNN), which follows a minimalistic and modular design with a focus on fast experimentation. Features of DNNs like neural layers, cost functions, optimizers, initialization schemes, activation functions and regularization schemes are available in Keras a standalone modules which can be plugged together as wanted to create sequence models or more complex architectures. Keras supports convolutions neural networks (CNN, used for image recognition resp. classification) and recurrent neural networks (RNN, suitable for sequence analysis like in natural language processing). It runs as an abstraction layer on the top of Theano (math expression compiler) by default, which makes it possible to accelerate the computations by using (GP)GPU devices. Alternatively, Keras could run on Google's TensorFlow (not yet available in Debian). Keras Preprocessing is the data preprocessing and data augmentation module of the Keras deep learning library. It provides utilities for working with image data, text data, and sequence data. This new package is to be a dependency for an updated keras package, following upstream's splitting of keras-preprocessing into its own Python module.
Bug#901318: mkdocs: package contains broken symlink to font-awesome.ttf
Package: mkdocs
Version: 0.17.3+dfsg-1
Severity: important
Dear Maintainer,
While building keras-doc, which uses mkdocs, I got the following error (full
trace later):
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/fontawesome-webfont.ttf'
It appears that this file is a broken symlink to a file that was
previously in the fonts-font-awesome package. In my chroot
fonts-font-awesome is installed, but,
$ ls -l
/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/fontawesome-webfont.ttf
lrwxrwxrwx 1 root root 78 May 25 13:08
/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/fontawesome-webfont.ttf
->
../../../../../../../share/fonts/truetype/font-awesome/fontawesome-webfont.ttf
$ ls
/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/../../../../../../../share/fonts/truetype/font-awesome/fontawesome-webfont.ttf
ls: cannot access
'/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/../../../../../../../share/fonts/truetype/font-awesome/fontawesome-webfont.ttf':
No such file or directory
# ls /usr/share/fonts/truetype/font-awesome/
fa-brands-400.ttf fa-regular-400.ttf fa-solid-900.ttf
Therefore I conclude that an important symlink is missing, and mkdocs
does not work as installed. Can you please verify?
kind regards,
Steve
Full traceback:
INFO- Building documentation to directory: /build/keras-2.2.0/docs/html
Traceback (most recent call last):
File "/usr/bin/mkdocs", line 11, in
load_entry_point('mkdocs==0.17.3', 'console_scripts', 'mkdocs')()
File "/usr/lib/python3/dist-packages/click/core.py", line 722, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/mkdocs/__main__.py", line 156, in
build_command
), dirty=not clean)
File "/usr/lib/python3/dist-packages/mkdocs/commands/build.py", line 276, in
build
theme_dir, config['site_dir'], exclude=['*.py', '*.pyc', '*.html',
'mkdocs_theme.yml'],
dirty=dirty
File "/usr/lib/python3/dist-packages/mkdocs/utils/__init__.py", line 179, in
copy_media_f
iles
copy_file(source_path, output_path)
File "/usr/lib/python3/dist-packages/mkdocs/utils/__init__.py", line 113, in
copy_file
shutil.copyfile(source_path, output_path)
File "/usr/lib/python3.6/shutil.py", line 120, in copyfile
with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/fontawesome-webfont.ttf'
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-22-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Versions of packages mkdocs depends on:
ii fonts-font-awesome 5.0.10-4
ii libjs-bootstrap 3.3.7+dfsg-2
ii libjs-highlight.js 9.12.0+dfsg1-4
ii libjs-jquery 3.2.1-1
ii libjs-modernizr 2.6.2+ds1-3
ii libjs-mustache 2.3.0-2
ii libjs-requirejs 2.3.2-1
ii libjs-requirejs-text 2.0.12-1
ii python3 3.6.5-3
ii python3-click6.7-4
ii python3-jinja2 2.10-1
ii python3-livereload 2.5.2-1
ii python3-markdown 2.6.9-1
ii python3-pkg-resources39.1.0-1
ii python3-tornado 5.0.2-1
ii python3-yaml 3.12-1+b1
ii sphinx-rtd-theme-common 0.2.4-1
mkdocs recommends no packages.
Versions of packages mkdocs suggests:
pn ghp-import
pn mkdocs-doc
-- no debconf information
Bug#896295: Tensorflow is missing
The upstream must have changed the default backend which is not surprising, it should be fixable with a patch. I can look into it in a few days when I am back from vacation and in front of a computer again. The autotestpkg tests set KERAS_BACKEND=theano which is why this was missed. In the meantime users can set this environment variable similarly as a work-around. I don't really like changing upstream default behaviour but perhaps in this case it is warranted as an interim solution. Regarding Tensorflow packaging I do not know, someone on debian-science mentioned difficulties with its build system. I do hope these are resolvable but it seems to be a big issue. On Mon, May 21, 2018, 1:16 AM Andreas Tille wrote: > Hi, > > the description says: > > ... Alternatively, Keras could run on Google's > TensorFlow (not yet available in Debian, but coming up). > > Is there some estimated time frame to package TensorFlow? > > If not please try to deactivate this alternative since the package does > not work as this bug report explains. > > Kind regards > > Andreas. > > -- > http://fam-tille.de >
Bug#894128: RFS: fclib/3.0.0 -- read and write problems in the Frictional Contact Library format
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "fclib": * Package name: fclib Version : 3.0.0-1 Upstream Author : Vincent Acary et al. * URL : https://frictionalcontactlibrary.github.io/ * License : Apache 2.0 Section : libs It builds those binary packages: libfclib0 - library file libfclib-dev - header file To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fclib Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fclib/fclib_3.0.0-1.dsc The package source is maintained on salsa in the science-team group: https://salsa.debian.org/science-team/fclib fclib is an open source collection of Frictional Contact (FC) problems stored in a specific HDF5 format, and an open source light implementation of Input/Output functions in C Language to read and write problems. The goal of this work is to set up a collection of 2D and 3D Frictional Contact (FC) problems in order to set up a list of benchmarks; provide a standard framework for testing available and new algorithms; and share common formulations of problems in order to exchange data. fclib is an open-source scientific software primarily targeted at modeling and simulating nonsmooth dynamical systems This package is also a future dependency of Siconos, a nonsmooth dynamical systems simulator from the same development team, for which I plan to propose a package shortly. More information about fclib can be obtained from https://frictionalcontactlibrary.github.io/ Regards, Stephen Sinclair
Bug#894120: ITP: fclib -- Library of C routines to read and write problems from the Friction Contact Library
Package: wnpp Severity: wishlist Owner: Stephen Sinclair * Package name: fclib Version : 3.0.0 Upstream Author : Vincent Acary et al. * URL : https://frictionalcontactlibrary.github.io * License : Apache 2.0 Programming Lang: C Description : Library of C routines to read and write problems from the Friction Contact Library fclib is an open source collection of Frictional Contact (FC) problems stored in a specific HDF5 format, and an open source light implementation of Input/Output functions in C Language to read and write problems. The goal of this work is to set up a collection of 2D and 3D Frictional Contact (FC) problems in order to set up a list of benchmarks; provide a standard framework for testing available and new algorithms; and share common formulations of problems in order to exchange data. Fclib is an open-source scientific software primarily targeted at modeling and simulating nonsmooth dynamical systems Package notes: fclib is an optional dependency of Siconos, a nonsmooth dynamical systems simulator. I plan to maintain it but propose it for consideration with the Debian Science team. It is a very minimal codebase with only libhdf5 and suitesparse as dependencies, and is not expected to change very often, with the exception of likely adding a higher-level layer in the future (e.g., a Python interface).
Bug#893656: transition: theano 0.9 -> 1.0 - please update lasagne
I was waiting for Lasagne to do a release, but I can take a look at it soon. I'll try to do it tomorrow. On Thu, Mar 22, 2018 at 6:41 PM, Rebecca N. Palmer wrote: > lasagne - 3 test failures; fixed upstream by >> https://github.com/Lasagne/Lasagne/pull/836 >> > Latest upstream (37ca134; only packaging change was to drop > remove-deprecated.patch) doesn't have these failures. There is a warning > that cuda_convnet is no longer available with Theano 1.0, but that has > another dependency (pybuild2) that was never in Debian anyway. > > pyopencl - FTBFS for unrelated reasons (#893050); the theano-using code >> appears to be build/test scripts (pyopencl/compyte/gen*, test*) we never >> actually run >> > Builds after applying the path in #893050; 7 tests fail or crash (in > Python 2, 6 also in Python 3), but they do this with or without Theano. > > sympy - build hangs at mkdir -p _build/logo (with mkdir using a full CPU >> core?!), probably unrelated as it also happens without *-theano installed >> > This hang is because faketime doesn't work well with cowbuilder --login, > i.e. nothing to do with sympy itself. Running the testsuite with new > Theano succeeds. > > Hence, it appears that updating lasagne is the only change required to > work with Theano 1.0, but testing on CUDA-capable hardware would still be > preferable. > >
Bug#881118: RFS: boost-numeric-bindings/0.99-1 [ITP] -- Numeric Library Bindings for Boost
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "boost-numeric-bindings": * Package name: boost-numeric-bindings Version : 0.99 Upstream Author : Kresimir Fresl et. al. * URL : https://github.com/uBLAS/numeric_bindings * License : Boost Software License - Version 1.0 Programming Lang: C++ Description : boost-numeric-bindings -- Numeric Library Bindings for Boost Boost Bindings is a bindings library (not just) for Boost.Ublas. It offers an easy way of calling BLAS, LAPACK, UMFPACK, MUMPS and many other mature legacy numerical codes from within C++. The package source may be found at: http://anonscm.debian.org/cgit/debian-science/packages/boost-numeric-bindings.git And the package description may be found at: https://mentors.debian.net/debian/pool/main/b/boost-numeric-bindings/boost-numeric-bindings_0.99-1.dsc Previously an ITP bug was filed by someone else (#536270) but then dropped. Since then a github repo was created by an upstream author and a "pre-release 0.99" was released with a bit more work, in 2015. I have updated the preliminary package by Teemu Ikonen from that bug to the latest version, as well as the latest Debian compat and policy versions. This version of the package installs the header files to the /usr/include/boost directory. Please note that this version 0.99 did not include a LICENSE file in the main directory, however all files nonetheless still have a reference to their license at the top and it remains the same as in debian/copyright. (I have filed an upstream issue to restore the license file.) Preliminary support for running some of the tests should hopefully come in the near future. I intend to improve this, add documentation if possible, and keep it up to date with any future releases. It would be beneficial to Debian to have these headers more easily available, since projects are currently often embedding them in their source distributions.
Bug#881109: ITP: boost-numeric-bindings -- boost-numeric-bindings -- Numeric Library Bindings for Boost
Package: wnpp Severity: wishlist Owner: Stephen Sinclair * Package name: boost-numeric-bindings Version : 0.99 Upstream Author : Kresimir Fresl et. al. * URL : https://github.com/uBLAS/numeric_bindings * License : Boost Software License - Version 1.0 Programming Lang: C++ Description : boost-numeric-bindings -- Numeric Library Bindings for Boost Boost Bindings is a bindings library (not just) for Boost.Ublas. It offers an easy way of calling BLAS, LAPACK, UMFPACK, MUMPS and many other mature legacy numerical codes from within C++. Previously an ITP bug was filed (#536270) but then dropped. Since then a github repo was created and a "pre-release 0.99" was released with a bit more work, in 2015. I have updated the preliminary package by Teemu Ikonen from that bug to the latest version, as well as the latest Debian compat and policy versions, based on his package repo: git://git.debian.org/debian-science/packages/boost-numeric-bindings.git The package already installs the header files successfully to within the /usr/include/boost directory and I have preliminary support for running some of the tests. I intend to improve this, add documentation if possible, and keep it up to date with any future releases. It would be beneficial to Debian to have these headers more easily available, since projects are currently often embedding them headers in their source distributions.
Bug#852133: ITA: keras -- deep learning framework running on Theano or TensorFlow
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: keras Version : 1.0.7-2 Upstream Author : François Chollet * URL : http://keras.io/ * License : MIT Section : python One can check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/keras.git Changes since the last upload: * Change maintainer to Debian Science, uploader to Stephen Sinclair (Closes: #852133). * Change Section to python. * Add gbp.conf default to using pristine-tar. * Adhere to Debian Policy to version 4.1.1. This update is mainly to adopt, move package to git, and update the policy. An update to the latest Keras version will come at a later time. Question: "gbp dch" naturally sets the package to UNRELEASED. Will the sponsor change UNRELEASED to experimental before uploading, or should I do it? Do I use "gbp tag" now, or after it is uploaded? regards, Steve
Bug#721617: [liblo] Bug#721617: pyliblo: FTBFS on sparc: testSendOthers (unit.ServerTestCase) ... Bus error (core dumped)
On Wed, Jun 1, 2016 at 2:48 AM, John Paul Adrian Glaubitz wrote: > Control: reopen -1 > Control: severity -1 normal > >> Closing because liblo is no longer in sparc, and will not be built again >> there. > > Re-opening because in Debian we don't "fix bugs" by sweeping them under the > carpet. Also, we're currently making sparc64 fit for release and there is > a very active upstream. That's a good attitude, currently I don't know anyone using sparc64 with liblo nor do I have access to such a machine, so reproducing and testing, and therefore fixing, this bug is not possible for me. So, I look forward to your contribution. >> It appears the problem is that in sparc, you can't just say >> *(datatype*)data. Depending on datatype, 'data' has to be aligned at a >> certain number of bytes from the original block (4 for int, 8 for >> int64): > > Which is absolutely not specific to SPARC. The moment you are recasting > a pointer that way, you are leaving the territory of the C99 specification > which explicitly states that declarations which refer to the same object must > have compatible types, otherwise the behavior is undefined (C99, 6.2.7/2) [1]. It is a good point. If you have some examples where this fails it would be a good contribution to our unit testing. (testlo.c) At the moment no one has actually complained about this bug, and therefore I can only assume it has not actually been encountered and remains an entirely theoretical bug, but I do welcome ideas for how to fix it nonetheless, because compatibility with future architectures is certainly a desirable goal. > The code in question is therefore buggy and has to be fixed anyway as there > is otherwise no guarantee it will work on future architectures or compilers. > > I'll have a look at this issue, it's a common programming mistake. Unfortunately one that seems to be baked into the liblo API, but perhaps there is a way to fix it without sacrificing efficiency, at least on unaffected architectures. If not, perhaps it can be fixed in a future API-breaking version of liblo. Proposals welcome. Steve
Bug#721617: [liblo] Bug#721617: pyliblo: FTBFS on sparc: testSendOthers (unit.ServerTestCase) ... Bus error (core dumped)
On Tue, Sep 3, 2013 at 2:42 AM, Felipe Sateler wrote: > On Mon, Sep 2, 2013 at 8:16 PM, Felipe Sateler wrote: >> On Mon, Sep 2, 2013 at 7:33 PM, Felipe Sateler wrote: >>> Hi liblo devs, >>> >>> The python liblo wrapper has a test suite that has uncovered a bug in >>> liblo. >> >> I just tried current git (5a7a54b4a0a) and the test provided by >> Sebastian continues to fail. > > It appears the problem is that in sparc, you can't just say > *(datatype*)data. Depending on datatype, 'data' has to be aligned at a > certain number of bytes from the original block (4 for int, 8 for > int64): > > char* src = something(); > int* tmp = (int*)(src + 1); // If 1 is replaced by 4, no bus error. > *src = 1; // Bus error here. > int a = *src; // This yields bus error too > > So, at least lo_message_add_data (plus all its users), > lo_arg_pp_internal and lo_arg_host_endian need to change to support > sparc. > Any idea how to get a sparc test environment running? Is there an emulator I can use for example? In the provided stack traces the "data" variable does seem to be 4-byte aligned, but the error is on a 64-bit data type. I am curious to know if this problem _only_ occurs for 64-bit types? Type-casting is somewhat fundamental to how liblo uses the lo_arg data structure and for interpreting raw memory blocks of OSC data. In general OSC is by-design 32-bit-aligned, so generally this shouldn't be an issue, but if there are cases where things need to be 64-bit-aligned I can see how this problem might creep in. Suggestions on how to debug would be useful as I am completely unfamiliar with sparc. thanks, Steve -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#588054: ITP: loopdub -- Software for live audio loop manipulation.
Package: wnpp Severity: wishlist Owner: Stephen Sinclair * Package name: loopdub Version : 0.4 Upstream Author : Stephen Sinclair * URL : http://loopdub.sf.net/ * License : GPL-2 Programming Lang: C++ Description : Software for live audio loop manipulation. LoopDub is software intended for musical performance based on live loop manipulation. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
