Bug#825895: [Pkg-octave-devel] Bug#825895: octave-interval: FTBFS: debian/rules:10: *** target file 'install-docs' has both : and :: entries. Stop.

* Sébastien Villemot [2016-05-31 10:45]: Le mardi 31 mai 2016 à 10:34 +0200, Oliver Heimlich a écrit : On 31.05.2016 10:11, Chris Lamb wrote: Source: octave-interval Version: 1.4.1-1 Severity: serious Justification: fails to build from source User:

Bug#826390: [Pkg-octave-devel] Bug#826390: Bug#826390: octave-epstk: FTBFS: Can't call method "get" on an undefined value at /usr/share/octave/debian/dh/octave-pkg-helper line 38.

Control: reassign -1 octave-pkg-dev 1.4.0 Control: tags -1 + confirmed * Oliver Heimlich [2016-06-05 12:47]: On 05.06.2016 10:27, Chris Lamb wrote: Source: octave-epstk Version: 2.4-3 Severity: serious Justification: fails to build from source User:

Bug#832415: Further information: upstream software works fine

* Eric S Fraga <e.fr...@ucl.ac.uk> [2016-07-25 17:50]: Just a quick update: building the latest upstream version of octave along with the parallel package results in a system that works as it should. No errors at all. You mean, building Octave from source? Which version? Thanks,

Bug#832415: octave-parallel: Any attempt to use parcellfun leads to unhandled error in subprocesses

arning: called from parcellfun at line 291 column 9 [...] traceback on my own code elided error: '__exit__' undefined near line 311 column 7 Could you please provide a script that replicates the bug? Thanks, Rafael Laboissière

Bug#832415: Further information: upstream software works fine

Control: tags -1 + unreproducible moreinfo * Rafael Laboissière <raf...@debian.org> [2016-08-08 16:29]: Could you please provide a script that triggers the bug, as I asked in a previous message? I cannot reproduce the bug. The simple example below works for me with the versions cur

Bug#832415: Further information: upstream software works fine

* Eric S Fraga <e.fr...@ucl.ac.uk> [2016-08-07 18:30]: On Wednesday, 3 Aug 2016 at 12:17, Rafael Laboissière wrote: * Eric S Fraga <e.fr...@ucl.ac.uk> [2016-07-25 17:50]: Just a quick update: building the latest upstream version of octave along with the parallel package results

Bug#847974: xmds2: FTBFS in stretch

* Rafael Laboissière <raf...@debian.org> [2017-01-14 12:35]: * Gilles Filippini <p...@debian.org> [2017-01-14 10:18]: Control: reassign -1 liboctave-dev Control: tag -1 + patch On Sat, 14 Jan 2017 09:57:42 +0100 Gilles Filippini <p...@debian.org> wrote: [snip] In

Bug#847974: xmds2: FTBFS in stretch

* Gilles Filippini [2017-01-14 10:18]: Control: reassign -1 liboctave-dev Control: tag -1 + patch On Sat, 14 Jan 2017 09:57:42 +0100 Gilles Filippini wrote: [snip] Indeed; xmds2 wasn't reported by ben with my hdf5 transition config file. Sorry about

Bug#871214: [Pkg-octave-devel] Bug#871214: octave-image FTBFS on i386: test hangs

* Adrian Bunk [2017-08-07 01:57]: Source: octave-image Version: 2.6.1-1 Severity: serious Tags: buster sid Some recent change in unstable and buster makes octave-image FTBFS on i386: https://tests.reproducible-builds.org/debian/history/octave-image.html

Bug#871214: [Pkg-octave-devel] Bug#871214: Bug#871214: Bug#871214: octave-image FTBFS on i386: test hangs

* Sébastien Villemot <sebast...@debian.org> [2017-08-10 11:06]: Le jeudi 10 août 2017 à 09:31 +0200, Rafael Laboissière a écrit : * Adrian Bunk <b...@debian.org> [2017-08-07 01:57]: Source: octave-image Version: 2.6.1-1 Severity: serious Tags: buster sid Some recent change

Bug#871907: praat FTBFS on non-amd64

Control: tags -1 confirmed pending * Adrian Bunk [2017-08-12 15:07]: Source: praat Version: 6.0.30-1 Severity: serious Tags: patch https://buildd.debian.org/status/package.php?p=praat=sid ... g++ -std=c++11 -DNO_GUI -DNO_NETWORK -D_FILE_OFFSET_BITS=64

Bug#865241: [Pkg-octave-devel] Bug#865241: Please update dependencies from latex-xcolor to tl-latex-recommended

Control: tags -1 + fixed-in-experimental Thanks for the bug report. Fixed version 0.1.5-3 is now in experimental. It will be uploaded to unstable once the transition Octave 4.0 → 4.2 will be sorted out. Rafael * norb...@preining.info [2017-06-20 14:05]: Source:

Bug#865241: [Pkg-octave-devel] Bug#865241: Bug#865241: Please update dependencies from latex-xcolor to tl-latex-recommended

* Sébastien Villemot <sebast...@debian.org> [2017-06-20 11:13]: Le mardi 20 juin 2017 à 10:21 +0200, Rafael Laboissière a écrit : Control: tags -1 + fixed-in-experimental Thanks for the bug report.  Fixed version 0.1.5-3 is now in experimental.  It will be uploaded to unstabl

Bug#876698: [Pkg-octave-devel] Bug#876698: octave-image FTBFS on 32bit: test failures

Control: reopen -1 Control: notfixed -1 1.3.2-3 Oops, I closed the wrong bug report. Sorry for the confusion. Rafael * Rafael Laboissière <raf...@debian.org> [2017-11-05 09:05]: Control: fixed -1 1.3.2-3 * Adrian Bunk <b...@debian.org> [2017-09-25 01:25]: Source: octave-i

Bug#890098: FTBFS: imagemagick in Build-Depends-Indep but needed for arch build

l look at this soon. Rafael Laboissière

Bug#902198: octave-odepkg FTBFS with octave 4.4.0

* Drew Parsons [2018-07-17 00:44]: On Tue, 2018-07-17 at 00:30 +0800, Drew Parsons wrote: On Mon, 2018-07-16 at 13:54 +0200, Rafael Laboissière wrote: I tried to build the package using the tip of the Mercurial repository Weird though, https://wiki.octave.org/Odepkg points at https

Bug#902198: octave-odepkg FTBFS with octave 4.4.0

* Sébastien Villemot [2018-06-28 21:57]: On Fri, Jun 29, 2018 at 03:04:56AM +0800, Drew Parsons wrote: Or does latest the upstream git work, should we just grab that? I remember having tried to apply some upstream patches, but maybe not the second one that you linked to. In any case,

Bug#903105: nlopt: FTBFS with to octave 4.4.0

* Andreas Tille [2018-07-06 10:59]: No idea whether Debian Octave Group is read by a human beeing. It is better to use the debian-octave mailing list for this kind of discussion. On Fri, Jul 06, 2018 at 09:59:46AM +0200, Andreas Tille wrote: Package: nlopt Severity: serious

Bug#895739: psychtoolbox-3: FTBFS: Include deprecated xlocale.h

removed from glibc >= 2.26. The patch attached to this bug report fixes the problem. I will soon upload a fixed package to unstable, which will also fix Bug#890087. Best, Rafael Laboissière -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (650, 'test

Bug#904669: xmds2: autopkgtest times out since 2018-07-19

Hi Paul, * Paul Gevers [2018-09-02 18:21]: Hi Rafael, On 02-09-18 18:10, Rafael Laboissière wrote: I just uploaded version 2.2.3+dfsg-11 of the xmds2 package to unstable. The time-out problem seems to be fixed in this version.  Could you please remove xmds2 from the blacklist to see what

Bug#904669: xmds2: autopkgtest times out since 2018-07-19

* Paul Gevers [2018-07-26 14:28]: Source: xmds2 Version: 2.2.3+dfsg-10 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: timeout Dear maintainers, Since 2018-07-19 the autopkgtest of your package times out (after 2:47h) on ci.debian.net. I have copied

Bug#938925: xmds2: fails mpi hdf5 tests

autopkgtest failure is holding back h5py with mpi support from migrating to testing. Thanks for this bug report. I established a preliminary diagnostic of the problem and kept the upstream authors informed. Rafael Laboissière

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

t-examples, with Arch:any, containing the examples/ directory that is currently in /usr/share/doc/plplot-doc/. @Ole: would you agree with this change? Best, Rafael Laboissière [1] https://salsa.debian.org/science-team/plplot/commit/d8ce3ed802eccecef8583d03a25712069f0643d2

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

Control: tags -1 confirmed * Ole Streicher [2020-01-05 14:19]: On 05.01.20 10:32, Rafael Laboissière wrote: A "simple" solution would be to create a new package plplot-examples, with Arch:any, containing the examples/ directory that is currently in /usr/share/doc/plplot-doc/. @

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

Control: tags -1 pending * Rafael Laboissière [2020-01-05 15:28]: 1) The package will have to go through the NEW queue after upload, because of the new binary package. Indeed: https://ftp-master.debian.org/new/plplot_5.15.0+dfsg-10+gnat8+1.html I am hereby tagging this bug report

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

* Rafael Laboissière [2020-01-05 15:28]: 3) Since 5.15.0+dfsg-11 has been already uploaded to experimental, that version cannot be used for uploading to unstable. I will use the versioning scheme 5.15.0+dfsg-10+unstable1, unless you have any objections. I changed my mind. I just uploaded

Bug#961334: octave-mapping FTBFS on big endian: test failures

* Adrian Bunk [2020-05-23 15:33]: Source: octave-mapping Version: 1.4.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=octave-mapping=s390x=1.4.0-1=1586986257=0 ... shaperead: file /tmp/oct-fdWy3e.dbf couldn't be read; no attributes appended !

Bug#961334: octave-mapping FTBFS on big endian: test failures

* Adrian Bunk [2020-05-28 12:40]: Control: reassign -1 octave-io 2.6.1-1 Control: affects -1 src:octave-mapping Control: close -1 2.6.1-2 On Thu, May 28, 2020 at 09:32:04AM +0200, Rafael Laboissière wrote: * Adrian Bunk [2020-05-23 15:33]: Source: octave-mapping Version: 1.4.0-1 Severity

Bug#976325: [ans...@debian.org: Bug#976325: src:libgdf: invalid maintainer address]

Dear Yaroslav and Michael, Are you aware of the problem related in Bug#976325, regarding the email address t...@neuro.debian.net? Best, Rafael Laboissière - Forwarded message from Ansgar - From: Ansgar Subject: Bug#976325: src:libgdf: invalid maintainer address Date: Thu, 03 Dec

Bug#976325: [ans...@debian.org: Bug#976325: src:libgdf: invalid maintainer address]

* Yaroslav Halchenko [2020-12-07 11:06]: mail server is back online so we are back to enjoying all the mail ;-) Thanks ! Rafael

Bug#974099: octave-database: diff for NMU version 2.4.4-3.1

* Sebastian Ramacher [2020-11-14 12:40]: I couldn't push them directly, so I've created a MR: https://salsa.debian.org/pkg-octave-team/octave-database/-/merge_requests/1 Great, thanks. It is merged now. Best, Rafael Laboissière

Bug#974099: octave-database: diff for NMU version 2.4.4-3.1

-database (versioned as 2.4.4-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Thank you for the upload. Could you please push your changes to the Git depository for the package ? https://salsa.debian.org/pkg-octave-team/octave-database Best, Rafael

Bug#979459: Reassigning, merging and rising severity level of Bugs #979458 and #979459

to the binary jed and jed-common packages, to the jed source package. I am also merging this two bug reports and rising their severity level to serious. The trivial patch that fixes the problem is attached to this message. Best, Rafael Laboissière P.S.: Note that removing the jed-common package from

Bug#979458: Reassigning, merging and rising severity level of Bugs #979458 and #979459

* Rafael Laboissière [2021-08-24 08:45]: […] The trivial patch that fixes the problem is attached to this message. Please, consider rather the patch that is attached to the present message. The jed-common.prerm script must honor the failed-upgrade argument, since the script in version 1

Bug#979458: Reassigning, merging and rising severity level of Bugs #979458 and #979459

* Rafael Laboissière [2021-08-25 13:43]: * Wookey [2021-08-25 12:30]: On 24/08/2021 07:45, Rafael Laboissière wrote: I am hereby reassigning the Bugs #979458 and #979459, which were assigned to the binary jed and jed-common packages, to the jed source package. I am also merging this two

Bug#979458: Reassigning, merging and rising severity level of Bugs #979458 and #979459

* Wookey [2021-08-25 12:30]: On 24/08/2021 07:45, Rafael Laboissière wrote: I am hereby reassigning the Bugs #979458 and #979459, which were assigned to the binary jed and jed-common packages, to the jed source package. I am also merging this two bug reports and rising their severity level

Bug#984148: [PATCH] Re: gcc-avr: ftbfs with GCC-11

find_reloads, defined in file gcc/gcc/reload.c, which accepts an integer as third argument. Caveat: I did not do extensive tests to check for side effects of this change. Best, Rafael Laboissière --- gcc-avr-5.4.0+Atmel3.6.2.orig/gcc/gcc/reload.h +++ gcc-avr-5.4.0+Atmel3.6.2/gcc/gcc/reload.h @@ -168,7

Bug#983993: [PATCH] Re: binutils-avr: ftbfs with GCC-11

Attached to this message is a trivial patch that makes the binutils-avr package build correctly against GCC 11. Best, Rafael Laboissière --- binutils-avr-2.26.20160125+Atmel3.6.2.orig/binutils/bfd/plugin.c +++ binutils-avr-2.26.20160125+Atmel3.6.2/binutils/bfd/plugin.c @@ -338,7 +338,7

Bug#991330: marked as pending in octave-zeromq

Control: tag -1 pending Hello, Bug #991330 in octave-zeromq reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1050796: marked as pending in octave-interval

Control: tag -1 pending Hello, Bug #1050796 in octave-interval reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

* Rafael Laboissière [2023-08-31 15:01]: * Sébastien Villemot [2023-08-31 12:05]: Le jeudi 03 août 2023 à 08:33 +0200, Rafael Laboissière a écrit : Just for the record, this is the offending unit test: 308s [inst/ConfusionMatrixChart.m] 308s >>>>> /tmp/

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

* Sébastien Villemot [2023-08-31 12:05]: Le jeudi 03 août 2023 à 08:33 +0200, Rafael Laboissière a écrit : Just for the record, this is the offending unit test: 308s [inst/ConfusionMatrixChart.m] 308s >>>>> /tmp/autopkgtest-lxc.9x_h6bvs/downtmp/bui

Bug#1050796: octave-interval tests need an update with mpfr4 4.2.1

upstream version of interval package for Octave is released soon. If not, I will released a patched version of octave-interval. Best, Rafael Laboissière * Matthias Klose [2023-08-29 12:20]: Package: octave-interval Version: 3.2.1-5 Severity: serious Tags: sid trixie Forwarded: https

Bug#1052973: octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1

Control: reassign -1 octave-dev 8.3.0-1 Control: affects -1 octave-image Control: notfound -1 octave-image/2.14.0-4 Control: forwarded -1 https://savannah.gnu.org/bugs/index.php?64725 * Rafael Laboissière [2023-09-26 22:00]: Control: tags -1 + confirmed upstream * Lucas Nussbaum [2023-09-26

Bug#1052973: marked as pending in octave

Control: tag -1 pending Hello, Bug #1052973 in octave reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1052973: octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1

, in the way it process its arguments, between versions 8.2 and 8.3 of Octave. I will try to get to this, as time permits. Best, Rafael Laboissière

Bug#1052973: marked as done (octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1)

* Sébastien Villemot [2023-10-07 08:23]: Hi Rafael, Le samedi 07 octobre 2023 à 14:15 +0200, Rafael Laboissière a écrit : I have a question for the Debian Octave Group, related to Bug#1052973, which has been fixed in version 8.3.0-3 of octave-dev. This bug was preventing the building

Bug#1052973: marked as done (octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1)

023 19:04:59 + To: 1052973-cl...@bugs.debian.org Reply-To: Rafael Laboissière Message-Id: Source: octave Source-Version: 8.3.0-3 Done: Rafael Laboissière We believe that the bug you reported is fixed in the latest version of octave, which is due to be installed in the Debian FTP arch

Bug#1053314: Depends: python3-h5py-mpi without python3-h5py

not found. On the other hand maybe that just hides the real problem, that h5py-serial was not installed when actually it was wanted after all. The ImportError correctly identifies that case. On 2023-10-08 17:38, Nilesh Patra wrote: Hello, On 10/8/23 17:22, Rafael Laboissière wrote: Ok, I tr

Bug#1053314: Depends: python3-h5py-mpi without python3-h5py

* Rafael Laboissière [2023-10-09 08:30]: […] At least, I hope that version 3.1.0+dfsg2-5 will really fix Bug#1053314 and the h5py transition will be completed. Unfortunately, it is still not working: https://ci.debian.net/data/autopkgtest/testing/arm64/x/xmds2/38836874/log.gz I guess

Bug#1053314: Depends: python3-h5py-mpi without python3-h5py

rial' from partially initialized module 'h5py' (most likely due to a circular import) (/usr/lib/python3/dist-packages/h5py/__init__.py) Is there a way to force h5py to import _debian_h5py_serial instead of _debian_h5py_mpi, via the generic h5py namespace? Best, Rafael * Rafael Laboissière [2023-10-0

Bug#1053314: Depends: python3-h5py-mpi without python3-h5py

* Nilesh Patra [2023-10-04 02:24]: On Sun, 01 Oct 2023 15:25:43 +0200 Drew Parsons wrote: Package: xmds2 Version: 3.1.0+dfsg2-4 Severity: serious Justification: debci xmds2 Depends: python3-h5py-mpi without depending on python3-h5py python3-h5py-mpi only provides the h5py._debian_h5py_mpi

Bug#1055228: plplot: FTBFS on armhf (test segfault)

* Rafael Laboissière [2023-11-09 17:11]: [snip] There may be a programming error in x09f.f90 or this may be a problem with gfortran on armhf. My knowledge of Fortran is almost non existent and I will need the help of experts, in order to fix the issue. Regarding this issue, I filed a bug

Bug#1013589: marked as pending in octave-interval

Control: tag -1 pending Hello, Bug #1013589 in octave-interval reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1013604: marked as pending in octave-communications

Control: tag -1 pending Hello, Bug #1013604 in octave-communications reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1004770: marked as pending in octave-video

Control: tag -1 pending Hello, Bug #1004770 in octave-video reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1004770: octave-video: Use this patch instead

. Best, Rafael * Rafael Laboissière [2022-08-13 12:17]: Complementing my message below, the unit test in inst/VideWriter.m passed successfully when the sources were compiled against ffmpeg 4, for instance in this build: https://buildd.debian.org/status/fetch.php?pkg=octave-video=amd64=2.0.2-1

Bug#1004770: octave-video: Use this patch instead

Complementing my message below, the unit test in inst/VideWriter.m passed successfully when the sources were compiled against ffmpeg 4, for instance in this build: https://buildd.debian.org/status/fetch.php?pkg=octave-video=amd64=2.0.2-1%2Bb2=1650535691=0 * Rafael Laboissière [2022-08-13 10

Bug#1004770: octave-video: Use this patch instead

defined in src/cap_ffmpeg_wrapper.cc. Do you experience the same problem in your system? Best, Rafael Laboissière

Bug#1025501: pvm: Uninstallable in sid when openssh-client is installed

* Rafael Laboissière [2022-12-06 10:08]: * Rafael Laboissière [2022-12-05 22:55]: The pvm package is currently installable in sid when openssh-client is installed and there is no other package providing rsh-client: Of course, I meant *uninstallable* in the sentence above. The pvm package

Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1

Control: forwarded -1 michelemart...@users.sourceforge.net Control: tags -1 unreproducible Hi Michele, There is a bug report filed against the librsb package (Bug#1016332 [1]) that has severity level "serious". This is blocking the package entering testing and, therefore, librsb will be

Bug#1025501: pvm: Uninstallable in sid when openssh-client is installed

* Rafael Laboissière [2022-12-05 22:55]: The pvm package is currently installable in sid when openssh-client is installed and there is no other package providing rsh-client: Of course, I meant *uninstallable* in the sentence above. The pvm package is orphaned. If nobody objects, I will do

Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1

* Michele Martone [2022-12-04 23:42]: latex is not able to compile a rsbtest-generated file looking like the one I attach. The problematic line is: \usepackage[utf8x]{inputenc} [...] It compiles fine here: $ pdflatex test.tex > /dev/null && grep utf8x.def test.log

Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1

* Michele Martone [2022-12-05 15:31]: In my 20221204@23:42 (yesterday) email I forgot to add that on my chroot setup, I can reproduce latex failing to compile the file I was attaching. In that setup I have a utf8x.def too, sized 8036 bytes and with md5sum 21f7ac37aafb6cfeddbb196b8bfd6280 .

Bug#1025501: pvm: Uninstallable in sid when openssh-client is installed

Package: pvm Version: 3.4.6-3.2 Severity: serious Dear Maintainer, The pvm package is currently installable in sid when openssh-client is installed and there is no other package providing rsh-client: # apt install pvm Reading package lists... Done Building dependency tree... Done

Bug#1042933: octave-statistics autopkg tests fail in unstable on amd64

308s ! test failed 308s set: "cameratarget" must be finite 308s shared variables visibility_setting = on 308s 1 test, 0 passed, 0 known failure, 0 skipped We have seen this problem already elsewhere. I will try to investigate it. Best, Rafael Laboissière

Bug#1042007: marked as pending in octave-sockets

Control: tag -1 pending Hello, Bug #1042007 in octave-sockets reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1035692: marked as pending in jed

Control: tag -1 pending Hello, Bug #1035692 in jed reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/jed/-/commit/40d282d560572a7807e19cc92240b285c7642cdc

Bug#1035839: closed by Debian FTP Masters (reply to Rafael Laboissière ) (Bug#1035839: fixed in jed 1:0.99.20~pre.178+dfsg-4)

Great, thanks for your help! * Axel Beckert [2023-05-10 13:20]: Hi Rafael, Debian Bug Tracking System wrote: jed (1:0.99.20~pre.178+dfsg-4) unstable; urgency=medium . * d/jed-common.preinst: Avoid non-fatal abortion of the script. Thanks to Axel Beckert for the fix (Closes:

Bug#1036096: marked as pending in jed

Control: tag -1 pending Hello, Bug #1036096 in jed reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/jed/-/commit/8541ffd990b36dd9c326326a284d21b06a909234

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie During a rebuild of all packages in sid, your package failed to build on amd64. Thanks for this bug report, but the issue has been already reported. I am hereby reassigning and merging this bug report. Best, Rafael Laboissière

Bug#1057590: Request for action on Bug#1057589, Bug#1057590, and Bug#1058281

Hi Santiago and Lucas, You have filed bug reports against octave-netcdf (Bug#1057590) and octave-ncarray (Bug#1057589 and Bug#1058281). These packages FTBFS due to an issue in the netcdf package (Bug#1058281), which has been fixed thanks to the recent upload of version 4.9.2-3. Would it be

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

* Rafael Laboissière [2023-12-22 04:36]: * Sébastien Villemot [2023-12-21 15:23]: Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit : * Santiago Vila [2023-12-20 22:03]: El 20/12/23 a las 21:08, Rafael Laboissière escribió: HOME := $(shell mktemp -d) so that the same

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

Rafael * Santiago Vila [2023-12-15 12:59]: El 13/12/23 a las 9:27, Rafael Laboissière escribió: i.e. you may rely on a writable $HOME if it's for a "good cause" (i.e. dh_auto_test). So, the simple question: Should this not be also implemented in dh_octave_check as well, whi

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

Control: block -1 by 1058621 Control: merge -1 1057590 Trying again…

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

it. Best, Rafael Laboissière

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

* Rafael Laboissière [2023-12-15 21:44]: * Santiago Vila [2023-12-15 18:15]: The thing I don't understand here is why this problem in octave-vibes was diagnosed as an "unwritable $HOME" in the first place. This is what I concluded after running some tests, but I do not

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

the Policy paragraph that you quoted: The Debian autobuilders set HOME to /nonexistent so that packages which try to write to a home directory will fail to build. would probably need to be reworded a little bit. I agree. I think that a bug report should be filed against debian-policy on this is

Bug#1057589: Reassign Bug#1057589 and merge it with #1057590

reassign 1057589 src:octave-netcdf merge 1057589 1057590 stop

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

* Santiago Vila [2023-12-20 13:43]: El 16/12/23 a las 22:30, Rafael Laboissière escribió: I did the investigation again, using pbuilder. Here is what I found: – In my case, pbuilder sets HOME=/nonexistent/ and debhelper (compat level = 13) keeps that setting. Hence, the package FTBFS

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

* Santiago Vila [2023-12-20 22:03]: El 20/12/23 a las 21:08, Rafael Laboissière escribió: HOME := $(shell mktemp -d) so that the same directory is never used twice between consecutive builds. Yes, this is a much better solution. Thanks for the suggestion. I am just wondering

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

* Sébastien Villemot [2023-12-21 15:23]: Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit : * Santiago Vila [2023-12-20 22:03]: El 20/12/23 a las 21:08, Rafael Laboissière escribió: HOME := $(shell mktemp -d) so that the same directory is never used twice between

Bug#1059652: Proposed-RM: slpvm -- RoQA; PVM no longer maintained

unmaintained. If there are no objections, I'll reassign this bug to the FTP team. I'll wait at least two weeks, i.e., at least until 2024-01-13; though it might take longer until I look at this again. Please, reassign this bug to ftp.debian.org. Thanks for your QA work. Best, Rafael Laboissière

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

Control: blocked -1 by 1058621 Control: merge -1 1057590 I hope that the merge goes well this time. Best, Rafael Laboissière

Bug#1055228: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

Control: severity -1 important * Sebastiaan Couwenberg [2024-01-01 20:13]: plplot got removed from armhf, the severity of this issue could be lowered to important to not have the package removed from testing. Thanks, I am doing it hereby. Best, Rafael Laboissière

Bug#1013584: octave-iso2mesh: FTBFS: dh_missing: error: missing files, aborting

and released version 1.9.6+ds-8 with eh proposed "fix" (adding debian/not-installed). Actually, this is not the right thing to do, since the files in debian/tmp/usr/share/octave/packages/ should go into the binary package octave-iso2mesh. I am hereby rectifying the situation. Best, Rafael Laboissière

Bug#1059040: libxml2: ABI change? (undefined references)

) and disables the call to the xmlNanoFTP* functions. However, this rebuilt will not be automatically triggered without a bump in the SONAME version of libxml2. In summary, the introduction of version 2.12 of libxml2 in unstable will need a proper and coordinated transition. Best, Rafael

Bug#1060999: marked as pending in octave-sockets

Control: tag -1 pending Hello, Bug #1060999 in octave-sockets reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1061011: marked as pending in octave-zeromq

Control: tag -1 pending Hello, Bug #1061011 in octave-zeromq reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1059040: libxml2: ABI change? (undefined references)

* Thorsten Glaser [2024-01-12 17:56]: On Fri, 12 Jan 2024, Rafael Laboissière wrote: experimental, the configure script does detect the absence of the xmlNanoFTPNewCtxt function in the libxml2 library (version 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. However

Bug#1057590: octave-netcdf: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

package failed to build: [snip] fatal: caught signal Segmentation fault -- stopping myself... Segmentation fault Thanks for the bug report. It seems to be an upstream problem. I have forwarded the bug to the upstream developers. Best, Rafael Laboissière

Bug#1057589: octave-ncarray: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

, on which octave-ncarray depends. I am hereby merging the present bug report with Bug#1057590 Best, Rafael Laboissière * Santiago Vila [2023-12-05 23:08]: Package: src:octave-ncarray Version: 1.0.5-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages

Bug#1057588: marked as pending in octave-nan

Control: tag -1 pending Hello, Bug #1057588 in octave-nan reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1062613: librsb: NMU diff for 64-bit time_t transition

Control: tags -1 + upstream Thanks for this bug report and for the upload to experimental, Steve. I am hereby forwarding your message to the upstream author. Best, Rafael Laboissière * Steve Langasek [2024-02-02 06:09]: Source: librsb Version: 1.3.0.2+dfsg-6 Severity: serious Tags

Bug#1062613: librsb: NMU diff for 64-bit time_t transition

Control: tags -1 - upstream * Steve Langasek [2024-02-02 08:48]: On Fri, Feb 02, 2024 at 02:06:38PM +0100, Rafael Laboissière wrote: Control: tags -1 + upstream Thanks for this bug report and for the upload to experimental, Steve. I am hereby forwarding your message to the upstream

Bug#1063045: vibes: NMU diff for 64-bit time_t transition

Thanks, Steve. I have added your changes to Git [*] Best, Rafael Laboissière [*] https://salsa.debian.org/debian/vibes/-/commit/566014ea0e7b29684b4391fbabd3ae5b8090c6e8 * Steve Langasek [2024-02-04 17:47]: Source: vibes Version: 0.2.3+dfsg-1 Severity: serious Tags: patch pending sid

Bug#1062613: librsb: NMU diff for 64-bit time_t transition

Hello Steve, * Rafael Laboissière [2024-02-02 18:19]: Control: tags -1 - upstream * Steve Langasek [2024-02-02 08:48]: On Fri, Feb 02, 2024 at 02:06:38PM +0100, Rafael Laboissière wrote: Control: tags -1 + upstream Thanks for this bug report and for the upload to experimental, Steve

Bug#1055228: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

have any reasons to believe the compiler is at fault really. Thanks for the suggestion, Emanuele. I am hereby merging both bugs, which are now both assigned to plplot. Best, Rafael Laboissière

Bug#1055228: Processed (with 1 error): Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

severity 1055750 serious merge 1055750 1055228

Bug#1055228: plplot: FTBFS on armhf (test segfault)

m with gfortran on armhf. My knowledge of Fortran is almost non existent and I will need the help of experts, in order to fix the issue. Best, Rafael Laboissière [1] https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=1d46b351f [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054583

  1   2   >