Bug#895411: they are waiting for qt 5.11
Hi, may I kindly ask why you keep on uploading new versions, while being fully aware that there is no way at all to make them even start? In case you wonder: I have a locally built Anki version where I patched out the QT version check. That works well enough for me. Your uploads are replacing this with a completely non-functional version. Please, stop uploading new, completely broken versions just for the sake of uploading. Thomas
Bug#852627: lcms2: diff for NMU version 2.8-3.1
On Fri, Jan 27, 2017 at 07:27:43AM +0100, Thomas Weber wrote: > HI Salvatore, > On Thu, Jan 26, 2017 at 09:44:49PM +0100, Salvatore Bonaccorso wrote: > > Control: tags 852627 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for lcms2 (versioned as 2.8-3.1) and > > uploaded it to DELAYED/2. Please feel free to tell me if I > > should delay it longer. > > Sorry, I just uploaded 2.8-4 without checking the bug log again (I > prepard the fix yesterday). So, your NMU will probably never hit > unstable. I am sorry for the extra work. Unblock request is https://bugs.debian.org/852770 Thomas
Bug#852627: marked as pending
tag 852627 pending thanks Hello, Bug #852627 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=collab-maint/lcms2.git;a=commitdiff;h=e16d58f --- commit e16d58fd5eee66d96d0f31b730eca299157f109a Author: Thomas Weber Date: Thu Jan 26 11:04:40 2017 +0100 Debian release 2.8-4 diff --git a/debian/changelog b/debian/changelog index 309a388..602f838 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +lcms2 (2.8-4) unstable; urgency=medium + + * New patch: debian/patches/fix-CVE-2016-10165.patch. +Fix for CVE-2016-10165. (Closes: #852627) +Thanks to Salvatore Bonaccorso + + -- Thomas Weber Thu, 26 Jan 2017 11:04:13 +0100 + lcms2 (2.8-3) unstable; urgency=medium * New patch: lcms2-fix-strFrom16-byte-order.patch.
Bug#852627: lcms2: diff for NMU version 2.8-3.1
HI Salvatore, On Thu, Jan 26, 2017 at 09:44:49PM +0100, Salvatore Bonaccorso wrote: > Control: tags 852627 + pending > > Dear maintainer, > > I've prepared an NMU for lcms2 (versioned as 2.8-3.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Sorry, I just uploaded 2.8-4 without checking the bug log again (I prepard the fix yesterday). So, your NMU will probably never hit unstable. I am sorry for the extra work. Thomas
Bug#807091: xfce4-terminal fails to start with an error message
Package: xfce4-terminal Version: 0.6.3-2 Severity: grave Justification: renders package unusable Launching xfce4-terminal as normal user gives the following error message in an error window: "Failed to execute child grantpt failed: Operation not permitted" After closing the error message, the terminal window appears, but there is no shell started in it. If I gain superuser rights via su and execute xfce4-terminal, the terminal launches (with an error message saying "Failed to connect to session manager: [...]". Some reports on the internet suggested that this might be a permission problem with /dev/pts. However, I do not have an entry for /dev/pts in my /etc/fstab and the rights are as follows: devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000) This (non-)behaviour of xfce4-terminal is fairly new, but I cannot pinpoint it to any recent update as I usually keep up just one instance of the terminal for some time. Thanks Thomas -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-terminal depends on: ii exo-utils 0.10.7-1 ii libatk1.0-0 2.18.0-1 ii libc6 2.21-3 ii libgdk-pixbuf2.0-0 2.32.2-1 ii libglib2.0-02.46.2-1 ii libgtk2.0-0 2.24.28-1 ii libpango-1.0-0 1.38.1-1 ii libvte9 1:0.28.2-5+b1 ii libx11-62:1.6.3-1 ii libxfce4ui-1-0 4.12.1-2 ii libxfce4util7 4.12.1-2 Versions of packages xfce4-terminal recommends: ii dbus-x11 1.10.6-1 xfce4-terminal suggests no packages. -- no debconf information
Bug#749975: [pkg-octave/master] New patch: fix-unaligned-access.patch Align access to double values
tag 749975 pending thanks Date: Thu Jun 5 14:45:10 2014 + Author: Thomas Weber Commit ID: e2c7cdda765d4fb64911d3219f87a117f962f8a4 Commit URL: http://anonscm.debian.org/gitweb/?p=collab-maint/lcms2.git;a=commitdiff;h=e2c7cdda765d4fb64911d3219f87a117f962f8a4 Patch URL: http://anonscm.debian.org/gitweb/?p=collab-maint/lcms2.git;a=commitdiff_plain;h=e2c7cdda765d4fb64911d3219f87a117f962f8a4 New patch: fix-unaligned-access.patch Align access to double values Closes: #749975 Thanks: Aurelien Jarno -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#713208: petsc: FTBFS: cp: cannot stat '/usr/share/automake-1.11/config.*': No such file or directory
On Mon, Sep 09, 2013 at 02:21:05PM +0200, Julien Cristau wrote: > On Mon, Sep 9, 2013 at 14:09:17 +0200, Thomas Weber wrote: > > @@ -89,7 +93,7 @@ build-indep: > > build-arch: > > dh_quilt_patch > > echo Using MPI implementation $(PETSC_MPI) in directory $(PETSC_MPI_DIR) > > - cp -fp /usr/share/automake-1.13/config.* > > config/BuildSystem/config/packages/ > > + cp -fp $(AUTOMAKE_LIB_DIR)/config.* config/BuildSystem/config/packages/ > > You could just copy them from /usr/share/misc, which doesn't change. Okay, new patch attached. Thomas >From 9af0f6fe749bcbd18c97f0e0a3407387d8e278f8 Mon Sep 17 00:00:00 2001 From: Thomas Weber Date: Mon, 9 Sep 2013 09:38:01 +0200 Subject: [PATCH] Make copying config.guess and config.sub independent of automake version Replace automake by autotools-dev for that. --- debian/control | 2 +- debian/rules | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/control b/debian/control index da5096a..04e9838 100644 --- a/debian/control +++ b/debian/control @@ -4,7 +4,7 @@ Priority: extra Maintainer: Debian Science Maintainers Uploaders: "Adam C. Powell, IV" Standards-Version: 3.9.2 -Build-Depends: debhelper (>= 7.0.50), quilt, python (>= 2.2), gfortran, automake, +Build-Depends: debhelper (>= 7.0.50), quilt, python (>= 2.2), gfortran, autotools-dev, libx11-dev, mpi-default-dev, libblas-dev, liblapack-dev, libsuitesparse-dev (>= 3.1.0-2), diff --git a/debian/rules b/debian/rules index 6046d46..908d150 100755 --- a/debian/rules +++ b/debian/rules @@ -89,7 +89,7 @@ build-indep: build-arch: dh_quilt_patch echo Using MPI implementation $(PETSC_MPI) in directory $(PETSC_MPI_DIR) - cp -fp /usr/share/automake-1.13/config.* config/BuildSystem/config/packages/ + cp -fp /usr/share/misc/config.* config/BuildSystem/config/packages/ if [ ! -f TAGS.backup ]; then cp -a TAGS TAGS.backup; fi PETSC_DIR=$(CURDIR) PETSC_ARCH=$(PETSC_ARCH)-c-debug \ ./config/configure.py --with-shared-libraries --with-debugging=1 \ -- 1.8.4.rc3
Bug#713208: petsc: FTBFS: cp: cannot stat '/usr/share/automake-1.11/config.*': No such file or directory
tags 713208 patch thanks On Sat, Jun 22, 2013 at 02:11:22PM +0200, Lucas Nussbaum wrote: > Relevant part: > > debian/rules build > > dh_quilt_patch > > File series fully applied, ends at patch umfpack.patch > > echo Using MPI implementation openmpi in directory /usr/lib/openmpi > > Using MPI implementation openmpi in directory /usr/lib/openmpi > > cp -fp /usr/share/automake-1.11/config.* config/BuildSystem/config/packages/ > > cp: cannot stat '/usr/share/automake-1.11/config.*': No such file or > > directory > > make: *** [build-arch] Error 1 The attached patch should get rid of the requirement for a path with the automake version in it. The build still fails at a later stage, though: makefile:15: linux-gnu-c-debug/conf/petscvariables: No such file or directory /tmp/petsc/conf/variables:108: /tmp/petsc/linux-gnu-c-debug/conf/petscvariables: No such file or directory /tmp/petsc/conf/rules:963: /tmp/petsc/linux-gnu-c-debug/conf/petscrules: No such file or directory make[1]: *** No rule to make target `/tmp/petsc/linux-gnu-c-debug/conf/petscrules'. Stop. Thomas >From f5f31590c3098971cefbce75903dba941dc54a4b Mon Sep 17 00:00:00 2001 From: Thomas Weber Date: Mon, 9 Sep 2013 09:38:01 +0200 Subject: [PATCH] Make copying config.guess and config.sub independent of automake version --- debian/rules | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 6046d46..55dba7c 100755 --- a/debian/rules +++ b/debian/rules @@ -56,6 +56,10 @@ PETSC_NAME=petsc$(PETSC_VERSION) ARCH_GENERATED_FILES=debian/lib$(PETSC_NAME)-dev.docs \ debian/lib$(PETSC_NAME)-dev.postinst debian/lib$(PETSC_NAME)-dev.prerm +# Get automake library directory, to make the copying later independent of the +# installed version of automake, see http://bugs.debian.org/713208 +AUTOMAKE_LIB_DIR=$(shell automake --print-libdir) + clean: dh_testdir if [ -f TAGS.backup ]; then mv -f TAGS.backup TAGS; fi @@ -89,7 +93,7 @@ build-indep: build-arch: dh_quilt_patch echo Using MPI implementation $(PETSC_MPI) in directory $(PETSC_MPI_DIR) - cp -fp /usr/share/automake-1.13/config.* config/BuildSystem/config/packages/ + cp -fp $(AUTOMAKE_LIB_DIR)/config.* config/BuildSystem/config/packages/ if [ ! -f TAGS.backup ]; then cp -a TAGS TAGS.backup; fi PETSC_DIR=$(CURDIR) PETSC_ARCH=$(PETSC_ARCH)-c-debug \ ./config/configure.py --with-shared-libraries --with-debugging=1 \ -- 1.8.4.rc3
Bug#696377: octave3.2: 35 octave-* packages fail to upgrade from lenny to squeeze: octave3.0: error while loading shared libraries: liblapack.so.3gf: cannot open shared object file: No such file or di
On Mon, Dec 31, 2012 at 02:48:13AM +0100, Andreas Beckmann wrote: > On 2012-12-26 10:38, Rafael Laboissiere wrote: > I'm currently doing lenny->squeeze->wheezy upgrade tests to find > packages that "did something wrong (but did not fail)" in lenny or > lenny->squeeze that makes the upgrade to wheezy fail (or makes > removing/purging in wheezy or some other checks in wheezy fail). > Upgrading long grown systems should work without problems ... Ah, shit. I so hoped that we could debate this issue away ;) > > I am curious: why is this bug popping out only now? Why was it not > > discovered during the release cycle of squeeze? > > without checking any logs ...: piuparts has seen a lot of improvements > since then and that probably increased the test coverage of the archive > (including old releases) > or maybe the problem was already discovered by earlier tests, but nobody > had the time to analyze the failed logfiles and therefore no bugs were filed I think Rafael meant that more along the lines of "if this is really an issue, why do we see it so late in the release cycle of squeeze". Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696377: [Pkg-octave-devel] Bug#696377: octave3.2: 35 octave-* packages fail to upgrade from lenny to squeeze: octave3.0: error while loading shared libraries: liblapack.so.3gf: cannot open shared
On Thu, Dec 20, 2012 at 07:08:27AM +0100, Andreas Beckmann wrote: > Package: octave3.2 > Version: 3.2.4-8 > Severity: serious > Tags: squeeze > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + octave-ad octave-zenity > > Hi, > > during a test with piuparts I noticed many octave packages failing to > upgrade from lenny to squeeze. To be honest, I don't quite see the value of checking for upgrades from lenny to squeeze at this point of the release cycle - octave3.0 was removed in 2010. Putting it another way, how many users do we help by fixing this issue now? > >From the attached log: > > Preparing to replace octave-zenity 0.5.5-1 (using > .../octave-zenity_0.5.7-2_all.deb) ... > octave3.0: error while loading shared libraries: liblapack.so.3gf: cannot > open shared object file: No such file or directory This looks more like an issue with atlas. However, I am not going to investigate this, unless a real user is upgrading to squeeze this late. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664797: [pkg-octave/master] Ensure that the "-fno-automatic" flag is passed to gfortran
tag 664797 pending thanks Date: Thu Aug 2 19:10:37 2012 +0200 Author: Thomas Weber Commit ID: 87b565a8939fbab1e0c151172049c50cff50c8e7 Commit URL: http://git.debian.org/?p=pkg-octave/octave-odepkg.git;a=commitdiff;h=87b565a8939fbab1e0c151172049c50cff50c8e7 Patch URL: http://git.debian.org/?p=pkg-octave/octave-odepkg.git;a=commitdiff_plain;h=87b565a8939fbab1e0c151172049c50cff50c8e7 Ensure that the "-fno-automatic" flag is passed to gfortran Closes: #664797 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681355: [pkg-octave/master] Set and use JAVA_ARCH correctly on all platforms
tag 681355 pending thanks Date: Sun Jul 22 23:12:37 2012 +0200 Author: Thomas Weber Commit ID: 401bd399aa005488f2152681a533ad0a15b426ea Commit URL: http://git.debian.org/?p=pkg-octave/octave-java.git;a=commitdiff;h=401bd399aa005488f2152681a533ad0a15b426ea Patch URL: http://git.debian.org/?p=pkg-octave/octave-java.git;a=commitdiff_plain;h=401bd399aa005488f2152681a533ad0a15b426ea Set and use JAVA_ARCH correctly on all platforms We use the javahelper package and change upstream's configure script such that it uses the given value. New patch: enable_preset_java_arch_value Closes: #681355 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681355: [Pkg-octave-devel] Bug#681355: octave-java: Not working on architecture armel
Hi Lutz, On Thu, Jul 12, 2012 at 04:28:49PM +0200, Lutz Kohl wrote: > Package: octave-java > Version: 1.2.8-3 > Severity: normal > > Invoking > > javaclasspath > > in octave on architecture armel produces the error Can you act as guinea pig for a new package? I don't have access to armel myself and you seem to already have everything set up. Code is available at http://people.debian.org/~tweber/octave-java/ The changelog and version need to be bumped, but it's just a quick test. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#517411: xcdroast: complains about cdrecord even with dummy-package cdrecord installed
On Fri, Feb 27, 2009 at 03:14:36PM +0100, Gordon Shumway wrote: > Package: xcdroast > Version: 0.98+0alpha16-1 > Severity: normal This grave bug is now 3 years old, with no apparent maintainer activity for the xcdroast package for as long. Hector, unless you disagree, I intend to ask for xcdroast's removal from unstable in the near future. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676800: [Pkg-octave-devel] Bug#676800: Bug#676800: Bug#676800: octave-java: completely breaks octave
On Thu, Jul 05, 2012 at 08:30:26PM +0200, Sébastien Villemot wrote: > > I wasn't able to reproduce it, and I didn't see anyone else having > > similar problems. > > I experience the crash on two different machines of mine (actually my > main machines at home and work), so this is a real blocker for me. Maybe > this can only be reproduced when a specific set of packages is installed > or with a specific configuration. I intend to spend more time soon to > isolate the factor causing the crash. Any chance you could try it in a virtual environment (chroot or maybe VirtualBox) and make that environment available somewhere (like taring up the chroot)? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676800: [Pkg-octave-devel] Bug#676800: octave-java: completely breaks octave
On Sat, Jun 09, 2012 at 12:17:48PM +, Sébastien Villemot wrote: > Package: octave-java > Version: 1.2.8-4 > Severity: grave > Tags: sid > > This version of octave-java completely breaks octave. Sébastien, is this the same issue we tried to debug in IRC? I wasn't able to reproduce it, and I didn't see anyone else having similar problems. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663088: [Pkg-octave-devel] Bug#663088: Bug#663088: octave: fails to install: error: could not find the file or path /usr/lib//octave/packages/
On Thu, Mar 08, 2012 at 02:21:05PM +0100, Sébastien Villemot wrote: > Thanks for noticing this. Obviously there is a missing dependency of > octave on dpkg-dev >= 1.16.0. Ah, shit. That's what I get for uploading late at night. > Thomas: can you push your git commits related to version 3.6.1-2 ? Then > I will fix this bug and upload 3.6.1-3. Pushed. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#652958: oggvideotools: oggCat crashes when trying to concatenate files
Hi, On Thu, Dec 22, 2011 at 02:19:13PM +0530, Noufal Ibrahim wrote: > Package: oggvideotools > Version: 0.8-1 > Severity: grave > Justification: renders package unusable oggvideotools seems to be dead upstream: 1) The latest release is from 2010-05-30. 2) The latest SVN checkin is from 2010-11-29 Maybe it's better to remove it from Debian instead of uploading the latest (18 months old) upstream version. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657004: libmusicbrainz-ruby: please remove from the archive
Hi Andres, On Mon, Jan 23, 2012 at 02:19:12PM +0200, Timo Aaltonen wrote: > Package: libmusicbrainz-ruby > Severity: grave > > This package depends on an obsolete version of libmusicbrainz, which > is going to be removed from the archive in the near future. Please > remove libmusicbrainz-ruby as well, since the upstream project seems > dead as well: > > http://pablotron.org/software/mb-ruby/ If you do mind a removal of this package from a) testing b) unstable please say so, otherwise I'll request a removal from one or both by the end of February. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555483: Seems to be fixed in new upstream as well
package: logjam fixed 555483 4.6.2-1 thanks I cannot reproduce the bug in the new upstream version, so I assume it's fixed there as well. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659893: [strigi-dbg] no debugging symbols found
On Tue, Feb 14, 2012 at 04:37:45PM +0100, bgr...@toplitzer.net wrote: > Package: strigi-dbg > Version: 0.7.7-1 > Severity: grave > > --- Please enter the report below this line. --- > > trying to debug on #659828 I found the following problem: > the strigi-dbg package doesn't work with gdb: There are no useful debug symbols because the package is built without debug information. Patch attached. The package is built without optimization right now and I didn't change that. If you want to change that as well, use 'RelWithDebInfo' instead of 'Debug'. Thomas diff --git a/debian/libstreams-dev.install b/debian/libstreams-dev.install index f14f624..8ab6229 100644 --- a/debian/libstreams-dev.install +++ b/debian/libstreams-dev.install @@ -29,7 +29,7 @@ usr/include/strigi/textutils.h usr/include/strigi/zipinputstream.h usr/lib/libstreams.so usr/lib/libstreams/LibStreamsConfig.cmake -usr/lib/libstreams/LibStreamsTargets-noconfig.cmake +usr/lib/libstreams/LibStreamsTargets-debug.cmake usr/lib/libstreams/LibStreamsTargets.cmake usr/lib/pkgconfig/libstreams.pc usr/lib/strigi/StrigiConfig.cmake diff --git a/debian/rules b/debian/rules index c56e25f..3fc927f 100755 --- a/debian/rules +++ b/debian/rules @@ -13,7 +13,7 @@ LIBPKGS := $(shell dh_listpackages | grep libs | sed -e '/dev/d;') dh $@ --parallel --list-missing --dbg-package=strigi-dbg --with pkgkde_symbolshelper override_dh_auto_configure: - dh_auto_configure -- -DCMAKE_SKIP_RPATH=ON + dh_auto_configure -- -DCMAKE_SKIP_RPATH=ON -DCMAKE_BUILD_TYPE=Debug override_dh_makeshlibs: dh_makeshlibs -V
Bug#645915: libafflib0: links against both readline and openssl on i386
Package: libafflib0 Severity 645915 normal thanks I'm downgrading the severity, because I cannot reproduce this in my i386 chroot. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645915: libafflib0: links against both readline and openssl on i386
On Wed, Oct 19, 2011 at 06:37:36PM +0200, Sven Joachim wrote: > Package: libafflib0 > Version: 3.6.6-1.1 > Severity: serious > > On i386 only, libafflib is linked against both libreadline which is > under GPLV3+, and libssl which is under a GPL-incompatible license. Are you sure about the linkage against libreadline? $ ldd /usr/lib/libafflib.so.0.0.0 linux-gate.so.1 => (0xf76ec000) libssl.so.1.0.0 => /usr/lib/i386-linux-gnu/i686/cmov/libssl.so.1.0.0 (0xf7629000) libcrypto.so.1.0.0 => /usr/lib/i386-linux-gnu/i686/cmov/libcrypto.so.1.0.0 (0xf747b000) libcurl.so.4 => /usr/lib/i386-linux-gnu/libcurl.so.4 (0xf740c000) libexpat.so.1 => /lib/i386-linux-gnu/libexpat.so.1 (0xf73e4000) librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf73db000) libz.so.1 => /usr/lib/i386-linux-gnu/libz.so.1 (0xf73c4000) libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf72db000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf72b4000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf716b000) libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf714e000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf714a000) libidn.so.11 => /usr/lib/i386-linux-gnu/libidn.so.11 (0xf7117000) libssh2.so.1 => /usr/lib/libssh2.so.1 (0xf70ef000) liblber-2.4.so.2 => /usr/lib/i386-linux-gnu/liblber-2.4.so.2 (0xf70e) libldap_r-2.4.so.2 => /usr/lib/i386-linux-gnu/libldap_r-2.4.so.2 (0xf708f000) libgssapi_krb5.so.2 => /usr/lib/i386-linux-gnu/libgssapi_krb5.so.2 (0xf7051000) librtmp.so.0 => /usr/lib/i386-linux-gnu/librtmp.so.0 (0xf7037000) libgnutls.so.26 => /usr/lib/i386-linux-gnu/libgnutls.so.26 (0xf6f6f000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf6f56000) /lib/ld-linux.so.2 (0xf76ed000) libgcrypt.so.11 => /lib/i386-linux-gnu/libgcrypt.so.11 (0xf6ed1000) libresolv.so.2 => /lib/i386-linux-gnu/libresolv.so.2 (0xf6ebc000) libsasl2.so.2 => /usr/lib/i386-linux-gnu/libsasl2.so.2 (0xf6ea) libkrb5.so.3 => /usr/lib/i386-linux-gnu/libkrb5.so.3 (0xf6dcd000) libk5crypto.so.3 => /usr/lib/i386-linux-gnu/libk5crypto.so.3 (0xf6da3000) libcom_err.so.2 => /lib/i386-linux-gnu/libcom_err.so.2 (0xf6d9f000) libkrb5support.so.0 => /usr/lib/i386-linux-gnu/libkrb5support.so.0 (0xf6d96000) libkeyutils.so.1 => /lib/i386-linux-gnu/libkeyutils.so.1 (0xf6d91000) libtasn1.so.3 => /usr/lib/i386-linux-gnu/libtasn1.so.3 (0xf6d7f000) libp11-kit.so.0 => /usr/lib/i386-linux-gnu/libp11-kit.so.0 (0xf6d6e000) libgpg-error.so.0 => /lib/i386-linux-gnu/libgpg-error.so.0 (0xf6d6a000) Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637787: [Pkg-octave-devel] Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: trivial fix
On Tue, Nov 01, 2011 at 12:45:05PM -0400, John W. Eaton wrote: > Did you see the following message from me? I think I found the reason > that libranlib.la is not being built, and a relatively simple fix. Yes, thanks for the help. I already pushed it to my quick-and-dirty repository at http://anonscm.debian.org/gitweb/?p=users/tweber/octave.git;a=commit;h=e6380e7629dc72292fa27ada8edc62fff3a708d9 Sorry, but my time is limited right now and this won't get better in the next few months. I do hope however to get the Octave packaging finished in November. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637787: [Pkg-octave-devel] Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: trivial fix
On Mon, Oct 24, 2011 at 11:07:50PM -0400, John W. Eaton wrote: > On 24-Oct-2011, Thomas Weber wrote: > | I've put a log file of the build at > | http://people.debian.org/~tweber/octave.log.bz2 > | > | The commands effectively run are: > | automake --foreign --verbose > | ./configure --build=x86_64-linux-gnu --prefix=/usr > | make -j1 > | > | Do you have any ideas? > > I can't reproduce the problem, but I'm not sure I'm doing exactly the > same thing as you. > > Can you please give me step-by-step instructions for how to download > exactly the Debian package files and what to do with them to try to > generate the package? Jordi gave me that info a few days ago and with > what he showed me, I was able to generate the error you mention > above. But now I can't find his instructions. You can clone the git repository via git clone git://anonscm.debian.org/users/tweber/.git I've put a tarball with the current status at http://people.debian.org/~tweber/octave-debian.tar.bz2 In order to build the software, you'll need the build-dependencies from the debian/control file. The following line should do this: aptitude install --without-recommends gfortran debhelper autotools-dev automake texinfo texlive-latex-base texlive-generic-recommended libreadline-dev libncurses5-dev gperf libhdf5-serial-dev libhdf5-lam-dev libblas-dev liblapack-dev gnuplot-nox libfftw3-dev texi2html less quilt slice libpcre3-dev flex libglpk-dev libsuitesparse-dev gawk ghostscript libcurl4-gnutls-dev libqhull-dev desktop-file-utils libfltk1.1-dev libgraphicsmagick++1-dev libftgl-dev libfontconfig1-dev libqrupdate-dev libarpack2-dev In addition, quilt is needed for the patches, together with a specific $HOME/.quiltrc: $ cat $HOME/.quiltrc QUILT_PATCHES=debian/patches QUILT_DIFF_ARGS="--no-timestamps --no-index -pab" QUILT_REFRESH_ARGS="--no-timestamps --no-index -pab" Now, go into the octave/ directory of the software (either git or tarball) and execute dpkg-buildpackage This should build the softwre and apply the patches first (the quilt usage is only needed if you want to build by hand). Another way of building is by issueing ./debian/rules binary This has the advantage that it doesn'c clean the tree before building (dpkg-buildpackage does clean it). Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637787: [Pkg-octave-devel] Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: trivial fix
On Thu, Sep 01, 2011 at 09:03:57PM +0200, Thomas Weber wrote: > On Tue, Aug 23, 2011 at 12:24:17PM -0400, John W. Eaton wrote: > > If you don't want to change octlibdir, then you can change the lines > > like > > > > octlib_LTLIBRARIES = liboctave.la > > > > in the Makefile.am files to be > > > > lib_LTLIBRARIES = liboctave.la > > > > instead. It's the octlib (or lib) prefix that is used to generate the > > variable that determines the installation directory. I did the change above, but the build fails almost always (almost = in a clean chroot). It builds reliable in my normal work directory, which is strange (I already looked at timestamp issues, but I do not think that that is the problem). It always fails when linking in libcruft/ with the error message: libtool: link: cannot find the library `libranlib.la' or unhandled argument `libranlib.la' I've put a log file of the build at http://people.debian.org/~tweber/octave.log.bz2 The commands effectively run are: automake --foreign --verbose ./configure --build=x86_64-linux-gnu --prefix=/usr make -j1 Do you have any ideas? Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#628353: [Pkg-octave-devel] Bug#628353: octave-symbolic: FTBFS: Inconsistency detected by ld.so: dl-close.c: 737: _dl_close: Assertion `map->l_init_called' failed!
Hi Colin, On Fri, Sep 09, 2011 at 10:20:29AM +0100, Colin Watson wrote: > On Thu, Sep 08, 2011 at 01:34:14PM +0100, Colin Watson wrote: > > Thanks to a note from John W. Eaton that the development version doesn't > > suffer from this problem, I tracked down the fix and have prepared a > > suitable patch against the Debian package. Please consider this to fix > > the octave-symbolic build failure. > > Urgh, I missed the existence of debian/in/series. Updated patch > follows. Thanks for taking care. I'm going to upload it in a moment. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637787: [Pkg-octave-devel] Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: trivial fix
On Tue, Aug 23, 2011 at 12:24:17PM -0400, John W. Eaton wrote: > If you don't want to change octlibdir, then you can change the lines > like > > octlib_LTLIBRARIES = liboctave.la > > in the Makefile.am files to be > > lib_LTLIBRARIES = liboctave.la > > instead. It's the octlib (or lib) prefix that is used to generate the > variable that determines the installation directory. I'm understanding that now. Thanks for helping. > Maybe we should change the Octave sources to install the Octave > libraries in $libdir instead of $octlibdir? Or would $pkglibdir be > better? That is predefined by automake, so writing > > pkglib_LTLIBRARIES = liboctave.la > > should cause liboctave to be installed in $(libdir)/@PACKAGE@ (with > "octave" substituted for @PACKAGE@ by configure. > Is the current problem that the libraries are placed in a directory > that has a version number in the name, or does dpkg-shlibeps not find > files in subdirectories of /usr/lib at all? That's a good question; I'm not really sure. I don't think however, that the version should be in the installation path - what happens when 3.4.3 comes around? You should take my words on this with a grain of salt, though. I'm new to it myself. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637787: [Pkg-octave-devel] Bug#637787: Bug#637787: Bug#637787: trivial fix
On Mon, Aug 22, 2011 at 02:28:54PM -0400, John W. Eaton wrote: > On 19-Aug-2011, Thomas Weber wrote: > > | The problem is that dpkg-shlibdeps doesn't like the fact that Octave > | uses normal SONAMEs for its libraries now, but ships them in a private > | path (so dpkg-shlibdeps doesn't find them and aborts). > | So, I'm reading through far too many books/tutorials about libtool and > | friends now just so that the libraries end up under /usr/lib. > > Octave's Makefile.am files have lines like > > octlib_LTLIBRARIES = liboctave.la > octlib_LTLIBRARIES = liboctinterp.la > > so these files are installed in $(octlibdir) and the default > definition of octlibdir is set in configure.ac to be > > '$(libdir)/octave/$(version)' > > You are of course free to redefine this to be '$(libdir)' instead, and > I think that will cause the libraries to be installed into /usr/lib if > you set $(prefix) to be /usr. Yes, but I don't want to change $(octlibdir), because other software might use that for specific libraries. Also, I need to get a better understanding of libtool, autoconf and friends anyway. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637787: [Pkg-octave-devel] Bug#637787: Bug#637787: trivial fix
On Fri, Aug 19, 2011 at 09:51:36AM -0500, Jordi Gutiérrez Hermoso wrote: > On 19 August 2011 06:11, Soeren Sonnenburg wrote: > > Package: octave3.2 > > Version: 3.2.4-8 > > Severity: normal > > Tags: patch > > > > it is sufficient to remove the curl/types.h line - octave builds just > > fine then. > > This has already been done in Octave 3.4.2. I think the easiest fix is > to just update the package, which addresses a bunch of other bugs we > have here. http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2011-August/008079.html This upload had that fix. About the updating to Octave 3.4.2 - the problem is not the Octave packaging, I have that completed for some time. The problem is that dpkg-shlibdeps doesn't like the fact that Octave uses normal SONAMEs for its libraries now, but ships them in a private path (so dpkg-shlibdeps doesn't find them and aborts). So, I'm reading through far too many books/tutorials about libtool and friends now just so that the libraries end up under /usr/lib. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624960: [Pkg-octave-devel] Bug#624960: octave3.2: FTBFS: oct-alloc.h:33:28: error: expected ')' before 'item_sz'
On Mon, May 02, 2011 at 02:36:21PM +0200, Lucas Nussbaum wrote:
> Relevant part:
> > g++ -c -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc
> > -DHAVE_CONFIG_H -I/usr/include/freetype2 -Wall -W -Wshadow -Wold-style-cast
> > -Wformat -O2 -g -pthread oct-alloc.cc -o pic/oct-alloc.o
> > In file included from oct-alloc.cc:30:0:
> > oct-alloc.h:33:28: error: expected ')' before 'item_sz'
> > oct-alloc.h:40:9: error: expected ';' at end of member declaration
> > oct-alloc.h:40:23: error: expected ')' before 'size'
> > oct-alloc.h:43:23: error: 'size_t' has not been declared
> > oct-alloc.h:58:3: error: 'size_t' does not name a type
> > oct-alloc.cc:33:26: error: 'void* octave_allocator::alloc' is not a static
> > member of 'class octave_allocator'
> > oct-alloc.cc:33:26: error: 'size_t' was not declared in this scope
> > oct-alloc.cc:33:26: note: suggested alternative:
> > /usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:155:26: note:
> > 'std::size_t'
> > oct-alloc.cc:34:1: error: expected ',' or ';' before '{' token
> > make[3]: *** [pic/oct-alloc.o] Error 1
Sigh, I suspect GCC 4.6 at fault/work. Do you plan a rebuild with GCC
4.5, by chance?
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#621942: [Pkg-octave-devel] Bug#621942: Bug#621942: qtoctave: FTBFS: rmdir: failed to remove `obj-x86_64-linux-gnu': No such file or directory
On Sat, Apr 09, 2011 at 11:09:30PM -0500, Jordi Gutiérrez Hermoso wrote: > I'm going to try to convince upstream again to accept all versions of > Qt 4 at least after 4.4. If not, I guess we'll go with the patch to > use Qt 4.7 instead of 4.6 Sorry, no. If there's no technical reason for a bump in the required Qt version *and* patches to fix this are rejected, then QtOctave will be removed (said with maintainer hat on). I'm not going to have random build failures because of bumped Qt versions. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#618139: marked as done (octave3.2: FTBFS: Nonexistent build-dependency: 'libcurl4-dev')
On Sat, Mar 19, 2011 at 09:54:13PM +, Adam D. Barratt wrote: > On Sat, 2011-03-19 at 22:45 +0100, Thomas Weber wrote: > > On Sat, Mar 19, 2011 at 08:45:07PM +, Adam D. Barratt wrote: > > > It won't work on the buildds, however, whether pbuilder handles it or > > > not. > [...] > > 1) If I build the package in a clean chroot, it will work because apt > > will install one of the providers. > [...] > > > libcurl4-dev is a virtual package with multiple providers, and the > > > buildd software won't automatically pick between them, so the same > > > situation will recur. > > > > Given that both apt and pbuilder easily cope with the situation, this > > sounds like a missing feature in the buildd software. > > Which version of apt? 0.8.13 certainly doesn't appear to "easily cope" > - on a system with none of the providers installed: My bad. I could have sworn I only ever used apt-get build-dep octave3.2 in the chroot. But that doesn't even try to pull in libcurl*. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#618139: marked as done (octave3.2: FTBFS: Nonexistent build-dependency: 'libcurl4-dev')
On Sat, Mar 19, 2011 at 08:45:07PM +, Adam D. Barratt wrote: > reopen 618139 > thanks > > On Sat, 2011-03-19 at 20:39 +, Debian Bug Tracking System wrote: > [...] > > > > Checking for source dependency conflicts... > > > > E: Package 'libcurl4-dev' has no installation candidate > [...] > > > I've built the package in a clean pbuilder chroot with no problems. > > It won't work on the buildds, however, whether pbuilder handles it or > not. So, just to make sure I get this correctly, the following is my understanding of the situation: 1) If I build the package in a clean chroot, it will work because apt will install one of the providers. 2) If I build it using pbuilder, it will work because pbuilder knows how to handle the situation. 3) The buildd software (sbuild?) doesn't cope with the situation anymore (obviously, at one point in the past this issue wasn't triggered - libcurl4-dev was added in 2007). Now, is there a simple way for me to prevent such problems in the future? I find setting up pbuilder both simple and well-documented neither of which can be said for sbuild. > libcurl4-dev is a virtual package with multiple providers, and the > buildd software won't automatically pick between them, so the same > situation will recur. Given that both apt and pbuilder easily cope with the situation, this sounds like a missing feature in the buildd software. > You need to prefer one of the alternatives to provide a concrete > package to install (e.g. "libcurl4-gnutls-dev | libcurl4-dev"). It worked for ~4 years. Did something change in curl packaging? I don't see anything obvious in its changelog. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#618139: [Pkg-octave-devel] Bug#618139: octave3.2: FTBFS: Nonexistent build-dependency: 'libcurl4-dev'
On Sun, Mar 13, 2011 at 06:31:27PM +0100, Lucas Nussbaum wrote: > Source: octave3.2 > Version: 3.2.4-8 > Severity: serious > Tags: wheezy sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20110313 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. I'm taking a look at it at the weekend. My laptop is too weak to compile Octave. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607071: [Pkg-octave-devel] Bug#607071: octave-symbolic: Segfaults, doesn't work at all
Hi Julien, On Mon, Dec 27, 2010 at 12:08:58AM +0100, Julien Cristau wrote: > user release.debian@packages.debian.org > usertag 607071 squeeze-will-remove > kthxbye > > On Tue, Dec 14, 2010 at 07:55:58 -0600, Jordi Gutiérrez Hermoso wrote: > > > This report is mostly a reminder to myself to either fix the package, > > or to the release managers to remove this package from squeeze if I > > don't manage to fix it before then. > > > Tagging as candidate for removal, will do that in a few days if no fix > is in sight. we probably have a one-liner patch from upstream for this. The package was already hinted out of testing. Any chance of getting a fixed package into testing? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607071: [Pkg-octave-devel] Bug#607071: Bug#607071: octave-symbolic: Segfaults, doesn't work at all
On Tue, Dec 28, 2010 at 05:04:03AM +0800, Geoff Gole wrote: > fwiw, I can reproduce this. > > $ apt-get install octave-symbolic > ... Ehm, the part above would have been interesting, because > $ octave > GNU Octave, version 3.0.1 3.0.1 is only available in Lenny. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607071: [Pkg-octave-devel] Bug#607071: octave-symbolic: Segfaults, doesn't work at all
package octave-symbolic tags 607071 unreproducible severity 607071 important thanks On Mon, Dec 27, 2010 at 08:32:27AM -0600, Jordi Gutiérrez Hermoso wrote: > On 26 December 2010 17:08, Julien Cristau wrote: > > On Tue, Dec 14, 2010 at 07:55:58 -0600, Jordi Gutiérrez Hermoso wrote: > > > >> This report is mostly a reminder to myself to either fix the package, > >> or to the release managers to remove this package from squeeze if I > >> don't manage to fix it before then. > >> > > Tagging as candidate for removal, will do that in a few days if no fix > > is in sight. I'm downgrading this bug. I can't reproduce it neither in an amd64 chroot nor an i386 physical installation. Jordi, can you check your local installation? Maybe there's some other package interfering here. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607071: [Pkg-octave-devel] Bug#607071: Bug#607071: Bug#607071: octave-symbolic: Segfaults, doesn't work at all
On Wed, Dec 15, 2010 at 11:18:34PM -0600, Jordi Gutiérrez Hermoso wrote: > On 15 December 2010 16:17, Thomas Weber wrote: > > On Tue, Dec 14, 2010 at 07:55:58AM -0600, Jordi Gutiérrez Hermoso wrote: > >> Package: octave-symbolic > >> Version: 1.0.9-1+b1 > >> Severity: grave > >> > >> octave-symbolic is largely unusable. Calling any of its functions > >> other than "sym" results in C++ exceptions like this one: > >> > >> error: T& Array::checkelem (2, -1, 2): range error > >> > >> and eventually the package segfaults Octave. > > > > Did anything change in Ginac? The package was built in February and all > > tests passed. > > Are you sure? Yes: https://buildd.debian.org/pkg.cgi?pkg=octave-symbolic > (The mark_as_command warning is from another package I have installed, > but I keep forgetting which one.) So something fishy is happening, > "! test failed" yet "PASSES 2 out of 2 tests". Can you reproduce > this? Perhaps this was happening in February so the tests were failing > but being reported as passing? No, see the build logs available from above. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607071: [Pkg-octave-devel] Bug#607071: octave-symbolic: Segfaults, doesn't work at all
On Tue, Dec 14, 2010 at 07:55:58AM -0600, Jordi Gutiérrez Hermoso wrote: > Package: octave-symbolic > Version: 1.0.9-1+b1 > Severity: grave > > octave-symbolic is largely unusable. Calling any of its functions > other than "sym" results in C++ exceptions like this one: > > error: T& Array::checkelem (2, -1, 2): range error > > and eventually the package segfaults Octave. Did anything change in Ginac? The package was built in February and all tests passed. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#588024: [Pkg-octave-devel] Bug#588024: segfault during trigger processing
package octave3.2 severity 588024 normal thanks I'm downgrading the severity of this bug. I can't reproduce it and have not heard back after one week from the submitter. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#588024: [Pkg-octave-devel] Bug#588024: segfault during trigger processing
Hi Bas, On Sun, Jul 04, 2010 at 09:49:06AM +0200, Bas Zoetekouw wrote: > Package: octave3.2 > Version: 3.2.4-6 > Severity: serious > > When upgrading octave, the octave segfaults during trigger processing: > > Get: 278 http://ftp.de.debian.org sid/main octave-control 1.0.11-2 [447kB] > Get: 279 http://ftp.de.debian.org sid/main octave-signal 1.0.11-2 [209kB] > [...] > Selecting previously deselected package octave-control. > Unpacking octave-control (from .../octave-control_1.0.11-2_all.deb) ... > Preparing to replace octave-signal 1.0.11-1 (using > .../octave-signal_1.0.11-2_i386.deb) ... > Unpacking replacement octave-signal ... > [...] > Processing triggers for octave3.2 ... > Segmentation fault > dpkg: error processing octave3.2 (--unpack): > subprocess installed post-installation script returned error exit status 139 > > > Unfortunately, I wasn't able to reproduce this by uninstalling and > reinstalling octave-signal and octavbe-control. Possibly it only > occurs when upgrading? What other octave-* package do you have installed? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#582937: php5-xdebug: xdebug doesn't show local variables with PHP 5.3
Package: php5-xdebug Version: 2.0.5-1+b1 Severity: grave Hi, with PHP 5.3, xdebug doesn't show the value of local variables anymore. This bug is fixed upstream, but only in development releases. Unfortunately, without the values of such variables, xdebug is nearly useless for debugging. Upstream bug: http://bugs.xdebug.org/view.php?id=376 Corresponding forum discussion with screenshot: http://www.eclipse.org/forums/index.php?t=tree&th=158396&#page_top I don't know if packaging the development snapshot is a good solution; however, releasing Squeeze with the current xdebug package would render it useless for me. Thanks Thomas -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages php5-xdebug depends on: ii libapache2-mod-php5 [phpapi-2 5.3.2-1server-side, HTML-embedded scripti ii libc6 2.10.2-8 Embedded GNU C Library: Shared lib ii php5-cgi [phpapi-20090626+lfs 5.3.2-1server-side, HTML-embedded scripti ii php5-cli [phpapi-20090626+lfs 5.3.2-1command-line interpreter for the p ii ucf 3.0025 Update Configuration File: preserv php5-xdebug recommends no packages. php5-xdebug suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#582073: (no subject)
Something is wrong with the ./configure run. It replaces the content on magick/magick-config.h with 'garbage', only lines like /* Define if you have the bzip2 library */ #ifndef MAGICKCORE_^A #define MAGICKCORE_^A ^B #endif remain in there. This happens even when calling ./configure in the pristine upstream source. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572265: horde3: Upgrade to php 5.3 results in fatal error
On Wed, Apr 28, 2010 at 08:35:30AM +0200, nb wrote: > Hi, > > I have installed the php-log 1.12.0 package, but I still have the same > problem. Are you sure the new package is used? 1.12 hasn't been uploaded to Debian yet, so you must have installed it outside of dpkg, is that correct? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579463: lapack: Versioned build-depends on blas needed
Package: lapack Severity: serious Justification: FTBFS on mipsel Hi, 3.2.1-7 FTBFS on mipsel due to blas 1.2-4 beind used during the build. I guess a (>=1.2.-7) is needed in the build dependencies. I tried to get the wanna-build team to give the build back (thereby not forcing a rebuild on every other architecture), but they didn't want to do that. http://lists.debian.org/debian-wb-team/2010/04/msg00058.html Thanks Thomas -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572265: New upstream version of php-log might fix this
On Fri, Mar 19, 2010 at 10:27:15PM +0100, gregor herrmann wrote: > tag 572265 + patch > thanks > > On Mon, 15 Mar 2010 22:01:40 +0100, Thomas Weber wrote: > > > I didn't actually test it, but > > http://pear.php.net/package/Log/download/ > > indicates that the 1.12.0 version of Pear Log fixes this. > > Looking at the code [0] the relevant change seems to be in: I've packaged the new 1.12.0 release. However, I didn't test it at all and have no experience with PHP package. I used the 1.11.5 version available on mentors to start with. If someone with more experience wants to check/upload, both the .deb and the source files are at http://alioth.debian.org/~thomas-guest/debian/ Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573972: pyxplot: Depends on obsolete libmagickcore2-extra
On Mon, Mar 15, 2010 at 02:06:52PM +, Stuart Prescott wrote: > > Hi, > > Following the soname bump of libmagickcore, I now have #573972: > > > pyxplot explicitly depends on libmagickcore2-extra, which no longer exists > > after the recent imagemagick upload to unstable; it's been replaced by > > libmagickcore3-extra. > > > > Please check and update your build-dependency. > > This is a trivial thing for me to fix in the pyxplot packaging, but the fact > that pyxplot requires a sourceful upload when something it only ever calls at > the command line undergoes a soname bump probably points to something wrong > here. > > The only reason that pyxplot build-depends on libmagickcore2-extra is to get > svg to png conversion functionality in imagemagick. Since pyxplot doesn't > actually use any symbols itself from imagemagick at all (it just calls > convert!), it shouldn't need to worry about transitions in helper utilities > that it calls. > > Is there already a better way for me to write a depends line that brings this > functionality into convert? If not, should there be? I don't really want > pyxplot (and however many other package out there) to require sourceful > uploads every time you need a soname bump on imagemagick :( Would "Provides: > libmagickcore-extra" be a reasonable solution so that packages can depend on > that instead? Stupid question: wouldn't graphicsmagick (and graphicsmagick-imagemagick-compat) be sufficient for your use case? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572265: New upstream version of php-log might fix this
I didn't actually test it, but http://pear.php.net/package/Log/download/ indicates that the 1.12.0 version of Pear Log fixes this. However, php-log is orphaned. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574020: h5utils: Please switch to octave3.2
Package: h5utils Severity: serious Tags: patch Hi, I want to drop octave3.0 for Squeeze (hence the RC severity of this bug). Please switch to octave3.2. Patch attached. Thanks Thomas -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash diff --git a/debian/changelog b/debian/changelog index 75ba0fa..fce81cf 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +h5utils (1.12-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Switch to octave3.2-headers + + -- Thomas Weber Mon, 15 Mar 2010 18:11:50 + + h5utils (1.12-2) unstable; urgency=low * Changed build-dep in libhdf4-dev instead of libhdf4g-dev. diff --git a/debian/control b/debian/control index 294c917..e9d9521 100644 --- a/debian/control +++ b/debian/control @@ -4,7 +4,7 @@ Priority: optional Maintainer: Debian GIS Project Uploaders: Francesco Paolo Lovergine Build-Depends: debhelper (>= 7), libhdf5-serial-dev (>= 1.8.3), libz-dev, libpng-dev, hdf5-tools, - libhdf4-dev, libmatheval1-dev, octave3.0-headers, quilt + libhdf4-dev, libmatheval1-dev, octave3.2-headers, quilt Standards-Version: 3.8.2 Homepage: http://ab-initio.mit.edu/h5utils/ Vcs-Browser: http://svn.debian.org/viewsvn/pkg-grass/packages/h5utils/trunk/
Bug#570771: [Pkg-octave-devel] Bug#570771: Bug#570771: FTBFS on mips* due to ld bug
On Mon, Mar 01, 2010 at 09:24:25PM +0100, Thomas Weber wrote: > On Mon, Mar 01, 2010 at 09:38:18AM +0100, Marc Brockschmidt wrote: > > Thomas Weber writes: > > > On Sun, Feb 21, 2010 at 01:24:39PM +0100, Marc 'HE' Brockschmidt wrote: > > >> It looks like building without -g might work around the problem, so > > >> removing > > >> the -dbg packages for mips* might be an option for now. > > > This is only an option if you (or one of the mipsel porters) agree to > > > sponsor the first upload re-introducing the -dbg package. I'm only a DM. > > > > If noone else is willing to do it, I will upload a package that just > > adds the debug package in when needed. > > This wasn't meant seriously :) > > If no mips porter is willing to upload such a package, then we'll go > without it on mips for the time being. > > > Sorry, I have no octave clue at all, so I would like to avoid any > > bigger sponsoring steps. Anyway, I think dropping the debug package > > for mips* should be enough. > > > > Could you do this soon? Problem: Newer graphicsmagick (>=1.3.8) changed it's behaviour and now Octave crashes in it's test suite. Upstream discussion: http://www-old.cae.wisc.edu/pipermail/octave-maintainers/2010-February/015292.html Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#570771: [Pkg-octave-devel] Bug#570771: FTBFS on mips* due to ld bug
On Mon, Mar 01, 2010 at 09:38:18AM +0100, Marc Brockschmidt wrote: > Thomas Weber writes: > > On Sun, Feb 21, 2010 at 01:24:39PM +0100, Marc 'HE' Brockschmidt wrote: > >> It looks like building without -g might work around the problem, so > >> removing > >> the -dbg packages for mips* might be an option for now. > > This is only an option if you (or one of the mipsel porters) agree to > > sponsor the first upload re-introducing the -dbg package. I'm only a DM. > > If noone else is willing to do it, I will upload a package that just > adds the debug package in when needed. This wasn't meant seriously :) If no mips porter is willing to upload such a package, then we'll go without it on mips for the time being. > Sorry, I have no octave clue at all, so I would like to avoid any > bigger sponsoring steps. Anyway, I think dropping the debug package > for mips* should be enough. > > Could you do this soon? Okay, will do. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571345: [Pkg-octave-devel] Bug#571345: octave-ga: FTBFS: Unsatisfiable build-dependency: octave-communications: Depends: libhdf5-serial-1.8.3 but it is not installable
Hi Lucas, On Thu, Feb 25, 2010 at 11:50:13AM +0100, Lucas Nussbaum wrote: > Source: octave-ga > Version: 0.9.7-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-2010-02-24 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. Yepp, hdf5 transition. BinNMUs have been requested. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571320: [Pkg-octave-devel] Bug#571320: octave3.2: package configuration fails because /usr/share/octave/packages/3.2 is missing
On Thu, Feb 25, 2010 at 10:32:53AM +0100, Michael Weitzel wrote: > Package: octave3.2 > Version: 3.2.3-1 > Severity: grave > Tags: patch > Justification: renders package unusable > > > Dear Maintainers, > > During installation the Octave 3.2 package does not create the directory > /usr/share/octave/packages/3.2. This results in the following problem > in package configuration: The directory is part of octave3.2-common, on which octave3.2 depends. I just tried this in a clean chroot and it works without problems. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#570690: [Pkg-octave-devel] Bug#570690: dynare: FTBFS: Testsuite times out
On Sat, Feb 20, 2010 at 07:35:38PM +0100, Kurt Roeckx wrote: > Source: dynare > Version: 4.1.0-1 > Severity: serious > > Hi, > > There was an error while trying to autobuild your package: Sébastien, any chance of disabling the longer running tests? Or having them print out something every few minutes? I would prefer option 1 (bonus points of you can speed up the test itself :) ) Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#570771: [Pkg-octave-devel] Bug#570771: FTBFS on mips* due to ld bug
On Sun, Feb 21, 2010 at 01:24:39PM +0100, Marc 'HE' Brockschmidt wrote: > Package: octave3.2 > Version: 3.2.4-2 > Severity: serious > > Heya, > > It looks like octave3.2 is hitting a ld bug: > | g++ -shared -Wl,-soname -Wl,liboctinterp.so -o liboctinterp.so [...] > | /usr/bin/ld: non-dynamic relocations refer to dynamic symbol > ceil(std::complex const&) > | /usr/bin/ld: failed to set dynamic section sizes: Bad value > | collect2: ld returned 1 exit status > > [From > https://buildd.debian.org/fetch.cgi?pkg=octave3.2;ver=3.2.4-2;arch=mipsel;stamp=1266531285] > > This seems to be due to a binutils bug in ld, filed here: > http://sources.redhat.com/bugzilla/show_bug.cgi?id=10144 > > It looks like building without -g might work around the problem, so removing > the -dbg packages for mips* might be an option for now. This is only an option if you (or one of the mipsel porters) agree to sponsor the first upload re-introducing the -dbg package. I'm only a DM. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567962: [Pkg-octave-devel] Bug#567962: Bug#567962: needs to be rebuilt against libhdf5-1.8.4
On Mon, Feb 08, 2010 at 04:03:20PM +0100, Bas Zoetekouw wrote: > Hi John! > > You wrote: > > > No, it hasn't changed. All .oct files depend on liboctinterp, which > > depends on liboctave and a number of other libraries, and liboctave > > depends on libcruft and a number of other libraries. So ultimately, a > > .oct file is linked with everything taht Octave is linked with. I > > don't see that it matters whether this is done directly or > > indirectly, and it seems to be that some systems cannot do the linking > > indirectly, so the dependencies are all listed when the .oct file is > > linked. > > Which platforms in Debian don't support indirect linking? Ehm, when John (he's upstream) talks about different systems, this includes Mac, Windows, BSD, ... Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567962: [Pkg-octave-devel] Bug#567962: Bug#567962: needs to be rebuilt against libhdf5-1.8.4
On Tue, Feb 02, 2010 at 01:06:24AM -0500, John W. Eaton wrote: > On 1-Feb-2010, Thomas Weber wrote: > > | On Mon, Feb 01, 2010 at 03:59:25PM +0100, Bas Zoetekouw wrote: > | > Hi! > | > > | > > octave-specfun is currently uninstallable in sid, as it depends on > | > > libhdf5-1.8.3, while octave3.2 depends on libhdf5-1.8.4. > | > > Please rebuild octave-specfun against libhdf5-1.8.4. > | > > | > Actually, on further inspection, it seems that there is no need at all > | > to link against libhdf (and zlib, and libfftw3, and libcurses5, etc). > | > The package itself doesn't use these symbols, so it shouldn't be linked > | > against them. > | > This seems to be an issue for all octave packages, BTW. > | > | Yes. mkoctfile (used to build these files) links them against all > | libraries that Octave itself uses. I think this has changed in > | upstream's development version, though. > > No, it hasn't changed. All .oct files depend on liboctinterp, which > depends on liboctave and a number of other libraries, and liboctave > depends on libcruft and a number of other libraries. So ultimately, a > .oct file is linked with everything taht Octave is linked with. I > don't see that it matters whether this is done directly or > indirectly, and it seems to be that some systems cannot do the linking > indirectly, so the dependencies are all listed when the .oct file is > linked. > > If you have a better solution that is platform neutral and fits > within the automake+libtool framework, then please start a thread on > the maintain...@octave.org list. I don't have a better solution, but I will need to learn some more about shared libraries anyway for the next major Octave version. So, I'll see what I can come up with. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567962: [Pkg-octave-devel] Bug#567962: needs to be rebuilt against libhdf5-1.8.4
On Mon, Feb 01, 2010 at 03:59:25PM +0100, Bas Zoetekouw wrote: > Hi! > > > octave-specfun is currently uninstallable in sid, as it depends on > > libhdf5-1.8.3, while octave3.2 depends on libhdf5-1.8.4. > > Please rebuild octave-specfun against libhdf5-1.8.4. > > Actually, on further inspection, it seems that there is no need at all > to link against libhdf (and zlib, and libfftw3, and libcurses5, etc). > The package itself doesn't use these symbols, so it shouldn't be linked > against them. > This seems to be an issue for all octave packages, BTW. Yes. mkoctfile (used to build these files) links them against all libraries that Octave itself uses. I think this has changed in upstream's development version, though. In other words, I won't change that behaviour in Debian. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562321: [Pkg-octave-devel] Bug#562321: Bug#562321: Bug#562321: dynare: FTBFS: cp: cannot stat `doc/manual.pdf': No such file or directory
On Thu, Dec 31, 2009 at 12:31:35AM +0100, Sébastien Villemot wrote: > > [Lucas, do you want to be kept in CC?] > > > > Alright, this is indeed a change in TexLive, and an intended one. See > > http://lists.debian.org/debian-tex-maint/2009/12/msg00630.html > > http://lists.debian.org/debian-tex-maint/2009/12/msg00661.html > > Thanks for having asked the TexLive maintainers. > > By the first half of January I will package the new upstream version of > Dynare. I will therefore include a patch for this TexLive issue (using > double anti-slashes). I'm not happy with that solution. IMO, it's up to dblatex to treat correctly. Otherwise, a lot of documents must be changed. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562321: [Pkg-octave-devel] Bug#562321: Bug#562321: dynare: FTBFS: cp: cannot stat `doc/manual.pdf': No such file or directory
On Sun, Dec 27, 2009 at 12:43:04AM +0100, Thomas Weber wrote: > On Thu, Dec 24, 2009 at 11:31:19AM +0100, Lucas Nussbaum wrote: > > Source: dynare > > Version: 4.0.4-6 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: qa-ftbfs-20091213 qa-ftbfs > > Justification: FTBFS on amd64 > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > [] > > > cp: cannot stat `doc/manual.pdf': No such file or directory > > > dh_installdocs: cp -a doc/manual.pdf > > > debian/dynare-doc/usr/share/doc/dynare-doc returned exit code 1 > > > make: *** [binary-indep] Error 2 > > This is a regression in pdflatex. Using the version in Lenny (on the > temporary file manual.tex) works fine. > > I'll follow-up with the TeX maintainers. [Lucas, do you want to be kept in CC?] Alright, this is indeed a change in TexLive, and an intended one. See http://lists.debian.org/debian-tex-maint/2009/12/msg00630.html http://lists.debian.org/debian-tex-maint/2009/12/msg00661.html Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562321: [Pkg-octave-devel] Bug#562321: dynare: FTBFS: cp: cannot stat `doc/manual.pdf': No such file or directory
On Thu, Dec 24, 2009 at 11:31:19AM +0100, Lucas Nussbaum wrote: > Source: dynare > Version: 4.0.4-6 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091213 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > [] > > cp: cannot stat `doc/manual.pdf': No such file or directory > > dh_installdocs: cp -a doc/manual.pdf > > debian/dynare-doc/usr/share/doc/dynare-doc returned exit code 1 > > make: *** [binary-indep] Error 2 This is a regression in pdflatex. Using the version in Lenny (on the temporary file manual.tex) works fine. I'll follow-up with the TeX maintainers. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548572: [Pkg-octave-devel] Bug#548572: Bug#548572: dynare: FTBFS: error: No such file or directory
On Sun, Sep 27, 2009 at 05:25:42PM +0200, Thomas Weber wrote: > On Sun, Sep 27, 2009 at 12:40:48PM +0200, Kurt Roeckx wrote: > > Source: dynare > > Version: 4.0.4-4 > > Severity: serious > > > > Hi, > > > > There was an error while trying to autobuild your package: > > > > > Start Time: 20090927-1023 > > > > [...] > > > > > Build-Depends: debhelper (>= 7), octave3.2-headers (>= 3.2.2), flex, > > > bison, texlive, texlive-publishers, xsltproc, dblatex, latex-beamer, > > > docbook-xsl, quilt, po-debconf, gnuplot-nox > > > > [...] > > > > > Toolchain package versions: libc6-dev_2.9-26 linux-libc-dev_2.6.30-6 > > > g++-4.3_4.3.4-3 gcc-4.3_4.3.4-3 binutils_2.19.91.20090910-1 > > > libstdc++6_4.4.1-4 libstdc++6-4.3-dev_4.3.4-3 > > > > > > > [...] > > > > > g++ -c -fPIC -I/usr/include/octave-3.2.2 > > > -I/usr/include/octave-3.2.2/octave -mieee-fp -I/usr/include/freetype2 -g > > > -O2 -I. -Isimulate -I../../preprocessor/include -DNO_BLAS_H -DNO_LAPACK_H > > > -DOCTAVE simulate/Mem_Mngr.cc -o simulate/Mem_Mngr.o > > > g++ -c -fPIC -I/usr/include/octave-3.2.2 > > > -I/usr/include/octave-3.2.2/octave -mieee-fp -I/usr/include/freetype2 -g > > > -O2 -I. -Isimulate -I../../preprocessor/include -DNO_BLAS_H -DNO_LAPACK_H > > > -DOCTAVE simulate/SparseMatrix.cc -o simulate/SparseMatrix.o > > > g++ -shared -Wl,-Bsymbolic -o ../octave/simulate.mex simulate/simulate.o > > > simulate/Interpreter.o simulate/Mem_Mngr.o simulate/SparseMatrix.o > > > -L/usr/lib/octave-3.2.2 -loctinterp -loctave -lcruft -llapackgf-3 > > > -lblas-3gf -lfftw3 -lfftw3f -lreadline -lncurses -ldl -lblas-3gf -lhdf5 > > > -lz -lm -lgfortranbegin -lgfortran > > > error: No such file or directory > > > terminate called after throwing an instance of > > > 'octave_execution_exception' > > > panic: Aborted -- stopping myself... > > > attempting to save variables to `octave-core'... > > > save to `octave-core' complete > > > Aborted > > > make: *** [build-stamp] Error 134 > > > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > > > A full build log can be found at: > > http://buildd.debian.org/build.php?arch=i386&pkg=dynare&ver=4.0.4-4 > > I've just built dynare in a clean i386 pbuilder chroot without problems. > However, as the build fails also for other architectures, I'm at a loss > here. > > Sébastien, do you have an idea? > > Thomas Okay, it seems this problem is not totally unknown: http://www.nabble.com/exit-error-td25199898.html I'll try to look into it tomorrow. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548572: [Pkg-octave-devel] Bug#548572: dynare: FTBFS: error: No such file or directory
On Sun, Sep 27, 2009 at 12:40:48PM +0200, Kurt Roeckx wrote: > Source: dynare > Version: 4.0.4-4 > Severity: serious > > Hi, > > There was an error while trying to autobuild your package: > > > Start Time: 20090927-1023 > > [...] > > > Build-Depends: debhelper (>= 7), octave3.2-headers (>= 3.2.2), flex, bison, > > texlive, texlive-publishers, xsltproc, dblatex, latex-beamer, docbook-xsl, > > quilt, po-debconf, gnuplot-nox > > [...] > > > Toolchain package versions: libc6-dev_2.9-26 linux-libc-dev_2.6.30-6 > > g++-4.3_4.3.4-3 gcc-4.3_4.3.4-3 binutils_2.19.91.20090910-1 > > libstdc++6_4.4.1-4 libstdc++6-4.3-dev_4.3.4-3 > > > > [...] > > > g++ -c -fPIC -I/usr/include/octave-3.2.2 -I/usr/include/octave-3.2.2/octave > > -mieee-fp -I/usr/include/freetype2 -g -O2 -I. -Isimulate > > -I../../preprocessor/include -DNO_BLAS_H -DNO_LAPACK_H -DOCTAVE > > simulate/Mem_Mngr.cc -o simulate/Mem_Mngr.o > > g++ -c -fPIC -I/usr/include/octave-3.2.2 -I/usr/include/octave-3.2.2/octave > > -mieee-fp -I/usr/include/freetype2 -g -O2 -I. -Isimulate > > -I../../preprocessor/include -DNO_BLAS_H -DNO_LAPACK_H -DOCTAVE > > simulate/SparseMatrix.cc -o simulate/SparseMatrix.o > > g++ -shared -Wl,-Bsymbolic -o ../octave/simulate.mex simulate/simulate.o > > simulate/Interpreter.o simulate/Mem_Mngr.o simulate/SparseMatrix.o > > -L/usr/lib/octave-3.2.2 -loctinterp -loctave -lcruft -llapackgf-3 > > -lblas-3gf -lfftw3 -lfftw3f -lreadline -lncurses -ldl -lblas-3gf -lhdf5 -lz > > -lm -lgfortranbegin -lgfortran > > error: No such file or directory > > terminate called after throwing an instance of 'octave_execution_exception' > > panic: Aborted -- stopping myself... > > attempting to save variables to `octave-core'... > > save to `octave-core' complete > > Aborted > > make: *** [build-stamp] Error 134 > > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > A full build log can be found at: > http://buildd.debian.org/build.php?arch=i386&pkg=dynare&ver=4.0.4-4 I've just built dynare in a clean i386 pbuilder chroot without problems. However, as the build fails also for other architectures, I'm at a loss here. Sébastien, do you have an idea? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#541444: [Pkg-octave-devel] Bug#541444: octave3.2-headers: can't be installed, two strong dependency on gcc/g++/gfortran
On Wed, Aug 19, 2009 at 03:24:47PM +0200, Aurelien Jarno wrote: > Thomas Weber a écrit : > > Hi Aurelien, > > > > On Fri, Aug 14, 2009 at 11:03:27AM +0200, Aurelien Jarno wrote: > >> Package: octave3.2-headers > >> Version: 3.2.0-2 > >> Severity: grave > >> Justification: renders package unusable > >> > >> # apt-get install octave3.2-headers > >> Reading package lists... Done > >> Building dependency tree > >> Reading state information... Done > >> Some packages could not be installed. This may mean that you have > >> requested an impossible situation or if you are using the unstable > >> distribution that some required packages have not yet been created > >> or been moved out of Incoming. > >> The following information may help to resolve the situation: > >> > >> The following packages have unmet dependencies: > >> octave3.2-headers: Depends: gcc-4.3 (< 4.3.4) but 4.3.4-1 is to be > >> installed > >> Depends: g++-4.3 (< 4.3.4) but 4.3.4-1 is to be > >> installed > >> Depends: gfortran-4.3 (< 4.3.4) but 4.3.4-1 is to be > >> installed > > > > > > hmm, maybe I can abuse your knowledge with compilers for this one :) > > > > The reason for tying the compiler versions so strict is that Octave adds > > the FLIBS (Fortran) found at configure time into one of its scripts for > > later use (building plugins, either in Debian or on the enduser's > > machine). > > > > FLIBS looks like this: > > -L/usr/lib/gcc/x86_64-linux-gnu/4.3.2 > > -L/usr/lib/gcc/x86_64-linux-gnu/4.3.2/../../../../lib -L/lib/../lib > > -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.3.2/../../.. -lhdf5 > > -lz -lgfortranbegin -lgfortran -lm > > > > Do you know if it's possible to get rid of the version specific compiler > > paths here? The macro is the default AC_F77_LIBRARY_LDFLAGS. > > > > On debian (at least), you can get rid of the subminor version (ie using > 4.3 instead of 4.3.2), as the gcc packages are providing the symlinks > for that. It should probably be possible to use a regular expression to > remove the subminor version from this path. Both on Ubuntu and on a Debian system, these links were found to be not there (no, I don't know why). https://bugs.launchpad.net/ubuntu/+source/octave3.0/+bug/348472 Anyway, I'll try to get rid of these paths completely. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#541444: [Pkg-octave-devel] Bug#541444: Recompiling from sources fixes problem
On Tue, Aug 18, 2009 at 05:32:28PM +0200, br...@ira.uka.de wrote: > Hi, > recompiling the package (apt-get source octave3.2 etc.) fixes the problem. That's a work-around, not a fix (well, the original code we introduced is already a work-around). I'm working on a better solution, but I need to ask for advice, so that I don't break things. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#541444: [Pkg-octave-devel] Bug#541444: octave3.2-headers: can't be installed, two strong dependency on gcc/g++/gfortran
Hi Aurelien, On Fri, Aug 14, 2009 at 11:03:27AM +0200, Aurelien Jarno wrote: > Package: octave3.2-headers > Version: 3.2.0-2 > Severity: grave > Justification: renders package unusable > > # apt-get install octave3.2-headers > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > octave3.2-headers: Depends: gcc-4.3 (< 4.3.4) but 4.3.4-1 is to be installed > Depends: g++-4.3 (< 4.3.4) but 4.3.4-1 is to be installed > Depends: gfortran-4.3 (< 4.3.4) but 4.3.4-1 is to be > installed hmm, maybe I can abuse your knowledge with compilers for this one :) The reason for tying the compiler versions so strict is that Octave adds the FLIBS (Fortran) found at configure time into one of its scripts for later use (building plugins, either in Debian or on the enduser's machine). FLIBS looks like this: -L/usr/lib/gcc/x86_64-linux-gnu/4.3.2 -L/usr/lib/gcc/x86_64-linux-gnu/4.3.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.3.2/../../.. -lhdf5 -lz -lgfortranbegin -lgfortran -lm Do you know if it's possible to get rid of the version specific compiler paths here? The macro is the default AC_F77_LIBRARY_LDFLAGS. Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#536503: [Pkg-octave-devel] Bug#536503: octave3.2: Dependency on suitesparse failed to stop upgrade...
On Fri, Jul 10, 2009 at 11:13:23AM -0400, Jason Riedy wrote: > Package: octave3.2 > Version: 3.2.0-2 > Severity: grave > Justification: renders package unusable > > > > octave: error while loading shared libraries: libumfpack.so.3.2.0: cannot > > open shared object file: No such file or directory I can't reproduce this, neither in a 32 nor a 64 bit chroot. > There's a dependency missing a version somewhere... Well, octave3.2 has libumfpack5.4.0 (>= 1:3.4.0) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524745: [Pkg-octave-devel] Bug#524745: Bug#524745: Postinst seems to run forever on mipsel
On Tue, Apr 28, 2009 at 06:31:32PM +0200, Martin Michlmayr wrote: > Just for the record, I see the same problem on an amd64 system (Intel > EM64T chip). Is this a normal installation or as part of a build process? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525113: [Pkg-octave-devel] Bug#525113: Bug#525113: Inconsistant complex matrix multiplication
On Thu, Apr 23, 2009 at 01:28:36PM +0200, Laurent Mazet wrote: > Hi Thomas, > > you was right, my problem is inthe atlas library: Thanks for the follow-up. > > $ LD_LIBRARY_PATH=/usr/lib /usr/bin/octave -q --eval '[1 2; 3 4] * [1; 1i]' > ans = >1 + 2i >3 + 4i > > $ lmt-linux ~ $ /usr/bin/octave -q --eval '[1 2; 3 4] * [1; 1i]' > ans = >1. + 0.i >3. + 0.i > > $ ldd /usr/bin/octave | grep -i lapack > liblapack.so.3gf => /usr/lib/sse2/atlas/liblapack.so.3gf (0xb653f000) > $ dpkg -S /usr/lib/sse2/atlas/liblapack.so.3gf > libatlas3gf-sse2: /usr/lib/sse2/atlas/liblapack.so.3gf > $ dpkg -l libatlas3gf-sse2 > ... > +++-==-==- > ii libatlas3gf-ss 3.6.0-24 Automatically Tuned Linear Algebra Software, > > Does I need to make a follow-up to the atlas package bug-report system? No, we will handle the reassignment. I want to test some things myself before assigning this to ATLAS. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525113: [Pkg-octave-devel] Bug#525113: Bug#525113: Inconsistant complex matrix multiplication
On Wed, Apr 22, 2009 at 11:04:14PM +0200, Thomas Weber wrote: > On Wed, Apr 22, 2009 at 12:01:19PM +0200, Laurent Mazet wrote: > > Package: octave3.0 > > Version: 1:3.0.1-7 > > Arch: i386 > > Severity: grave > > > > Hi, > > > > I've just realized that I can multiply a real 2x2 matrix by a complex > > vector. > > Uh, yes. Why shouldn't this work? Or in other words, how do you > distinguish the real matrix from a complex matrix with its complex > coefficients being zero > > [ 1, 2; 3,4] is the same as [1+0i, 2+0i; 3+0i, 4+0i], isn't it? Sorry, I just realized that the problem was the result, not the act of multiplication. Anyway, which BLAS/ATLAS libraries are installed on your system? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525113: [Pkg-octave-devel] Bug#525113: Bug#525113: Bug#525113: Inconsistant complex matrix multiplication
On Thu, Apr 23, 2009 at 01:35:01AM +0200, Rafael Laboissiere wrote: > * Thomas Weber [2009-04-22 23:04]: > > > On Wed, Apr 22, 2009 at 12:01:19PM +0200, Laurent Mazet wrote: > > > Package: octave3.0 > > > Version: 1:3.0.1-7 > > > Arch: i386 > > > Severity: grave > > > > > > Hi, > > > > > > I've just realized that I can multiply a real 2x2 matrix by a complex > > > vector. > > > > Uh, yes. Why shouldn't this work? Or in other words, how do you > > distinguish the real matrix from a complex matrix with its complex > > coefficients being zero > > > > [ 1, 2; 3,4] is the same as [1+0i, 2+0i; 3+0i, 4+0i], isn't it? > > I think Laurent meant "I've just realized that I CANNOT multiply [...]" Ah, sorry. I only briefly glanzed over the actual number. On my system, the results were right, though. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525113: [Pkg-octave-devel] Bug#525113: Inconsistant complex matrix multiplication
On Wed, Apr 22, 2009 at 12:01:19PM +0200, Laurent Mazet wrote: > Package: octave3.0 > Version: 1:3.0.1-7 > Arch: i386 > Severity: grave > > Hi, > > I've just realized that I can multiply a real 2x2 matrix by a complex vector. Uh, yes. Why shouldn't this work? Or in other words, how do you distinguish the real matrix from a complex matrix with its complex coefficients being zero [ 1, 2; 3,4] is the same as [1+0i, 2+0i; 3+0i, 4+0i], isn't it? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524745: [Pkg-octave-devel] Bug#524745: Postinst seems to run forever on mipsel
On Sun, Apr 19, 2009 at 05:47:11PM +0200, Luk Claes wrote: > Package: octave3.0 > Version: 1:3.0.5-2 > Severity: grave > > Hi > > The postinst of octave3.0 seems to hang on at least the mipsel buildds (for > unstable) [1]. > > This issue blocks the buildds from building any other package till the > octave3.0 process (mentioned in the build log) is killed manually. This has > already caused delays for security updates and transitions... Installation of octave3.0 in a mipsel (qemu) environment works without a problem. Is there something specific about the mipsel buildds? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523042: [Pkg-octave-devel] Bug#523042: Bug#523042: octave3.0: loading a datafile skips every second line
On Wed, Apr 08, 2009 at 09:19:19PM -0500, John W. Eaton wrote: > On 9-Apr-2009, Drew Parsons wrote: > > | Hi Rafael, thanks for the forthcoming fix to the problem. > | > | About the severity, I appreciate you need to get the new version across > | to testing but I don't think I could justify it with this bug. > > I agree that we should limit the spread of 3.0.4 as much as possible. > 3.0.5 is now available (there is just one patch applied to 3.0.4 to > fix this bug) so it would seem to me that it is better to generate the > 3.0.5 package and upload that instead, and do whatever we can to keep > 3.0.4 from being used by anyone. I'm building 3.0.5 right now. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520220: [Pkg-octave-devel] Bug#520220: octave3.0: This release candidate snapshot should not enter testing
On Wed, Mar 18, 2009 at 09:30:59AM +0100, Rafael Laboissiere wrote: > Package: octave3.0 > Version: 1:3.0.4~rc5-2 > Severity: serious > > This version of the octave3.0 package is based on a release candidate > snapshot for the upcoming 3.0.4 version. The upstream authors have told > us [1] that release candidates should not be distributed as Debian packages. > > Let us keep this version in unstable for now. Any plan how we should continue with this? We can't let any binary octave-forge package into testing like that. The current octave3.0 packages in unstable and testing are ABI-incompatible. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516942: [Pkg-octave-devel] Bug#516942: octave-symbolic: typing symbols in octave doesn't work
package octave-symbolic severity 516942 normal tags 516942 moreinfo thanks Hi, On Tue, Feb 24, 2009 at 12:20:23PM +0100, Oz N wrote: > Package: octave-symbolic > Version: 1.0.7-1 > Severity: grave > Justification: renders package unusable > > Hi, I have installed octave symbolic from 'experimental' on a clean 'squeeze' > installation. You have a mixture of testing and experimental (your Octave package is from experimental as well). > Typing symbols - octave complains about 'undefined symbol. > I believe these is still the same bug as 512075 which was closed. > I installed the package 'octave-headers' and 'libginac-dev' and used the > command 'pkg install symbolic-1.0.7.tar.gz' inside octave on the source > file I downloaded from octave forge to bypass this problem. I just tested this in a pure experimental chroot, where the package works. I'm thus downgrading the severity. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513576: [Pkg-octave-devel] Bug#513576: octave-symbolic does not uninstall
package octave3.0 tags 513576 confirmed tags 513576 upstream forwarded 513576 http://www-old.cae.wisc.edu/pipermail/octave-maintainers/2009-February/010599.html thanks On Sun, Feb 01, 2009 at 04:09:06PM +0100, Samuel Thibault wrote: > I guess octave3 could just provide the > > /usr/share/octave/packages > > directory itself, so that that command never fails. I agree, but want upstream's opinion first (mainly to avoid having one way out and upstream choosing a different one). Thanks Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512075: [Pkg-octave-devel] Bug#512075: Bug#512075: #512075 octave-symbolic: Undefined symbol
On Sat, Jan 17, 2009 at 04:14:50PM +0100, Thomas Weber wrote: > Attached the diff between upstream's 1.0.6 and 1.0.7. I'll ask the > release-team about the preferred solution (either patching or uploading > the new upstream version). Okay, we are clear from debian-release to upload 1.0.7 to unstable. I think we should revert the change to debhelper 7, though. What's the best way forward from here? Should I take the 1.0.7-1 package from experimental, revert these packaging changes and upload it as 1.0.7-2 to unstable? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512075: [Pkg-octave-devel] Bug#512075: #512075 octave-symbolic: Undefined symbol
Attached the diff between upstream's 1.0.6 and 1.0.7. I'll ask the release-team about the preferred solution (either patching or uploading the new upstream version). Thomas 1.0.6-1.0.7.diff.bz2 Description: Binary data
Bug#512075: [Pkg-octave-devel] Bug#512075: #512075 octave-symbolic: Undefined symbol
package: octave-symbolic tag 512075 confirmed fixed 512075 1.0.7-1 thanks On Sat, Jan 17, 2009 at 02:20:47AM +, Steve Cotton wrote: > 1. octave-symbolic is missing a dependency on libginac1.4 > > 2. Even with libginac1.4 installed, Octave doesn't find the > library without the help of > export LD_PRELOAD=/usr/lib/libginac-1.4.so.0 Thanks for the report. The build script in the 1.0.6 package didn't link the .oct file against the ginac library. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#502762: mailcrypt: piuparts test fails: emacs-install error
On Wed, Oct 22, 2008 at 02:15:40PM +0200, Davide G. M. Salvetti wrote: > >>>>> TW == Thomas Weber [2008-10-21] > > TW> Package is dead upstream, maintainer seems MIA. > > Maintainer is here and reads what you write. Sorry then, I thought your latest upload was about a year ago. BTW, thanks for maintaing auctex. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502762: mailcrypt: piuparts test fails: emacs-install error
This bug is triggered by a normal installation with emacs22. It works with emacs21 however. Package is dead upstream, maintainer seems MIA. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499918: [Pkg-octave-devel] Bug#499918: Bug#499918: Bug#499918: octave-vrml: "freewrl" is not packaged in Debian
Am Mittwoch, den 24.09.2008, 09:15 +0200 schrieb Thomas Weber: > Am Mittwoch, den 24.09.2008, 08:38 +0200 schrieb Thomas Weber: > > Am Dienstag, den 23.09.2008, 22:30 +0200 schrieb Thomas Weber: > > > On Tue, Sep 23, 2008 at 06:30:37PM +0200, [EMAIL PROTECTED] wrote: > > > > Package: octave-vrml > > > > Version: 1.0.6-2 > > > > Severity: serious > > > > Justification: Policy 3.5 > > > > > > > > When calling a vrml function from octave the error > > > > sh: freewrl: command not found > > > > cmd = freewrl/tmp/octave_vrml_output.wrl > > > > vrml_browse : Can't start browser 'freewrl'. Is it installed? > > > > occurs. I could not find a package in Debian which contains freewrl. > > > > > > > > Possible solutions: > > > > - Modify this error message, so it contains a link, where to download > > > > freewrl > > > > & update Package description. > > > > - A not so nice, but working replacement for freewrl is whitedune > > > > I've overlooked this one; that might be an option. > > I've asked upstream if whitedune is a suitable replacement for freewrl. > Let's see what they think. As octave-vrml is unusable in the current state, I'll upload a version with freewrl replaced by whitedune over the weekend. As far as I can tell, whitedune works at least somewhat. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499918: [Pkg-octave-devel] Bug#499918: Bug#499918: Bug#499918: octave-vrml: "freewrl" is not packaged in Debian
Am Mittwoch, den 24.09.2008, 08:38 +0200 schrieb Thomas Weber: > Am Dienstag, den 23.09.2008, 22:30 +0200 schrieb Thomas Weber: > > On Tue, Sep 23, 2008 at 06:30:37PM +0200, [EMAIL PROTECTED] wrote: > > > Package: octave-vrml > > > Version: 1.0.6-2 > > > Severity: serious > > > Justification: Policy 3.5 > > > > > > When calling a vrml function from octave the error > > > sh: freewrl: command not found > > > cmd = freewrl/tmp/octave_vrml_output.wrl > > > vrml_browse : Can't start browser 'freewrl'. Is it installed? > > > occurs. I could not find a package in Debian which contains freewrl. > > > > > > Possible solutions: > > > - Modify this error message, so it contains a link, where to download > > > freewrl > > > & update Package description. > > > - A not so nice, but working replacement for freewrl is whitedune > > I've overlooked this one; that might be an option. I've asked upstream if whitedune is a suitable replacement for freewrl. Let's see what they think. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499918: [Pkg-octave-devel] Bug#499918: Bug#499918: octave-vrml: "freewrl" is not packaged in Debian
Am Dienstag, den 23.09.2008, 22:30 +0200 schrieb Thomas Weber: > On Tue, Sep 23, 2008 at 06:30:37PM +0200, [EMAIL PROTECTED] wrote: > > Package: octave-vrml > > Version: 1.0.6-2 > > Severity: serious > > Justification: Policy 3.5 > > > > When calling a vrml function from octave the error > > sh: freewrl: command not found > > cmd = freewrl/tmp/octave_vrml_output.wrl > > vrml_browse : Can't start browser 'freewrl'. Is it installed? > > occurs. I could not find a package in Debian which contains freewrl. > > > > Possible solutions: > > - Modify this error message, so it contains a link, where to download > > freewrl > > & update Package description. > > - A not so nice, but working replacement for freewrl is whitedune I've overlooked this one; that might be an option. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499918: [Pkg-octave-devel] Bug#499918: octave-vrml: "freewrl" is not packaged in Debian
On Tue, Sep 23, 2008 at 06:30:37PM +0200, [EMAIL PROTECTED] wrote: > Package: octave-vrml > Version: 1.0.6-2 > Severity: serious > Justification: Policy 3.5 > > When calling a vrml function from octave the error > sh: freewrl: command not found > cmd = freewrl/tmp/octave_vrml_output.wrl > vrml_browse : Can't start browser 'freewrl'. Is it installed? > occurs. I could not find a package in Debian which contains freewrl. > > Possible solutions: > - Modify this error message, so it contains a link, where to download > freewrl > & update Package description. > - A not so nice, but working replacement for freewrl is whitedune > - Package freewrl in Debian - Remove octave-vrml from Debian. I have zero motivation maintaining freewrl and looking at #279757, I have quite some company in that. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480431: Please unblock octaviz 0.4.7-2
Hi,
can you please unblock octaviz 0.4.7-2 (just uploaded). It fixes #480431
(crash on amd64, but is working on x86 probably only by accident).
Changelog:
octaviz (0.4.7-2) unstable; urgency=low
[ Ólafur Jens Sigurðsson ]
* debian/control: Bumped Standards-Version to 3.8.0 (no changes
needed)
* added myself to the uploaders list.
[ Thomas Weber ]
* New patch: patches/no-nan-values
Error out in case of NaN values, they are not
supported by VTK (closes: 480431)
I didn't remove the standards bump, it was already in our VCS.
Added patch attached.
Thanks
Thomas
--- a/Scripts/vtk_trisurf.m
+++ b/Scripts/vtk_trisurf.m
@@ -117,6 +117,10 @@
end
pts = [x y z];
end
+
+ if (find(isnan(pts)) || find(isnan(t)))
+error("Sorry, NaN values are not supported in VTK\n");
+ endif
vtk_init;
Bug#480431: [Pkg-octave-devel] Bug#480431: Bug#480431: Bug#480431: octaviz: Segfault on AMD64
On Fri, Sep 05, 2008 at 01:15:07PM +0200, Rafael Laboissiere wrote: > * Thomas Weber <[EMAIL PROTECTED]> [2008-06-09 09:11]: > > > Am Samstag, den 10.05.2008, 07:33 +0200 schrieb Thomas Weber: > > > On 09/05/08 18:34 -0500, Jordi Gutiérrez Hermoso wrote: > > > > Package: octaviz > > > > Version: 0.4.7-1 > > > > Severity: important > > > > > > > > With the attached script and data, Octaviz segfaults on AMD64. > > > > > > As I discussed with Jordi earlier: this is arch-specific, it doesn't > > > happen on i386. > > > > I've tracked this back till line 271 of vtkClipPolyData.cxx, where > > cellScalars->GetComponent(1,0) > > is a NaN value. > > Should this bug be considered release-critical, as it is now (severity level > "serious")? The octaviz package is essentially functional and the problem > reported happens in the vtk_surf function (well, maybe also in others, who > knows...) > > Anyway, I think that it is too harsh to drop octaviz from lenny only because > of that. I would prefer to downgrade the severity to "important" and, as an > interim solution, upload a new version of octaviz with a patched vtk_surf > file. For instance, we could change the doc string by alerting the user > about NaN or, better, return an error message if the input Z matrix contains > NaN values. At any rate, the user can circumvent this bug by changing her > script (see the modified plotresults_vtk.m attached below). > > What do you think? Aarrgg, Rafael, you are my hero. Up until now, I thought that there was a bug in Octaviz/VTK, that created these NaN values. Now I see that they are coming from griddata(). Well, VTK doesn't support NaNs, at least according to http://www.vtk.org/pipermail/vtk-developers/2007-January/004421.html http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/295 So, my "solution" would be: patch vtk_surf() to check for NaN and error out if it finds them. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493417: octave-tsa: FTBFS: `sumskipnan' undefined
On 03/08/08 10:40 -0700, Daniel Schepler wrote: > On Sunday 03 August 2008 10:34:45 Thomas Weber wrote: > > On 03/08/08 10:23 -0700, Daniel Schepler wrote: > > > OK, I've posted those files at > > > http://math.berkeley.edu/~schepler/octave-nan/ . > > > > Sorry, 403 on all files. Can you check the permissions? > > Sorry, that should be fixed now. Your octave-nan .deb works fine here. However, I just noticed that the octave3.0 package used to build octave-nan in your setup has a "pb1" suffix, whereas it was "pb2" for . Did you change something between those runs? Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493417: octave-tsa: FTBFS: `sumskipnan' undefined
On 03/08/08 10:23 -0700, Daniel Schepler wrote: > OK, I've posted those files at http://math.berkeley.edu/~schepler/octave-nan/ > . Sorry, 403 on all files. Can you check the permissions? > Some possibly relevant information: the chroot is set up with /bin/sh > pointing > to dash, and the pbuilderrc sets DEB_BUILD_OPTIONS to "parallel=3". Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493417: octave-tsa: FTBFS: `sumskipnan' undefined
On 02/08/08 23:18 -0700, Daniel Schepler wrote: > On Saturday 02 August 2008 13:09:23 ?lafur Jens Sigur?sson wrote: > > This works fine for me on an i386 machine with a sid pbuilder. > > > > The error that you are getting implies that the octave-nan package is > > not getting installed (the octave-tsa build depends on this package). > > Why that is I don't know. Please supply the whole build log. > > > > Oli > > I was testing this with a chroot set up to use a repository of locally > rebuilt > packages, so it's certainly possible that the octave-nan build was broken. > Let me know how I can check whether that's the case. It is broken, from octave-tsa's build log: Setting up octave-nan (1.0.6-1+pb2) ... attempting to save variables to `octave-core'... save to `octave-core' complete > In the meantime, here's the full build log for octave-tsa. Can you make the build log and the final package of octave-nan available somewhere? Thanks Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479928: [Pkg-octave-devel] Bug#479928: octave-epstk: FTBFS: error: `localtime' undefined near line 39 column 8
Hi Lucas, Am Mittwoch, den 07.05.2008, 10:47 +0200 schrieb Lucas Nussbaum: > Package: octave-epstk > Version: 2.2-10 > Severity: serious > User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20080506 qa-ftbfs > Justification: FTBFS on i386 this error is real, but not due to the different gcc versions. A fix will be uploaded soonish. Thanks Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477041: matwrap: FTBFS: string.h:100: error: declaration of 'int strcmp(const char*, const char*) throw ()' throws different exceptions
package matwrap severity 477041 important thanks On 27/04/08 10:38 +0200, Thomas Weber wrote: > On 20/04/08 18:03 +0200, Lucas Nussbaum wrote: > > Package: matwrap > > Version: 0.57-10 > > Severity: serious > > User: [EMAIL PROTECTED] > > Usertags: qa-ftbfs-20080419 qa-ftbfs > > Justification: FTBFS on i386 > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build on > > i386. > > > > Feel free to downgrade this bug to 'important' if your package is only built > > on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine > > with > > gcc 4.2). I'm downgrading the bug, in order to let the current unstable version into testing (I can't reproduce the bug with gcc 4.3 on amd64 and gcc 4.2 is still default for i386). Once the package is migrated, I will upload a fixed package, but I don't want to keep the fix for #474826 out of testing. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477041: matwrap: FTBFS: string.h:100: error: declaration of 'int strcmp(const char*, const char*) throw ()' throws different exceptions
On 20/04/08 18:03 +0200, Lucas Nussbaum wrote: > Package: matwrap > Version: 0.57-10 > Severity: serious > User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20080419 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on i386. > > This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now > the default on most architectures (even if it's not the case on i386 yet). Strange. The package builds fine for me with gcc 4.3 on AMD64 gcc 4.2 on i386 > Feel free to downgrade this bug to 'important' if your package is only built > on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with > gcc 4.2). I'm thinking about doing just that. Thanks Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#470327: [Pkg-octave-devel] Bug#470327: Bug#470327: problem in fltk-config
Am Dienstag, den 11.03.2008, 11:05 +0100 schrieb Rafael Laboissiere:
> * Thomas Weber <[EMAIL PROTECTED]> [2008-03-11 09:42]:
>
> > package octplot
> > reassign 470327 fltk1.1
> > found 1.1.8~rc1-2
> > thanks
> >
> > Hi Aaron,
> >
> > fltk-config outputs several lines instead of one when called as
> >
> > $ fltk-config --use-gl --libs
> >
> > [...]
>
> As a workaround, while waiting for the upstream fix, we could use instead:
>
> fltk-config --use-gl --libs | perl -e 'print join (" ", map {s/\n//;$_} <>)'
>
> Although, I am afraid my fellows of the DOG will kill me for proposing a
> Perl-based solution :-)
I don't think Shai will be too happy if we propose adding Perl (or any
other language) to his build system. But for our needs, why not?
Other option:
fltk-config --libs --use-gl | tr '\n' ' '
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#470327: [Pkg-octave-devel] Bug#470327: problem in fltk-config
package octplot
reassign 470327 fltk1.1
found 1.1.8~rc1-2
thanks
Hi Aaron,
fltk-config outputs several lines instead of one when called as
$ fltk-config --use-gl --libs
which makes it difficult to use the output in further commands. The
problem is in the "if" part, starting at line 319.
This change happened in upstream Subversion revision 5985, which was a
fix for STR #1799. I don't know fltk's upstream, so can you please
clarify if this change will stay? I'll then try to come up with a
work-around, although I think outputting everything on one line is
preferred.
See below for the corresponding FTBFS bug report for octplog.
Am Montag, den 10.03.2008, 12:04 -0700 schrieb Larry Doolittle:
> The origin of the problem is a change (between fltk1.1-1.1.7 and
> fltk1.1-1.1.8~rc1) in the output of fltk-config.
>
> With libfltk1.1{,-dev} version 1.1.7-7 installed, I get
>
> $ fltk-config --use-gl --libs
> /usr/lib/libfltk.a /usr/lib/libfltk_gl.a
> $
>
> but with revision 1.1.8~rc1-2 I get
>
> $ fltk-config --use-gl --libs
> /usr/lib/libfltk.a
> /usr/lib/libfltk_gl.a
> $
>
> The octplot configure script gets tripped up by the extra linefeed,
> so the resulting Makefile has
>
> LIBS = /usr/lib/libfltk.a
> /usr/lib/libfltk_gl.a -lfltk_gl -lfltk -lGLU -lGL -lm -lfreetype -lz
>
> instead of
>
> LIBS = /usr/lib/libfltk.a /usr/lib/libfltk_gl.a -lfltk_gl -lfltk -lGLU -lGL
> -lm -lfreetype -lz
>
> I humbly suggest reassigning to package fltk1.1,
Doing so now, thanks for the analysis.
> although I could also
> make an argument that autoconf should deal with this case. There's not
> really anything to fix in octplot, which just does
>LIBS="$LIBS `$FLTK_CONFIG $fltkconf_args --use-gl --libs`"
> in configure.ac.
Thanks
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#458852: octave3.0 crashes on arm
On 03/01/08 10:56 +0100, Soeren Sonnenburg wrote: > Package: octave3.0 > Version: 3.0.0-1 > Severity: grave > > panic: Segmentation fault -- stopping myself... > attempting to save variables to `octave-core'... > save to `octave-core' complete > Segmentation fault This turns out to be a toolchain issue; using gcc-4.1 and friends, it works in qemu. I suppose this is related to #467503 (the bug symptoms under gdb are pretty much the same). So, that's the good news. The bad news is that octave3.0 build failed on europa with an ICE. Sigh, and all this with the knowledge that probably no real person uses Octave and friends on ARM. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464334: [Pkg-octave-devel] Bug#464334: octave2.1: installation fails
Am Mittwoch, den 06.02.2008, 15:28 +0100 schrieb Lucas Nussbaum: > On 06/02/08 at 10:59 +0100, Thomas Weber wrote: > > package: octave2.1 > > tags 464334 unreproducible > > thanks > > > > Am Mittwoch, den 06.02.2008, 09:44 +0100 schrieb Lucas Nussbaum: > > > Package: octave2.1 > > > Version: 1:2.1.73-16 > > > Severity: serious > > > > > > Hi, > > > > > > In a clean chroot: > > > > > > Setting up octave2.1 (1:2.1.73-16) ... > > > ls: cannot access /usr/share/octave/3.0.0/m/startup/octaverc: No such > > > file or directory > > > dpkg: error processing octave2.1 (--configure): > > > subprocess post-installation script returned error exit status 1 > > > > I can't reproduce this in neither amd64 nor i386 chroots. Did you build > > the package yourself? > > no. > > However, I can't reproduce it anymore, so something changed in unstable > between yesterday and today that caused this to be "solved". > > Closing the bug. I'm not happy with this. The 3.0.0 path does exist in octave3.0, so you might have found something that's just difficult to trigger. Was the clean chroot generated by scratch or did you install something in it before the installation of octave2.1? Similarly, did you install octave2.1 or the virtual octave package? Thanks Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464334: [Pkg-octave-devel] Bug#464334: octave2.1: installation fails
package: octave2.1 tags 464334 unreproducible thanks Am Mittwoch, den 06.02.2008, 09:44 +0100 schrieb Lucas Nussbaum: > Package: octave2.1 > Version: 1:2.1.73-16 > Severity: serious > > Hi, > > In a clean chroot: > > Setting up octave2.1 (1:2.1.73-16) ... > ls: cannot access /usr/share/octave/3.0.0/m/startup/octaverc: No such file or > directory > dpkg: error processing octave2.1 (--configure): > subprocess post-installation script returned error exit status 1 I can't reproduce this in neither amd64 nor i386 chroots. Did you build the package yourself? Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
