Bug#708812: [aptitude] aptitude segfaults upon being called.
Package: aptitude Version: 0.6.8.2-1 Followup-For: Bug #708812 Dear Maintainer, Quite a lot packages, e.g. [1-5], FTBFS on debian mipsel buildd due to this bug. I'm trying to fix it on my mipsel box, but the package suffers another FTBFS bug [6]. Is there any plan to fix these bugs? I can help to fix it on mipsel. [1] https://buildd.debian.org/status/fetch.php?pkg=lzdarch=mipselver=0.2-2stamp=1370782631 [2] https://buildd.debian.org/status/fetch.php?pkg=abiwordarch=mipselver=3.0.0~svn20130523-1stamp=1370791622 [3] https://buildd.debian.org/status/fetch.php?pkg=gnome-shellarch=mipselver=3.8.3-1stamp=1371098758 [4] https://buildd.debian.org/status/fetch.php?pkg=mcarch=mipselver=3%3A4.8.8-1stamp=1371103323 [5] https://buildd.debian.org/status/fetch.php?pkg=beefarch=mipselver=1.0.0-1stamp=137520 [6] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716828 Regards, Lifeng -- 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#686753: libroot-core-dev: wrong include #include snprintf.h
tag 686753 + moreinfo severity 686753 normal thanks Hi, It's likely you didn't specified -I/usr/include/root option for your compiler, so I downgrade severity to normal. Regards, Lifeng On Wed, Sep 5, 2012 at 6:00 PM, alessandro -oggei- ogier alessandro.og...@scimmia.net wrote: Package: libroot-core-dev Severity: grave Justification: renders package unusable /usr/include/root/Rtypes.h:35:67: fatal error: snprintf.h: No such file or directory according to apt-file, snprintf resides in libroot-core-dev so maybe we have to patch it ? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (999, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681589: givaro: uses system include syntax for local header
Hi Neil, On 09:04 Sat 07/14/12 Jul , Neil Williams wrote: givaro-3.7.0/src/kernel/gmp++/gmp++.h specifies an include for one of it's own header files (gmpxx.h) using system include syntax instead of Thanks for report. Actually gmpxx.h is a header file of libgmp-dev, and givaro contains no file named gmpxx.h, so IMHO this is not a bug. However, givaro-3.7.0/src/kernel/zpz/StaticElement.h does include givaro's own header file (gmp++.h) using system include syntax. I would like to fix it in the next upload (givaro_3.7.1-1). 1: linbox and other packages which use givaro_check.m4 will fail to build from source because gmpxx.h cannot be found by the configure check. The FTBFS bug of linbox in sid is likely caused by givaro API incompatibility. I would file an RFS for linbox-1.3.2 to fix the bug if Vincent Danjean is no longer interested in this package (I got permission from Tim Abbott to adopt linbox and other SAGE-related packages). Thanks, Lifeng -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681589: givaro: uses system include syntax for local header
Hi release team, Could you please remove givaro, fflas-ffpack and linbox from testing if you don't want to make a new transition from libgivaro0 to libgivaro1? Thanks. Regards, Lifeng On 11:42 Sat 07/14/12 Jul , Neil Williams wrote: OK, in that case, givaro_check.m4 is irretrievably broken and givaro needs to provide pkg-config support which linbox can use instead. givaro_check tries to link a test program against libgivaro0 simply by including the givinteger.h header and this *was* a valid method for older versions of givaro. 1: linbox and other packages which use givaro_check.m4 will fail to build from source because gmpxx.h cannot be found by the configure check. The FTBFS bug of linbox in sid is likely caused by givaro API incompatibility. It definitely is - however, even if givaro migrates API, linbox will still not get a valid result from givaro_check.m4. Givaro can help this situation by providing a givaro.pc file. I would file an RFS for linbox-1.3.2 to fix the bug if Vincent Danjean is no longer interested in this package (I got permission from Tim Abbott to adopt linbox and other SAGE-related packages). There is no point thinking about uploading libgivaro1 without talking to the release team who are unlikely to want a new transition at this point. See #678769 - that's why I blocked this bug by #678769. At this stage of the release freeze, the release team may be more willing to consider removing givaro, linbox and fflas-ffpack. This problem should have been noticed before the 3.7.0-1 upload. It is difficult to fix now and you should talk to the release team about what can be done and whether givaro can be released as part of Wheezy. Currently, it looks unlikely. -- signature.asc Description: Digital signature
Bug#679720: vsftpd uninstallable: init script syntax error
Package: vsftpd Version: 3.0.0-3 Severity: serious The installation fails with following message: /etc/init.d/vsftpd: 36: /etc/init.d/vsftpd: Syntax error: } unexpected invoke-rc.d: initscript vsftpd, action start failed. dpkg: error processing vsftpd (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: vsftpd Regards, Lifeng -- signature.asc Description: Digital signature
Bug#678807: ttf-root-installer: post installation fails
Hi Robert, Thanks for report. The upstream web/ftp server is offline in last a few days due to security issues (the upstream claims that it's the first 1 days outage in 16 years). Although the web server is recovered today, the ftp port is still blocked, which causes the failure of postinst script. At the moment you can fix it by replacing ftp://root.cern.ch/root/ttf/; with http://root.cern.ch/download/ttf/; in the postinst script. I would add error-handling in version 5.34.00-2. Thanks, Lifeng On 14:36 Sun 06/24/12 Jun , Robert Luberda wrote: Package: ttf-root-installer Upgrade of ttf-root-installer fails: Setting up ttf-root-installer (5.34.00~rc1-1) ... dpkg: error processing ttf-root-installer (--configure): subprocess installed post-installation script returned error exit status 4 When I add set -x into /var/lib/dpkg/info/ttf-root-installer.postinst, it is visible that the last command the script tries to download something with wget: + test -z + wget --continue --tries=1 --dns-timeout=10 --connect-timeout=5 --read-timeout=300 -q --directory-prefix . -c ftp://root.cern.ch/root/ttf/ttf_fonts.tar.gz dpkg: error processing ttf-root-installer (--configure): subprocess installed post-installation script returned error exit status 4 but it fails to do any error-handling in case of any downloads issues. -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642495: Fail to install stardict-gtk
Package: stardict
Version: 3.0.1-8
Severity: grave
Hi,
stardict-gtk and stardict-gnome both ship stardict.desktop now, while
in the earlier versions it is shipped within stardict-common,
$ cat debian/stardict-gtk.install
stardict usr/bin/
debian/tmp/usr/share/applications/* # stardict.desktop
$ cat debian/stardict-gnome.install
debian/tmp/usr/bin/stardict
debian/tmp/usr/lib/bonobo/servers/GNOME_Stardict.server
debian/tmp/usr/share/gnome/*
debian/tmp/usr/share/applications/* # stardict.desktop
debian/tmp/etc/gconf/schemas/*
debian/tmp/usr/share/idl/*
it causes error during installation such as,
Unpacking replacement stardict-gtk ...
dpkg: error processing
/var/cache/apt/archives/stardict-gtk_3.0.1-8_amd64.deb (--unpack):
trying to overwrite '/usr/share/applications/stardict.desktop', which
is also in package stardict-common 3.0.1-7
configured to not write apport reports
Preparing to replace
stardict-common 3.0.1-7 (using .../stardict-common_3.0.1-8_all.deb) ...
Unpacking replacement stardict-common ...
Preparing to replace stardict 3.0.1-7 (using .../stardict_3.0.1-8_all.deb) ...
Unpacking replacement stardict ...
Processing triggers for menu ...
Processing triggers for man-db ...
Processing triggers for bash-completion ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for install-info ...
Processing triggers for doc-base ...
Processing 1 changed doc-base file...
Registering documents with scrollkeeper...
Errors were encountered while processing:
/var/cache/apt/archives/stardict-gtk_3.0.1-8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
dpkg: dependency problems prevent configuration of stardict:
stardict depends on stardict-gtk (= 3.0.1-8) | stardict-gnome (= 3.0.1-8);
however:
Version of stardict-gtk on system is 3.0.1-7+b1.
Package stardict-gnome is not installed.
dpkg: error processing stardict (--configure):
dependency problems - leaving unconfigured
it might work by moving stardict.desktop to stardict-common or
declaring stardict-{gtk,gnome} conflicted with earlier versions of
stardict-common.
Kind regards,
Lifeng Sun
--
signature.asc
Description: GnuPG digital signature
Bug#640572: paw: FTBFS: sed: can't read debian/paw-common/usr/share/man/man1/paw.1: No such file or directory
Hi, Thank you for reporting, and sorry for reply late, I just returned from annual leave. This bug was introduced during fixing the lintian error temporary-debhelper-file of cernlib, it also occurs, though not FTBFS, in the packages mclibs and geant321. I would upload a new version of these packages after miagrating their patch system to quilt. To fix this FTBFS bug at the moment, you can rename the debian/debhelper directory to debian/dh. Best regards, Lifeng 2011/9/6 Mònica Ramírez mon...@probeta.net: Source: paw Version: 1:2.14.04.dfsg.2-7 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110902 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/paw-P6ek6k/paw-2.14.04.dfsg.2' make[1]: Nothing to be done for `install-indep-local'. make[1]: Leaving directory `/build/paw-P6ek6k/paw-2.14.04.dfsg.2' dh_testdir dh_testroot dh_install -i dh_installdocs -i dh_installexamples -i # reference to kuesvr man page (cernlib source package) now moved # to section 7 sed -i -e '/kuesvr/s/1/7/' debian/paw-common/usr/share/man/man1/paw.1 sed: can't read debian/paw-common/usr/share/man/man1/paw.1: No such file or directory make: *** [binary-indep] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/02/paw_1:2.14.04.dfsg.2-7_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614471:
Hello,
On 09:38 Tue 02/22/11 Feb , Mathieu Malaterre wrote:
reassign 614471 ffmpeg
thanks
[ 29%] Building CXX object
VTK/IO/CMakeFiles/vtkIO.dir/vtkPostgreSQLQuery.cxx.o
In file included from /usr/include/libavutil/avutil.h:81,
from /usr/include/libavcodec/avcodec.h:30,
from /usr/include/libavformat/avformat.h:56,
from
/build/user-paraview_3.8.1-2-amd64-4Wj_N7/paraview-3.8.1/VTK/IO/vtkFFMPEGWriter.cxx:27:
/usr/include/libavutil/common.h: In function 'int32_t
av_clipl_int32(int64_t)':
/usr/include/libavutil/common.h:154: error: 'UINT64_C' was not declared in
this scope
Clearly the issue is in the libavutil.h code (not in paraview)
This is an issue of paraview. Paraview is written in C++ while
libavutil is written in C. The ISO C99 standard (7.18.4) specifies
that C++ implementations should define UINT64_C only when
__STDC_CONSTANT_MACROS is defined, so even when stdint.h is included,
UINT64_C may be not in scope in C++ programs, but this never happens
in C programs.
Regards,
Lifeng
/**
* Clips a signed 64-bit integer value into the -2147483648,2147483647 range.
* @param a value to clip
* @return clipped value
*/
static inline av_const int32_t av_clipl_int32(int64_t a)
{
if ((a+0x8000u) ~UINT64_C(0x)) return (a63) ^ 0x7FFF;
else return a;
}
Thanks
--
debian-science-maintainers mailing list
debian-science-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-science-maintainers
--
--- a/VTK/IO/vtkFFMPEGWriter.cxx
+++ b/VTK/IO/vtkFFMPEGWriter.cxx
@@ -21,6 +21,10 @@
#include vtkFFMPEGConfig.h
extern C {
+#ifndef __STDC_CONSTANT_MACROS
+# define __STDC_CONSTANT_MACROS
+#endif
+
#ifdef VTK_FFMPEG_HAS_OLD_HEADER
# include ffmpeg/avformat.h
#else
signature.asc
Description: GnuPG digital signature
Bug#614083: guiqwt: FTBFS on multiple architectures - unrecognized command line option -msse2
Hi all, On 11:43 Mon 02/21/11 Feb , Picca Frédéric-Emmanuel wrote: Le Mon, 21 Feb 2011 10:56:39 +0100, Julien Cristau jcris...@debian.org a écrit : This patch is wrong. We don't want to pass -msse2 on ANY architecture. Whatever the build cpu. Can you provide an explaination, that way it would be easier for me to convince the upstream to remove this flag. I think the point is that, for one architecture, only the binaries contain the COMMON instruction set should be shipped in debian, otherwise the binary will be broken on some users' platforms, so this patch could be accepted by the upstream but not debian (and other binary-based distributions). In debian, simply remove the -msse2 flags should be okay. thanks Frederic PS: I suppose that the authors whant sse2 optimisation in ht egenerated code. -- GPG public key 4096R/4696E015 2011-02-14 fingerprint = E92E 7E6E 9E9D A6B1 AA31 39DC 5632 906F 4696 E015 uid Picca Frédéric-Emmanuel pi...@synchrotron-soleil.fr Regards, Lifeng -- signature.asc Description: GnuPG digital signature
Bug#614083: guiqwt: FTBFS on multiple architectures - unrecognized command line option -msse2
Hello, -msse2 is hard-coded as default compile option, which is not supported on non-PC archs. The attached patch detects SSE2 support. CCed to upstream author. regards, Lifeng On 15:13 Sat 02/19/11 Feb , Hector Oron wrote: Package: guiqwt Version: 2.0.8.1-1 Severity: serious Hello, Your package fails to build on many architectures: Find full build log information at: https://buildd.debian.org/fetch.cgi?pkg=guiqwt;ver=2.0.8.1-1;arch=armel;stamp=1298113143 Find an overview of failing architectures at: https://buildd.debian.org/pkg.cgi?pkg=guiqwt Best regards, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/debian-science-maintainers -- --- a/setup.py +++ b/setup.py @@ -97,6 +97,15 @@ cmdclass['build_doc'] = build_doc +from numpy.distutils.cpuinfo import cpu + +sse2_flag= + +try: +if cpu._has_sse2(): +sse2_flag=-msse2 +except KeyError: +pass setup(name=LIBNAME, version=version, download_url='http://%s.googlecode.com/files/%s-%s.zip' % ( @@ -108,7 +117,7 @@ ext_modules=[Extension(LIBNAME+'._ext', [join(src, 'histogram.f')]), Extension(LIBNAME+'._mandel', [join(src, 'mandel.f90')]), Extension(LIBNAME+'._scaler', [join(src, scaler.cpp)], - extra_compile_args=[-msse2 -Wall -Werror,], + extra_compile_args=[sse2_flag+-Wall -Werror,], depends=[join(src, traits.hpp), join(src, points.hpp), join(src, arrays.hpp), signature.asc Description: GnuPG digital signature
Bug#614148: guiqwt: FTBFS: tries to include non-PIC FORTRAN object in shared library
Hello, I find it works on my MIPS box by simply export FFLAGS=-fPIC in debian/rules. regards, Lifeng On 18:13 Sat 02/19/11 Feb , Aaron M. Ucko wrote: Package: guiqwt Version: 2.0.8.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of guiqwt are failing on architectures such as amd64 that require all objects comprising a shared library to have been compiled as position-independent code: /usr/bin/gfortran -Wall -shared build/temp.linux-x86_64-2.5/build/src.linux-x86_64-2.5/guiqwt/_extmodule.o build/temp.linux-x86_64-2.5/build/src.linux-x86_64-2.5/fortranobject.o build/temp.linux-x86_64-2.5/src/histogram.o -lgfortran -o build/lib.linux-x86_64-2.5/guiqwt/_ext.so /usr/bin/ld: build/temp.linux-x86_64-2.5/src/histogram.o: relocation R_X86_64_PC32 against undefined symbol `lround@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC Could you please contrive to pass the (undocumented!) -fPIC option to the FORTRAN compiler as well as the C one? Thanks! -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/debian-science-maintainers -- signature.asc Description: GnuPG digital signature
