Bug#713750: marked as done (geotranz: FTBFS: dpkg-gensymbols errors)
Your message dated Fri, 11 Oct 2013 06:34:21 +
with message-id e1vuwin-0001l0...@franck.debian.org
and subject line Bug#713750: fixed in geotranz 3.2-1.1
has caused the Debian Bug report #713750,
regarding geotranz: FTBFS: dpkg-gensymbols errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
713750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: geotranz
Version: 3.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
fakeroot debian/rules binary
make[1]: Leaving directory `/«PKGBUILDDIR»'
test -x debian/rules
dh_testroot
dh_prep
dh_installdirs -A
mkdir -p .
DEB_MAKE_CHECK_TARGET unset, not running checks
DEB_MAKE_INSTALL_TARGET unset, skipping default makefile.mk common-install
target
Adding cdbs dependencies to debian/geotranz.substvars
dh_installdirs -pgeotranz
convert GEOTRANS3/java_gui/geotrans3/gui/icons/Geotrans.gif
debian/geotranz/usr/share/pixmaps/geotrans.xpm
Adding cdbs dependencies to debian/geotranz-doc.substvars
dh_installdirs -pgeotranz-doc
Adding cdbs dependencies to debian/geotranz-help.substvars
dh_installdirs -pgeotranz-help
dh_installdocs -pgeotranz
dh_installexamples -pgeotranz
dh_installman -pgeotranz
dh_installinfo -pgeotranz
dh_installmenu -pgeotranz
dh_installcron -pgeotranz
dh_installinit -pgeotranz
dh_installdebconf -pgeotranz
dh_installemacsen -pgeotranz
dh_installcatalogs -pgeotranz
dh_installpam -pgeotranz
dh_installlogrotate -pgeotranz
dh_installlogcheck -pgeotranz
dh_installchangelogs -pgeotranz
dh_installudev -pgeotranz
dh_lintian -pgeotranz
dh_bugfiles -pgeotranz
dh_install -pgeotranz
dh_link -pgeotranz
dh_installmime -pgeotranz
dh_installgsettings -pgeotranz
dh_installdocs -pgeotranz-doc
dh_installexamples -pgeotranz-doc
dh_installman -pgeotranz-doc
dh_installinfo -pgeotranz-doc
dh_installmenu -pgeotranz-doc
dh_installcron -pgeotranz-doc
dh_installinit -pgeotranz-doc
dh_installdebconf -pgeotranz-doc
dh_installemacsen -pgeotranz-doc
dh_installcatalogs -pgeotranz-doc
dh_installpam -pgeotranz-doc
dh_installlogrotate -pgeotranz-doc
dh_installlogcheck -pgeotranz-doc
dh_installchangelogs -pgeotranz-doc
dh_installudev -pgeotranz-doc
dh_lintian -pgeotranz-doc
dh_bugfiles -pgeotranz-doc
dh_install -pgeotranz-doc
dh_link -pgeotranz-doc
dh_installmime -pgeotranz-doc
dh_installgsettings -pgeotranz-doc
dh_installdocs -pgeotranz-help
dh_installexamples -pgeotranz-help
dh_installman -pgeotranz-help
dh_installinfo -pgeotranz-help
dh_installmenu -pgeotranz-help
dh_installcron -pgeotranz-help
dh_installinit -pgeotranz-help
dh_installdebconf -pgeotranz-help
dh_installemacsen -pgeotranz-help
dh_installcatalogs -pgeotranz-help
dh_installpam -pgeotranz-help
dh_installlogrotate -pgeotranz-help
dh_installlogcheck -pgeotranz-help
dh_installchangelogs -pgeotranz-help
dh_installudev -pgeotranz-help
dh_lintian -pgeotranz-help
dh_bugfiles -pgeotranz-help
dh_install -pgeotranz-help
dh_link -pgeotranz-help
dh_installmime -pgeotranz-help
dh_installgsettings -pgeotranz-help
dh_strip -pgeotranz
dh_compress -pgeotranz
dh_fixperms -pgeotranz
dh_makeshlibs -pgeotranz
dh_strip -pgeotranz-doc
dh_compress -pgeotranz-doc
dh_fixperms -pgeotranz-doc
dh_makeshlibs -pgeotranz-doc
dh_strip -pgeotranz-help
dh_compress -pgeotranz-help
dh_fixperms -pgeotranz-help
dh_makeshlibs -pgeotranz-help
dh_installdeb -pgeotranz
dh_perl -pgeotranz
dh_shlibdeps -pgeotranz
dh_installdeb -pgeotranz-doc
dh_perl -pgeotranz-doc
dh_shlibdeps -pgeotranz-doc
dh_installdeb -pgeotranz-help
dh_perl -pgeotranz-help
dh_shlibdeps -pgeotranz-help
dh_gencontrol -pgeotranz
dpkg-gencontrol: warning: Depends field of package geotranz: unknown
substitution variable ${shlibs:Depends}
dh_md5sums -pgeotranz
dh_builddeb -pgeotranz
dpkg-deb: building package `geotranz' in `../geotranz_3.2-1_all.deb'.
dh_gencontrol -pgeotranz-doc
dpkg-gencontrol: warning: Depends field of package geotranz-doc: unknown
substitution variable ${shlibs:Depends}
dh_md5sums -pgeotranz-doc
dh_builddeb -pgeotranz-doc
dpkg-deb: building package `geotranz-doc' in `../geotranz-doc_3.2-1_all.deb'.
dh_gencontrol -pgeotranz-help
dpkg-gencontrol: warning:
Bug#701286: marked as done (geotranz: ftbfs with GCC-4.8)
Your message dated Fri, 11 Oct 2013 06:34:21 + with message-id e1vuwin-0001kv...@franck.debian.org and subject line Bug#701286: fixed in geotranz 3.2-1.1 has caused the Debian Bug report #701286, regarding geotranz: ftbfs with GCC-4.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:geotranz Version: 3.2-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. XXX The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/geotranz_3.2-1_unstable_gcc48.log The last lines of the build log are at the end of this report. To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues might be caused by the updated glibc. [...] (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_copy(std::_Rb_tree_nodestd::pairchar const, MSP::CCS::PolarStereographic* const*, std::_Rb_tree_nodestd::pairchar const, MSP::CCS::PolarStereographic* *)@Base 3.2 (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_erase(std::_Rb_tree_nodestd::pairchar const, MSP::CCS::PolarStereographic* *)@Base 3.2 - (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_insert_(std::_Rb_tree_node_base const*, std::_Rb_tree_node_base const*, std::pairchar const, MSP::CCS::PolarStereographic* const)@Base 3.2 - (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_insert_unique(std::pairchar const, MSP::CCS::PolarStereographic* const)@Base 3.2 - (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_insert_unique_(std::_Rb_tree_const_iteratorstd::pairchar const, MSP::CCS::PolarStereographic* , std::pairchar const, MSP::CCS::PolarStereographic* const)@Base 3.2 - (c++|optional)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::~_Rb_tree()@Base 3.2 +#MISSING: 3.2-1# (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_insert_(std::_Rb_tree_node_base const*, std::_Rb_tree_node_base const*, std::pairchar const, MSP::CCS::PolarStereographic* const)@Base 3.2 +#MISSING: 3.2-1# (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_insert_unique(std::pairchar const, MSP::CCS::PolarStereographic* const)@Base 3.2 +#MISSING: 3.2-1# (c++)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*, std::_Select1ststd::pairchar const, MSP::CCS::PolarStereographic* , std::lesschar, std::allocatorstd::pairchar const, MSP::CCS::PolarStereographic* ::_M_insert_unique_(std::_Rb_tree_const_iteratorstd::pairchar const, MSP::CCS::PolarStereographic* , std::pairchar const, MSP::CCS::PolarStereographic* const)@Base 3.2 +#MISSING: 3.2-1# (c++|optional)std::_Rb_treechar, std::pairchar const, MSP::CCS::PolarStereographic*,
Bug#726009: yade: FTBFS on i386 (and others)
Source: yade Version: 1.00.0-2 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hello, yade 1.00.0-2 FTBFS on the i396 autobuilder with message: /usr/bin/c++ -Dyade_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DYADE_PTR_CAST=static_pointer_cast -DYADE_CAST=static_cast -fPIC -DYADE_VTK -DYADE_OPENMP -fopenmp -DYADE_GTS -DQGLVIEWER_FOUND -DYADE_OPENGL -frounding-math -DYADE_CGAL -DFLOW_ENGINE -frounding-math -DLINSOLV -DFLOW_ENGINE -DYADE_GL2PS -O3 -DNDEBUG -fPIC -I/usr/lib/pymodules/python2.7/numpy/core/include -I/usr/include/eigen3 -I/usr/include/vtk-5.8 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/usr/include/suitesparse -I/usr/include/python2.7 -I/usr/include/i386-linux-gnu/python2.7 -I/«PKGBUILDDIR»/extra/floating_point_utilities_v3 -I/«PKGBUILDDIR»/debian/build-o CMakeFiles/yade.dir/pkg/dem/DomainLimiter.cpp.o -c /«PKGBUILDDIR»/pkg/dem/DomainLimiter.cpp virtual memory exhausted: Cannot allocate memory make[3]: *** [CMakeFiles/yade.dir/pkg/dem/DomainLimiter.cpp.o] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/debian/build' make[2]: *** [CMakeFiles/yade.dir/all] Error 2 make[2]: Leaving directory `/«PKGBUILDDIR»/debian/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»/debian/build' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 See https://buildd.debian.org/status/fetch.php?pkg=yadearch=i386ver=1.00.0-2stamp=1380696072 There are also build failures on other architectures. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613191: marked as done (Please stop using HAL)
Your message dated Fri, 11 Oct 2013 07:10:26 + with message-id e1vuwri-000753...@franck.debian.org and subject line Bug#725834: Removed package(s) from unstable has caused the Debian Bug report #613191, regarding Please stop using HAL to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 613191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: synce-trayicon Version: 0.15-1 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: halectomy Hi, HAL has been deprecated and declared dead upstream so we want to get rid of it eventually in Debian [1]. Please consider disabling HAL support in synce-trayicon and/or porting it to newer interfaces like upower, udisks or libudev. Regards, Michael [1] http://wiki.debian.org/HALRemoval -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 0.15-1.2+rm Dear submitter, as the package synce-trayicon has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/725834 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#713507: marked as done (whizzytex: FTBFS: ! I can't find file `pgfutil-common.tex'.)
Your message dated Fri, 11 Oct 2013 07:49:05 + with message-id e1vuxt7-0003yi...@franck.debian.org and subject line Bug#713507: fixed in whizzytex 1.3.2-1.2 has caused the Debian Bug report #713507, regarding whizzytex: FTBFS: ! I can't find file `pgfutil-common.tex'. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: whizzytex Version: 1.3.2-1.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 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 `/«PKGBUILDDIR»/doc' ln -s manual.sty manual.hva latex manual.tex This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) restricted \write18 enabled. entering extended mode (./manual.tex LaTeX2e 2011/06/27 Babel 3.9f and hyphenation patterns for 2 languages loaded. (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2007/10/19 v1.4h Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo)) (./version.tex) (./manual.sty (/usr/share/texmf/tex/latex/misc/hevea.sty (/usr/share/texlive/texmf-dist/tex/latex/comment/comment.sty Excluding comment 'comment') Excluding comment 'rawhtml' Excluding comment 'htmlonly') (/usr/share/texlive/texmf-dist/tex/latex/preprint/fullpage.sty) (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/color.cfg) (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def) (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def)) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg))) (/usr/share/texlive/texmf-dist/tex/latex/pst-node/pst-node.sty (/usr/share/texlive/texmf-dist/tex/latex/pstricks/pstricks.sty (/usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks.tex (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/pst-xkey.tex (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex))) (/usr/share/texlive/texmf-dist/tex/generic/pstricks/pst-fp.tex `pst-fp' v0.05, 2010/01/17 (hv)) ! I can't find file `pgfutil-common.tex'. l.101 \input pgfutil-common.tex (Press Enter to retry, or Control-D to exit) Please type another input file name: ! Emergency stop. l.101 \input pgfutil-common.tex No pages of output. Transcript written on manual.log. make[1]: *** [whizzytex.dvi] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/whizzytex_1.3.2-1.1_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: whizzytex Source-Version: 1.3.2-1.2 We believe that the bug you reported is fixed in the latest version of whizzytex, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane henr...@debian.org (supplier of updated whizzytex package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Oct 2013 16:06:20 +0900 Source: whizzytex Binary: whizzytex Architecture: source all Version: 1.3.2-1.2 Distribution: unstable Urgency: low Maintainer: Junichi Uekawa dan...@debian.org Changed-By: Hideki Yamane henr...@debian.org Description: whizzytex - a
Bug#724186: frei0r: fix for new automake
The only change _required_ now is adding -i to autoreconf (in debian/rules), but it seemed a good idea to also fix the deprecation warnings (copied below) before they become errors in a future version. configure.ac:8: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see: configure.ac:8: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation configure.ac:12: installing './compile' src/Makefile.am:72: warning: source file 'filter/3dflippo/3dflippo.c' is in a subdirectory, src/Makefile.am:72: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726015: gnupg2: Incorrect Build-Conflicts on automake (= 1.12) doesn't take into account epoch
Package: gnupg2 Version: 2.0.21-2~deb7u1 Severity: serious Justification: fails to build from source (but built successfully in the past) The package has a Build-Conflicts on automake (= 1.12), which only happens to work on sid due to automake1.11 being a package in its own right. When rebuilding gnupg2 on wheezy for a private backport, automake1.11 is provided by the automake package, which is 1:1.11.6-1 and makes the build fail. Adding the epoch to the Build-Conflicts line fixes the build, and I think is what was originally intended: Build-Conflicts: automake (= 1:1.12) Regards, Chris -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.10.12-0.bootc.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnupg2 depends on: ii dpkg 1.16.10 ii gnupg-agent 2.0.21-2~deb7u1 ii install-info 4.13a.dfsg.1-10 ii libassuan0 2.0.3-1 ii libbz2-1.0 1.0.6-4 ii libc62.13-38 ii libcurl3-gnutls 7.26.0-1+wheezy3 ii libgcrypt11 1.5.0-5+deb7u1 ii libgpg-error01.12-0.2~deb7u1 ii libksba8 1.2.0-2 ii libreadline6 6.2+dfsg-0.1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages gnupg2 recommends: ii libldap-2.4-2 2.4.31-1+nmu2 Versions of packages gnupg2 suggests: pn gnupg-doc none pn xloadimage none -- 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
Processed: your mail
Processing commands for cont...@bugs.debian.org: found 726015 2.0.21-1 Bug #726015 [gnupg2] gnupg2: Incorrect Build-Conflicts on automake (= 1.12) doesn't take into account epoch Marked as found in versions gnupg2/2.0.21-1. notfound 726015 2.0.20-1 Bug #726015 [gnupg2] gnupg2: Incorrect Build-Conflicts on automake (= 1.12) doesn't take into account epoch Ignoring request to alter found versions of bug #726015 to the same values previously set -- Stopping processing here. Please contact me if you need assistance. -- 726015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724153: marked as done (librime: FTBFS: config.cc:556:17: error: 'class YAML::Parser' has no member named 'GetNextDocument')
Your message dated Fri, 11 Oct 2013 09:07:37 + with message-id e1vuyh7-0006vd...@franck.debian.org and subject line Bug#724153: fixed in librime 0.9.9-1 has caused the Debian Bug report #724153, regarding librime: FTBFS: config.cc:556:17: error: 'class YAML::Parser' has no member named 'GetNextDocument' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: librime Version: 0.9.8-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[4]: Entering directory `/«PKGBUILDDIR»/build' [ 1%] Building CXX object src/CMakeFiles/rime.dir/translation.cc.o [ 2%] Building CXX object src/CMakeFiles/rime.dir/switcher.cc.o In file included from /usr/include/boost/signals.hpp:9:0, from /«PKGBUILDDIR»/include/rime/context.h:11, from /«PKGBUILDDIR»/src/switcher.cc:13: /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. [-Wcpp] # warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. ^ [ 4%] Building CXX object src/CMakeFiles/rime.dir/service.cc.o In file included from /usr/include/boost/signals.hpp:9:0, from /«PKGBUILDDIR»/include/rime/context.h:11, from /«PKGBUILDDIR»/src/service.cc:8: /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. [-Wcpp] # warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. ^ [ 5%] Building CXX object src/CMakeFiles/rime.dir/segmentation.cc.o [ 7%] Building CXX object src/CMakeFiles/rime.dir/schema.cc.o [ 8%] Building CXX object src/CMakeFiles/rime.dir/rime_api.cc.o In file included from /usr/include/boost/signals.hpp:9:0, from /«PKGBUILDDIR»/include/rime/context.h:11, from /«PKGBUILDDIR»/src/rime_api.cc:12: /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. [-Wcpp] # warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. ^ [ 10%] Building CXX object src/CMakeFiles/rime.dir/registry.cc.o [ 11%] Building CXX object src/CMakeFiles/rime.dir/menu.cc.o [ 13%] Building CXX object src/CMakeFiles/rime.dir/key_table.cc.o [ 14%] Building CXX object src/CMakeFiles/rime.dir/key_event.cc.o [ 16%] Building CXX object src/CMakeFiles/rime.dir/engine.cc.o In file included from /usr/include/boost/signals.hpp:9:0, from /«PKGBUILDDIR»/include/rime/context.h:11, from /«PKGBUILDDIR»/src/engine.cc:14: /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. [-Wcpp] # warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. To disable this warning message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING. ^ [ 17%] Building CXX object src/CMakeFiles/rime.dir/deployer.cc.o In file included from /usr/include/boost/signals.hpp:9:0, from /«PKGBUILDDIR»/include/rime/messenger.h:11, from /«PKGBUILDDIR»/include/rime/deployer.h:14, from /«PKGBUILDDIR»/src/deployer.cc:10: /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is no longer being maintained and is now deprecated. Please switch
Bug#710629: marked as done (most: FTBFS: ld: cannot find -ltermcap)
Your message dated Fri, 11 Oct 2013 09:07:48 + with message-id e1vuyhi-0006yk...@franck.debian.org and subject line Bug#710629: fixed in most 5.0.0a-2.2 has caused the Debian Bug report #710629, regarding most: FTBFS: ld: cannot find -ltermcap to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 710629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: most Version: 5.0.0a-2.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc /«PKGBUILDDIR»/src/objs/chkslang.o -o /«PKGBUILDDIR»/src/objs/chkslang /«PKGBUILDDIR»/src/objs/chkslang most 2 cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/buffer.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/cmd.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/display.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/edit.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/file.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/help.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/keym.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/keyparse.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/line.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/main.c if [ -x /sbuild-nonexistent/bin/update_changes_version ]; then \ /sbuild-nonexistent/bin/update_changes_version /«PKGBUILDDIR»/src/../changes.txt /«PKGBUILDDIR»/src/version.h; \ fi cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/most.c /«PKGBUILDDIR»/src/most.c: In function 'do_most': /«PKGBUILDDIR»/src/most.c:352:8: warning: variable 'piped' set but not used [-Wunused-but-set-variable] /«PKGBUILDDIR»/src/most.c: In function 'most': /«PKGBUILDDIR»/src/most.c:425:18: warning: variable 'context' set but not used [-Wunused-but-set-variable] /«PKGBUILDDIR»/src/most.c:424:33: warning: variable 'a_opt' set but not used [-Wunused-but-set-variable] cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/search.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/sysdep.c cd /«PKGBUILDDIR»/src/objs; gcc -c -O2 -g -Wall -DUTF8 -Dunix -DMOST_SYSTEM_INITFILE='/etc/most.conf' /«PKGBUILDDIR»/src/window.c /«PKGBUILDDIR»/src/window.c: In function 'most_split_window': /«PKGBUILDDIR»/src/window.c:701:28: warning: variable 'old' set but not used [-Wunused-but-set-variable] /«PKGBUILDDIR»/src/window.c: In function 'delete_as_top_window': /«PKGBUILDDIR»/src/window.c:877:17: warning: variable 'b2' set but not used [-Wunused-but-set-variable] /«PKGBUILDDIR»/src/window.c:877:14: warning: variable 'b1' set but not used [-Wunused-but-set-variable] /«PKGBUILDDIR»/src/window.c:877:11: warning: variable 't2' set but not used [-Wunused-but-set-variable] /«PKGBUILDDIR»/src/window.c: In function 'most_delete_window': /«PKGBUILDDIR»/src/window.c:938:15: warning: variable 'old_b' set but not used [-Wunused-but-set-variable] cd /«PKGBUILDDIR»/src/objs; gcc buffer.o cmd.o display.o edit.o file.o help.o keym.o keyparse.o line.o main.o most.o search.o sysdep.o window.o -o most -Wl,-R/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -lslang -ltermcap -lm /usr/bin/ld: cannot find -ltermcap collect2: error: ld returned 1 exit status The full build log is available from: http://deiv.vzpla.net/logs/2013/05/29/most_5.0.0a-2.1_unstable.log A list of current common problems and possible solutions is available at
Bug#707352: dee: diff for NMU version 1.0.10-3.1
tags 707352 + patch tags 707352 + pending thanks Dear maintainer, I've prepared an NMU for dee (versioned as 1.0.10-3.1). Please find the attached debdiff, based on the fix suggested by pochu in his replies to this bug report. Regards. -- Andrea Colangelo | http://andreacolangelo.com Ubuntu Developer www.ubuntu.com | Debian Maintainer www.debian.org diff -Nru dee-1.0.10/debian/changelog dee-1.0.10/debian/changelog --- dee-1.0.10/debian/changelog 2012-06-02 19:01:13.0 +0200 +++ dee-1.0.10/debian/changelog 2013-10-11 11:36:54.0 +0200 @@ -1,3 +1,11 @@ +dee (1.0.10-3.1) unstable; urgency=low + + * Non-maintainer upload. + * Add versioned B-D on valac to fix FTBFS with the new gobject-introspection. +(Closes: #707352 ) + + -- Andrea Colangelo war...@ubuntu.com Fri, 11 Oct 2013 11:35:08 +0200 + dee (1.0.10-3) unstable; urgency=low * debian/control: diff -Nru dee-1.0.10/debian/control dee-1.0.10/debian/control --- dee-1.0.10/debian/control 2012-06-02 18:17:00.0 +0200 +++ dee-1.0.10/debian/control 2013-10-11 11:35:06.0 +0200 @@ -14,7 +14,7 @@ libglib2.0-dev (= 2.26.0), libicu-dev (= 4.8), python (= 2.6.5), - valac + valac (= 0.20) Standards-Version: 3.9.3 Section: libs Homepage: https://launchpad.net/dee signature.asc Description: Digital signature
Processed: dee: diff for NMU version 1.0.10-3.1
Processing commands for cont...@bugs.debian.org: tags 707352 + patch Bug #707352 [src:dee] dee: FTBFS: Dee-1.0.gir:66.11-66.28: error: expected start element of `parameter' Added tag(s) patch. tags 707352 + pending Bug #707352 [src:dee] dee: FTBFS: Dee-1.0.gir:66.11-66.28: error: expected start element of `parameter' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 707352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 724203
Processing commands for cont...@bugs.debian.org: tags 724203 + confirmed upstream fixed-upstream pending Bug #724203 [src:umockdev] umockdev: FTBFS: Tests failed Added tag(s) upstream, confirmed, pending, and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 724203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723856: marked as done (ace: May need rebuilt for g++4.8 to fix ivtools FTBFS)
Your message dated Fri, 11 Oct 2013 10:04:16 + with message-id e1vuzzw-0006hb...@franck.debian.org and subject line Bug#723856: fixed in ace 6.0.3+dfsg-0.2 has caused the Debian Bug report #723856, regarding ace: May need rebuilt for g++4.8 to fix ivtools FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 723856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:ivtools Version: 1.2.10a1-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. ./.libs/libComTerp.so: undefined reference to `ACE_Event_Handler::handle_signal(int, siginfo_t*, ucontext*)' The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/ivtools_1.2.10a1-1_unstable_gcc48.log The last lines of the build log are at the end of this report. To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues might be caused by the updated glibc. [...] libtool: link: ( cd .libs rm -f libAttrGlyph.la ln -s ../libAttrGlyph.la libAttrGlyph.la ) libtool: link: (cd .libs rm -f libComTerp.so.1 ln -s libComTerp.so.1.2.8 libComTerp.so.1) libtool: link: (cd .libs rm -f libComTerp.so ln -s libComTerp.so.1.2.8 libComTerp.so) libtool: link: (cd .libs/libComTerp.lax/libComTerpPART1.a ar x /«PKGBUILDDIR»/./.libs/libComTerpPART1.a) libtool: link: (cd .libs/libComTerp.lax/libComTerpPART2.a ar x /«PKGBUILDDIR»/./.libs/libComTerpPART2.a) libtool: link: ar cru .libs/libComTerp.a src/ComTerp/libComTerp_la-comhandler.o src/ComTerp/libComTerp_la-comterpserv.o src/ComTerp/libComTerp_la-ctrlfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-assignfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-bitfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-boolfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-bquotefunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-charfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-comfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-comvalue.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-condfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-debugfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-dotfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-helpfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-iofunc.o .li bs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-listfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-mathfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-numfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-parser.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-postfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-randfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-scanner.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-statfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-strmfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-symbolfunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-typefunc.o .libs/libComTerp.lax/libComTerpPART1.a/libComTerpPART1_la-xformfunc.o .libs/libComTerp.lax/libComTerpPART2.a/libComTerpPART2_la-comterp.o libtool: link: ranlib .libs/libComTerp.a libtool: link: rm -fr .libs/libComTerp.lax libtool: link: ( cd .libs rm -f libComTerp.la ln -s ../libComTerp.la libComTerp.la ) /bin/bash ./libtool --tag=CXX --mode=link g++ -Wno-write-strings -Wno-deprecated -g -O2 -fstack-protector --param=ssp-buffer-size=4 -version-info 3:8:2 -Wl,-z,relro -o libComGlyph.la -rpath /usr/lib/x86_64-linux-gnu src/ComGlyph/libComGlyph_la-attrdialog.lo src/ComGlyph/libComGlyph_la-comtextedit.lo src/ComGlyph/libComGlyph_la-comtextview.lo src/ComGlyph/libComGlyph_la-terpdialog.lo libAttribute.la libComTerp.la libIVGlyph.la libIV.la libComUtil.la /bin/bash ./libtool --tag=CXX --mode=link g++ -Wno-write-strings -Wno-deprecated -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wl,-z,relro
Bug#724203: marked as done (umockdev: FTBFS: Tests failed)
Your message dated Fri, 11 Oct 2013 10:19:26 + with message-id e1vuzoc-000356...@franck.debian.org and subject line Bug#724203: fixed in umockdev 0.4.6-1 has caused the Debian Bug report #724203, regarding umockdev: FTBFS: Tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: umockdev Version: 0.4.5-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[5]: Entering directory `/«PKGBUILDDIR»' == Running test-umockdev test against build tree == /umockdev-testbed/empty: OK /umockdev-testbed/add_devicev: OK /umockdev-testbed/add_device: OK /umockdev-testbed/add_device_errors: OK /umockdev-testbed/child_device: OK /umockdev-testbed/set_attribute: OK /umockdev-testbed/set_property: OK /umockdev-testbed/add_from_string: OK /umockdev-testbed/add_from_string_errors: OK /umockdev-testbed/add_from_file: OK /umockdev-testbed/dev_access: OK /umockdev-testbed/add_from_string_dev_char: OK /umockdev-testbed/add_from_string_dev_block: OK /umockdev-testbed/dev_query_gudev: OK /umockdev-testbed/script_replay_simple: OK /umockdev-testbed/script_replay_socket_stream: OK /umockdev-testbed/script_replay_fuzz: OK /umockdev-testbed/clear: OK /umockdev-testbed/disable: OK /umockdev-testbed/remove: OK /umockdev-testbed/uevent/libudev: OK /umockdev-testbed/uevent/gudev: OK /umockdev-testbed/uevent/error: OK /umockdev-testbed-usb/lsusb: OK == Running test-ioctl-tree test against build tree == /umockdev-ioctl-tree/type_get_by: OK /umockdev-ioctl-tree/create_from_bin: OK /umockdev-ioctl-tree/write: OK /umockdev-ioctl-tree/read: OK /umockdev-ioctl-tree/iteration: OK /umockdev-ioctl-tree/execute: OK /umockdev-ioctl-tree/execute_unknown: OK /umockdev-ioctl-tree/evdev: OK == Running test-umockdev-vala test against build tree == /umockdev-testbed-vala/empty: OK /umockdev-testbed-vala/add_devicev: OK /umockdev-testbed-vala/gudev-query-list: OK /umockdev-testbed-vala/usbfs_ioctl_static: OK /umockdev-testbed-vala/usbfs_ioctl_tree: OK /umockdev-testbed-vala/usbfs_ioctl_tree_xz: OK /umockdev-testbed-vala/tty_stty: OK /umockdev-testbed-vala/tty_data: OK == Running test-umockdev-run test against build tree == /umockdev-run/exit_code: OK /umockdev-run/version: OK /umockdev-run/pipes: OK /umockdev-run/invalid-args: OK /umockdev-run/invalid-device: OK /umockdev-run/invalid-ioctl: [SKIP: gphoto2 not installed] [SKIP: gphoto2 not installed] [SKIP: gphoto2 not installed] [SKIP: gphoto2 not installed] OK /umockdev-run/invalid-script: OK /umockdev-run/invalid-program: OK /umockdev-run/script-chatter: OK /umockdev-run/script-chatter-socket-stream: OK /umockdev-run/integration/gphoto-detect: [SKIP: gphoto2 not installed] OK /umockdev-run/integration/gphoto-folderlist: [SKIP: gphoto2 not installed] OK /umockdev-run/integration/gphoto-filelist: [SKIP: gphoto2 not installed] OK /umockdev-run/integration/gphoto-thumbs: [SKIP: gphoto2 not installed] OK /umockdev-run/integration/gphoto-download: [SKIP: gphoto2 not installed] OK /umockdev-run/integration/input-touchpad: OK /umockdev-run/integration/input-evtest: [SKIP: evtest not installed] OK == Running test-umockdev-record test against build tree == /umockdev-record/testbed-all-empty: OK /umockdev-record/testbed-one: OK /umockdev-record/testbed-multiple: OK /umockdev-record/testbed-no-ioctl-record: OK ** ERROR:tests/test-umockdev-record.c:672:t_system_single: assertion failed (serr == ): (Invalid device /sys/dev/block/7:0, has no uevent attribute\n == ) /bin/bash: line 1: 19842 Aborted TOP_BUILDDIR=. TOP_SRCDIR=. LD_LIBRARY_PATH=./.libs:$LD_LIBRARY_PATH GI_TYPELIB_PATH=. PATH=./src:$PATH G_SLICE=debug-blocks MALLOC_PERTURB_=85 MALLOC_CHECK_=3 ./src/umockdev-wrapper $f make[5]: *** [check-local] Error 134 /umockdev-record/system-single: make[5]: Leaving directory `/«PKGBUILDDIR»' make[4]: *** [check-am] Error 2 make[3]: *** [check-recursive] Error 1 make[2]: *** [check] Error 2 dh_auto_test: make -j1 check returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/umockdev_0.4.5-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS .
Bug#713181: marked as done (pam-shield: FTBFS: autoreconf: failed to run /usr/bin/aclocal-1.11: No such file or directory)
Your message dated Fri, 11 Oct 2013 10:50:32 + with message-id e1vuaii-0007n4...@franck.debian.org and subject line Bug#713181: fixed in pam-shield 0.9.6-1.1 has caused the Debian Bug report #713181, regarding pam-shield: FTBFS: autoreconf: failed to run /usr/bin/aclocal-1.11: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pam-shield Version: 0.9.2-3.3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build QUILT_PATCHES=debian/patches \ quilt --quiltrc /dev/null push -a || test $? = 2 Applying patch automake.patch patching file Makefile.am patching file autogen.sh patching file configure.ac Applying patch pam_shield.patch patching file pam_shield.c Applying patch shield-trigger-iptables.patch patching file shield-trigger-iptables.sh Applying patch cron_fix.patch patching file pam_shield.cron Applying patch missing_dns.patch patching file pam_shield.c Now at patch missing_dns.patch touch debian/stamp-patched dh_clean Makefile sh ./autogen.sh Can't exec /usr/bin/aclocal-1.11: No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 326. autoreconf: failed to run /usr/bin/aclocal-1.11: No such file or directory make: *** [config.status] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/pam-shield_0.9.2-3.3_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: pam-shield Source-Version: 0.9.6-1.1 We believe that the bug you reported is fixed in the latest version of pam-shield, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane henr...@debian.org (supplier of updated pam-shield package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Oct 2013 17:23:17 +0900 Source: pam-shield Binary: libpam-shield Architecture: source amd64 Version: 0.9.6-1.1 Distribution: unstable Urgency: low Maintainer: Jonathan Niehof jtnie...@gmail.com Changed-By: Hideki Yamane henr...@debian.org Description: libpam-shield - locks out remote attackers trying password guessing Closes: 713181 Changes: pam-shield (0.9.6-1.1) unstable; urgency=low . * Non-maintainer upload. * Upload to unstable (probably last upload just avoids freeze) * debian/patches - add dont-specify-automake-and-autoconf-version.patch (Closes: #713181) Checksums-Sha1: 83e84880152d95a8679ef35b1dac36e33fd9c510 1811 pam-shield_0.9.6-1.1.dsc 4f6ddd398c739b097fd07f7dee6dbc28ea7d1cc1 5351 pam-shield_0.9.6-1.1.debian.tar.gz cd26ccabac548d2d16372f12b9e2cf03c95ca899 30406 libpam-shield_0.9.6-1.1_amd64.deb Checksums-Sha256: 8ec61cc2c2eba6dcaa20d49e97e265a1068d6af92090c77d83dc6d1de6668711 1811 pam-shield_0.9.6-1.1.dsc 265539e0928efafcb76b1b66f6818da6813c66f5cef22c8365bb0bcf10d20495 5351 pam-shield_0.9.6-1.1.debian.tar.gz 3fac5ec3e8d07e1a7413090ffb4850fa7fb13e84f5fc9e431a32a04c07848de7 30406 libpam-shield_0.9.6-1.1_amd64.deb Files: f644cbd6cb042237c317460f96f750aa 1811 admin optional pam-shield_0.9.6-1.1.dsc cc0fdea07f769390b40cf7aa3413fdce 5351 admin optional pam-shield_0.9.6-1.1.debian.tar.gz b525e24ac6577298aabc247cdd5b4b19 30406 admin optional libpam-shield_0.9.6-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCgAGBQJSUSGUAAoJEF0yjQgqqrFATFYP/RjUBFH57ARySAcOo4BnTzFX
Bug#707352: dee: diff for NMU version 1.0.10-3.1
On Fri, Oct 11, 2013 at 3:12 PM, Andrea Colangelo war...@ubuntu.com wrote:
I've prepared an NMU for dee (versioned as 1.0.10-3.1). Please find the
attached
debdiff, based on the fix suggested by pochu in his replies to this bug
report.
Go ahead with NMU!
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726039: djblets: CVE-2013-4409
Package: djblets Severity: grave Tags: security Justification: user security hole Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4409 for details. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713760: marked as done (boo: FTBFS: External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2))
Your message dated Fri, 11 Oct 2013 13:18:27 + with message-id e1vucbr-0004xb...@franck.debian.org and subject line Bug#713760: fixed in nant 0.92~rc1+dfsg-3 has caused the Debian Bug report #713760, regarding boo: FTBFS: External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: boo Version: 0.9.5~git20110729.r1.202a430-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build test -x debian/rules mkdir -p . if test -e /usr/share/misc/config.guess ; then \ for i in ./lib/antlr-2.7.5/scripts/config.guess ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.guess $i ; \ fi ; \ done ; \ fi if test -e /usr/share/misc/config.sub ; then \ for i in ./lib/antlr-2.7.5/scripts/config.sub ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.sub $i ; \ fi ; \ done ; \ fi test -d debian/patched || install -d debian/patched dpatch apply-all applying patch fix_boo.pc.in to ./ ... ok. dpatch cat-all patch-stampT mv -f patch-stampT patch-stamp nant -D:install.prefix=/usr -D:skip.vs=true NAnt 0.92 (Build 0.92.4526.0; rc1; 05/23/2012) Copyright (C) 2001-2012 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///«PKGBUILDDIR»/default.build Target framework: Mono 4.0 Profile Target(s) specified: all [property] Read-only property skip.vs cannot be overwritten. [property] Read-only property install.prefix cannot be overwritten. init: sign: [mkdir] Creating directory '/«PKGBUILDDIR»/build'. Boo.Lang: [csc] Compiling 59 files to '/«PKGBUILDDIR»/build/Boo.Lang.dll'. [csc] Cannot open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory. BUILD FAILED - 0 non-fatal error(s), 3 warning(s) /«PKGBUILDDIR»/default.build(521,4): External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2) Total time: 0.2 seconds. make: *** [debian/stamp-nant-build] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/boo_0.9.5~git20110729.r1.202a430-2_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: nant Source-Version: 0.92~rc1+dfsg-3 We believe that the bug you reported is fixed in the latest version of nant, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jo Shields direct...@apebox.org (supplier of updated nant package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Oct 2013 15:06:40 +0200 Source: nant Binary: nant Architecture: source all Version: 0.92~rc1+dfsg-3 Distribution: unstable Urgency: low Maintainer: Debian CLI Applications Team pkg-cli-apps-t...@lists.alioth.debian.org Changed-By: Jo Shields direct...@apebox.org Description: nant - build tool similar to Ant Closes: 713760 713768 Changes: nant (0.92~rc1+dfsg-3) unstable; urgency=low . * [93b6f15] Add debian/patches/ use_mono_mcs_common_compiler_infrastructure.patch (Cherry picked from
Bug#713768: marked as done (ikvm: FTBFS: External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2):)
Your message dated Fri, 11 Oct 2013 13:18:27 + with message-id e1vucbr-0004xf...@franck.debian.org and subject line Bug#713768: fixed in nant 0.92~rc1+dfsg-3 has caused the Debian Bug report #713768, regarding ikvm: FTBFS: External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2): to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ikvm Version: 7.0.4335.0+ds-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 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 `/«BUILDDIR»/ikvm-7.0.4335.0+ds' dh_clideps --exclude-moduleref=fusion --exclude-moduleref=winspool.drv \ --exclude-moduleref=secur32.dll --exclude-moduleref=ikvm-native-win32-x86 \ --exclude-moduleref=ikvm-native-win32-x64 dh_clideps: Warning! No Build-Depends(-Indep) on cli-common-dev (= 0.8~)! make[1]: Leaving directory `/«BUILDDIR»/ikvm-7.0.4335.0+ds' dh_installdeb -a dh_gencontrol -a dh_md5sums -a dh_builddeb -a dpkg-deb: building package `libikvm-native' in `../libikvm-native_7.0.4335.0+ds-1_amd64.deb'. nant -v -f:ikvm-7.0.4335.0/ikvm.build signed NAnt 0.92 (Build 0.92.4526.0; rc1; 05/23/2012) Copyright (C) 2001-2012 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/ikvm.build Target framework: Mono 4.0 Profile Base Directory: /«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0. Target(s) specified: signed [include] Including file /«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/ikvm.include. Function platform::is-win32 is deprecated. Use the is-windows function instead. signed: clean-managed: CommonAssemblyInfo: [copy] Copying 1 file to '/«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/CommonAssemblyInfo.cs'. [copy] Copying '/«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/CommonAssemblyInfo.cs.in' to '/«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/CommonAssemblyInfo.cs'. managed: [nant] /«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/tools.build Buildfile: file:///«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/tools.build Target framework: Mono 4.0 Profile Base Directory: /«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools. Target(s) specified: tools tools: [csc] Output file '/«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/asmref.exe' does not exist, rebuilding. [csc] Compiling 1 files to '/«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/asmref.exe'. [csc] Contents of /tmp/tmp12f6d70b.tmp. [csc] /fullpaths [csc] /optimize [csc] /nologo [csc] /target:exe [csc] /out:/«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/asmref.exe [csc] /«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/asmref.cs [csc] [csc] Starting '/usr/bin/mono ( /usr/lib/mono/4.0/dmcs.exe @/tmp/tmp12f6d70b.tmp)' in '/«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools' [csc] Cannot open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory. BUILD FAILED - 0 non-fatal error(s), 1 warning(s) /«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/tools.build(4,10): External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2): NAnt.Core.BuildException: /«BUILDDIR»/ikvm-7.0.4335.0+ds/ikvm-7.0.4335.0/tools/tools.build(4,10): External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2) at NAnt.Core.Tasks.ExternalProgramBase.ExecuteTask () [0x0] in filename unknown:0 Total time: 0.1 seconds. BUILD FAILED - 0 non-fatal error(s), 1 warning(s) Nested build failed. Refer to build log for exact reason.: NAnt.Core.BuildException: Nested build failed. Refer to build log for exact reason. at NAnt.Core.Tasks.NAntTask.RunBuild (System.IO.FileInfo buildFile) [0x0] in filename unknown:0 at NAnt.Core.Tasks.NAntTask.ExecuteTask ()
Bug#713617: marked as done (presage: FTBFS: ld: ./.libs/libscintilla.a(libscintilla_la-PlatGTK.o): undefined reference to symbol 'lroundf@@GLIBC_2.2.5')
Your message dated Fri, 11 Oct 2013 13:33:42 + with message-id e1vucqc-0006kz...@franck.debian.org and subject line Bug#713617: fixed in presage 0.8.9-1 has caused the Debian Bug report #713617, regarding presage: FTBFS: ld: ./.libs/libscintilla.a(libscintilla_la-PlatGTK.o): undefined reference to symbol 'lroundf@@GLIBC_2.2.5' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: presage Version: 0.8.8-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add explicitly the offending lib to LD flags. Relevant part: gcc -DHAVE_CONFIG_H -I. -I../../.. -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../../../src/lib -I./scintilla/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o gprompter-gprompter.o `test -f 'gprompter.c' || echo './'`gprompter.c /bin/bash ../../../libtool --tag=CC --mode=link gcc -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../../../src/lib -I./scintilla/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -L/usr/local/lib -Wl,-z,relro -o gprompter gprompter-gprompter.o -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -pthread -lgthread-2.0 -lglib-2.0 ../../../src/lib/libpresage.la libscintilla.la -lstdc++ libtool: link: gcc -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../../../src/lib -I./scintilla/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z -Wl,relro -o .libs/gprompter gprompter-gprompter.o -pthread -L/usr/local/lib ../../../src/lib/.libs/libpresage.so ./.libs/libscintilla.a -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 /usr/lib/x86_64-linux-gnu/libcairo.so -lpango-1.0 /usr/lib/x86_64-linux-gnu/libfreetype.so -lfontconfig -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lstdc++ -pthread /usr/bin/ld: ./.libs/libscintilla.a(libscintilla_la-PlatGTK.o): undefined reference to symbol 'lroundf@@GLIBC_2.2.5' /lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/presage_0.8.8-1_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: presage Source-Version: 0.8.9-1 We believe that the bug you reported is fixed in the latest version of presage, which is due to be installed in the Debian
Bug#726043: python-babel-doc: missing Breaks, Replaces: python-babel ( 1.3-1)
Package: python-babel-doc Version: 1.3-1 Severity: serious python-babel-doc took over /usr/share/doc-base/python-babel from python-babel in 1.3-1, but doesn't declare the appropriate Breaks, Replaces relationship. This makes python-babel-doc fail to install if python-babel 1.3-1 is installed: | Unpacking python-babel-doc (from .../python-babel-doc_1.3-1_all.deb) ... | dpkg: error processing /var/cache/apt/archives/python-babel-doc_1.3-1_all.deb (--unpack): | trying to overwrite '/usr/share/doc-base/python-babel', which is also in package python-babel 0.9.6-1 Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: moomin invasion
Processing commands for cont...@bugs.debian.org:
reassign 713762 nant
Bug #713762 [src:cecil-flowanalysis] cecil-flowanalysis: FTBFS: [csc] Cannot
open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory.
Bug reassigned from package 'src:cecil-flowanalysis' to 'nant'.
No longer marked as found in versions
cecil-flowanalysis/0.1~vcs20110809.r1.b34edf6-2.
Ignoring request to alter fixed versions of bug #713762 to the same values
previously set
reassign 713768 nant
Bug #713768 {Done: Jo Shields direct...@apebox.org} [src:ikvm] ikvm: FTBFS:
External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2):
Bug reassigned from package 'src:ikvm' to 'nant'.
No longer marked as found in versions ikvm/7.0.4335.0+ds-1.
No longer marked as fixed in versions nant/0.92~rc1+dfsg-3.
reassign 713760 nant
Bug #713760 {Done: Jo Shields direct...@apebox.org} [src:boo] boo: FTBFS:
External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2)
Bug reassigned from package 'src:boo' to 'nant'.
No longer marked as found in versions boo/0.9.5~git20110729.r1.202a430-2.
No longer marked as fixed in versions nant/0.92~rc1+dfsg-3.
fixed 713762 0.92~rc1+dfsg-3
Bug #713762 [nant] cecil-flowanalysis: FTBFS: [csc] Cannot open assembly
'/usr/lib/mono/4.0/dmcs.exe': No such file or directory.
Marked as fixed in versions nant/0.92~rc1+dfsg-3.
fixed 713768 0.92~rc1+dfsg-3
Bug #713768 {Done: Jo Shields direct...@apebox.org} [nant] ikvm: FTBFS:
External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2):
Marked as fixed in versions nant/0.92~rc1+dfsg-3.
fixed 713760 0.92~rc1+dfsg-3
Bug #713760 {Done: Jo Shields direct...@apebox.org} [nant] boo: FTBFS:
External Program Failed: /usr/lib/mono/4.0/dmcs.exe (return code was 2)
Marked as fixed in versions nant/0.92~rc1+dfsg-3.
End of message, stopping processing here.
Please contact me if you need assistance.
--
713760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713760
713762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713762
713768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713762: marked as done (cecil-flowanalysis: FTBFS: [csc] Cannot open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory.)
Your message dated Fri, 11 Oct 2013 16:04:15 +0200 with message-id 1381500255.4231.15.camel@barnabas and subject line moomin invasion has caused the Debian Bug report #713762, regarding cecil-flowanalysis: FTBFS: [csc] Cannot open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cecil-flowanalysis Version: 0.1~vcs20110809.r1.b34edf6-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build dh_testdir touch configure-stamp dh_testdir nant -v -buildfile:default.build -D:Mono.Cecil.dll=/usr/lib/mono-cecil/Mono.Cecil.dll \ -D:keyfile=debian/mono.snk NAnt 0.92 (Build 0.92.4526.0; rc1; 05/23/2012) Copyright (C) 2001-2012 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///«PKGBUILDDIR»/default.build Target framework: Mono 4.0 Profile Base Directory: /«PKGBUILDDIR». Target(s) specified: test [property] Read-only property Mono.Cecil.dll cannot be overwritten. [property] Read-only property keyfile cannot be overwritten. init: [mkdir] Creating directory '/«PKGBUILDDIR»/bin'. [copy] Copying 1 file to '/«PKGBUILDDIR»/bin'. [copy] Copying '/usr/lib/mono-cecil/Mono.Cecil.dll' to '/«PKGBUILDDIR»/bin'. build: [csc] Output file '/«PKGBUILDDIR»/bin/Cecil.FlowAnalysis.dll' does not exist, rebuilding. [csc] Compiling 46 files to '/«PKGBUILDDIR»/bin/Cecil.FlowAnalysis.dll'. [csc] Contents of /tmp/tmp4ec9b6c9.tmp. [csc] /fullpaths [csc] /debug [csc] /define:DEBUG [csc] /define:TRACE [csc] /nologo [csc] /target:library [csc] /define:NO_DEFINE [csc] /out:/«PKGBUILDDIR»/bin/Cecil.FlowAnalysis.dll [csc] /keyfile:/«PKGBUILDDIR»/debian/mono.snk [csc] /reference:/«PKGBUILDDIR»/bin/Mono.Cecil.dll [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/AbstractFallThroughActionBlock.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/ActionBlock.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/ActionFlowGraph.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/ActionFlowGraphBuilder.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/ActionType.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/AssignActionBlock.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/BranchActionBlock.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/ConditionalBranchActionBlock.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/ExpressionDecompiler.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/InvokeActionBlock.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/ActionFlow/ReturnActionBlock.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/AbstractCodeStructureVisitor.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/ArgumentReferenceExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/AssignExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/BinaryExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/BinaryOperator.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/BlockStatement.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/CastExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/CodeElementType.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/Expression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/ExpressionPrinter.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/FieldReferenceExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/ICodeElement.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/ICodeStructureVisitor.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/LiteralExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/MethodInvocationExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/MethodReferenceExpression.cs [csc] /«PKGBUILDDIR»/Cecil.FlowAnalysis/CodeStructure/PropertyReferenceExpression.cs [csc]
Processed: fear the moomin army
Processing commands for cont...@bugs.debian.org: fixed 708808 0.92~rc1+dfsg-3 Bug #708808 [src:nant] nant: FTBFS: [csc] Cannot open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory. Marked as fixed in versions nant/0.92~rc1+dfsg-3. thanks Stopping processing here. Please contact me if you need assistance. -- 708808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708808: marked as done (nant: FTBFS: [csc] Cannot open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory.)
Your message dated Fri, 11 Oct 2013 16:34:17 +0200 with message-id 1381502057.4231.16.camel@barnabas and subject line fear the moomin army has caused the Debian Bug report #708808, regarding nant: FTBFS: [csc] Cannot open assembly '/usr/lib/mono/4.0/dmcs.exe': No such file or directory. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 708808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: nant Version: 0.92~rc1+dfsg-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130517 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[2]: Entering directory `/«BUILDDIR»/nant-0.92~rc1+dfsg' mkdir -p bootstrap # Mono loads log4net before privatebinpath is set-up, so we need this in the same directory # as NAnt.exe cp src/NAnt.Console/App.config bootstrap/NAnt.exe.config /usr/bin/mono-csc -target:exe -define:MONO,NET_1_0,NET_1_1,NET_2_0,NET_3_5,NET_4_0,ONLY_4_0 -out:bootstrap/NAnt.exe -pkg:log4net \ -r:System.Configuration.dll -recurse:src/NAnt.Console/*.cs src/CommonAssemblyInfo.cs src/NAnt.Console/ConsoleStub.cs(415,45): warning CS0618: `System.AppDomain.AppendPrivatePath(string)' is obsolete: `AppDomain.AppendPrivatePath has been deprecated. Please investigate the use of AppDomainSetup.PrivateBinPath instead.' src/NAnt.Console/ConsoleStub.cs(423,49): warning CS0618: `System.AppDomain.AppendPrivatePath(string)' is obsolete: `AppDomain.AppendPrivatePath has been deprecated. Please investigate the use of AppDomainSetup.PrivateBinPath instead.' Compilation succeeded - 2 warning(s) resgen src/NAnt.Core/Resources/Strings.resx bootstrap/NAnt.Core.Resources.Strings.resources Read in 198 resources from '/«BUILDDIR»/nant-0.92~rc1+dfsg/src/NAnt.Core/Resources/Strings.resx' Writing resource file... Done. /usr/bin/mono-csc -target:library -warn:0 -define:MONO,NET_1_0,NET_1_1,NET_2_0,NET_3_5,NET_4_0,ONLY_4_0 -out:bootstrap/NAnt.Core.dll -debug \ -resource:bootstrap/NAnt.Core.Resources.Strings.resources -pkg:log4net \ -r:System.Web.dll -recurse:src/NAnt.Core/*.cs src/CommonAssemblyInfo.cs resgen src/NAnt.DotNet/Resources/Strings.resx bootstrap/NAnt.DotNet.Resources.Strings.resources Read in 77 resources from '/«BUILDDIR»/nant-0.92~rc1+dfsg/src/NAnt.DotNet/Resources/Strings.resx' Writing resource file... Done. /usr/bin/mono-csc -target:library -warn:0 -define:MONO,NET_1_0,NET_1_1,NET_2_0,NET_3_5,NET_4_0,ONLY_4_0 -out:bootstrap/NAnt.DotNetTasks.dll \ -r:./bootstrap/NAnt.Core.dll \ -recurse:src/NAnt.DotNet/*.cs -resource:bootstrap/NAnt.DotNet.Resources.Strings.resources \ src/CommonAssemblyInfo.cs /usr/bin/mono-csc -target:library -warn:0 -define:MONO,NET_1_0,NET_1_1,NET_2_0,NET_3_5,NET_4_0,ONLY_4_0 -out:bootstrap/NAnt.CompressionTasks.dll \ -r:./bootstrap/NAnt.Core.dll -r:ICSharpCode.SharpZipLib.dll \ -recurse:src/NAnt.Compression/*.cs src/CommonAssemblyInfo.cs /usr/bin/cli bootstrap/NAnt.exe -t:mono-4.0 -f:NAnt.build build NAnt 0.92 (Build 0.92.4526.0; rc1; 05/23/2012) Copyright (C) 2001-2012 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///«BUILDDIR»/nant-0.92~rc1+dfsg/NAnt.build Target framework: Mono 4.0 Profile Target(s) specified: build [tstamp] Friday, 17 May 2013 20:30:38. init: debug: set-framework-configuration: set-mono-4.0-framework-configuration: build: [echo] Build Directory is /«BUILDDIR»/nant-0.92~rc1+dfsg/build/mono-4.0.unix/nant-debug [mkdir] Creating directory '/«BUILDDIR»/nant-0.92~rc1+dfsg/build/mono-4.0.unix/nant-debug/bin'. [mkdir] Creating directory '/«BUILDDIR»/nant-0.92~rc1+dfsg/build/mono-4.0.unix/nant-debug/bin/lib'. [copy] Copying 1 file to '/«BUILDDIR»/nant-0.92~rc1+dfsg/build/mono-4.0.unix/nant-debug/bin/lib'. [nant] /«BUILDDIR»/nant-0.92~rc1+dfsg/src/NAnt.Core/NAnt.Core.build build Buildfile: file:///«BUILDDIR»/nant-0.92~rc1+dfsg/src/NAnt.Core/NAnt.Core.build Target framework: Mono 4.0 Profile Target(s) specified: build build: [csc] Compiling 178 files to '/«BUILDDIR»/nant-0.92~rc1+dfsg/build/mono-4.0.unix/nant-debug/bin/NAnt.Core.dll'. [resgen] Read in 198 resources from
Bug#708405: marked as done (Rebuilding looses /usr/share/java/geronimo-jta_1.1_spec-1.1.1.jar from package)
Your message dated Fri, 11 Oct 2013 16:40:56 +0200 with message-id 52580df8.1020...@gambaru.de and subject line Rebuilding looses /usr/share/java/geronimo-jta_1.1_spec-1.1.1.jar from package has caused the Debian Bug report #708405, regarding Rebuilding looses /usr/share/java/geronimo-jta_1.1_spec-1.1.1.jar from package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 708405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jetty Version: 6.1.26-1 Severity: serious Justification: fails to build from source (but built successfully in the past) I am trying to create a small subset of wheezy that is self contained, and as part of building things, jetty failed to build. Strangely it looks a lot like an old bug #642783, although that was supposedly fixed by an update to geronimo, and the fixed version of that is what is in wheezy. I can provide the build log if that would help, but the error seen is: [javadoc] Constructing Javadoc information... [javadoc] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:19: cannot find symbol [javadoc] symbol : class UserTransaction [javadoc] location: package javax.transaction [javadoc] import javax.transaction.UserTransaction; [javadoc] ^ [javadoc] Standard Doclet version 1.6.0_27 [javadoc] Building tree for all the packages and classes... [javadoc] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:58: cannot find symbol [javadoc] symbol : class UserTransaction [javadoc] location: class org.mortbay.jetty.plus.naming.Transaction [javadoc] public Transaction (UserTransaction userTransaction) [javadoc] ^ and [javac] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:19: cannot find symbol [javac] symbol : class UserTransaction [javac] location: package javax.transaction [javac] import javax.transaction.UserTransaction; [javac] ^ [javac] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:58: cannot find symbol [javac] symbol : class UserTransaction [javac] location: class org.mortbay.jetty.plus.naming.Transaction [javac] public Transaction (UserTransaction userTransaction) [javac] ^ [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors Any idea what the problem is and how to fix it? -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 1.1.1-3 Tags: jessie sid I have rebuilt geronimo-jta-1.1-spec 1.1.1-3 in a clean chroot environment but I cannot reproduce the problem neither in wheezy nor in sid. I assume the latest revision of geronimo-jta-1.1-spec and the fix for #688043 solved the issue completely. Hence I'm closing this bug report now. Markus signature.asc Description: OpenPGP digital signature ---End Message---
Bug#725004: marked as done (haskell-cryptocipher: FTBFS on big-endian archs)
Your message dated Fri, 11 Oct 2013 15:08:01 +
with message-id 20131011150801.ga14...@scru.org
and subject line irrelevant
has caused the Debian Bug report #725004,
regarding haskell-cryptocipher: FTBFS on big-endian archs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
725004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: haskell-cryptocipher
Version: 0.5.2-1
Severity: serious
Hi,
The buildd logs all appear to have a log that looks something like:
*** Failed! Falsifiable (after 1 test):
DESEDE2Message ~\134\162\184\232O\193\150n{#\180m\SYNi\240
3;\157\243Q\a\SYN\SOH6[\138D\129Og\134\143m\rWE8\188\157k7Y\171A\n\DC1
j\248\217e\166O|c
(used seed 9713386)
DES-EDE2 (CTR): [OK, passed 100 tests]
DES-EDE2 (CFB): [OK, passed 100 tests]
DES-EDE2 (OFB): [OK, passed 100 tests]
Properties Total
Passed 15 15
Failed 88
Total 23 23
Test suite test-cryptocipher: FAIL
Test suite logged to: dist-ghc/test/cryptocipher-0.5.2-test-cryptocipher.log
0 of 1 test suites (0 of 1 test cases) passed.
make: *** [check-ghc-stamp] Error 1
These build failures are currently preventing haskell-cryptocipher
from migrating to testing (and quite possibly blocking several other
haskell packages as well).
~Niels
---End Message---
---BeginMessage---
haskell-cryptocipher now builds regardless of endianness
Whether or not it's buggy on BE is a different question.---End Message---
Bug#716859: marked as done (pdns-server: fails to install: chmod: cannot access '/etc/powerdns/pdns.d/pdns.local.conf': No such file or directory)
Your message dated Fri, 11 Oct 2013 15:23:56 + with message-id e1vuezi-0004xu...@franck.debian.org and subject line Bug#716859: fixed in pdns 3.3-1 has caused the Debian Bug report #716859, regarding pdns-server: fails to install: chmod: cannot access '/etc/powerdns/pdns.d/pdns.local.conf': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 716859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pdns-server Version: 3.3-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package pdns-server. (Reading database ... 6715 files and directories currently installed.) Unpacking pdns-server (from .../pdns-server_3.3-1~exp1_amd64.deb) ... Setting up pdns-server (3.3-1~exp1) ... Creating user and group pdns...done Creating config file /etc/powerdns/pdns.d/pdns.local.conf with new version Creating config file /etc/powerdns/pdns.d/pdns.simplebind.conf with new version Creating config file /etc/powerdns/pdns.conf with new version Creating config file /etc/default/pdns with new version Not replacing deleted config file /etc/powerdns/pdns.d/pdns.local.conf Not replacing deleted config file /etc/powerdns/pdns.d/pdns.simplebind.conf chmod: cannot access '/etc/powerdns/pdns.d/pdns.local.conf': No such file or directory dpkg: error processing pdns-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: pdns-server cheers, Andreas pdns-server_3.3-1~exp1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: pdns Source-Version: 3.3-1 We believe that the bug you reported is fixed in the latest version of pdns, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 716...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthijs Möhlmann matth...@cacholong.nl (supplier of updated pdns package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 13 Jul 2013 14:30:30 + Source: pdns Binary: pdns-server pdns-server-dbg pdns-backend-pipe pdns-backend-ldap pdns-backend-geo pdns-backend-mysql pdns-backend-pgsql pdns-backend-sqlite3 pdns-backend-lua Architecture: source amd64 Version: 3.3-1 Distribution: unstable Urgency: low Maintainer: Debian PowerDNS Maintainers pkg-pdns-maintain...@lists.alioth.debian.org Changed-By: Matthijs Möhlmann matth...@cacholong.nl Description: pdns-backend-geo - geo backend for PowerDNS pdns-backend-ldap - LDAP backend for PowerDNS pdns-backend-lua - lua backend for PowerDNS pdns-backend-mysql - generic MySQL backend for PowerDNS pdns-backend-pgsql - generic PostgreSQL backend for PowerDNS pdns-backend-pipe - pipe/coprocess backend for PowerDNS pdns-backend-sqlite3 - sqlite 3 backend for PowerDNS pdns-server - extremely powerful and versatile nameserver pdns-server-dbg - debugging symbols for PowerDNS Closes: 374779 685808 698911 707761 708861 710360 714145 716859 717356 718713 725073 725195 Changes: pdns (3.3-1) unstable; urgency=low . * The Habbie saves the World release . [ Matthijs Möhlmann ] . * Standards-Version: 3.9.4 (no changes needed) * Move files used by dbconfig-common to /usr/share/PACKAGE (Closes: #710360) * Upstream fixes self notification (Closes: #374779) * Added Brazilian Portuguese translation, thanks to Adriano Rafael Gomes (Closes: #718713) * All other nameservers are optional in insserv, so make that happen for pdns too. (Closes: #714145) * Update the default schema for the PostgreSQL backend (Closes: #698911) * Reworked README fixes also #717356 (Closes: #717356) * Add a SQL script for updating the database scheme in PostgreSQL, this will be applied automatically by
Bug#710360: marked as done (pdns-backend-sqlite{,3}: postinst uses /usr/share/doc content (Policy 12.3))
Your message dated Fri, 11 Oct 2013 15:23:56 +
with message-id e1vuezi-0004xg...@franck.debian.org
and subject line Bug#710360: fixed in pdns 3.3-1
has caused the Debian Bug report #710360,
regarding pdns-backend-sqlite{,3}: postinst uses /usr/share/doc content (Policy
12.3)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
710360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pdns-backend-sqlite,pdns-backend-sqlite3
Version: 3.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: Packages must not require the existence of any files in
/usr/share/doc/ in order to function.
http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3
These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.
This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.
From the attached log (scroll to the bottom...):
Selecting previously unselected package pdns-backend-sqlite.
(Reading database ... 7123 files and directories currently installed.)
Unpacking pdns-backend-sqlite (from .../pdns-backend-sqlite_3.1-4_amd64.deb)
...
Setting up pdns-backend-sqlite (3.1-4) ...
dbconfig-common: writing config to
/etc/dbconfig-common/pdns-backend-sqlite.conf
Creating config file /etc/dbconfig-common/pdns-backend-sqlite.conf with new
version
error: template infile
/usr/share/doc/pdns-backend-sqlite/examples/pdns.local.gsqlite does not exist
dpkg: error processing pdns-backend-sqlite (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pdns-backend-sqlite
Selecting previously unselected package pdns-backend-sqlite3.
(Reading database ... 7116 files and directories currently installed.)
Unpacking pdns-backend-sqlite3 (from
.../pdns-backend-sqlite3_3.1-4_amd64.deb) ...
Setting up pdns-backend-sqlite3 (3.1-4) ...
dbconfig-common: writing config to
/etc/dbconfig-common/pdns-backend-sqlite3.conf
Creating config file /etc/dbconfig-common/pdns-backend-sqlite3.conf with new
version
error: template infile
/usr/share/doc/pdns-backend-sqlite3/examples/pdns.local.gsqlite3 does not exist
dpkg: error processing pdns-backend-sqlite3 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pdns-backend-sqlite3
Cheers,
Andreas
pdns-backend-sqlite3_3.1-4.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: pdns
Source-Version: 3.3-1
We believe that the bug you reported is fixed in the latest version of
pdns, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 710...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthijs Möhlmann matth...@cacholong.nl (supplier of updated pdns package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 13 Jul 2013 14:30:30 +
Source: pdns
Binary: pdns-server pdns-server-dbg pdns-backend-pipe pdns-backend-ldap
pdns-backend-geo pdns-backend-mysql pdns-backend-pgsql pdns-backend-sqlite3
pdns-backend-lua
Architecture: source amd64
Version: 3.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian PowerDNS Maintainers
pkg-pdns-maintain...@lists.alioth.debian.org
Changed-By: Matthijs Möhlmann matth...@cacholong.nl
Description:
pdns-backend-geo - geo backend for PowerDNS
pdns-backend-ldap - LDAP backend for PowerDNS
pdns-backend-lua - lua backend for PowerDNS
pdns-backend-mysql - generic MySQL backend for PowerDNS
pdns-backend-pgsql - generic PostgreSQL backend for PowerDNS
pdns-backend-pipe - pipe/coprocess backend for PowerDNS
pdns-backend-sqlite3 - sqlite 3 backend for PowerDNS
pdns-server - extremely powerful and versatile nameserver
pdns-server-dbg - debugging symbols for PowerDNS
Closes: 374779 685808 698911 707761 708861
Bug#714063: marked as done (translate-toolkit: build-depends on obsolete package python-aeidon)
Your message dated Fri, 11 Oct 2013 15:27:09 + with message-id e1vuecp-0004sa...@franck.debian.org and subject line Bug#714063: fixed in translate-toolkit 1.10.0-2 has caused the Debian Bug report #714063, regarding translate-toolkit: build-depends on obsolete package python-aeidon to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 714063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: translate-toolkit Version: 1.10.0-1 Severity: serious translate-toolkit build-depends on the obsolete package python-aeidon. gaupol now only builds a python3 version (python3-aeidon). Ansgar ---End Message--- ---BeginMessage--- Source: translate-toolkit Source-Version: 1.10.0-2 We believe that the bug you reported is fixed in the latest version of translate-toolkit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 714...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stuart Prescott stu...@debian.org (supplier of updated translate-toolkit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 12 Oct 2013 00:30:10 +1100 Source: translate-toolkit Binary: translate-toolkit Architecture: source all Version: 1.10.0-2 Distribution: unstable Urgency: low Maintainer: Debian l10n developers debian-l10n-de...@lists.alioth.debian.org Changed-By: Stuart Prescott stu...@debian.org Description: translate-toolkit - Toolkit assisting in the localization of software Closes: 714063 Changes: translate-toolkit (1.10.0-2) unstable; urgency=low . * Remove build and runtime dependencies on obsolete package python-aeidon (Closes: #714063) Checksums-Sha1: 9d24f465f6f0b8848c83aeaa57b3bbc44f8bc89d 1677 translate-toolkit_1.10.0-2.dsc 4c4645294ca2bcf4fc8eb33422d6f93503662f4d 103652 translate-toolkit_1.10.0-2.debian.tar.gz 8440e36c7c7d4883fa0ba46a280fd7910c14dc6f 1166314 translate-toolkit_1.10.0-2_all.deb Checksums-Sha256: 4e5d5dc8a50b7a5ef4f45a7b3a10162d1bf919e1c901314b1417b42018adf8f1 1677 translate-toolkit_1.10.0-2.dsc 775be065a19598be98e934af8285350c59619f364ffeb9f51740b43d5867c54b 103652 translate-toolkit_1.10.0-2.debian.tar.gz b23b70281253c4db8643370d05f0c9550203100be5ebc87cc7691f55152017bb 1166314 translate-toolkit_1.10.0-2_all.deb Files: 7487567bb33bd4337a46bdbb7c092967 1677 python optional translate-toolkit_1.10.0-2.dsc d94d25a74c228189e3276eee129479b8 103652 python optional translate-toolkit_1.10.0-2.debian.tar.gz 5e6110095d0c7dbf2cd9744a79569e07 1166314 python optional translate-toolkit_1.10.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlJYA1YACgkQn+i4zXHF0ajXOACffZzXdw4U9zhUGzBs5cd8t3IQ 09oAnjfI1eIxGhUgW9XA7s3LN6xrSZ05 =La2m -END PGP SIGNATUREEnd Message---
Bug#726050: linux-user-chroot: FTBFS: Invalid configuration `totools-dev'
Source: linux-user-chroot Version: 2013.1-1 Severity: serious Justification: fails to build from source Builds of linux-user-chroot have been failing, apparently due to a stray space in dh's invocation: dh build-arch --with autoreconf, autotools-dev [...] dh_auto_configure -aautotools-dev [...] Invalid configuration `totools-dev': machine `totools' not recognized configure: error: /bin/bash build-aux/config.sub totools-dev failed Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 725004 in 0.6.1-1
Processing commands for cont...@bugs.debian.org:
fixed 725004 0.6.1-1
Bug #725004 {Done: Clint Adams cl...@debian.org} [haskell-cryptocipher]
haskell-cryptocipher: FTBFS on big-endian archs
There is no source info for the package 'haskell-cryptocipher' at version
'0.6.1-1' with architecture ''
Unable to make a source version for version '0.6.1-1'
Marked as fixed in versions 0.6.1-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
725004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692739: gdm3/experimental: FTBFS on kfreebsd-any, needs porting and testing
On Thu, 08 Nov 2012 at 12:18:22 +, Simon McVittie wrote: Alternatively, someone could implement g_credentials_get_unix_pid(), which clearly ought to exist anyway, and would move the problem into GIO. (GNOME #687920.) I did that, and it's available in glib2.0/unstable (2.36). Using it in gdm is left as an exercise to the reader^W^Wsomeone who can test it :-) halfline said on https://bugzilla.gnome.org/show_bug.cgi?id=687921 that he'd accept a patch. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jnr-netdb: FTBFS: tests failed
Processing commands for cont...@bugs.debian.org: reassign 712695 src:jnr-netdb Bug #712695 [jnr-netdb] jnr-netdb FTBFS:some tests failed on mips Bug reassigned from package 'jnr-netdb' to 'src:jnr-netdb'. No longer marked as found in versions 1.0.3-2. Ignoring request to alter fixed versions of bug #712695 to the same values previously set forcemerge 712695 713781 Bug #712695 [src:jnr-netdb] jnr-netdb FTBFS:some tests failed on mips Bug #713781 [src:jnr-netdb] jnr-netdb: FTBFS: tests failed Added tag(s) wheezy. Bug #712695 [src:jnr-netdb] jnr-netdb FTBFS:some tests failed on mips Marked as found in versions jnr-netdb/1.0.3-2. Added tag(s) sid and jessie. Merged 712695 713781 thanks Stopping processing here. Please contact me if you need assistance. -- 712695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712695 713781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724935: Imaging experts opinion wanted: Should we keep ctn?
Hi, On Tue, Jul 16, 2013 at 12:04:09PM +0200, Mathieu Malaterre wrote: On Tue, Jul 16, 2013 at 9:04 AM, Andreas Tille andr...@an3as.eu wrote: I remember that I had a hard time when I updated ctn the last time which was five years ago. Upstream did not even issued a new version since ten years. So I wonder what you might think about ctn: Should I simply update the package to todays Debian standards of packaging or is this rather a waste of time and we have better software to deal with the tasks that could be done with ctn? I think we should move on to mirctn: https://sourceforge.net/projects/mirctn/files/mirctn/ AFAIK ctn from debian and mirctn are compatible, mainly thanks to: http://patch-tracker.debian.org/patch/series/view/ctn/3.0.6-13/20_mysql_4.2.patch CTN may not be as active as dcmtk, but still being used AFAIK. Any volunteer for this? Specifically since #724935 ctn is in danger to be removed and I somehow do not feel my time spent very well to sort out issues like this on unmaintained software like ctn. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712695: jnr-netdb: FTBFS: tests failed
tags 712695 - wheezy thanks Wheezy is not affected. The package builds just fine. signature.asc Description: OpenPGP digital signature
Bug#726057: msr-tools and cpuid: error when trying to install together
Package: cpuid,msr-tools Version: cpuid/20130610-2 Version: msr-tools/1.3-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-10-11 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package cpuid. (Reading database ... 10879 files and directories currently installed.) Unpacking cpuid (from .../cpuid_20130610-2_amd64.deb) ... Selecting previously unselected package msr-tools. Unpacking msr-tools (from .../msr-tools_1.3-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/msr-tools_1.3-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/cpuid.1.gz', which is also in package cpuid 20130610-2 dpkg: unrecoverable fatal error, aborting: unable to install updated status of `msr-tools': No such file or directory This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/man/man1/cpuid.1.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jnr-netdb: FTBFS: tests failed
Processing commands for cont...@bugs.debian.org: tags 712695 - wheezy Bug #712695 [src:jnr-netdb] jnr-netdb FTBFS:some tests failed on mips Bug #713781 [src:jnr-netdb] jnr-netdb: FTBFS: tests failed Removed tag(s) wheezy. Removed tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 712695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712695 713781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
Processing commands for cont...@bugs.debian.org: severity 726009 wishlist Bug #726009 [src:yade] yade: FTBFS on i386 (and others) Severity set to 'wishlist' from 'serious' retitle 726009 Yade requires too much RAM for building Bug #726009 [src:yade] yade: FTBFS on i386 (and others) Changed Bug title to 'Yade requires too much RAM for building' from 'yade: FTBFS on i386 (and others)' thanks Stopping processing here. Please contact me if you need assistance. -- 726009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726009: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
severity 726009 wishlist retitle 726009 Yade requires too much RAM for building thanks Hello, thanks for bug-report. The problem is, that all build-failures are due to insufficient RAM on build-machines [1]. I do not really know how to fix that except of backlisting of some machines, as was suggested by Julien [2]. The same package builds fine on Launchpad's PPA. It seems, the package builds only on machines, where 4Gb RAM is available. Thus I am reducing the bug's severity and CC-ing -devel with the hope to get dome more ideas how to fix the problem. I am also one of upstream-authors of this software and during last several years we did not add to the code something, what can sufficiently increase RAM-consumption. [1] https://buildd.debian.org/status/package.php?p=yade [2] https://lists.debian.org/debian-science/2013/10/msg7.html Thanks, Anton On 10/11/2013 09:12 AM, Ralf Treinen wrote: Source: yade Version: 1.00.0-2 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hello, yade 1.00.0-2 FTBFS on the i396 autobuilder with message: /usr/bin/c++ -Dyade_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DYADE_PTR_CAST=static_pointer_cast -DYADE_CAST=static_cast -fPIC -DYADE_VTK -DYADE_OPENMP -fopenmp -DYADE_GTS -DQGLVIEWER_FOUND -DYADE_OPENGL -frounding-math -DYADE_CGAL -DFLOW_ENGINE -frounding-math -DLINSOLV -DFLOW_ENGINE -DYADE_GL2PS -O3 -DNDEBUG -fPIC -I/usr/lib/pymodules/python2.7/numpy/core/include -I/usr/include/eigen3 -I/usr/include/vtk-5.8 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/Qt3Support -I/usr/include/q t4/QtGui -I/usr/include/qt4/QtCore -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/usr/include/suitesparse -I/usr/include/python2.7 -I/usr/include/i386-linux-gnu/python2.7 -I/«PKGBUILDDIR»/extra/floating_point_utilities_v3 -I/«PKGBUILDDIR»/debian/build-o CMakeFiles/yade.dir/pkg/dem/DomainLimiter.cpp.o -c /«PKGBUILDDIR»/pkg/dem/DomainLimiter.cpp virtual memory exhausted: Cannot allocate memory make[3]: *** [CMakeFiles/yade.dir/pkg/dem/DomainLimiter.cpp.o] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/debian/build' make[2]: *** [CMakeFiles/yade.dir/all] Error 2 make[2]: Leaving directory `/«PKGBUILDDIR»/debian/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»/debian/build' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 See https://buildd.debian.org/status/fetch.php?pkg=yadearch=i386ver=1.00.0-2stamp=1380696072 There are also build failures on other architectures. -Ralf. signature.asc Description: OpenPGP digital signature
Bug#713510: derivations: FTBFS: /usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks.tex:101: I can't find file `pgfutil-common.tex'.
Hi,
El Jueves, 10 de octubre de 2013 22:31:57 Lucas Nussbaum escribió:
On 10/10/13 at 21:36 +0200, Bill Allombert wrote:
On Thu, Oct 10, 2013 at 08:52:36PM +0200, Lucas Nussbaum wrote:
On 10/10/13 at 18:21 +0200, Bill Allombert wrote:
On Sat, Jun 22, 2013 at 03:50:10PM +0200, Lucas Nussbaum wrote:
Source: derivations
Version: 0.53.20120414-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 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[2]: Entering directory `/«PKGBUILDDIR»/tex'
sed derivations-book.cls
/usr/share/texlive/texmf-dist/tex/latex/base/book.cls \
-e
's/^\(\\ProvidesClass{\)book\(}\)[[:space:]]*$/\1deriva
tions-book\2/' \
-e
's/^\(\\newcommand\*\\l@section{\\@dottedtocline{1}{\)\([^{}]*
\)\(}{\)\([^{}]*\)\(}}\)[[:space:]]*$/\1\2\32.5em\5/' \ -e
's/^\(\\newcommand\*\\l@subsection{\\@dottedtocline{2}{\)\([^{
}]*\)\(}{\)\([^{}]*\)\(}}\)[[:space:]]*$/\14.0em\33.3em\5/' \
-e
's/^\(\\newcommand\*\\l@subsubsection{\\@dottedtocline{3}{\)\(
[^{}]*\)\(}{\)\([^{}]*\)\(}}\)[[:space:]]*$/\17.3em\3\4\5/'
rubber main.tex
compiling main.tex...
/usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks.tex:10
1: I can't find file `pgfutil-common.tex'.
/usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks.tex:1
01: leading text: \input pgfutil-common.tex make[2]: ***
[derivations.dvi] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/derivations_0.53
.20120414-1.1_unstable.log
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!
Could you retry it ? As far as I see this bug is fixed in
texlive-pstricks 2013.20130722-1, see bug #713791:
the package Build-Depends on texlive-pstricks which depends on pgf
which
contains pgfutil-common.tex.
At least I cannot reproduce it.
The package buils ok now.
I can't retry easily, so I'm closely the bug, and assuming it will be
reopened in the future if it's reproducible.
Could you grep yours build logs for similar reports ?
(grepping for pgfutil-common.tex should do)
I can't find anything related in failed build logs.
Thanks
David
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724152: marked as done (axiom: FTBFS: cp: cannot stat '/«PKGBUILDDIR»/int/interp/bookvol5.lsp': No such file or directory)
Your message dated Fri, 11 Oct 2013 21:11:38 +0200 with message-id 2353954.QLyEEESCIR@sephirot and subject line Re: Bug#724152: axiom: FTBFS: cp: cannot stat '/«PKGBUILDDIR»/int/interp/bookvol5.lsp': No such file or directory has caused the Debian Bug report #724152, regarding axiom: FTBFS: cp: cannot stat '/«PKGBUILDDIR»/int/interp/bookvol5.lsp': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: axiom Version: 20120501-10 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): 298 making /«PKGBUILDDIR»/int/interp/bookvol5.lsp from /«PKGBUILDDIR»/src/interp/bookvol5.pamphlet GCL (GNU Common Lisp) 2.6.9 CLtL1Aug 28 2013 17:00:47 Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl) Binary License: GPL due to GPL'ed components: (XGCL READLINE UNEXEC) Modifications of this banner must retain notice of a compatible license Dedicated to the memory of W. Schelter Use (help) to get some basic information on how to use GCL. Temporary directory for compiler files set to /«PKGBUILDDIR»/obj/tmp/ making /«PKGBUILDDIR»/obj/linux/interp/bookvol5.lsp from /«PKGBUILDDIR»/int/interp/bookvol5.lsp cp: cannot stat '/«PKGBUILDDIR»/int/interp/bookvol5.lsp': No such file or directory make[4]: *** [/«PKGBUILDDIR»/obj/linux/interp/bookvol5.lsp] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/axiom_20120501-10_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Hi, El Jueves, 10 de octubre de 2013 13:38:05 Bill Allombert escribió: axiom 20120501-11 was built correctly on nearly all architectures on 2013-10-03, so it seems this bux is fixed in 20120501-11 and should be closed. Closing it. Very much thanks Bill :) Thanks David ---End Message---
Processed: Re: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
Processing commands for cont...@bugs.debian.org: severity 726009 serious Bug #726009 [src:yade] Yade requires too much RAM for building Severity set to 'serious' from 'wishlist' thanks Stopping processing here. Please contact me if you need assistance. -- 726009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711627: [PATCH] fix t/05-scoping.t with hash random problem; review please
Hi,
I think this actually fixes the problem, but if someone more confident than me
can confirm I would go ahead preparing a release and mailing upstream.
Regards,
cstamas
---
debian/patches/hash-random-test-fix.patch | 16
debian/patches/series |1 +
2 files changed, 17 insertions(+)
create mode 100644 debian/patches/hash-random-test-fix.patch
diff --git a/debian/patches/hash-random-test-fix.patch
b/debian/patches/hash-random-test-fix.patch
new file mode 100644
index 000..9a2fd89
--- /dev/null
+++ b/debian/patches/hash-random-test-fix.patch
@@ -0,0 +1,16 @@
+Description: hash random test case fix
+Author: CSILLAG Tamas csta...@cstamas.hu
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711627
+Last-Update: 2013-10-11
+
+--- libyaml-appconfig-perl-0.16.orig/t/05-scoping.t
libyaml-appconfig-perl-0.16/t/05-scoping.t
+@@ -43,7 +43,7 @@ BEGIN { use_ok('YAML::AppConfig') }
+ like( $@, qr/Circular reference in simple_circ/,
+ Checking circular dynamic variables. );
+ eval {$app-get_circ};
+-like( $@, qr/Circular reference in prolog/,
++like( $@, qr/Circular reference in (?:prolog|circ|cows_are_good)/,
+ Checking circular dynamic variables. );
+ eval {$app-get_bigcirc};
+ like( $@, qr/Circular reference in thing/,
diff --git a/debian/patches/series b/debian/patches/series
index fc442a8..41af9b2 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
no-UNIVERSAL-import.patch
fix-POD-errors.patch
qw-parenthesis.patch
+hash-random-test-fix.patch
--
1.7.10.4
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726009: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
On Fri, Oct 11, 2013 at 12:32:27PM -0700, Steve Langasek wrote: severity 726009 serious thanks This remains a serious bug. Your package, which previously built on multiple architectures, is now failing to build due to memory exhaustion. While in some circumstances it is permissible to remove the old binaries and drop support for an architecture, this remains a serious bug until this has been done. (And anyway, your package won't reach testing in the current state, so is de facto unreleasable.) On Fri, Oct 11, 2013 at 09:00:36PM +0200, Anton Gladky wrote: severity 726009 wishlist retitle 726009 Yade requires too much RAM for building thanks thanks for bug-report. The problem is, that all build-failures are due to insufficient RAM on build-machines [1]. I do not really know how to fix that except of backlisting of some machines, as was suggested by Julien [2]. The same package builds fine on Launchpad's PPA. It seems, the package builds only on machines, where 4Gb RAM is available. This diagnosis is incorrect. The error you are hitting here is not that you are exhausting the available memory on the machine, it's that you're exhausting the *address space* on the machine. Adding more memory to the buildd would have zero effect, because you're on a 32-bit system which has a limit of 4GB of address space anyway. (In practice, I believe this is 3GB for userspace and 1GB for kernel on i386.) I've explained this same thing to people before. All i386 buildds are now actually running on an amd64 hosts with an amd64 kernel. All of them have more than 4 GB available except from brahms which only as 2 GB + 512 MB of swap. The buildds it failed on (babin, biber) each have 8 GB of RAM available. With an amd64 kernel, i386 userspace can actually use 4 GB, which is more than it can on a real i386 host. If you fix it on the other buildds and it still fails on brahms I can either ask DSA to give more RAM to it or I can exclude the package there. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726009: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
On 11 October 2013 20:32, Steve Langasek vor...@debian.org wrote: severity 726009 serious thanks This remains a serious bug. Your package, which previously built on multiple architectures, is now failing to build due to memory exhaustion. While in some circumstances it is permissible to remove the old binaries and drop support for an architecture, this remains a serious bug until this has been done. (And anyway, your package won't reach testing in the current state, so is de facto unreleasable.) On Fri, Oct 11, 2013 at 09:00:36PM +0200, Anton Gladky wrote: severity 726009 wishlist retitle 726009 Yade requires too much RAM for building thanks thanks for bug-report. The problem is, that all build-failures are due to insufficient RAM on build-machines [1]. I do not really know how to fix that except of backlisting of some machines, as was suggested by Julien [2]. The same package builds fine on Launchpad's PPA. It seems, the package builds only on machines, where 4Gb RAM is available. This diagnosis is incorrect. The error you are hitting here is not that you are exhausting the available memory on the machine, it's that you're exhausting the *address space* on the machine. Adding more memory to the buildd would have zero effect, because you're on a 32-bit system which has a limit of 4GB of address space anyway. (In practice, I believe this is 3GB for userspace and 1GB for kernel on i386.) The buildd almost certainly has swap already, giving it total available memory in excess of 4GB, but that doesn't help if you have a single process - in this case g++ - that needs more than 3GB all to itself. If this same package version built on Launchpad but is failing to build in Debian unstable, then you should look at differences in toolchain versions between the two. It's possible that Ubuntu has a compiler fix that isn't yet available in unstable; it's equally possible that the successful builds in Launchpad were done with an earlier toolchain, and that there's a more recent regression in g++ memory usage. Either way, it's not the buildd's fault. I'm not sure, but launchpad is running 64-bit machines even when compiling for the i386 architecture, and then launchpad supports PAE only and thus can get 4GB of address space. I think debian buildds are also all 64-bit apart from one (or something like that) thus it shouldn't be a problem there. Last time I spoke with Colin about yade FTBFS due to memory exhaustion, the recommendation he gave was to reduce translation units and thus to reduce the compiler memory usage. GCC memory usage can go very large and has regressed since 3.3 when templates are used http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12850 It has been done before for some other packages, but i haven't yet had time to look more into yade. I think that's the best way to go for yade, to address it in the source-code / restructure it to use less memory at compile time. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726050: marked as done (linux-user-chroot: FTBFS: Invalid configuration `totools-dev')
Your message dated Fri, 11 Oct 2013 21:19:16 + with message-id e1vuk7a-0003ls...@franck.debian.org and subject line Bug#726050: fixed in linux-user-chroot 2013.1-2 has caused the Debian Bug report #726050, regarding linux-user-chroot: FTBFS: Invalid configuration `totools-dev' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 726050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-user-chroot Version: 2013.1-1 Severity: serious Justification: fails to build from source Builds of linux-user-chroot have been failing, apparently due to a stray space in dh's invocation: dh build-arch --with autoreconf, autotools-dev [...] dh_auto_configure -aautotools-dev [...] Invalid configuration `totools-dev': machine `totools' not recognized configure: error: /bin/bash build-aux/config.sub totools-dev failed Could you please take a look? Thanks! ---End Message--- ---BeginMessage--- Source: linux-user-chroot Source-Version: 2013.1-2 We believe that the bug you reported is fixed in the latest version of linux-user-chroot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 726...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) g...@debian.org (supplier of updated linux-user-chroot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Oct 2013 22:52:56 +0200 Source: linux-user-chroot Binary: linux-user-chroot linux-user-chroot-dbg Architecture: source amd64 Version: 2013.1-2 Distribution: unstable Urgency: low Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Changed-By: Laszlo Boszormenyi (GCS) g...@debian.org Description: linux-user-chroot - setuid helper for making bind mounts and chrooting linux-user-chroot-dbg - setuid helper for making bind mounts and chrooting (debug files) Closes: 726050 Changes: linux-user-chroot (2013.1-2) unstable; urgency=low . * Unspace with options for dh (closes: #726050). Checksums-Sha1: 7f4a6c2d1e439a3cd787d87e09d1c776e5f89937 1416 linux-user-chroot_2013.1-2.dsc 552977a6cf5a08d8ab65bd7642acafb9b5d9ac3e 2037 linux-user-chroot_2013.1-2.debian.tar.gz 437910395eee6b3a27837d63bdbd28fe3da02129 9258 linux-user-chroot_2013.1-2_amd64.deb b82c10ab27aa3a5261da80313b7e852f42caed57 10388 linux-user-chroot-dbg_2013.1-2_amd64.deb Checksums-Sha256: 768b55c1e44069dc16c91f57c5245828937af6532fa4d5ce7456c0f27ee3fc67 1416 linux-user-chroot_2013.1-2.dsc 0700ef4f8a61bed670254fbdf1f30e47dbc263f2b1abb31cf3419b7fe7bcdb22 2037 linux-user-chroot_2013.1-2.debian.tar.gz 5e9530b42ae1f1178719b927bfc9c6709a8f6fd60a94395d224457dea294a94e 9258 linux-user-chroot_2013.1-2_amd64.deb 74cc0b06b145aeb4bc70077e6652c73f983a6e4dda04cbdfa28881bebb765cf7 10388 linux-user-chroot-dbg_2013.1-2_amd64.deb Files: e8748aeebd73d841c4ca0465c9fd647c 1416 devel optional linux-user-chroot_2013.1-2.dsc 2b691a41a24abec2fb41cc6678983c3e 2037 devel optional linux-user-chroot_2013.1-2.debian.tar.gz bc4862d7491c3865bb083c98149e6265 9258 devel optional linux-user-chroot_2013.1-2_amd64.deb e72eebf7bbfe1887d77202dc8001097b 10388 debug extra linux-user-chroot-dbg_2013.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlJYaR0ACgkQMDatjqUaT909MQCcDRh78olCldHfmdNnKoQBGvdQ uUAAoKlFnloB7XrZdWdh/YEofOztyMKe =y4I1 -END PGP SIGNATUREEnd Message---
Processed: Re: [Aptitude-devel] Bug#726047: aptitude: segfault during upgrade
Processing control commands: tag -1 + confirmed Bug #726047 [aptitude] aptitude: segfault during upgrade Added tag(s) confirmed. severity -1 grave Bug #726047 [aptitude] aptitude: segfault during upgrade Severity set to 'grave' from 'normal' -- 726047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726009: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
On Fri, Oct 11, 2013 at 09:55:34PM +0100, Dmitrijs Ledkovs wrote: [...] I'm not sure, but launchpad is running 64-bit machines even when compiling for the i386 architecture, and then launchpad supports PAE only and thus can get 4GB of address space. [...] Which bit of 'Physical Address Extension' do you not understand? Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720685: marked as done (cappuccino: FTBFS: polygen: not found)
Your message dated Fri, 11 Oct 2013 22:03:26 +
with message-id e1vuknu-000206...@franck.debian.org
and subject line Bug#720685: fixed in cappuccino 0.5.1-2.2
has caused the Debian Bug report #720685,
regarding cappuccino: FTBFS: polygen: not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
720685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: cappuccino
Version: 0.5.1-2.1
Severity: serious
From my pbuilder build log:
...
fakeroot debian/rules binary
dh_testdir
dh_testroot
dh_clean -k
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_clean: Compatibility levels before 5 are deprecated (level 4 in use)
dh_installdirs
dh_installdirs: Compatibility levels before 5 are deprecated (level 4 in use)
# Add here commands to install the package into debian/cappuccino.
#/usr/bin/make install prefix=/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr
#/usr/bin/make install DESTDIR=/tmp/buildd/cappuccino-0.5.1/debian/cappuccino
python setup.py install
--prefix=/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr --install-layout=deb
running install
running build
running build_scripts
creating build
creating build/scripts-2.7
copying and adjusting cappuccino - build/scripts-2.7
changing mode of build/scripts-2.7/cappuccino from 644 to 755
running install_scripts
creating /tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr
creating /tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/bin
copying build/scripts-2.7/cappuccino -
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/bin
changing mode of
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/bin/cappuccino to 755
running install_data
creating /tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/share
creating /tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/share/cappuccino
copying cappuccino.grm -
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/share/cappuccino
copying compileline.grm -
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/share/cappuccino
copying cappuccino.jpg -
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/share/cappuccino
running install_egg_info
Creating
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/lib/python2.7/dist-packages/
Writing
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/lib/python2.7/dist-packages/cappuccino-0.5.1.egg-info
polygen
/tmp/buildd/cappuccino-0.5.1/debian/cappuccino/usr/share/cappuccino/cappuccino.grm
/dev/null
/bin/sh: 1: polygen: not found
make: *** [binary-indep] Error 127
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
--
Daniel Schepler
---End Message---
---BeginMessage---
Source: cappuccino
Source-Version: 0.5.1-2.2
We believe that the bug you reported is fixed in the latest version of
cappuccino, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 720...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bill Allombert ballo...@debian.org (supplier of updated cappuccino package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Oct 2013 22:42:57 +0200
Source: cappuccino
Binary: cappuccino
Architecture: source all
Version: 0.5.1-2.2
Distribution: unstable
Urgency: low
Maintainer: Christian Surchi csur...@debian.org
Changed-By: Bill Allombert ballo...@debian.org
Description:
cappuccino - utility to let your boss think that you're working hard
Closes: 720685
Changes:
cappuccino (0.5.1-2.2) unstable; urgency=low
.
* Non-maintainer upload.
* debian/rules
- add /usr/games to PATH (for polygen). Closes: #720685
- fix build target to actually build, and binary-arch to actually generate
the package
* debian/control
- remove article from synopsis
- add ${misc:Depends} to Depends
Checksums-Sha1:
0a97054b23843b55c9d9c954577ba955bcb23381 1056 cappuccino_0.5.1-2.2.dsc
2383d1b61be3ecac27d6a8223970b75f7a377420 1442 cappuccino_0.5.1-2.2.diff.gz
8548aaade0f97ee2a485e61226c8bb36e0f3c9ab 91300 cappuccino_0.5.1-2.2_all.deb
Checksums-Sha256:
8f322b3b55eb9b43743d5d4462474cfe8868b94ff0fd5ff201fb6b480969cc3b 1056
cappuccino_0.5.1-2.2.dsc
Bug#723036: marked as done (qt4-x11: missing source for minimized javascript)
Your message dated Fri, 11 Oct 2013 22:09:17 + with message-id e1vuktz-000544...@franck.debian.org and subject line Bug#723036: fixed in qt4-x11 4:4.8.5+git121-g2a9ea11+dfsg1-1 has caused the Debian Bug report #723036, regarding qt4-x11: missing source for minimized javascript to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 723036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: qt4-x11 Version: 4:4.8.5+git121-g2a9ea11+dfsg-1 Severity: serious qt4-x11 includes minimized copies of jquery without source: ./doc/src/template/scripts/jquery.js ./tools/qdoc3/doc/config/scripts/jquery.js ./examples/webkit/fancybrowser/jquery.min.js -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: qt4-x11 Source-Version: 4:4.8.5+git121-g2a9ea11+dfsg1-1 We believe that the bug you reported is fixed in the latest version of qt4-x11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 723...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org (supplier of updated qt4-x11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 11 Oct 2013 15:23:32 -0300 Source: qt4-x11 Binary: libqtcore4 qtcore4-l10n libqt4-core libqtgui4 libqt4-gui libqt4-network libqt4-opengl libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-ibase libqt4-sql-mysql libqt4-sql-odbc libqt4-sql-psql libqt4-sql-sqlite libqt4-sql-sqlite2 libqt4-sql-tds libqt4-svg libqt4-webkit libqt4-xml libqt4-xmlpatterns libqt4-dbus libqtdbus4 libqt4-qt3support libqt4-designer libqt4-help libqt4-assistant libqt4-test libqt4-phonon libqt4-declarative libqt4-declarative-folderlistmodel libqt4-declarative-gestures libqt4-declarative-particles libqt4-declarative-shaders libqt4-dev libqt4-dev-bin libqt4-private-dev libqt4-opengl-dev libqt4-dbg libqt4-designer-dbg libqt4-qt3support-dbg libqt4-script-dbg libqt4-webkit-dbg libqt4-xmlpatterns-dbg qt4-bin-dbg qt4-demos-dbg qt4-designer qt4-dev-tools qt4-qmake qt4-qtconfig qt4-demos qt4-qmlviewer qt4-linguist-tools qdbus qt4-doc qt4-doc-html qt4-default Architecture: source amd64 all Version: 4:4.8.5+git121-g2a9ea11+dfsg1-1 Distribution: unstable Urgency: low Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org Description: libqt4-assistant - transitional package for Qt 4 assistant module libqt4-core - transitional package for Qt 4 core non-GUI runtime libraries libqt4-dbg - Qt 4 library debugging symbols libqt4-dbus - Qt 4 D-Bus module libqt4-declarative - Qt 4 Declarative module libqt4-declarative-folderlistmodel - Qt 4 folderlistmodel QML plugin libqt4-declarative-gestures - Qt 4 gestures QML plugin libqt4-declarative-particles - Qt 4 particles QML plugin libqt4-declarative-shaders - Qt 4 shaders QML plugin libqt4-designer - Qt 4 designer module libqt4-designer-dbg - Qt 4 designer library debugging symbols libqt4-dev - Qt 4 development files libqt4-dev-bin - Qt 4 development programs libqt4-gui - transitional package for Qt 4 GUI runtime libraries libqt4-help - Qt 4 help module libqt4-network - Qt 4 network module libqt4-opengl - Qt 4 OpenGL module libqt4-opengl-dev - Qt 4 OpenGL library development files libqt4-phonon - Qt 4 Phonon module libqt4-private-dev - Qt 4 private development files libqt4-qt3support - Qt 3 compatibility library for Qt 4 libqt4-qt3support-dbg - Qt 3 compatibility library for Qt 4 debugging symbols libqt4-script - Qt 4 script module libqt4-script-dbg - Qt 4 script library debugging symbols libqt4-scripttools - Qt 4 script tools module libqt4-sql - Qt 4 SQL module libqt4-sql-ibase - Qt 4 InterBase/FireBird database driver libqt4-sql-mysql - Qt 4 MySQL database driver libqt4-sql-odbc - Qt 4 ODBC database driver libqt4-sql-psql - Qt 4 PostgreSQL database driver libqt4-sql-sqlite - Qt 4 SQLite 3 database driver libqt4-sql-sqlite2 - Qt 4 SQLite 2 database driver libqt4-sql-tds - Qt 4 FreeTDS
Bug#725577: [Pkg-haskell-maintainers] Bug#725577: yi: FTBFS: The program alex version =3.0.3 =3.0.5 is required but the version found at /usr/bin/alex is version 3.1.0
Hello again! The bug on the test suite has been fixed by dd691fa6791d67981388ec044b28343879d8c2b1, commit by Johan Tibell, last year on 29th October. He fixed the exact bug I ran into. I'm creating a patch on the Cabal included in ghc applying the fix with quilt. No conflict. I'm tuning the patch metadata and I'm sending it. Good night, Louis -- When I grow up, I will run a Tor node around the clock, To help threatened protesters 'round the world. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713537: marked as done (ygraph: FTBFS: ld: axis.o: undefined reference to symbol 'floor@@GLIBC_2.2.5')
Your message dated Fri, 11 Oct 2013 22:18:29 +
with message-id e1vul2t-0006uu...@franck.debian.org
and subject line Bug#713537: fixed in ygraph 0.16~cvs20090218-1.2
has caused the Debian Bug report #713537,
regarding ygraph: FTBFS: ld: axis.o: undefined reference to symbol
'floor@@GLIBC_2.2.5'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
713537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ygraph
Version: 0.16~cvs20090218-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Maybe you need to add explicitly the offending lib to LD flags.
Relevant part:
gcc -g -O2 -Winline -W -Wall -Wpointer-arith -Wcast-align -g -O2 -o ygraph
about.o axis.o callbacks.o color.o control_panel.o export.o legend.o
message.o plot_window.o plot_area.o read_data.o scale_panel.o special_fn.o
util.o ygraph.o -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0
-lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0
-lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0-lpopt -ljpeg -lpng
-ltiff -lz -lbz2 -lpthread -lX11 -lpopt -ljpeg -lpng -ltiff -lz -lbz2
-lpthread -lX11
/usr/bin/ld: axis.o: undefined reference to symbol 'floor@@GLIBC_2.2.5'
/lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from
command line
collect2: error: ld returned 1 exit status
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/ygraph_0.16~cvs20090218-1.1_unstable.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: ygraph
Source-Version: 0.16~cvs20090218-1.2
We believe that the bug you reported is fixed in the latest version of
ygraph, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 713...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bill Allombert ballo...@debian.org (supplier of updated ygraph package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 11 Oct 2013 23:57:59 +0200
Source: ygraph
Binary: ygraph
Architecture: source amd64
Version: 0.16~cvs20090218-1.2
Distribution: unstable
Urgency: low
Maintainer: Daniel Kobras kob...@debian.org
Changed-By: Bill Allombert ballo...@debian.org
Description:
ygraph - plot and animate data sets
Closes: 713537
Changes:
ygraph (0.16~cvs20090218-1.2) unstable; urgency=low
.
* Non-maintainer upload.
* src/Makefile*: Add -lm to LIB to fix FTBFS (closes: #713537).
* debian/control:
- Depends on ${misc:Depends}
* debian/rules:
- remove call to dh_desktop
Checksums-Sha1:
bcd7654f5da5b7b11f61baf3665adb50eee56152 1246 ygraph_0.16~cvs20090218-1.2.dsc
506dcaf67c8ad48e4c8f98823c48a202918eff7b 6189
ygraph_0.16~cvs20090218-1.2.diff.gz
8c032a67d9b36ae7b8fbfef28d129b1b149ad3ef 69284
ygraph_0.16~cvs20090218-1.2_amd64.deb
Checksums-Sha256:
1b6700c1fc5f3ec0856859c2d56d8b54a1d516d8f307aa80b1898dc4c71bf9e2 1246
ygraph_0.16~cvs20090218-1.2.dsc
74e7c56f24e45e9b860263d5b73f26b63479a9469eb113dc34c1dfbdacff6f6a 6189
ygraph_0.16~cvs20090218-1.2.diff.gz
524206be8009f099a7943f9dbb605b59539abb9e87f852a5c131ed94fb0aed4f 69284
ygraph_0.16~cvs20090218-1.2_amd64.deb
Files:
250b0e163975d47f381d2cb80eef624c 1246 science optional
ygraph_0.16~cvs20090218-1.2.dsc
56797e1197b2216a996bfcf457424cc4 6189 science optional
ygraph_0.16~cvs20090218-1.2.diff.gz
99baeeb5c2c66ecba28a9c4f291ef5bf 69284 science optional
ygraph_0.16~cvs20090218-1.2_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJYducACgkQeDPs8bVESBVLJgCfXLZ3pf3dM090unRpRJ9UKtr+
QN8An07WSrM9T5DxOCxqxpDJ+y2PVFa2
=PTy8
-END
Bug#726009: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
On Fri, Oct 11, 2013 at 09:55:34PM +0100, Dmitrijs Ledkovs wrote: I'm not sure, but launchpad is running 64-bit machines even when compiling for the i386 architecture, and then launchpad supports PAE only and thus can get 4GB of address space. A 32-bit process can still only address 32-bits of memory. PAE only lets you extend past 4GB across *multiple* processes; the 4GB limit still applies to any one 32-bit process. I think debian buildds are also all 64-bit apart from one (or something like that) thus it shouldn't be a problem there. Last time I spoke with Colin about yade FTBFS due to memory exhaustion, the recommendation he gave was to reduce translation units and thus to reduce the compiler memory usage. GCC memory usage can go very large and has regressed since 3.3 when templates are used http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12850 It has been done before for some other packages, but i haven't yet had time to look more into yade. I think that's the best way to go for yade, to address it in the source-code / restructure it to use less memory at compile time. Yes, even if we can pinpoint a specific recent change in the compiler that caused increased memory usage, the most reliable fix for the problem is going to be to just refactor this code. If your compiler is taking anywhere near 3GB of memory to build a single object file, that's not a good thing anyway. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#726009: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))
On 11 October 2013 22:34, Ben Hutchings b...@decadent.org.uk wrote: On Fri, Oct 11, 2013 at 09:55:34PM +0100, Dmitrijs Ledkovs wrote: [...] I'm not sure, but launchpad is running 64-bit machines even when compiling for the i386 architecture, and then launchpad supports PAE only and thus can get 4GB of address space. [...] Which bit of 'Physical Address Extension' do you not understand? ignore me, friday evening. the parts where virtual address space is limitted to 4gb per process none the less. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#726055: libapt-pkg.so.4.12: segmentation fault in pkgDPkgPM::ProcessDpkgStatusLine
Processing commands for cont...@bugs.debian.org: package aptitude libapt-pkg4.12 Limiting to bugs with field 'package' containing at least one of 'aptitude', 'libapt-pkg4.12' Limit currently set to 'package':'aptitude', 'libapt-pkg4.12' severity 726055 grave Bug #726055 [libapt-pkg4.12] libapt-pkg.so.4.12: segmentation fault in pkgDPkgPM::ProcessDpkgStatusLine Severity set to 'grave' from 'normal' reassign 726047 libapt-pkg4.12 0.9.12 Bug #726047 [aptitude] aptitude: segfault during upgrade Bug reassigned from package 'aptitude' to 'libapt-pkg4.12'. No longer marked as found in versions aptitude/0.6.8.2-1.2. Ignoring request to alter fixed versions of bug #726047 to the same values previously set Bug #726047 [libapt-pkg4.12] aptitude: segfault during upgrade Marked as found in versions apt/0.9.12. merge 726055 726047 Bug #726055 [libapt-pkg4.12] libapt-pkg.so.4.12: segmentation fault in pkgDPkgPM::ProcessDpkgStatusLine Bug #726055 [libapt-pkg4.12] libapt-pkg.so.4.12: segmentation fault in pkgDPkgPM::ProcessDpkgStatusLine Added tag(s) confirmed. Bug #726047 [libapt-pkg4.12] aptitude: segfault during upgrade Merged 726047 726055 affects 726055 aptitude Bug #726055 [libapt-pkg4.12] libapt-pkg.so.4.12: segmentation fault in pkgDPkgPM::ProcessDpkgStatusLine Bug #726047 [libapt-pkg4.12] aptitude: segfault during upgrade Added indication that 726055 affects aptitude Added indication that 726047 affects aptitude thanks Stopping processing here. Please contact me if you need assistance. -- 726047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726047 726055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726047: Bug#726055: libapt-pkg.so.4.12: segmentation fault in pkgDPkgPM::ProcessDpkgStatusLine
package aptitude libapt-pkg4.12 severity 726055 grave reassign 726047 libapt-pkg4.12 0.9.12 merge 726055 726047 affects 726055 aptitude thanks Hi *, On Fri, Oct 11, 2013 at 6:30 PM, Sven Hartge s...@svenhartge.de wrote: dpkg: error processing /var/cache/apt/archives/msr-tools_1.3-1_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/cpuid.1.gz', which is also in package cpuid 20130610-2 Program received signal SIGSEGV, Segmentation fault. 0xf7f5436b in pkgDPkgPM::ProcessDpkgStatusLine(int, char*) () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 With symbols and everything attached gdb says a bit more: #1 pkgDPkgPM::ProcessDpkgStatusLine (this=this@entry=0x626190, OutStatusFd=OutStatusFd@entry=-1, line=optimized out) at deb/dpkgpm.cc:603 [apt-dbg doesn't exist because somehow we always fall for the this time, we gonna get automatic -dbg generation goal… oh my.] This is a regression in 0.9.12, the buggy change being: * Fix status-fd progress calculation for certain multi-arch install/upgrade situations which triggers on dpkg errors (like not declared file overrides as shown here) or on conffile prompts (not tested yet, just assuming from the code). #726001 seems to be different and aptitude related. [The error being that the 4th element of an array with 3 elements is read] Also, the advertised fix isn't complete as it assumes every package which dpkg isn't qualifying with an architecture is native, which isn't the case, as dpkg only qualifies :same packages, but not foreign packages (with the logic that only one architecture could be meant at all times, so no need to qualify). So while it will be correct for many, it certainly isn't for all and somehow, throwing in the architecture suddenly smells like our front ends are going to hate us… (at least if they parse what they hand to them with this). [The code parsing dpkg status lines is a bloody mess, but I hope I will find some time in-between vintage this weekend to have a closer look] Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to gmpc, tagging 725127
Processing commands for cont...@bugs.debian.org: #gmpc (11.8.16-8) unstable; urgency=low # # * Add a Breaks clause to force gmpc-plugins to be multiarch-aware. #(Closes: #725127) # limit source gmpc Limiting to bugs with field 'source' containing at least one of 'gmpc' Limit currently set to 'source':'gmpc' tags 725127 + pending Bug #725127 [gmpc] gmpc: seems not to be compatible with gmpc-plugins Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 725127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721320: bug 721320
Its now well into October and libpgplot-perl still needs rebuild against perl 5.18.
Bug#718140: cardpeek: FTBFS: configure: error: Could not find lua 5.1-dev
Hi Hans! Last time I checked the maintainer's mail address was bouncing, so he probably doesn't know about this bug report. I'd be willing to help with an NMU if you'd be interested in uploading a package including your fix to mentors. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): reassign 713785 to texlive-lang-italian, forcibly merging 725928 713785
Processing commands for cont...@bugs.debian.org:
reassign 713785 texlive-lang-italian
Bug #713785 [src:maint-guide] maint-guide: FTBFS: Error: xelatex compilation
failed
Bug reassigned from package 'src:maint-guide' to 'texlive-lang-italian'.
No longer marked as found in versions maint-guide/1.2.31.
Ignoring request to alter fixed versions of bug #713785 to the same values
previously set
forcemerge 725928 713785
Bug #725928 {Done: Norbert Preining prein...@debian.org}
[texlive-lang-italian] typo in CyrilicCaporali
Bug #725928 {Done: Norbert Preining prein...@debian.org}
[texlive-lang-italian] typo in CyrilicCaporali
Added tag(s) sid and jessie.
Bug #713785 [texlive-lang-italian] maint-guide: FTBFS: Error: xelatex
compilation failed
Severity set to 'normal' from 'serious'
Failed to forcibly merge 725928: It is nonsensical for a bug to block itself
(or a merged partner): 713785
Debbugs::Control::set_blocks('bug', 713785, 'block', 713785, 'add', 1,
'request_msgid', '1381541026-2933-bts-taf...@debian.org', 'request_replyto',
...) called at /usr/local/lib/site_perl/Debbugs/Control.pm line 2125
Debbugs::Control::set_merged('transcript', 'GLOB(0x17d3c58)',
'requester', 'David Prévot taf...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1381541026-2933-bts-taf...@debian.org', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', 'forcemerge 725928
713785', 'clonebugs', 'HASH(0x174b630)', 'limit', 'HASH(0x174b018)',
'common_control_options', 'ARRAY(0x174b060)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
713785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713785
725928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 725928 713785
Processing commands for cont...@bugs.debian.org:
# hopefully end of noise, sorry
forcemerge 725928 713785
Bug #725928 {Done: Norbert Preining prein...@debian.org}
[texlive-lang-italian] typo in CyrilicCaporali
Bug #713785 [texlive-lang-italian] maint-guide: FTBFS: Error: xelatex
compilation failed
713777 was blocked by: 725928
713777 was not blocking any bugs.
Added blocking bug(s) of 713777: 713785
Marked Bug as done
Marked as fixed in versions texlive-lang/2013.20131010-1.
Marked as found in versions texlive-lang/2013.20130918-1.
Added tag(s) upstream.
Merged 713785 725928
thanks
Stopping processing here.
Please contact me if you need assistance.
--
713777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713777
713785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713785
725928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724065: marked as done (quodlibet: Missing dependency on gir1.2-gtk-3.0)
Your message dated Sat, 12 Oct 2013 03:48:34 + with message-id e1vuqbu-0002h9...@franck.debian.org and subject line Bug#724065: fixed in quodlibet 3.0.2-3 has caused the Debian Bug report #724065, regarding quodlibet: Missing dependency on gir1.2-gtk-3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: quodlibet Version: 3.0.2-2 Severity: serious Justification: Policy 3.5 Without gir1.2-gtk-3.0, quodlibet fails with the following error. ERROR:root:Could not find any typelib for Gtk Traceback (most recent call last): File /usr/bin/quodlibet, line 445, in module main() File /usr/bin/quodlibet, line 38, in main from quodlibet import browsers File /usr/lib/python2.7/dist-packages/quodlibet/browsers/__init__.py, line 13, in module from quodlibet.browsers._base import Browser File /usr/lib/python2.7/dist-packages/quodlibet/browsers/_base.py, line 11, in module from gi.repository import Gtk, GObject ImportError: cannot import name Gtk -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (600, 'unstable'), (570, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10.7+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages quodlibet depends on: ii exfalso 3.0.2-2 ii gir1.2-gst-plugins-base-1.0 1.0.10-1 ii gir1.2-gstreamer-1.0 1.0.10-1 ii gstreamer1.0-plugins-base1.0.10-1 ii gstreamer1.0-plugins-good1.0.10-1 ii gstreamer1.0-plugins-ugly1.0.10-1 ii gstreamer1.0-pulseaudio 1.0.10-1 ii python 2.7.5-5 Versions of packages quodlibet recommends: pn gir1.2-gtksource-3.0 none pn gir1.2-keybinder-3.0 none pn libgpod4 none pn media-player-info none ii python-dbus 1.2.0-2+b1 ii python-feedparser 5.1.3-1 ii udisks1.0.4-8+b1 Versions of packages quodlibet suggests: ii gstreamer1.0-plugins-bad 1.0.10-3 ii quodlibet-plugins 1:2.4-1 -- no debconf information signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: quodlibet Source-Version: 3.0.2-3 We believe that the bug you reported is fixed in the latest version of quodlibet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Kuzník on...@mistotebe.net (supplier of updated quodlibet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 27 Sep 2013 22:44:35 +0100 Source: quodlibet Binary: exfalso quodlibet Architecture: source all Version: 3.0.2-3 Distribution: unstable Urgency: low Maintainer: Ondřej Kuzník on...@mistotebe.net Changed-By: Ondřej Kuzník on...@mistotebe.net Description: exfalso- audio tag editor for GTK+ quodlibet - audio library manager and player for GTK3 Closes: 724065 Changes: quodlibet (3.0.2-3) unstable; urgency=low . * Properly depend on GTK-3.0 (Closes: #724065) Checksums-Sha1: f5e590ea6fc34a7529d1ccd79d65b960192153e7 2023 quodlibet_3.0.2-3.dsc 88610f1f20a02f8b14f9a79bad66646977f76fdf 9533 quodlibet_3.0.2-3.debian.tar.gz ef0acee8da904389762282e250b1d1ee164a8589 1627152 exfalso_3.0.2-3_all.deb 2ff320c3117335693ec3af9cbb64d8b236048455 1153158 quodlibet_3.0.2-3_all.deb Checksums-Sha256: f536d17703414d1542f0f632515800777577c1cd91abfcdea13c71a01c3d7c1c 2023 quodlibet_3.0.2-3.dsc 9ac5a1b42630f91edbf20bd70242457574d729b9653aa225e3a0eeb8841b50e4 9533 quodlibet_3.0.2-3.debian.tar.gz 1e6aabfb45887399fac10a769725cc5d862b3eae1c74a25ca4a621dc6276a90a 1627152 exfalso_3.0.2-3_all.deb 62c11d4e71313800b9a864a8f5fcaf0102c77dd25775ddedd4160e706e3be443 1153158 quodlibet_3.0.2-3_all.deb Files: d2b750d283e20b934cd14f05087fbc07 2023 sound optional quodlibet_3.0.2-3.dsc 000d9ee3d85c9689b30f59422a4edb15 9533 sound optional quodlibet_3.0.2-3.debian.tar.gz db7e70eb07702a78e7ee840ba921043e
Bug#725616: hplip: no longer buildable on kfreebsd-*
On Sun, 6 Oct 2013 23:06:55 Cyril Brulebois wrote: as seen on: https://buildd.debian.org/status/package.php?p=hplipsuite=sid Feel free to ping debian-bsd@ (cc-d) to get some help. debian-bsd, Can you provide any assistance? Mark signature.asc Description: This is a digitally signed message part.
