Bug#716892: marked as done (context: documentation disappears during wheezy-sid upgrade)
Your message dated Wed, 17 Jul 2013 06:18:26 + with message-id e1uzl4e-h4...@franck.debian.org and subject line Bug#716892: fixed in context 2013.05.28.20130704-2 has caused the Debian Bug report #716892, regarding context: documentation disappears during wheezy-sid upgrade 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.) -- 716892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: context Version: 2013.05.28.20130704-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts shows that a lot of documentation files are disappearing (as in debsums reports missing file) during wheezy-sid upgrades. This is probably caused by installing files over existing symlinks that get changed later on. The wrong installation location was either used in the old or the new packages. From the attached log (usually somewhere in the middle...): 1m31.3s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /usr/share/texmf/doc/context/document/general/manuals/mreadme.pdf (from context package) debsums: missing file /usr/share/texmf/doc/context/document/general/manuals/tiptrick.pdf (from context package) debsums: missing file /usr/share/texmf/doc/context/manuals/allkind/mcommon.tex (from context package) debsums: missing file /usr/share/texmf/doc/context/manuals/allkind/mreadme.tex (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkii/ctxtools.html (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkii/ctxtools.man (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkii/ctxtools.xml (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkii/imgtopdf.html (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkii/imgtopdf.man (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkii/imgtopdf.xml (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkii/mptopdf.html (from context package) ... debsums: missing file /usr/share/texmf/doc/context/scripts/mkiv/mtx-watch.xml (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkiv/mtxrun.html (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkiv/mtxrun.man (from context package) debsums: missing file /usr/share/texmf/doc/context/scripts/mkiv/mtxrun.xml (from context package) debsums: missing file /usr/share/texmf/doc/context/third/gnuplot/example.plt (from context package) debsums: missing file /usr/share/texmf/doc/context/third/gnuplot/fullpage-example.pdf (from context package) debsums: missing file /usr/share/texmf/doc/context/third/gnuplot/fullpage-example.tex (from context package) debsums: missing file /usr/share/texmf/doc/context/third/gnuplot/gnuplot-context-doc.pdf (from context package) debsums: missing file /usr/share/texmf/doc/context/third/gnuplot/gnuplot-context-doc.tex (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/context.1 (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/context.man1.pdf (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/ctxtools.1 (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/ctxtools.man1.pdf (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/luatools.1 (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/luatools.man1.pdf (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/mtx-babel.1 (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/mtx-babel.man1.pdf (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/mtx-base.1 (from context package) ... debsums: missing file /usr/share/texmf/doc/man/man1/mtxrun.1 (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/mtxrun.man1.pdf (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/pstopdf.1 (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/pstopdf.man1.pdf (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/texexec.1 (from context package) debsums: missing file /usr/share/texmf/doc/man/man1/texexec.man1.pdf (from context package) debsums: missing file
Bug#717131: minidlna: CVE-2013-2745 CVE-2013-2738 CVE-2013-2739
Package: minidlna Severity: grave Tags: security Justification: user security hole Please see http://www.securityfocus.com/archive/1/527299/30/0 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#715568: ibus-anthy 1.5.3 doesn't work
Hi, I installed ibus-anthy1.5.3 from experimental. However, this new input method is not listed in input sources of Gnome 3.8 Region Language settings. So it is no way for Gnome to activate it. If this input method is added via ibus-setup, ibus-anthy will be activated all the time and cannot be turned off. There seems to be a specific step needed to register input method installed to Gnome. But I don't know what it is. Thanks, Hongzheng -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717138: lightproof: dummy bug to prevent migrating to testing before LO 4.0.4-3
Package: lightproof Severity: serious hrm: $ grep-excuses lightproof lightproof (1.5+git20121204-3 to 1.5+git20121204-4) Maintainer: Debian LibreOffice Maintainers Too young, only 1 of 10 days old Not considered Apparently britney sees the | python-uno and declares it as installable and thus doesn't make it wait for libreoffice. I don't think we should make people dist-upgrading to back to the obsolete python-uno (what apt probably will do when lightproof enters without a python3-uno (= 4.0) ) when we can avoid it. So this blocking bug. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713790: marked as done (kross-interpreters: FTBFS: CMake Error: The following variables are used in this project, but they are set to NOTFOUND. PYTHON_LIBRARY)
Your message dated Wed, 17 Jul 2013 10:42:50 +0200 with message-id 1671050.lVJ47ImTbW@amadeus and subject line kross-interpreters: FTBFS: CMake Error: The following variables are used in this project, but they are set to NOTFOUND. PYTHON_LIBRARY has caused the Debian Bug report #713790, regarding kross-interpreters: FTBFS: CMake Error: The following variables are used in this project, but they are set to NOTFOUND. PYTHON_LIBRARY 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.) -- 713790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kross-interpreters Version: 4:4.8.4-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»' dh_testdir dh_auto_configure '--buildsystem=kde' --parallel -u-DCMAKE_USE_RELATIVE_PATHS=ON -- The C compiler identification is GNU 4.8.1 -- The CXX compiler identification is GNU 4.8.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - not found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found -- Found Qt-Version 4.8.4 (using /usr/bin/qmake) -- Looking for include file pthread.h -- Looking for include file pthread.h - found -- Looking for pthread_create -- Looking for pthread_create - not found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE -- Looking for _POSIX_TIMERS -- Looking for _POSIX_TIMERS - found -- Found Automoc4: /usr/bin/automoc4 -- Found Perl: /usr/bin/perl (found version 5.14.2) -- Found Phonon: /usr/include -- Performing Test _OFFT_IS_64BIT -- Performing Test _OFFT_IS_64BIT - Success -- Performing Test HAVE_FPIE_SUPPORT -- Performing Test HAVE_FPIE_SUPPORT - Success -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success -- Performing Test __KDE_HAVE_GCC_VISIBILITY -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success -- Found KDE 4.8 include dir: /usr/include -- Found KDE 4.8 library dir: /usr/lib -- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler -- Found automoc4: /usr/bin/automoc4 -- Found PythonInterp: /usr/bin/python (found version 2.7.5) -- Found Python executable: /usr/bin/python -- Found Python version: 2.7.5+ -- Found Python library: PYTHON_LIBRARY-NOTFOUND -- Could NOT find FALCON (missing: FALCON_INCLUDE_DIR FALCON_LIBRARIES) -- Found Python executable: /usr/bin/python -- Found Python version: 2.7.5+ -- Found Python library: PYTHON_LIBRARY-NOTFOUND -- Could NOT find Ruby (missing: RUBY_EXECUTABLE RUBY_INCLUDE_DIR RUBY_LIBRARY) -- Could NOT find JNI (missing: JAVA_AWT_LIBRARY JAVA_JVM_LIBRARY JAVA_INCLUDE_PATH JAVA_INCLUDE_PATH2 JAVA_AWT_INCLUDE_PATH) -- using FindKrossJNI.cmake -- JAVA_HOME: -- JAVA_AWT_LIB_PATH: -- JAVA_JVM_LIB_PATH: -- JAVA_INCLUDE_PATH: JAVA_INCLUDE_PATH-NOTFOUND -- JAVA_INCLUDE_PATH2: JAVA_INCLUDE_PATH2-NOTFOUND -- JAVA_AWT_INCLUDE_PATH: JAVA_AWT_INCLUDE_PATH-NOTFOUND -- JAVA_JVM_LIBRARY: JAVA_JVM_LIBRARY-NOTFOUND - -- The following external packages were located on your system. -- This installation will have the extra features provided by these packages. - * Python - Python is a programming language that lets you work more quickly and integrate your systems more effectively. - -- The following OPTIONAL packages could NOT be located on your system. -- Consider installing them to enable more features from this software.
Bug#717140: maxima: On testing (amd64), maxima crashes at startup
Package: maxima Version: 5.30.0-4 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Following testing... * What exactly did you do (or not do) that was effective (or ineffective)? -- Trying to launch maxima (in a gnome terminal) : charpent@SAP5057241:~$ maxima Maxima encountered a Lisp error: Error in INITIALIZE-RUNTIME-GLOBALS [or a callee]: Cannot open the file /usr/share/doc/maxima/info/./maxima-index.lisp. Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. Error in CL-INFO::LOAD-PRIMARY-INDEX [or a callee]: The tag RETURN-FROM- DEBUGGER is undefined. Fast links are on: do (use-fast-links nil) for debugging Broken at CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER. Type :H for Help. 1 (Continue) Retry loading file /usr/share/doc/maxima/info/./maxima- index.lisp. 2 Maxima top-level 3 (Abort) Return to top level. dbl:MAXIMA -- * What was the outcome of this action? At this point, any attempt to get back to the toplevel results in another break : -- dbl:MAXIMA1 Maxima encountered a Lisp error: Error in INITIALIZE-RUNTIME-GLOBALS [or a callee]: Cannot open the file /usr/share/doc/maxima/info/./maxima-index.lisp. Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. Error in CL-INFO::LOAD-PRIMARY-INDEX [or a callee]: The tag RETURN-FROM- DEBUGGER is undefined. Fast links are on: do (use-fast-links nil) for debugging Broken at CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER. Type :H for Help. 1 (Continue) Retry loading file /usr/share/doc/maxima/info/./maxima- index.lisp. 2 Maxima top-level 3 (Abort) Return to top level. dbl:MAXIMA2 Error in LISP:LAMBDA-CLOSURE [or a callee]: The tag #:G33007 is missing. Fast links are on: do (use-fast-links nil) for debugging Broken at GO. 1 (Abort) Return to debug level 1. 2 Retry loading file /usr/share/doc/maxima/info/./maxima-index.lisp. 3 Maxima top-level 4 Return to top level. dbl:MAXIMA4 Error in GO [or a callee]: The tag (NIL) is undefined. Fast links are on: do (use-fast-links nil) for debugging Broken at CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER. 1 (Abort) Return to debug level 2. 2 Return to debug level 1. 3 Retry loading file /usr/share/doc/maxima/info/./maxima-index.lisp. 4 Maxima top-level 5 Return to top level. dbl:MAXIMA -- The only way out I found was to killall maxima from another rerminal * What outcome did you expect instead? A working maxima :-)... I *think* that the problem might be lisp-related. Maxima is currently compiled wit gcl in Debian ; the Sage team has standardized on ECL, which, apparently, gives better performance. Time to reconsider ? Or better, to have a multi-lisp solution ? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages maxima depends on: ii gnuplot-x11 4.6.3-2 ii libc6 2.17-7 ii libgmp10 2:5.1.2+dfsg-2 ii libreadline6 6.2+dfsg-0.1 ii libx11-6 2:1.6.0-1 Versions of packages maxima recommends: ii maxima-share 5.30.0-4 Versions of packages maxima suggests: ii maxima-doc5.30.0-4 ii maxima-emacs 5.30.0-4 pn texmacs none ii tk8.5 [wish] 8.5.14-2 ii xmaxima 5.30.0-4 -- 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: bug 710215 is forwarded to https://bugs.kde.org/show_bug.cgi?id=322473
Processing commands for cont...@bugs.debian.org: forwarded 710215 https://bugs.kde.org/show_bug.cgi?id=322473 Bug #710215 [src:grantlee] Compressed JavaScript library Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=322473'. thanks Stopping processing here. Please contact me if you need assistance. -- 710215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710215 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: jessie
Processing commands for cont...@bugs.debian.org: tags 714263 + sid jessie Bug #714263 [couchdb] couchdb: Fails to start with Erlang 16 Added tag(s) sid and jessie. tags 717067 + sid jessie Bug #717067 [src:chicken] chicken: FTBFS due to missing build-dep on chicken-bin Added tag(s) sid and jessie. thanks Stopping processing here. Please contact me if you need assistance. -- 714263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714263 717067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717067 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#717067: marked as done (chicken: FTBFS due to missing build-dep on chicken-bin)
Your message dated Wed, 17 Jul 2013 09:48:28 + with message-id e1uzolu-0001tv...@franck.debian.org and subject line Bug#717067: fixed in chicken 4.8.0.3-2 has caused the Debian Bug report #717067, regarding chicken: FTBFS due to missing build-dep on chicken-bin 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.) -- 717067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: chicken Version: 4 Severity: serious Tags: patch Hi, latest chicken FTBFS on all arches due to missing (cyclic!) build-dependency on chicken-bin: gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DC_BUILDING_LIBCHICKEN library.c -o library-static.o -I. -I./ gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DC_BUILDING_LIBCHICKEN eval.c -o eval-static.o -I. -I./ gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DC_BUILDING_LIBCHICKEN data-structures.c -o data-structures-static.o -I. -I./ gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DC_BUILDING_LIBCHICKEN ports.c -o ports-static.o -I. -I./ gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DC_BUILDING_LIBCHICKEN files.c -o files-static.o -I. -I./ gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DC_BUILDING_LIBCHICKEN extras.c -o extras-static.o -I. -I./ gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DC_BUILDING_LIBCHICKEN lolevel.c -o lolevel-static.o -I. -I./ chicken utils.scm -optimize-level 2 -include-path . -include-path ./ -inline -ignore-repository -feature chicken-bootstrap -no-warnings -specialize -types ./types.db -explicit-use -no-trace -output-file utils.c make[2]: chicken: Command not found make[2]: *** [utils.c] Error 127 make[1]: make[2]: Leaving directory `/«PKGBUILDDIR»' *** [all] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: chicken Source-Version: 4.8.0.3-2 We believe that the bug you reported is fixed in the latest version of chicken, 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 717...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Davide Puricelli (evo) e...@debian.org (supplier of updated chicken 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: Wed, 17 Jul 2013 10:49:42 +0200 Source: chicken Binary: chicken-bin libchicken6 libchicken-dev Architecture: source amd64 Version: 4.8.0.3-2 Distribution: unstable Urgency: high Maintainer: Davide Puricelli (evo) e...@debian.org Changed-By: Davide Puricelli (evo) e...@debian.org Description: chicken-bin - Practical and portable Scheme system - compiler libchicken-dev - Practical and portable Scheme system - development libchicken6 - Practical and portable Scheme system - runtime Closes: 717067 Changes: chicken (4.8.0.3-2) unstable; urgency=high . * Added
Processed: forcibly merging 689239 717141
Processing commands for cont...@bugs.debian.org: forcemerge 689239 717141 Bug #689239 [qemu-system] qemu-system: rbd images (ceph) are not working any more Bug #705111 [qemu-system] Please enable the --enable-rdb option when building Bug #710124 [qemu-system] Please add --enable-rbd in the configure Bug #717141 [qemu-system] qemu-kvm: add rbd support 717141 was not blocked by any bugs. 717141 was not blocking any bugs. Added blocking bug(s) of 717141: 679686 Marked as found in versions qemu/1.1.2+dfsg-2. Bug #705111 [qemu-system] Please enable the --enable-rdb option when building Bug #710124 [qemu-system] Please add --enable-rbd in the configure Merged 689239 705111 710124 717141 thanks Stopping processing here. Please contact me if you need assistance. -- 689239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689239 705111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705111 710124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710124 717141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717141 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#708942: marked as done ([gprbuild] GFDL non free file with front cover)
Your message dated Wed, 17 Jul 2013 11:33:15 + with message-id e1uzpyt-0001ff...@franck.debian.org and subject line Bug#708942: fixed in gprbuild 2011-4 has caused the Debian Bug report #708942, regarding [gprbuild] GFDL non free file with front cover 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.) -- 708942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gprbuild user: debian...@lists.debian.org usertags: gfdl-invariant severity: serious The files have front cover and thus non free: doc/gprbuild_ug.texi doc/html/gprbuild_ug.html doc/info/gprbuild_ug.info doc/txt/gprbuild_ug.txt Thanks Bastien ---End Message--- ---BeginMessage--- Source: gprbuild Source-Version: 2011-4 We believe that the bug you reported is fixed in the latest version of gprbuild, 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 708...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez nico...@debian.org (supplier of updated gprbuild 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: Tue, 16 Jul 2013 12:30:21 +0200 Source: gprbuild Binary: gprbuild gprbuild-doc Architecture: source amd64 all Version: 2011-4 Distribution: unstable Urgency: low Maintainer: Nicolas Boulenguez nico...@debian.org Changed-By: Nicolas Boulenguez nico...@debian.org Description: gprbuild - multi-language extensible build tool gprbuild-doc - multi-language extensible build tool (documentation) Closes: 673751 705812 708942 Changes: gprbuild (2011-4) unstable; urgency=low . * New maintainer. Closes: #673751. * copyright, patches/correct_doc_license.diff, source.lintian-overrides: Replace obsolete license headers. Closes: #708942. * patches/libraries_after_link_options.diff. Closes: #705812. When linking libraries, put -l arguments after the others. * control: removed obsolete Suggests: ada-compiler and DM-Upload-Allowed. * rules: debhelper 9, hardening flags. Rebuild documentation from its sources, register it in doc-base. Checksums-Sha1: d3cbf88102ecb90645474cd0b0996f9136c31cb4 1998 gprbuild_2011-4.dsc 57377be2cb76f24ba8a2bb6cf553ed13ace8f8a2 18855 gprbuild_2011-4.debian.tar.gz 8b127279970d0de5ac219e399dc84c7e3dcaddb2 3618482 gprbuild_2011-4_amd64.deb a4ab38db3b7e0c6ac519299797c9568f7437a89e 817568 gprbuild-doc_2011-4_all.deb Checksums-Sha256: 3c250fc3e21a6a6882492c2fcc5ecd56f0f00bdf421a157540e20074abe56342 1998 gprbuild_2011-4.dsc 4566e7bdf73e9d6ea33baae92193db895f08602439d24bd6ea45f7793aecd660 18855 gprbuild_2011-4.debian.tar.gz f230d81d89f6b0a673c96a77221ceca205407546f51b7c63c81132fff401759d 3618482 gprbuild_2011-4_amd64.deb b85a26827f4aa6eda3237d7b743209db595e35ef3a8a688592b190a12f8e84cf 817568 gprbuild-doc_2011-4_all.deb Files: 87067dc5bca0a1f1ca5c2e6033ab9b4b 1998 devel optional gprbuild_2011-4.dsc 37534435f76234eeb7444f648f2bf0e7 18855 devel optional gprbuild_2011-4.debian.tar.gz 9169a94776a4b829ea0b4227ff826f0a 3618482 devel optional gprbuild_2011-4_amd64.deb 232a3304446e2ace660b11c5e87733ec 817568 doc optional gprbuild-doc_2011-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJR5n5aAAoJELUqnPRJDfyNiYIP/2So7pqKhBxtU2eiUmApb1sV S6Ow/jDo35ALGC5/gtyvACcunXkBMoV0TfGonHhyT61hOQRKacqbEtZl37VWAHLL eC2JWxJgTPTyVo/gkUUGH3fJlAoRVpghh5E8ZxL1hb7afmuwztAoDO/RdnKXVkDD 8DNBQQRIu0rTjDYk9Wy+D4c7H7DezPDxSQvPmY7y5g5RC3tkWzNU1+4fpBqASfaI gyHTalxhoohWyZJyl9/GXOKwSmJIKRKeVV+kayk9W5Fu1BLwUGtSGvu9GXxgTjhE hRXo6i79Y4Xz0/L3Ibdf4B1xFv3UWA459KBbk/T6y6SyMGoEZsjsPJ0RlnutzETd RInpexIlNw3V64ACJShCafmTHgQMcrCwPD4zOQ0hW/qHZJYYUBieTT52gnM6udyb 1xQGKUzye7w9umUZwVvCKxzRCLflRGf3PQxa2fH7/pduZWra9Ug6gEaimrh7Kv27 VhWxHHFaBLVGn857aOxnjoIij0COR7NEeBTtnErpOWRDNwJhnS4vqZSI0A/f5AMI I5FBArDvDJp8Z2dXLhH72Z+hirTZIh7sDv25Df7mZM/uSSNZ/uuZB5UhepIGfeZC jY0gxX5u3WodBM7rjNJwyl5Oel58G3zb6C/euEDPc8DWpBskPNz/JQYjdW9J3+Bp s/Yyzb7/PTevETWF6ZHV =6EyA -END PGP SIGNATUREEnd Message---
Bug#717152: ndiswrapper: Fails to build with Linux 3.10
Package: ndiswrapper Severity: grave Hi, ndiswrapper-dkms FTBFS with Linux 3.10-1 from current unstable: Cheers, Moritz CC [M] /var/lib/dkms/ndiswrapper/1.58/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.58/build/proc.o /var/lib/dkms/ndiswrapper/1.58/build/proc.c: In function ‘wrap_procfs_add_ndis_device’: /var/lib/dkms/ndiswrapper/1.58/build/proc.c:391:3: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:399:19: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:400:19: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:402:2: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration] /var/lib/dkms/ndiswrapper/1.58/build/proc.c:402:15: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/ndiswrapper/1.58/build/proc.c:408:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:409:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:410:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:411:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:414:15: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/ndiswrapper/1.58/build/proc.c:420:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:421:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:422:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:423:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:426:15: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/ndiswrapper/1.58/build/proc.c:432:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:433:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:434:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:435:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:438:15: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/ndiswrapper/1.58/build/proc.c:445:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:446:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:447:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:448:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:449:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:460:37: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c: In function ‘wrap_procfs_remove_ndis_device’: /var/lib/dkms/ndiswrapper/1.58/build/proc.c:476:33: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c: In function ‘wrap_procfs_init’: /var/lib/dkms/ndiswrapper/1.58/build/proc.c:536:19: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:537:19: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:539:15: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/ndiswrapper/1.58/build/proc.c:545:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:546:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:547:15: error: dereferencing pointer to incomplete type /var/lib/dkms/ndiswrapper/1.58/build/proc.c:548:15: error: dereferencing pointer to incomplete type cc1: some warnings being treated as errors make[3]: *** [/var/lib/dkms/ndiswrapper/1.58/bui -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717154: open-vm-tools-dkms: Fails to build against Linux 3.10
Package: open-vm-tools-dkms Severity: grave open-vm-tools-dkms fails to build against Linux 3.10-1 from current Debian sid: Mi 17. Jul 14:26:10 CEST 2013 Using 2.6.x kernel build system. make: Entering directory `/var/lib/dkms/open-vm-tools/9.2.3/build/vmblock' make -C /lib/modules/3.10-1-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.2.3/build modules make[1]: Entering directory `/usr/src/linux-headers-3.10-1-amd64' CC [M] /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/block.o CC [M] /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.o /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c: In function ‘SetupProcDevice’: /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c:211:4: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration] /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c:211:21: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c:221:20: error: dereferencing pointer to incomplete type /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c: In function ‘ExecuteBlockOp’: /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default] /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c:296:4: warning: passing argument 1 of ‘putname’ from incompatible pointer type [enabled by default] In file included from /usr/src/linux-headers-3.10-1-common/include/linux/proc_fs.h:8:0, from /var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.c:28: /usr/src/linux-headers-3.10-1-common/include/linux/fs.h:2042:13: note: expected ‘struct filename *’ but argument is of type ‘char *’ cc1: some warnings being treated as errors make[4]: *** [/var/lib/dkms/open-vm-tools/9.2.3/build/vmblock/linux/control.o] Fehler 1 make[3]: *** [_module_/var/lib/dkms/open-vm-tools/9.2.3/build/vmblock] Fehler 2 make[2]: *** [sub-make] Fehler 2 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717155: iscsitarget-dkms: Fails to build against Linux 3.10
Package: iscsitarget-dkms Severity: grave Hi, iscsitarget-dkms FTBFS against Linux 3.10-1 from unstable: Cheers, Moritz make: Entering directory `/usr/src/linux-headers-3.10-1-amd64' LD /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/built-in.o LD /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/built-in.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/tio.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/iscsi.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/nthread.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/wthread.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.o /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.c: In function ‘iet_procfs_exit’: /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.c:37:32: error: dereferencing pointer to incomplete type /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.c:37:52: error: dereferencing pointer to incomplete type /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.c: In function ‘iet_procfs_init’: /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.c:49:3: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration] /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.c:49:7: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.c:51:7: error: dereferencing pointer to incomplete type cc1: some warnings being treated as errors make[4]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel/config.o] Fehler 1 make[3]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn490/build/kernel] Fehler 2 make[2]: *** [_module_/var/lib/dkms/iscsitarget/1.4.20.3+svn490/build] Fehler 2 make[1]: *** [sub-make] Fehler 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: broadcom-sta-dkms: Fails to build on linux 3.10 (procfs API change)
Processing commands for cont...@bugs.debian.org: severity 716999 grave Bug #716999 [broadcom-sta-dkms] broadcom-sta-dkms: Fails to build on linux 3.10 (procfs API change) Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 716999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716999 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#717157: blktap-dkms: Fails to build against Linux 3.10
Package: blktap-dkms Severity: grave Justification: renders package unusable Hi, blktap-dkms FTBFS against linux 3.10-1 from unstable: Cheers, Moritz CC [M] /var/lib/dkms/blktap/2.0.91/build/control.o In file included from /var/lib/dkms/blktap/2.0.91/build/control.c:30:0: /var/lib/dkms/blktap/2.0.91/build/blktap.h:75:41: warning: variably modified ‘pending’ at file scope [enabled by default] CC [M] /var/lib/dkms/blktap/2.0.91/build/ring.o In file included from /var/lib/dkms/blktap/2.0.91/build/ring.c:30:0: /var/lib/dkms/blktap/2.0.91/build/blktap.h:75:41: warning: variably modified ‘pending’ at file scope [enabled by default] /var/lib/dkms/blktap/2.0.91/build/ring.c: In function ‘blktap_ring_map_request’: /var/lib/dkms/blktap/2.0.91/build/ring.c:206:2: error: too few arguments to function ‘do_mmap_pgoff’ In file included from /usr/src/linux-headers-3.10-1-common/include/linux/pagemap.h:7:0, from /usr/src/linux-headers-3.10-1-common/include/linux/blkdev.h:13, from /var/lib/dkms/blktap/2.0.91/build/ring.c:27: /usr/src/linux-headers-3.10-1-common/include/linux/mm.h:1516:22: note: declared here /var/lib/dkms/blktap/2.0.91/build/ring.c: In function ‘blktap_ring_mmap_request’: /var/lib/dkms/blktap/2.0.91/build/ring.c:438:19: error: ‘VM_RESERVED’ undeclared (first use in this function) /var/lib/dkms/blktap/2.0.91/build/ring.c:438:19: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/blktap/2.0.91/build/ring.c: In function ‘blktap_ring_mmap_sring’: /var/lib/dkms/blktap/2.0.91/build/ring.c:474:19: error: ‘VM_RESERVED’ undeclared (first use in this function) make[3]: *** [/var/lib/dkms/blktap/2.0.91/build/ring.o] Fehler 1 make[2]: *** [_module_/var/lib/dkms/blktap/2.0.91/build] Fehler 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 714633 is grave
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 714633 grave Bug #714633 [flashcache] flashcache: Flashcache fails to build against kernel 3.10 sources Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 714633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714633 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#717159: asus-oled-dkms: Fails to build against Linux 3.10
Package: asus-oled-dkms Severity: grave Hi, asus-oled-dkms fails to build against Linux 3.10 from unstable: LD /var/lib/dkms/asus-oled-dkms/0.04/build/built-in.o CC [M] /var/lib/dkms/asus-oled-dkms/0.04/build/asus_oled.o /var/lib/dkms/asus-oled-dkms/0.04/build/asus_oled.c:733:8: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/asus-oled-dkms/0.04/build/asus_oled.c:733:8: warning: (near initialization for ‘class_attr_version.show’) [enabled by default] /var/lib/dkms/asus-oled-dkms/0.04/build/asus_oled.c: In function ‘asus_oled_init’: /var/lib/dkms/asus-oled-dkms/0.04/build/asus_oled.c:741:9: error: implicit declaration of function ‘err’ [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors make[3]: *** [/var/lib/dkms/asus-oled-dkms/0.04/build/asus_oled.o] Fehler 1 make[2]: *** [_module_/var/lib/dkms/asus-oled-dkms/0.04/build] Fehler 2 Since asus_led has been merged into staging, please file a bug against the Linux package to have ASUS_OLED enabled and remove asus-oled-dkms from the archive. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717161: r8168-dkms: Fails to build against Linux 3.10
Package: r8168-dkms Severity: grave Justification: renders package unusable Hi, r8168-dkms fails to build against Linux 3.10-1 from unstable: Cheers, Moritz LD /var/lib/dkms/r8168/8.036.00/build/built-in.o CC [M] /var/lib/dkms/r8168/8.036.00/build/r8168_n.o /var/lib/dkms/r8168/8.036.00/build/r8168_n.c: In function ‘rtl8168_rx_vlan_skb’: /var/lib/dkms/r8168/8.036.00/build/r8168_n.c:2237:9: error: too few arguments to function ‘__vlan_hwaccel_put_tag’ In file included from /var/lib/dkms/r8168/8.036.00/build/r8168_n.c:46:0: /usr/src/linux-headers-3.10-1-common/include/linux/if_vlan.h:237:31: note: declared here /var/lib/dkms/r8168/8.036.00/build/r8168_n.c: In function ‘rtl8168_hw_set_features’: /var/lib/dkms/r8168/8.036.00/build/r8168_n.c:2298:25: error: ‘NETIF_F_HW_VLAN_RX’ undeclared (first use in this function) /var/lib/dkms/r8168/8.036.00/build/r8168_n.c:2298:25: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/r8168/8.036.00/build/r8168_n.c: In function ‘rtl8168_init_one’: /var/lib/dkms/r8168/8.036.00/build/r8168_n.c:16198:26: error: ‘NETIF_F_HW_VLAN_TX’ undeclared (first use in this function) /var/lib/dkms/r8168/8.036.00/build/r8168_n.c:16198:47: error: ‘NETIF_F_HW_VLAN_RX’ undeclared (first use in this function) make[3]: *** [/var/lib/dkms/r8168/8.036.00/build/r8168_n.o] Fehler 1 make[2]: *** [_module_/var/lib/dkms/r8168/8.036.00/build] Fehler 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717163: pvcam-dkms: Fails to build against Linux 3.10
Package: pvcam-dkms Severity: grave Hi, pvcam-dkms fails to build against Linux 3.10-1 from unstable: Cheers, Moritz make -f /usr/src/linux-headers-3.10-1-common/scripts/Makefile.build obj=/var/lib/dkms/pvcam/4.1.0/build gcc-4.7 -Wp,-MD,/var/lib/dkms/pvcam/4.1.0/build/.pvcam.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/4.7/include -I/usr/src/linux-headers-3.10-1-common/arch/x86/include -Iarch/x86/include/generated -I/usr/src/linux-headers-3.10-1-common/include -Iinclude -I/usr/src/linux-headers-3.10-1-common/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-headers-3.10-1-common/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-headers-3.10-1-common/include/linux/kconfig.h -I/var/lib/dkms/pvcam/4.1.0/build -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -Os -Wno-maybe-uninitialized -m64 -mno-sse -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCO NFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=2048 -Wno-unused-but-set-variable -fomit-frame-pointer -g -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -DMODULE -DKBUILD_STR(s)=#s -DKBUILD_BASENAME=KBUILD_STR(pvcam) -DKBUILD_MODNAME=KBUILD_STR(pvcam) -c -o /var/lib/dkms/pvcam/4.1.0/build/.tmp_pvcam.o /var/lib/dkms/pvcam/4.1.0/build/pvcam.c /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:831:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘pvcam_probe’ /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:947:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘pvcam_remove’ /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:1604:20: error: ‘pvcam_probe’ undeclared here (not in a function) /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:1605:2: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:1605:32: error: ‘pvcam_remove’ undeclared here (not in a function) /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:1467:20: warning: ‘pvcam_intr’ defined but not used [-Wunused-function] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c: In function ‘device_ioctl’: /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:429:25: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result [-Wunused-result] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:433:27: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result [-Wunused-result] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:438:25: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result [-Wunused-result] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:442:27: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result [-Wunused-result] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:644:25: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result [-Wunused-result] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:650:25: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result [-Wunused-result] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:656:25: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result [-Wunused-result] /var/lib/dkms/pvcam/4.1.0/build/pvcam.c:683:25: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result [-Wunused-result] cc1: some warnings being treated as errors make[4]: *** [/var/lib/dkms/pvcam/4.1.0/build/pvcam.o] Fehler 1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713841: Acknowledgement (oss4-dkms: oss4-4.2-build2006 cp: stat failed /source/include/linux/limits.h)
This is the build failure with Linux 3.10-1 from current Debian unstable: Cheers, Moritz make: Entering directory `/usr/src/linux-headers-3.10-1-amd64' CC [M] /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.o /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c: In function ‘init_proc_fs’: /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c:287:8: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration] /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c:286:22: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c:293:26: warning: assignment makes pointer from integer without a cast [enabled by default] /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c:300:20: error: dereferencing pointer to incomplete type /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c: In function ‘alloc_fop’: /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c:945:14: warning: assignment from incompatible pointer type [enabled by default] /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c: In function ‘oss_pci_read_devpath’: /var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.c:1619:3: warning: return discards ‘const’ qualifier from pointer target type [enabled by default] cc1: some warnings being treated as errors make[3]: *** [/var/lib/dkms/oss4/4.2-build2007/build/core/oss_core.o] Fehler 1 make[2]: *** [_module_/var/lib/dkms/oss4/4.2-build2007/build/core] Fehler 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706330: Re: Some applications segfaults after upgrade to 3.8.0-1
Hi, I've looked at proposed patch and by my opinion it is not a good solution. This patch is just temporary workaround and it is not included in the upstream version. At the moment, I can not find a satisfactory solution, and I am rather for removing gtk3-engines-unico from testing than to upload with this patch. Karolina On Mon, Jul 15, 2013 at 8:31 PM, Vladimir K pzs...@yandex.ru wrote: I've tested the patch, it works. Tested with nm-connection-editor and seahorse. They still output a LOT of errors about the theme, but at least they work. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717165: lttng-modules-dkms: Fails to build against Linux 3.10-1
Package: lttng-modules-dkms Severity: grave Hi, lttng-modules-dkms fails to build against 3.10-1 from unstable: Cheers, Moritz CC [M] /var/lib/dkms/lttng-modules/2.1.0/build/probes/lttng-probe-sched.o In file included from /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:701:0, from /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/define_trace.h:117, from /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/sched.h:464, from /var/lib/dkms/lttng-modules/2.1.0/build/probes/lttng-probe-sched.c:39: /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h: In function ‘__event_probe__sched_switch’: /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h:139:1: error: ‘MAX_RT_PRIO’ undeclared (first use in this function) /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h:139:1: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h: In function ‘__event_probe__sched_migrate_task’: /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h:186:1: error: ‘MAX_RT_PRIO’ undeclared (first use in this function) /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h: In function ‘__event_probe__sched_process_template’: /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h:213:1: error: ‘MAX_RT_PRIO’ undeclared (first use in this function) /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h: In function ‘__event_probe__sched_process_wait’: /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h:266:1: error: ‘MAX_RT_PRIO’ undeclared (first use in this function) /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h: In function ‘__event_probe__sched_pi_setprio’: /var/lib/dkms/lttng-modules/2.1.0/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/sched.h:436:1: error: ‘MAX_RT_PRIO’ undeclared (first use in this function) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717166: openswan-modules-dkms: Fails to build against Linux 3.10-1
Package: openswan-modules-dkms Severity: grave Justification: renders package unusable Hi, openswan-modules-dkms FTFBS against Linux 3.10-1: Cheers, Moritz CC [M] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_life.o ln -s -f /var/lib/dkms/openswan/2.6.38/build/linux/net/ipsec/ipsec_proc.c /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c CC [M] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.o /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1053:2: error: unknown type name ‘read_proc_t’ /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1054:2: error: unknown type name ‘write_proc_t’ /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1058:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1058:2: warning: (near initialization for ‘proc_items[0].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1060:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1060:2: warning: (near initialization for ‘proc_items[2].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1062:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1062:2: warning: (near initialization for ‘proc_items[4].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1064:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1064:2: warning: (near initialization for ‘proc_items[6].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1070:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1070:2: warning: (near initialization for ‘proc_items[8].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1070:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1070:2: warning: (near initialization for ‘proc_items[8].writething’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1071:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1071:2: warning: (near initialization for ‘proc_items[9].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1071:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1071:2: warning: (near initialization for ‘proc_items[9].writething’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1072:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1072:2: warning: (near initialization for ‘proc_items[10].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1075:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1075:2: warning: (near initialization for ‘proc_items[11].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1078:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1078:2: warning: (near initialization for ‘proc_items[13].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1079:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1079:2: warning: (near initialization for ‘proc_items[14].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1080:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1080:2: warning: (near initialization for ‘proc_items[15].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1081:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1081:2: warning: (near initialization for ‘proc_items[16].readthing’) [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1082:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/openswan/2.6.38/build/modobj26/ipsec_proc.c:1082:2: warning: (near initialization for
Bug#666794: libapache2-svn package
libapache2-svn package still depends on apache2.2-common
Processed: severity of 717153 is serious
Processing commands for cont...@bugs.debian.org: severity 717153 serious Bug #717153 [system-config-printer] system-config-printer: Missing dependency on python-gi Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 717153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717153 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#717177: grub-pc: impossible to have a working grub or a working kernel
Package: grub-pc
Version: 2.00-15
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
mew version and same shit
E: Sub-process /usr/bin/dpkg returned an error code (1)
Errore durante l'installazione di un pacchetto. Tentativo di ripristino:
Configurazione di linux-image-3.9-1-686-pae (3.9.8-1)...
Running depmod.
vmlinuz(/boot/vmlinuz-3.9-1-686-pae
) points to /boot/vmlinuz-3.9-1-686-pae
(/boot/vmlinuz-3.9-1-686-pae) -- doing nothing at /var/lib/dpkg/info/linux-
image-3.9-1-686-pae.postinst line 268.
initrd.img(/boot/initrd.img-3.9-1-686-pae
) points to /boot/initrd.img-3.9-1-686-pae
(/boot/initrd.img-3.9-1-686-pae) -- doing nothing at /var/lib/dpkg/info/linux-
image-3.9-1-686-pae.postinst line 268.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
update-initramfs: Generating /boot/initrd.img-3.9-1-686-pae
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
P: Checking for EXTLINUX directory... found.
P: Writing config for /boot/vmlinuz-3.9-1-686-pae...
P: Writing config for /boot/vmlinuz-3.8-2-686-pae...
P: Writing config for /boot/vmlinuz-3.8-1-686-pae...
P: Writing config for /boot/vmlinuz-3.2.0-4-686-pae...
P: Writing config for Windows 7 (loader) on /dev/sda1...
P: Installing debian theme... done.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
Creazione di grub.cfg...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-
image-3.9-1-686-pae.postinst line 696.
dpkg: errore nell'elaborare linux-image-3.9-1-686-pae (--configure):
il sottoprocesso installato script di post-installation ha restituito lo stato
di errore 1
Configurazione di grub-pc (2.00-15)...
Installazione completata, nessun errore segnalato.
Creazione di grub.cfg...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
dpkg: errore nell'elaborare grub-pc (--configure):
il sottoprocesso installato script di post-installation ha restituito lo stato
di errore 1
dpkg: problemi con le dipendenze impediscono la configurazione di linux-
image-686-pae:
linux-image-686-pae dipende da linux-image-3.9-1-686-pae; comunque:
Il pacchetto linux-image-3.9-1-686-pae non è ancora configurato.
dpkg: errore nell'elaborare linux-image-686-pae (--configure):
problemi con le dipendenze - lasciato non configurato
Si sono verificati degli errori nell'elaborazione:
linux-image-3.9-1-686-pae
grub-pc
linux-image-686-pae
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/136c4dd3-50f0-403b-b91a-84457ef2051f / ext4
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda2 /mnt/windows fuseblk
rw,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-TOSHIBA_MK5076GSX_61DTD1C4B
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/#00_header# ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 136c4dd3-50f0-403b-b91a-84457ef2051f
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=1366x768
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 136c4dd3-50f0-403b-b91a-84457ef2051f
set locale_dir=($root)/boot/grub/locale
set lang=it_IT
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/#00_header# ###
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
Bug#706525: marked as done (chicken: CVE-2013-2024: OS command injection vulnerability)
Your message dated Wed, 17 Jul 2013 16:34:01 +0200 with message-id 20130717143401.ga29...@elende.valinor.li and subject line Re: Bug#706525: chicken: CVE-2013-2024: OS command injection vulnerability has caused the Debian Bug report #706525, regarding chicken: CVE-2013-2024: OS command injection vulnerability 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.) -- 706525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: chicken Version: 4.5.0-1 Severity: grave Tags: security patch Hi, @Release Team: This probably should not delay the release for wheezy, as chicken has other security relevant bugreport open (#702410) with wheezy-ignore tag. The same can be done here, IMO. the following vulnerability was published for chicken. CVE-2013-2024[0]: OS command injection vulnerability in Chicken Scheme If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information and patch see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2024 http://security-tracker.debian.org/tracker/CVE-2013-2024 [1] http://lists.nongnu.org/archive/html/chicken-hackers/2013-02/msg00135.html [2] http://lists.nongnu.org/archive/html/chicken-announce/2013-04/msg0.html [3] http://lists.nongnu.org/archive/html/chicken-hackers/2013-04/msg00060.html Regards, Salvatore ---End Message--- ---BeginMessage--- Source: chicken Source-Version: 4.8.0.3-1 Fixed with chicken/4.8.0.3-1 upload.---End Message---
Bug#717175: rubyluabridge: Contains unattributed copied Lua source code
Package: rubyluabridge Version: 0.7.0 Severity: serious Dear maintainer, Please document that this package contains some MIT-licensed code in debian/copyright. rubyluabridge.cc: // copied from: // http://www.lua.org/source/5.1/lbaselib.c.html#luaB_tostring Cheers, Luke -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise'), (100, 'precise-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-48-generic (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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702410: marked as done (chicken: CVE-2012-6122 CVE-2012-6123 CVE-2012-6124 CVE-2012-6125 CVE-2013-1874)
Your message dated Wed, 17 Jul 2013 16:32:52 +0200 with message-id 20130717143252.ga29...@elende.valinor.li and subject line Re: Bug#702410: chicken: CVE-2012-6122 CVE-2012-6123 CVE-2012-6124 CVE-2012-6125 has caused the Debian Bug report #702410, regarding chicken: CVE-2012-6122 CVE-2012-6123 CVE-2012-6124 CVE-2012-6125 CVE-2013-1874 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.) -- 702410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: chicken Severity: grave Tags: security Hi, multiple security issues have been found in chicken. Please see here for more information: http://marc.info/?l=oss-securitym=136030422026406w=2 These are fixed in sid, but if simple, isolated backports of the changes can be identified, we could still fix this up before the Wheezy release or in a later point update. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: chicken Source-Version: 4.8.0.3-1 Fixed in version 4.8.0.3-1.---End Message---
Bug#717177: grub-pc: impossible to have a working grub or a working kernel
On Wed, Jul 17, 2013 at 04:10:52PM +0200, cosimo morelli wrote: Package: grub-pc Version: 2.00-15 Severity: critical Justification: breaks the whole system Dear Maintainer, mew version and same shit This sort of language does not persuade me to spend much time helping you. Please tone it down. Creazione di grub.cfg... Found background image: /usr/share/images/desktop-base/desktop-grub.png run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 The output of this command, run as root, would help: sh -x /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713148: marked as done (rubyluabridge: FTBFS: ERROR: 'rake/rdoctask' is obsolete and no longer supported. Use 'rdoc/task' (available in RDoc 2.4.2+) instead.)
Your message dated Wed, 17 Jul 2013 15:00:06 + with message-id e1uztd4-0008t7...@franck.debian.org and subject line Bug#713148: fixed in rubyluabridge 0.7.0-2 has caused the Debian Bug report #713148, regarding rubyluabridge: FTBFS: ERROR: 'rake/rdoctask' is obsolete and no longer supported. Use 'rdoc/task' (available in RDoc 2.4.2+) instead. 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.) -- 713148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rubyluabridge Version: 0.7.0-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: debian/rules build dh_testdir build/extconf_ubuntu.sh checking for lua.h... yes checking for lua_pushvalue() in -llua5.1... yes creating Makefile rake rake aborted! ERROR: 'rake/rdoctask' is obsolete and no longer supported. Use 'rdoc/task' (available in RDoc 2.4.2+) instead. /«PKGBUILDDIR»/Rakefile:1:in `top (required)' (See full trace by running task with --trace) make: *** [build-stamp] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/rubyluabridge_0.7.0-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: rubyluabridge Source-Version: 0.7.0-2 We believe that the bug you reported is fixed in the latest version of rubyluabridge, 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. Roberto C. Sanchez robe...@connexer.com (supplier of updated rubyluabridge 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: Tue, 16 Jul 2013 19:30:48 -0400 Source: rubyluabridge Binary: ruby-luabridge libluabridge-ruby1.8 libluabridge-ruby Architecture: source all amd64 Version: 0.7.0-2 Distribution: unstable Urgency: low Maintainer: Athena Capital Research acr-deb...@athenacr.com Changed-By: Roberto C. Sanchez robe...@connexer.com Description: libluabridge-ruby - access Lua from Ruby - transitional package libluabridge-ruby1.8 - access Lua from Ruby (Ruby 1.8) - transitional package ruby-luabridge - access Lua from Ruby Closes: 713148 Changes: rubyluabridge (0.7.0-2) unstable; urgency=low . * Acknowledge NMU, thanks to Scott Kitterman * Patch Rakefile to work with newer rake version (Closes: #713148) * Rename libluabridge-ruby and libluabridge-ruby1.8 to ruby-luabridge * Build arch:all only when binary-indep called * Build with hardening options * Update to Standards-Version 3.9.4 (no changes) Checksums-Sha1: 7d21a4ed86829c58b383431287c9dd016dd89229 2168 rubyluabridge_0.7.0-2.dsc d176832ca3c8422cd52865be6bc209b9309cf7ed 4841 rubyluabridge_0.7.0-2.debian.tar.gz 164b34fdbcb5855361a00e0f5cc5417a1c6e3dd5 3040 libluabridge-ruby1.8_0.7.0-2_all.deb f0032f43b65ee247d432c5a5f0a68722c08aa6e1 3008 libluabridge-ruby_0.7.0-2_all.deb b9512d281c5665d1168240c1c2150037509a96b0 86254 ruby-luabridge_0.7.0-2_amd64.deb Checksums-Sha256: 4d318db230d9fbe67fb4847286e4dc3a22c51c423e08183ae30755bf55a76283 2168 rubyluabridge_0.7.0-2.dsc 250a8a9f42eafcf59cb3400e5f4ebb611a99e1f77bd2f0e5fefa98025adad207 4841 rubyluabridge_0.7.0-2.debian.tar.gz c5d32207bc120a3da9bbbc376591cfc11cc9818b146ebda270857bc218dfca0a 3040 libluabridge-ruby1.8_0.7.0-2_all.deb bd1d7c352c3631024ab5e6081e121f020b16c5a47519a5485d33ed305df69f43 3008 libluabridge-ruby_0.7.0-2_all.deb 2431f6ea054a67100bda1f333171f5f60fbb7ae54d4e01930acd8f9530514407 86254 ruby-luabridge_0.7.0-2_amd64.deb Files: 8a07d1b2fc10a6054a6d9582954a7818 2168 ruby optional rubyluabridge_0.7.0-2.dsc
Bug#707361: marked as done (clinica: FTBFS: GIRepository-2.0.gir:240.11-240.30: error: expected start element of `parameter')
Your message dated Wed, 17 Jul 2013 15:00:08 + with message-id e1uztd6-0008tl...@franck.debian.org and subject line Bug#707361: fixed in clinica 0.3.0-1 has caused the Debian Bug report #707361, regarding clinica: FTBFS: GIRepository-2.0.gir:240.11-240.30: error: expected start element of `parameter' 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.) -- 707361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: clinica Version: 0.2.1~dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 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»' ./waf --nocache build Waf: Entering directory `/«PKGBUILDDIR»/_build_' [ 1/76] valac: libclinica/DoctorContextMenu.vala libclinica/VisitBrowser.vala libclinica/PluginManager.vala libclinica/Medicine.vala libclinica/MedicineDetailDialog.vala libclinica/PatientFilteredStore.vala libclinica/Visit.vala libclinica/DateSwitcher.vala libclinica/MedicineTreeView.vala libclinica/PatientListView.vala libclinica/PatientListStore.vala libclinica/StartPage.vala libclinica/CalendarEventList.vala libclinica/Calendar.vala libclinica/UserInterfaceActivatable.vala libclinica/Settings.vala libclinica/VisitDetail.vala libclinica/EventEditor.vala libclinica/Patient.vala libclinica/VisitTab.vala libclinica/MedicineSearchEngine.vala libclinica/Day.vala libclinica/CalendarHeader.vala libclinica/DoctorEditor.vala libclinica/FindEntry.vala libclinica/AboutDialog.vala libclinica/Utils.vala libclinica/EventListStore.vala libclinica/PatientListPage.vala libclinica/Event.vala libclinica/CalendarToolbar.vala libclinica/VisitListStore.vala libclinica/CalendarView.vala libclinica/SqlDataType.vala libclinica/Page.vala libclinica/VisitWindow.vala libclinica/DoctorListPage.vala libclinica/DoctorListStore.vala libclinica/VisitToolbar.vala libclinica/CalendarWindow.vala libclinica/DateHandler.vala libclinica/SettingsManager.vala libclinica/ResourceManager.vala libclinica/VisitActions.vala libclinica/UserInterface.vala libclinica/DoctorFilteredStore.vala libclinica/DoctorListView.vala libclinica/MedicineSearchPage.vala libclinica/PatientDetail.vala libclinica/EventDetail.vala libclinica/PatientEntry.vala libclinica/PluginEngine.vala libclinica/VisitPrinter.vala libclinica/PatientEditorActivatable.vala libclinica/PatientContextMenu.vala libclinica/PatientEditor.vala libclinica/Doctor.vala - _build_/libclinica/clinica.h _build_/libclinica/clinica.vapi _build_/libclinica/Clinica-0.2.gir _build_/libclinica/clinica.deps _build_/libclinica/DoctorContextMenu.c _build_/libclinica/VisitBrowser.c _build_/libclinica/PluginManager.c _build_/libclinica/Medicine.c _build_/libclinica/MedicineDetailDialog.c _build_/libclinica/PatientFilteredStore.c _build_/libclinica/Visit.c _build_/libclinica/DateSwitcher.c _build_/libclinica/MedicineTreeView.c _build_/libclinica/PatientListView.c _build_/libclinica/PatientListStore.c _build_/libclinica/StartPage.c _build_/libclinica/CalendarEventList.c _build_/libclinica/Calendar.c _build_/libclinica/UserInterfaceActivatable.c _build_/libclinica/Settings.c _build_/libclinica/VisitDetail.c _build_/libclinica/EventEditor.c _build_/libclinica/Patient.c _build_/libclinica/VisitTab.c _build_/libclinica/MedicineSearchEngine.c _build_/libclinica/Day.c _build_/libclinica/CalendarHeader.c _build_/libclinica/DoctorEditor.c _build_/libclinica/FindEntry.c _build_/libclinica/AboutDialog.c _build_/libclinica/Utils.c _build_/libclinica/EventListStore.c _build_/libclinica/PatientListPage.c _build_/libclinica/Event.c _build_/libclinica/CalendarToolbar.c _build_/libclinica/VisitListStore.c _build_/libclinica/CalendarView.c _build_/libclinica/SqlDataType.c _build_/libclinica/Page.c _build_/libclinica/VisitWindow.c _build_/libclinica/DoctorListPage.c _build_/libclinica/DoctorListStore.c _build_/libclinica/VisitToolbar.c _build_/libclinica/CalendarWindow.c _build_/libclinica/DateHandler.c _build_/libclinica/SettingsManager.c _build_/libclinica/ResourceManager.c _build_/libclinica/VisitActions.c _build_/libclinica/UserInterface.c _build_/libclinica/DoctorFilteredStore.c _build_/libclinica/DoctorListView.c _build_/libclinica/MedicineSearchPage.c _build_/libclinica/PatientDetail.c _build_/libclinica/EventDetail.c _build_/libclinica/PatientEntry.c
Processed: Re: [Pkg-utopia-maintainers] Bug#717081: network-manager: Segementation fault when 'nm-applet' and 'nm-connection-editor' as non-root
Processing commands for cont...@bugs.debian.org: reassign 717081 gtk3-engines-unico Bug #717081 [network-manager-gnome] network-manager: Segementation fault when 'nm-applet' and 'nm-connection-editor' as non-root Bug reassigned from package 'network-manager-gnome' to 'gtk3-engines-unico'. Ignoring request to alter found versions of bug #717081 to the same values previously set Ignoring request to alter fixed versions of bug #717081 to the same values previously set forcemerge 706330 717081 Bug #706330 [gtk3-engines-unico] Some applications segfaults after upgrade to 3.8.0-1 Bug #709548 [gtk3-engines-unico] libgtk-3-0: most recent gtk upload breaks (nearly) everything (in GNOME) Bug #709946 [gtk3-engines-unico] gnome-settings-daemon: Segmentation fault during startup Bug #716714 [gtk3-engines-unico] dwb: Segmentation fault on startup Bug #716771 [gtk3-engines-unico] libgtk-3-0: Segmentation fault in gtk_style_context_get_valist Bug #717081 [gtk3-engines-unico] network-manager: Segementation fault when 'nm-applet' and 'nm-connection-editor' as non-root Severity set to 'critical' from 'important' Marked as found in versions gtk3-engines-unico/1.0.2-1. Added tag(s) patch and wheezy-ignore. Bug #716771 [gtk3-engines-unico] libgtk-3-0: Segmentation fault in gtk_style_context_get_valist Added tag(s) moreinfo. Added tag(s) moreinfo. Added tag(s) moreinfo. Added tag(s) moreinfo. Added tag(s) moreinfo. Bug #709548 [gtk3-engines-unico] libgtk-3-0: most recent gtk upload breaks (nearly) everything (in GNOME) Bug #709946 [gtk3-engines-unico] gnome-settings-daemon: Segmentation fault during startup Bug #716714 [gtk3-engines-unico] dwb: Segmentation fault on startup Merged 706330 709548 709946 716714 716771 717081 thanks Stopping processing here. Please contact me if you need assistance. -- 706330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706330 709548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709548 709946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709946 716714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716714 716771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716771 717081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717081 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#712038: marked as done (Missing copyright information)
Your message dated Wed, 17 Jul 2013 15:50:02 + with message-id e1uztzo-00023e...@franck.debian.org and subject line Bug#712038: fixed in orthanc 0.6.0-1 has caused the Debian Bug report #712038, regarding Missing copyright information 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.) -- 712038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: orthanc Version: 0.4.0-1 Severity: serious File: orthanc Tags: upstream Neither d/copyright nor upstream COPYING seems to inform that source contains code lifted from another project: $ grep BSD OrthancServer/FromDcmtkBridge.cpp * Mathieu Malaterre (under a BSD license). ---End Message--- ---BeginMessage--- Source: orthanc Source-Version: 0.6.0-1 We believe that the bug you reported is fixed in the latest version of orthanc, 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 712...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne s.jodo...@gmail.com (supplier of updated orthanc 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: Wed, 17 Jul 2013 10:55:49 +0200 Source: orthanc Binary: orthanc Architecture: source amd64 Version: 0.6.0-1 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Sebastien Jodogne s.jodo...@gmail.com Description: orthanc- RESTful DICOM server for healthcare and medical research Closes: 712038 716958 Changes: orthanc (0.6.0-1) unstable; urgency=low . [ Sebastien Jodogne ] * New upstream version: 0.6.0 * Fix image preview. Closes: #716958 * Fix missing copyright information. Closes: #712038 * Remove explicit dependency on boost1.53 . [ Mathieu Malaterre ] * Remove RelWithDebInfo, because of change in behavior in cmake Checksums-Sha1: 1580d35ee09fb4a5123c2e9da29cfcf9dc9b0fcf 2226 orthanc_0.6.0-1.dsc f0bd96f1a6d70bc298f96adc1f6cf23ae7ea6eeb 429962 orthanc_0.6.0.orig.tar.gz d2d8ee65c7af7668d6ba50f7d9f0c476511ef453 119394 orthanc_0.6.0-1.debian.tar.gz 24994b4d5acdc9ed57d03326f22df5a90aefb7ad 530954 orthanc_0.6.0-1_amd64.deb Checksums-Sha256: 453737cc20aaf7387b2b5ad4b0f5842de0d5e40fed75532c2e55a77ffaa1bfcc 2226 orthanc_0.6.0-1.dsc e65bc491cd8671a78645dc9b8e442244a353d392485f7220c7312ba6649eed50 429962 orthanc_0.6.0.orig.tar.gz 12a7ec8c268efa8c5d79611a30c495fbd4bc706bc805a2c79f840cd3a6ae8e29 119394 orthanc_0.6.0-1.debian.tar.gz 463565211b4ccb3e7142bc6eb34aa01bb64c29cbff857e9da9dc0b2be4678d97 530954 orthanc_0.6.0-1_amd64.deb Files: d365a0a7fa001683082caca3963ef663 2226 science optional orthanc_0.6.0-1.dsc 7947a35126668c59b0ed3be4fef771d0 429962 science optional orthanc_0.6.0.orig.tar.gz 0122454fc96880a010ecd01906c227bb 119394 science optional orthanc_0.6.0-1.debian.tar.gz 008a59794164cd46149e103add89990c 530954 science optional orthanc_0.6.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJR5rivAAoJEAFx4YKK4JNF5WUP/iGhN2579Bn4j8esjrU8D+sv 3FDHaCp7p9GEsvbe2/xwaNUXfPdxMTTOddcwsLpAol4fLVSB+0/mODnZ7OnXQC69 Jambfqoun8TJJYRO0cEcz/SWJ4rGyYEIrdvAKA8278bWO1UOWdTbGM4hHp652+2p Ugc1HSPCvIzN5WaishCoCSSa3mFtsDccJ7JDmUwrRuMPhoAell+xAHsOG7VCrIeu +ZIeKsBQillzBtUy2gPWsn5kypj77tyyec9z8hObq5C4Pe+DwISPWFEKby6JEOLa UP0l4PKhYJyUzFoYzSwbmccBiNldbYk2NO0QFIOQwZ9VPGkjnrzLhgZw0wHQr6xg BfI2pZKXZnLkxlEDZhUBD3HXO6gOK6yLSvs6DjRe5vMVbpPRnSPRX+VIss+oCVD+ 8VB8iLPgjmlBHNEpESvHQv33bV8DkohBngUxKwm0g/0HTDEYDJ7uJ9ea4jtCy0ip Cv3YRe2AixP5HZciFU/paJBAANl3/cF+C4Ws84ueD3Ov/TrrGkk+eWMuOCLNlgXJ c6MHaewP+36kJ+9uOvqf2CY7NUaSV2bf6khAi6K1eeQJH1HuZ7/oRoxGWRZLW6sP senTpirM/LqfydX7oVQwDpfOl0pcIYu3YMeimyXQibZBz6GAij5NlcadNEawjZ3v YGpn5F+VLg/vxXzL8rPo =uJWJ -END PGP SIGNATUREEnd Message---
Bug#717177: marked as done (grub-pc: impossible to have a working grub or a working kernel)
Your message dated Wed, 17 Jul 2013 17:20:50 +0100
with message-id 20130717162050.gl27...@riva.ucam.org
and subject line Re: Bug#717177: grub-pc: impossible to have a working grub or
a working kernel
has caused the Debian Bug report #717177,
regarding grub-pc: impossible to have a working grub or a working kernel
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.)
--
717177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: grub-pc
Version: 2.00-15
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
mew version and same shit
E: Sub-process /usr/bin/dpkg returned an error code (1)
Errore durante l'installazione di un pacchetto. Tentativo di ripristino:
Configurazione di linux-image-3.9-1-686-pae (3.9.8-1)...
Running depmod.
vmlinuz(/boot/vmlinuz-3.9-1-686-pae
) points to /boot/vmlinuz-3.9-1-686-pae
(/boot/vmlinuz-3.9-1-686-pae) -- doing nothing at /var/lib/dpkg/info/linux-
image-3.9-1-686-pae.postinst line 268.
initrd.img(/boot/initrd.img-3.9-1-686-pae
) points to /boot/initrd.img-3.9-1-686-pae
(/boot/initrd.img-3.9-1-686-pae) -- doing nothing at /var/lib/dpkg/info/linux-
image-3.9-1-686-pae.postinst line 268.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
update-initramfs: Generating /boot/initrd.img-3.9-1-686-pae
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
P: Checking for EXTLINUX directory... found.
P: Writing config for /boot/vmlinuz-3.9-1-686-pae...
P: Writing config for /boot/vmlinuz-3.8-2-686-pae...
P: Writing config for /boot/vmlinuz-3.8-1-686-pae...
P: Writing config for /boot/vmlinuz-3.2.0-4-686-pae...
P: Writing config for Windows 7 (loader) on /dev/sda1...
P: Installing debian theme... done.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.9-1-686-pae
/boot/vmlinuz-3.9-1-686-pae
Creazione di grub.cfg...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-
image-3.9-1-686-pae.postinst line 696.
dpkg: errore nell'elaborare linux-image-3.9-1-686-pae (--configure):
il sottoprocesso installato script di post-installation ha restituito lo stato
di errore 1
Configurazione di grub-pc (2.00-15)...
Installazione completata, nessun errore segnalato.
Creazione di grub.cfg...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
dpkg: errore nell'elaborare grub-pc (--configure):
il sottoprocesso installato script di post-installation ha restituito lo stato
di errore 1
dpkg: problemi con le dipendenze impediscono la configurazione di linux-
image-686-pae:
linux-image-686-pae dipende da linux-image-3.9-1-686-pae; comunque:
Il pacchetto linux-image-3.9-1-686-pae non è ancora configurato.
dpkg: errore nell'elaborare linux-image-686-pae (--configure):
problemi con le dipendenze - lasciato non configurato
Si sono verificati degli errori nell'elaborazione:
linux-image-3.9-1-686-pae
grub-pc
linux-image-686-pae
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/136c4dd3-50f0-403b-b91a-84457ef2051f / ext4
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda2 /mnt/windows fuseblk
rw,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-TOSHIBA_MK5076GSX_61DTD1C4B
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/#00_header# ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
Processed: Re: epiphany-browser seems to lack a dependency on gnome-icon-theme-symbolic
Processing commands for cont...@bugs.debian.org: severity 705665 serious Bug #705665 [epiphany-browser] epiphany-browser is missing button icons! Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 705665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705665 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#714279: marked as done (fontconfig-config: Not correct view anti-aliasing fonts and incorrect visualization.)
reopen 714279 thanks Please don't close this bug (even when you are the original reporter) only because you managed to find a workaround. This issue has to be fixed in a way that no user will run into it in the future after an upgrade. cu Adrian On Sat, Jul 13, 2013 at 11:15:05PM +, Debian Bug Tracking System wrote: Your message dated Sun, 14 Jul 2013 01:11:10 +0200 with message-id 51e1de8e.4040...@local.sjlopezb.es and subject line fontconfig has caused the Debian Bug report #714279, regarding fontconfig-config: Not correct view anti-aliasing fonts and incorrect visualization. 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.) -- 714279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Date: Thu, 27 Jun 2013 15:40:32 +0200 From: Santiago José López Borrazás sjlop...@gmx.es To: Debian Bug Tracking System sub...@bugs.debian.org Subject: fontconfig-config: Not correct view anti-aliasing fonts and incorrect visualization. Package: fontconfig-config Version: 2.10.2-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? The fonts are not shown correctly, they are smaller than normal. * What exactly did you do (or not do) that was effective (or ineffective)? thing more Ask the installation, deleting files essential to Windows fonts and dejavu * What was the outcome of this action? Fonts smaller and less anti-aliasing * What outcome did you expect instead? The same fonts and display the version 2.9.0.7-1. : ( Files changes: ~/.fonts.config at ~/.config/fonts/fonts.config ~/.fontconfig at ~/.cache/fontconfig ~/.fonts at ~/.local/share/fonts And creates links this directories. File fonts.conf: ?xml version='1.0'? !DOCTYPE fontconfig SYSTEM 'fonts.dtd' fontconfig match target=font edit mode=assign name=rgba constrgb/const /edit /match match target=font edit mode=assign name=hinting booltrue/bool /edit /match match target=font edit mode=assign name=hintstyle consthintfull/const /edit /match match target=font edit mode=assign name=antialias booltrue/bool /edit /match /fontconfig *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.9.5 (SMP w/2 CPU cores) Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages fontconfig-config depends on: ii debconf [debconf-2.0] 1.5.50 ii fonts-freefont-ttf [ttf-freefont] 20120503-1 ii gsfonts-x110.22 ii ttf-bitstream-vera 1.10-8 ii ttf-dejavu-core2.33+svn2514-3 ii ttf-freefont 20120503-1 ii ucf3.0027 fontconfig-config recommends no packages. fontconfig-config suggests no packages. -- debconf information: * fontconfig/subpixel_rendering: Always * fontconfig/enable_bitmaps: true * fontconfig/hinting_type: Autohinter Date: Sun, 14 Jul 2013 01:11:10 +0200 From: Santiago José López Borrazás sjlop...@gmx.es To: 714279-d...@bugs.debian.org Subject: fontconfig Close. Solved. -- Saludos de Santiago José López Borrazás. -- 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#714279: marked as done (fontconfig-config: Not correct view anti-aliasing fonts and incorrect visualization.)
Processing commands for cont...@bugs.debian.org:
reopen 714279
Bug #714279 {Done: Santiago José López Borrazás sjlop...@gmx.es}
[fontconfig-config] fontconfig-config: Not correct view anti-aliasing fonts and
incorrect visualization.
Bug reopened
Ignoring request to alter fixed versions of bug #714279 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
714279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714279
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#714279: marked as done (fontconfig-config: Not correct view anti-aliasing fonts and incorrect visualization.)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 El 17/07/13 19:20, Adrian Bunk escribió: reopen 714279 thanks Please don't close this bug (even when you are the original reporter) only because you managed to find a workaround. This issue has to be fixed in a way that no user will run into it in the future after an upgrade. Ok. Sorry. - -- Saludos de Santiago José López Borrazás. -BEGIN PGP SIGNATURE- iQIVAwUBUebkwIFZAuZYtJmMAQoNog//WeyzuC5AVdqHmV6RbaoeltyfUXr1iTHk YcLrlZeWT13bWCcPoL39nRMy6rw2pZvwcJKMXpyBW1YtfF3W6IgxvXjsnCyCiFye JxwfyAqDz7bHd5fSMX9i0J60Ef19KcOjUylHBgK5YYPGLAS2tTu3VEYD7tqbN6KP 3RGvVTmBihjHEGvvCa5OQBXswr4O1RFToAfFmNi//O9zlXzb+tzd9SaOmJlKnxgL da0Yl21P6soXVC6myQsuA6w2i6LeOdf8HIwA7eAxgfq9vfJGoduKAy1vIvdMvBAr PmY8E47Hf2HjlhVhrADgFhLRSFxIU0I2115oAAwJh8daPPaoge7Gt1UNIaIvxNAb XnEb9qzz0kXVDSDMi3Y3/RkIfAnkLJwTlvGWqrUzHQo36nTBpPRHy0vqTEVz0UXV MbGhRPGgpYXKXuQWr8EYS/Hy4qQhsT3FbSDb9VbQRbm1vSAOMZF0yde1AUJotL9L BnNfKwLxRcwai3l9+C/zB6teMfw6BjnYqflXL+jNlTwU2UqhZxBgEwlUPHZqjPIT zXFqcg6H27WS9NU1jTNYCVl3Lg/mr77PTz/MpWBszNnXjP0pGcgjLiGvOCWQkarx AwSsbPIXi0iezxcMQd6SfHVgGr1baNrfKpBvPRVC9S7WA39aGqztQbq1fJCZNwyZ fHtGRMe3A0U= =KhWb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717190: Leaves RAID sync speed set to 0
Package: hdparm Version: 9.39-1+b1 Severity: grave File: /lib/udev/rules.d/85-hdparm.rules X-Debbugs-CC: anth...@derobert.net I enabled RAID_WORKAROUND, and it managed to leave sync_speed_min and sync_speed_max set to 0. That of course had a degraded RAID array sitting there, not rebuilding—a scenario that puts data at great risk. Looking at the scripts, I think what happens is that 85-hdparm.rules calls the init script, which does: 1. save current value of sync speeds to variables 2. change both to 0. 3. call hdparm 4. restore from variables. but udev works in parallel, so multiple hotplugs can happen at once. Leading to a race: a1. save (200k) a2. change (from 200k to 0) b1. save (this will save 0!) a3. hdparm b2. change (from 0 to 0) b3. hdparm a4. restore (back to 200k) b4. restore (back to 0) (!) Of course, that race can go other ways, such as calling hdparm with the rebuild in progress (which supposedly corrupts data). Or both could happen. The most obvious approach to fix this is locking. There are related bugs, such as each RAID array actually can use a non-default set of sync speed parameters, set in /sys. But I think that can be documented and left to the user to solve. -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) 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 hdparm depends on: ii libc6 2.13-38 ii lsb-base 4.1+Debian8+deb7u1 Versions of packages hdparm recommends: ii powermgmt-base 1.31 Versions of packages hdparm suggests: pn apmd none -- Configuration Files: /etc/default/hdparm changed: harddisks=/dev/sd[a-f] hdparm_opts=-B 255 RAID_WORKAROUND=yes -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712340: marked as done (monotone: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors))
Your message dated Wed, 17 Jul 2013 18:48:30 + with message-id e1uzwm6-0004nf...@franck.debian.org and subject line Bug#712340: fixed in monotone 1.0-9 has caused the Debian Bug report #712340, regarding monotone: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into 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.) -- 712340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: monotone Version: 1.0-8 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130609 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[3]: Entering directory `/«PKGBUILDDIR»/doc' rm -rf monotone.htp if /bin/bash /«PKGBUILDDIR»/missing --run makeinfo --html -I ../src -I . --number-sections --no-split --no-headers --css-ref=texinfo.css -I . \ -o monotone.htp monotone.texi; \ then \ rm -rf monotone.html; \ if test ! -d monotone.htp test -d monotone; then \ mv monotone monotone.html; else mv monotone.htp monotone.html; fi; \ else \ if test ! -d monotone.htp test -d monotone; then \ rm -rf monotone; else rm -Rf monotone.htp monotone.html; fi; \ exit 1; \ fi monotone.texi:4782: @itemx must follow @item monotone.texi:6153: @itemx must follow @item monotone.texi:12100: warning: @item missing argument ./pcrepattern.texi:77: warning: @itemx should not begin @table ./pcrepattern.texi:79: @itemx must follow @item ./pcrepattern.texi:81: @itemx must follow @item ./pcrepattern.texi:83: @itemx must follow @item ./pcrepattern.texi:85: @itemx must follow @item ./pcrepattern.texi:87: @itemx must follow @item ./pcrepattern.texi:89: @itemx must follow @item ./pcrepattern.texi:91: @itemx must follow @item ./pcrepattern.texi:93: @itemx must follow @item ./pcrepattern.texi:97: @itemx must follow @item ./pcrepattern.texi:99: @itemx must follow @item ./pcrepattern.texi:102: @itemx must follow @item ./pcrepattern.texi:111: warning: @itemx should not begin @table ./pcrepattern.texi:113: @itemx must follow @item ./pcrepattern.texi:115: @itemx must follow @item ./pcrepattern.texi:117: @itemx must follow @item ./pcrepattern.texi:120: @itemx must follow @item ./pcrepattern.texi:162: warning: @itemx should not begin @table ./pcrepattern.texi:164: @itemx must follow @item ./pcrepattern.texi:166: @itemx must follow @item ./pcrepattern.texi:168: @itemx must follow @item ./pcrepattern.texi:170: @itemx must follow @item ./pcrepattern.texi:172: @itemx must follow @item ./pcrepattern.texi:174: @itemx must follow @item ./pcrepattern.texi:176: @itemx must follow @item ./pcrepattern.texi:178: @itemx must follow @item ./pcrepattern.texi:180: @itemx must follow @item ./pcrepattern.texi:247: warning: @itemx should not begin @table ./pcrepattern.texi:249: @itemx must follow @item ./pcrepattern.texi:252: @itemx must follow @item ./pcrepattern.texi:254: @itemx must follow @item ./pcrepattern.texi:257: @itemx must follow @item ./pcrepattern.texi:259: @itemx must follow @item ./pcrepattern.texi:261: @itemx must follow @item ./pcrepattern.texi:264: @itemx must follow @item ./pcrepattern.texi:267: @itemx must follow @item ./pcrepattern.texi:297: warning: @itemx should not begin @table ./pcrepattern.texi:299: @itemx must follow @item ./pcrepattern.texi:301: @itemx must follow @item ./pcrepattern.texi:303: @itemx must follow @item ./pcrepattern.texi:305: @itemx must follow @item ./pcrepattern.texi:307: @itemx must follow @item ./pcrepattern.texi:309: @itemx must follow @item ./pcrepattern.texi:311: @itemx must follow @item ./pcrepattern.texi:313: @itemx must follow @item ./pcrepattern.texi:315: @itemx must follow @item ./pcrepattern.texi:345: warning: @itemx should not begin @table ./pcrepattern.texi:347: @itemx must follow @item ./pcrepattern.texi:349: @itemx must follow @item ./pcrepattern.texi:351: @itemx must follow @item ./pcrepattern.texi:353: @itemx must follow @item ./pcrepattern.texi:357: @itemx must follow @item ./pcrepattern.texi:359: @itemx must follow @item ./pcrepattern.texi:361: @itemx must follow @item ./pcrepattern.texi:363: @itemx must follow @item ./pcrepattern.texi:365: @itemx must follow @item ./pcrepattern.texi:367: @itemx must follow @item ./pcrepattern.texi:371: @itemx must follow @item ./pcrepattern.texi:373: @itemx
Bug#716705: konsole: libpulse0 vesion 4 is not listed as a dependency for konsole.
reassign 716705 libpulse-mainloop-glib0 forcemerge 712919 716705 thanks Hi, Alle giovedì 11 luglio 2013, ami ha scritto: libpulse0 vesion 4 is not listed as a dependency for konsole. konsole: error while loading shared libraries: libpulsecommon-4.0.so: cannot open shared object file: No such file or directory ldd /usr/bin/konsole | grep pulse libpulse.so.0 = /usr/lib/x86_64-linux-gnu/libpulse.so.0 (0x7fcecaf64000) libpulse-mainloop-glib.so.0 = /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0 (0x7fcecad5f000) libpulsecommon-2.0.so = /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.0.so (0x7fcec8ce2000) libpulsecommon-4.0.so = not found This is a duplicate of #716705 (too loose dependencies in pulse packages). -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: reassign 716705 to libpulse-mainloop-glib0, forcibly merging 712919 716705
Processing commands for cont...@bugs.debian.org: reassign 716705 libpulse-mainloop-glib0 Bug #716705 [konsole] konsole: libpulse0 vesion 4 is not listed as a dependency for konsole. Bug reassigned from package 'konsole' to 'libpulse-mainloop-glib0'. No longer marked as found in versions konsole/4:4.8.4-3. Ignoring request to alter fixed versions of bug #716705 to the same values previously set forcemerge 712919 716705 Bug #712919 [libpulse-mainloop-glib0] gnome-shell: error while loading shared libraries: libpulsecommon-4.0.so: cannot open shared object file: No such file or directory Bug #716705 [libpulse-mainloop-glib0] konsole: libpulse0 vesion 4 is not listed as a dependency for konsole. Marked as found in versions pulseaudio/3.0-1. Added tag(s) sid and jessie. Merged 712919 716705 thanks Stopping processing here. Please contact me if you need assistance. -- 712919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712919 716705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716705 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#678696: Your patch works
Hi Goswin, I had reported the bug #712984 which has been merged with this bug #678696. I am using Debian/Testing and have initramfs-tools-0.113 and lvm2_2.02.95-7 installed. I have my root and swap on logical volumes of the lvm. This configuration didn't work for the new 3.9 kernel. Now, I have used your patch initramfs-tools-0.106.events.patch and created a NMU package for initramfs-tools. I also added your lmv2 script as lvm2-2.02.95/debian/tree/lvm2/usr/share/initramfs-tools/scripts/local-block/lvm2 and created there a NMU package too. Using those updated packages, I could boot my system using the new kernel. So as a test report: Your changes do work. Regards, Vincent Smeets
Bug#717177: closed by Colin Watson cjwat...@debian.org (Re: Bug#717177: grub-pc: impossible to have a working grub or a working kernel)
Adding set -x near the top of /etc/grub.d/07_debian_theme may help diagnose exactly what's going on; but perhaps this is simply a leftover from some local experiment and should be removed in favour of /etc/grub.d/05_debian_theme. Oh so the problem is the file /etc/grub.d/07_debian_theme ? I have just to remove the file or I have to modify something inside the other files of grub? P.S. I know that we are all full of work in this period, my frustration comes from the fact that I can't turn off the pc and every time I do an upgrade I have to remove the file /boot/grub/grub.cfg.new or I have to put a live distrution inside and replace all the files with my backup of the folders of Grub :) 2013/7/17 Debian Bug Tracking System ow...@bugs.debian.org This is an automatic notification regarding your Bug report which was filed against the grub-pc package: #717177: grub-pc: impossible to have a working grub or a working kernel It has been closed by Colin Watson cjwat...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Colin Watson cjwat...@debian.org by replying to this email. -- 717177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Messaggio inoltrato -- From: Colin Watson cjwat...@debian.org To: 717177-cl...@bugs.debian.org Cc: Date: Wed, 17 Jul 2013 17:20:50 +0100 Subject: Re: Bug#717177: grub-pc: impossible to have a working grub or a working kernel On Wed, Jul 17, 2013 at 05:55:57PM +0200, cosimo morelli wrote: This sort of language does not persuade me to spend much time helping you. Please tone it down. Well, it works :D This time I had an answer ;) That was only because I was procrastinating thinking about a complicated problem at work. + grub_file_is_not_garbage /etc/grub.d/07_debian_theme + test -f /etc/grub.d/07_debian_theme + return 0 + test -x /etc/grub.d/07_debian_theme + echo + echo ### BEGIN /etc/grub.d/07_debian_theme ### + /etc/grub.d/07_debian_theme So /etc/grub.d/07_debian_theme is apparently the problem. This file isn't shipped by any Debian package, which means that the problem was created at your end. Adding set -x near the top of /etc/grub.d/07_debian_theme may help diagnose exactly what's going on; but perhaps this is simply a leftover from some local experiment and should be removed in favour of /etc/grub.d/05_debian_theme. -- Colin Watson [cjwat...@debian.org] -- Messaggio inoltrato -- From: cosimo morelli lordofenup...@gmail.com To: Debian Bug Tracking System sub...@bugs.debian.org Cc: Date: Wed, 17 Jul 2013 16:10:52 +0200 Subject: grub-pc: impossible to have a working grub or a working kernel Package: grub-pc Version: 2.00-15 Severity: critical Justification: breaks the whole system Dear Maintainer, mew version and same shit E: Sub-process /usr/bin/dpkg returned an error code (1) Errore durante l'installazione di un pacchetto. Tentativo di ripristino: Configurazione di linux-image-3.9-1-686-pae (3.9.8-1)... Running depmod. vmlinuz(/boot/vmlinuz-3.9-1-686-pae ) points to /boot/vmlinuz-3.9-1-686-pae (/boot/vmlinuz-3.9-1-686-pae) -- doing nothing at /var/lib/dpkg/info/linux- image-3.9-1-686-pae.postinst line 268. initrd.img(/boot/initrd.img-3.9-1-686-pae ) points to /boot/initrd.img-3.9-1-686-pae (/boot/initrd.img-3.9-1-686-pae) -- doing nothing at /var/lib/dpkg/info/linux- image-3.9-1-686-pae.postinst line 268. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.9-1-686-pae /boot/vmlinuz-3.9-1-686-pae run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.9-1-686-pae /boot/vmlinuz-3.9-1-686-pae update-initramfs: Generating /boot/initrd.img-3.9-1-686-pae run-parts: executing /etc/kernel/postinst.d/pm-utils 3.9-1-686-pae /boot/vmlinuz-3.9-1-686-pae run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.9-1-686-pae /boot/vmlinuz-3.9-1-686-pae P: Checking for EXTLINUX directory... found. P: Writing config for /boot/vmlinuz-3.9-1-686-pae... P: Writing config for /boot/vmlinuz-3.8-2-686-pae... P: Writing config for /boot/vmlinuz-3.8-1-686-pae... P: Writing config for /boot/vmlinuz-3.2.0-4-686-pae... P: Writing config for Windows 7 (loader) on /dev/sda1... P: Installing debian theme... done. run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.9-1-686-pae /boot/vmlinuz-3.9-1-686-pae Creazione di grub.cfg... Found background image: /usr/share/images/desktop-base/desktop-grub.png run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux- image-3.9-1-686-pae.postinst line 696. dpkg: errore nell'elaborare
Bug#717177: closed by Colin Watson cjwat...@debian.org (Re: Bug#717177: grub-pc: impossible to have a working grub or a working kernel)
On Wed, Jul 17, 2013 at 10:15:10PM +0200, cosimo morelli wrote: Oh so the problem is the file /etc/grub.d/07_debian_theme ? I have just to remove the file or I have to modify something inside the other files of grub? The problem appears to be in that file, yes. Since I don't know what it contains I can't give accurate advice; I can only guess from its name. (It's possible there's some other problem further on. I can't tell. Fix the problem with 07_debian_theme, either by removing it or by fixing it, and either the problem will go away or tracing grub-mkconfig again will show the next target.) -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 709634 with 713070
Processing commands for cont...@bugs.debian.org: # migrating the new rails stack breaks puppet-testsuite; fixed in sid but blocked by an RC bug block 709634 with 713070 Bug #709634 [release.debian.org] RM: ruby-activesupport-2.3/2.3.14-7, ruby-actionmailer-2.3/2.3.14-3, ruby-actionpack-2.3/2.3.14-5, ruby-activerecord-2.3/2.3.14-6, ruby-activeresource-2.3/2.3.14-3, ruby-rails-2.3/2.3.14-4 709634 was not blocked by any bugs. 709634 was not blocking any bugs. Added blocking bug(s) of 709634: 713070 thanks Stopping processing here. Please contact me if you need assistance. -- 709634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709634 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#694252: marked as done (sysv-rc: migration to dependency based boot order fails if bootchart from lenny is still installed)
Your message dated Wed, 17 Jul 2013 21:02:21 + with message-id e1uzyrd-0004b8...@franck.debian.org and subject line Bug#694252: fixed in sysvinit 2.88dsf-41+deb7u1 has caused the Debian Bug report #694252, regarding sysv-rc: migration to dependency based boot order fails if bootchart from lenny is still installed 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.) -- 694252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sysv-rc Version: 2.88dsf-32 Severity: important User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + bootchart Hi, during a test with piuparts I noticed an error while enabling the dependency based boot sequencing if the bootchart package from lenny is still installed. From the attached log: Preparing to replace sysv-rc 2.88dsf-13.1+squeeze1 (using .../sysv-rc_2.88dsf-32_all.deb) ... Unpacking replacement sysv-rc ... Setting up sysv-rc (2.88dsf-32) ... info: Reordering boot system, log to /var/lib/insserv/run-20121123T0359.log error: Something failed while migrating. error: Unable to migrate to dependency based boot sequencing. See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more information about dependency based boot sequencing. To reattempt the migration process run 'dpkg --configure sysv-rc'. dpkg: error processing sysv-rc (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: sysv-rc and /var/lib/insserv/run-20121123T0359.log contains: info: Converting rc0.d/S* and rc6.d/S* to K*. info: running insserv insserv: There is a loop at service bootchart if started insserv: There is a loop at service rmnologin if started insserv: There is a loop between service rmnologin and mountall if started insserv: loop involving service mountall at depth 1 insserv: There is a loop between service rmnologin and mountnfs if started insserv: loop involving service mountnfs at depth 2 insserv: loop involving service mountoverflowtmp at depth 1 insserv: loop involving service urandom at depth 5 insserv: loop involving service checkfs at depth 3 insserv: loop involving service mountnfs-bootclean at depth 6 insserv: There is a loop between service rmnologin and mountoverflowtmp if started insserv: loop involving service mountall-bootclean at depth 7 insserv: There is a loop between service rmnologin and bootlogd if started insserv: loop involving service bootlogd at depth 2 insserv: loop involving service mountdevsubfs at depth 1 insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true! insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true! insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true! ... insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true! insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true! insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true! insserv: Max recursions depth 99 reached insserv: loop involving service bootlogs at depth 1 insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true! insserv: loop involving service hostname at depth 4 insserv: exiting now without changing boot order! This was observed on a distupgrade test from lenny to squeeze to wheezy. There is no bootchart package in squeeze, but since there were no conflicts the lenny package has been kept installed in squeeze, too. Wheezy comes with an updated bootchart package, but sysv-rc got upgraded first. Maybe a Breaks/Conflicts could be inserted somewhere to ensure that bootchart gets upgraded first. cheers, Andreas bootchart_0.10~svn407-3.3.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: sysvinit Source-Version: 2.88dsf-41+deb7u1 We believe that the bug you reported is fixed in the latest version of sysvinit, 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 694...@bugs.debian.org, and the
Bug#711847: marked as done (security upgrade to iceweasel 17 (needlessly) breaks cookie monster)
Your message dated Wed, 17 Jul 2013 21:02:22 + with message-id e1uzyre-0004bu...@franck.debian.org and subject line Bug#711847: fixed in cookie-monster 1.1.0-5~deb7u1 has caused the Debian Bug report #711847, regarding security upgrade to iceweasel 17 (needlessly) breaks cookie monster 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.) -- 711847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xul-ext-cookie-monster Version: 1.1.0-4 Severity: grave With the upgrade to iceweasel 17, cookie monster 1.1.0-4 became uninstallable. The changes from -5 fix that, so this is a request to migrate 1.1.0-5 to wheezy. ---End Message--- ---BeginMessage--- Source: cookie-monster Source-Version: 1.1.0-5~deb7u1 We believe that the bug you reported is fixed in the latest version of cookie-monster, 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 711...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot taf...@debian.org (supplier of updated cookie-monster 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: Sun, 14 Jul 2013 18:36:07 -0400 Source: cookie-monster Binary: xul-ext-cookie-monster Architecture: source all Version: 1.1.0-5~deb7u1 Distribution: wheezy Urgency: low Maintainer: Debian Mozilla Extension Maintainers pkg-mozext-maintain...@lists.alioth.debian.org Changed-By: David Prévot taf...@debian.org Description: xul-ext-cookie-monster - makes it very easy to manage cookies in a whitelist-based way Closes: 711847 Changes: cookie-monster (1.1.0-5~deb7u1) wheezy; urgency=low . * Team upload * Upload to stable (Closes: #711847) Checksums-Sha1: 836c9431dea14fb0c6e9a7d55037daaa46c2dada 1781 cookie-monster_1.1.0-5~deb7u1.dsc 3e06a6bc9d7a05e4ae88d19512768c3a8418caaa 15475 cookie-monster_1.1.0-5~deb7u1.debian.tar.gz d20394d091f0c388fe516e8631d18e11eaa542dd 97290 xul-ext-cookie-monster_1.1.0-5~deb7u1_all.deb Checksums-Sha256: d1b9cda75155f6bd55eac0e80db864108dac9168366003933c351530c46c42e4 1781 cookie-monster_1.1.0-5~deb7u1.dsc 4b7b32350538448ca1b50c420c89cc7e5c9640f71f55a7efdb0da03161fca473 15475 cookie-monster_1.1.0-5~deb7u1.debian.tar.gz 3dae9bb3602535e432a8691f9c3a5b3d62e86d8125b384012bbdd7557b4218ea 97290 xul-ext-cookie-monster_1.1.0-5~deb7u1_all.deb Files: 657491b3db33a5e731da287b04009a28 1781 web optional cookie-monster_1.1.0-5~deb7u1.dsc c38eef5dc1386c3abf8dc14a1bf88cf0 15475 web optional cookie-monster_1.1.0-5~deb7u1.debian.tar.gz 5dee75c219c7d8e81c09b68013023020 97290 web optional xul-ext-cookie-monster_1.1.0-5~deb7u1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJR4zFOAAoJEAWMHPlE9r084A0H/jFAU7SgGCkc//GGckPIIgWO eQ1FtisrVgwyDsHOM+lf2vRkjmpUUkQ2s/rw+Q5S7KLODMCPFwQS6TWUuNKLRZyS MVVV4ICM4hSuOzwhBSErRoNGmwraWBdhXbzK6JV1BKxCMIgt8xDdCEhu0z6qbVFu lOLKmTJe0+ihYSpGXMIYldhhInj8KElpIi4avltj6A6fNas+/tMUi5NalEhC3+oN KLSHmU3WipFYWak41e4bKPpKRK4NJpBlun/1IrQmcITokxhOr99zHMQI0/gxgGf5 QAQR6gmKMZdKHbv/8zIMLcIKV9cWt07EUKSZxsq7hCIy/ghJhvVbHMIbpUGE55A= =YW8s -END PGP SIGNATUREEnd Message---
Bug#717199: quickfix: FTBFS when not building -doc package: chmod: missing operand after `644'
Source: quickfix Version: 1.13.3+dfsg-5 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of quickfix (as on the autobuilders) covering only its architecture-dependent packages have been failing: dh_fixperms -a # dh_fixperms doesn't quite handle everything find /«BUILDDIR»/quickfix-1.13.3+dfsg/debian/libquickfix-doc/usr/share/doc/libquickfix-doc/examples -type f |xargs chmod 644 chmod: missing operand after `644' Try `chmod --help' for more information. make: *** [binary-arch] Error 123 Please either conditionalize this command appropriately or use xargs's --no-run-if-empty flag. 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 in RDF::LinkedData dev release 0.57_04
Processing commands for cont...@bugs.debian.org: tags 713235 + fixed-upstream Bug #713235 [src:librdf-linkeddata-perl] librdf-linkeddata-perl: FTBFS: tests failed Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 713235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713235 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#702359: marked as done (psi-plus: FTBFS with libotr5)
Your message dated Wed, 17 Jul 2013 22:48:23 + with message-id e1uzawf-0005op...@franck.debian.org and subject line Bug#702359: fixed in psi-plus 0.16.132-1 has caused the Debian Bug report #702359, regarding psi-plus: FTBFS with libotr5 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.) -- 702359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: psi-plus Version: 0.15.5338-1 Severity: normal Tags: patch sid Hi, libotr2-dev is replaced by libotr5-dev, so psi-plus currently FTBFS in unstable. Consider the attached patch. Thanks, Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.8.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash --- psi-plus-0.15.5338/debian/control.orig 2013-03-05 16:42:30.828439481 +0100 +++ psi-plus-0.15.5338/debian/control 2013-03-05 16:42:40.548417671 +0100 @@ -5,7 +5,7 @@ Build-Depends: debhelper (= 7.0.50~), libqtwebkit-dev , qconf, libqca2-dev (= 2.0.0), libxss-dev, libaspell-dev, zlib1g-dev, libsm-dev, - libotr2-dev, libtidy-dev + libotr5-dev, libtidy-dev Homepage: http://psi-dev.googlecode.com/ Vcs-Git: git://github.com/tehnick/psi-plus-debian.git Vcs-Browser: https://github.com/tehnick/psi-plus-debian ---End Message--- ---BeginMessage--- Source: psi-plus Source-Version: 0.16.132-1 We believe that the bug you reported is fixed in the latest version of psi-plus, 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 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boris Pek tehn...@debian.org (supplier of updated psi-plus 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, 18 Jul 2013 00:28:09 +0300 Source: psi-plus Binary: psi-plus psi-plus-dbg psi-plus-webkit psi-plus-webkit-dbg psi-plus-common psi-plus-plugins psi-plus-plugins-dbg psi-plus-content-downloader psi-plus-skins psi-plus-sounds Architecture: source i386 all Version: 0.16.132-1 Distribution: unstable Urgency: low Maintainer: Boris Pek tehn...@debian.org Changed-By: Boris Pek tehn...@debian.org Description: psi-plus - Qt-based XMPP/Jabber client (basic version) psi-plus-common - common files for Psi+ psi-plus-content-downloader - content downloader plugin for Psi+ psi-plus-dbg - Qt-based XMPP/Jabber client (basic version) [debug symbols] psi-plus-plugins - plugins for Psi+ psi-plus-plugins-dbg - plugins for Psi+ [debug symbols] psi-plus-skins - skins for Psi+ psi-plus-sounds - sound files for Psi+ psi-plus-webkit - Qt-based XMPP/Jabber client (WebKit version) psi-plus-webkit-dbg - Qt-based XMPP/Jabber client (WebKit version) [debug symbols] Closes: 702359 Changes: psi-plus (0.16.132-1) unstable; urgency=low . * New upstream release. * Fixed in upstream: added support of libotr = 4.0.0. (Closes: #702359) * Change build dependency from libotr2-dev to libotr5-dev. * Update get-orig-source section in debian/rules. * Update debian/psi-plus-webkit.desktop. * Update debian/copyright. Checksums-Sha1: c249365f77e0a5190e92fe09664aac0e825bf6e3 2451 psi-plus_0.16.132-1.dsc 888c234a0e1fad22fa32a702a13cf288fefaf54e 6997816 psi-plus_0.16.132.orig.tar.xz 4572a5c86ea99e1275dccab4e461d88fec5586ac 18265 psi-plus_0.16.132-1.debian.tar.gz 007cb54a2a7cd4e731cc07d596e85ef5f4562958 3799780 psi-plus_0.16.132-1_i386.deb 4298877653d6ba596a7686a7a4930ca6c5ba5c2e 40755526 psi-plus-dbg_0.16.132-1_i386.deb 5e6ad8b14daa7d8cc45416ba9e38563a56cc9bcc 4107428 psi-plus-webkit_0.16.132-1_i386.deb 74c14b64869b531e6a6bcd1a7e3b688da368a9cd 41603994 psi-plus-webkit-dbg_0.16.132-1_i386.deb 625b4e083860cdb655688e8a8787f8d847fc5649 530900 psi-plus-common_0.16.132-1_all.deb a2986f241be7a8bee9b76b855f8907b5324321fa 2045388 psi-plus-plugins_0.16.132-1_i386.deb fbd9333f1339ec5cf6f82aa0e8b19135da0aff47 17595518 psi-plus-plugins-dbg_0.16.132-1_i386.deb c4590001f9994e68e79432a358e5d6f07c25ee75
Bug#711074: marked as done (psi-plus: please port to libotr5-dev)
Your message dated Wed, 17 Jul 2013 22:48:23 + with message-id e1uzawf-0005op...@franck.debian.org and subject line Bug#702359: fixed in psi-plus 0.16.132-1 has caused the Debian Bug report #702359, regarding psi-plus: please port to libotr5-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.) -- 702359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: psi-plus Version: 0.16.117-1 Severity: serious Hi, your package build-depends on libotr2-dev, which is no longer built in sid as it has been replaced by libotr5-dev. Please port your package to the new library. Thanks, Julien ---End Message--- ---BeginMessage--- Source: psi-plus Source-Version: 0.16.132-1 We believe that the bug you reported is fixed in the latest version of psi-plus, 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 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boris Pek tehn...@debian.org (supplier of updated psi-plus 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, 18 Jul 2013 00:28:09 +0300 Source: psi-plus Binary: psi-plus psi-plus-dbg psi-plus-webkit psi-plus-webkit-dbg psi-plus-common psi-plus-plugins psi-plus-plugins-dbg psi-plus-content-downloader psi-plus-skins psi-plus-sounds Architecture: source i386 all Version: 0.16.132-1 Distribution: unstable Urgency: low Maintainer: Boris Pek tehn...@debian.org Changed-By: Boris Pek tehn...@debian.org Description: psi-plus - Qt-based XMPP/Jabber client (basic version) psi-plus-common - common files for Psi+ psi-plus-content-downloader - content downloader plugin for Psi+ psi-plus-dbg - Qt-based XMPP/Jabber client (basic version) [debug symbols] psi-plus-plugins - plugins for Psi+ psi-plus-plugins-dbg - plugins for Psi+ [debug symbols] psi-plus-skins - skins for Psi+ psi-plus-sounds - sound files for Psi+ psi-plus-webkit - Qt-based XMPP/Jabber client (WebKit version) psi-plus-webkit-dbg - Qt-based XMPP/Jabber client (WebKit version) [debug symbols] Closes: 702359 Changes: psi-plus (0.16.132-1) unstable; urgency=low . * New upstream release. * Fixed in upstream: added support of libotr = 4.0.0. (Closes: #702359) * Change build dependency from libotr2-dev to libotr5-dev. * Update get-orig-source section in debian/rules. * Update debian/psi-plus-webkit.desktop. * Update debian/copyright. Checksums-Sha1: c249365f77e0a5190e92fe09664aac0e825bf6e3 2451 psi-plus_0.16.132-1.dsc 888c234a0e1fad22fa32a702a13cf288fefaf54e 6997816 psi-plus_0.16.132.orig.tar.xz 4572a5c86ea99e1275dccab4e461d88fec5586ac 18265 psi-plus_0.16.132-1.debian.tar.gz 007cb54a2a7cd4e731cc07d596e85ef5f4562958 3799780 psi-plus_0.16.132-1_i386.deb 4298877653d6ba596a7686a7a4930ca6c5ba5c2e 40755526 psi-plus-dbg_0.16.132-1_i386.deb 5e6ad8b14daa7d8cc45416ba9e38563a56cc9bcc 4107428 psi-plus-webkit_0.16.132-1_i386.deb 74c14b64869b531e6a6bcd1a7e3b688da368a9cd 41603994 psi-plus-webkit-dbg_0.16.132-1_i386.deb 625b4e083860cdb655688e8a8787f8d847fc5649 530900 psi-plus-common_0.16.132-1_all.deb a2986f241be7a8bee9b76b855f8907b5324321fa 2045388 psi-plus-plugins_0.16.132-1_i386.deb fbd9333f1339ec5cf6f82aa0e8b19135da0aff47 17595518 psi-plus-plugins-dbg_0.16.132-1_i386.deb c4590001f9994e68e79432a358e5d6f07c25ee75 158634 psi-plus-content-downloader_0.16.132-1_i386.deb 05e6de65ed3e83b34e7b2c6600c68614a83f5094 4082622 psi-plus-skins_0.16.132-1_all.deb 1a65b9325e14ded9063136cd111ff64d5cf8d30c 1009672 psi-plus-sounds_0.16.132-1_all.deb Checksums-Sha256: bfa9ddcd24a9a32da9f6636cb8ce6c5713099840282d7fb1d6d25172d673d2e3 2451 psi-plus_0.16.132-1.dsc 1f3f5eb72b402d0a2b60e2d875c85ffeda770de3f6b8d141841c8579020593a1 6997816 psi-plus_0.16.132.orig.tar.xz e903e9a6f18f8d7d5c2a66f7bb682bf008393f687ec0e2f06e0d5393c849173a 18265 psi-plus_0.16.132-1.debian.tar.gz 9b7210c9157971683b89f28397e84d328f41a743e38b1883b5eca865c5085755 3799780 psi-plus_0.16.132-1_i386.deb 103952fb02a1cb70d59cfdbb2e0c28ca40fbf0dd840e32f4e986667db2b41365 40755526 psi-plus-dbg_0.16.132-1_i386.deb
Bug#717214: php5-imagick: fails to install: cp: cannot create regular file '/etc/php5/conf.d/imagick.ini': No such file or directory
Package: php5-imagick Version: 3.1.0~rc1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: piuparts Control: block 706830 with -1 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 php5-imagick. (Reading database ... 9229 files and directories currently installed.) Unpacking php5-imagick (from .../php5-imagick_3.1.0~rc1-1+b3_amd64.deb) ... Setting up php5-imagick (3.1.0~rc1-1+b3) ... Creating config file /etc/php5/conf.d/imagick.ini with new version cp: cannot create regular file '/etc/php5/conf.d/imagick.ini': No such file or directory dpkg: error processing php5-imagick (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: php5-imagick cheers, Andreas php5-imagick_3.1.0~rc1-1+b3.log.gz Description: GNU Zip compressed data
Processed: php5-imagick: fails to install: cp: cannot create regular file '/etc/php5/conf.d/imagick.ini': No such file or directory
Processing control commands: block 706830 with -1 Bug #706830 [release.debian.org] transition: php5 5.5 706830 was blocked by: 715472 710937 706830 was not blocking any bugs. Added blocking bug(s) of 706830: 717214 -- 706830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706830 717214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717214 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#712352: marked as done (sml-mode: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors))
Your message dated Thu, 18 Jul 2013 00:33:57 +
with message-id e1uzcap-0001m7...@franck.debian.org
and subject line Bug#712352: fixed in sml-mode 5.0-1
has caused the Debian Bug report #712352,
regarding sml-mode: FTBFS: manuals build fails against textinfo5 because some
incompatibles changes wrt 4.13 and below (some warnings have turned into 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.)
--
712352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: sml-mode
Version: 4.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 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»'
echo \
;;; sml-mode-startup.el --- automatically extracted autoloads\n\
;;; Code:\n\
(add-to-list 'load-path\n\
(or (file-name-directory load-file-name) (car
load-path)))\n\
sml-mode-startup.el
emacs --batch --eval '(setq generated-autoload-file
'`pwd`'/sml-mode-startup.el)' -f batch-update-autoloads .
Loading 00debian-vars...
Generating autoloads for sml-compat.el...
Generating autoloads for sml-compat.el...done
Generating autoloads for sml-defs.el...
Generating autoloads for sml-defs.el...done
Generating autoloads for sml-mode.el...
Generating autoloads for sml-mode.el...done
Generating autoloads for sml-move.el...
Generating autoloads for sml-move.el...done
Generating autoloads for sml-proc.el...
Generating autoloads for sml-proc.el...done
Generating autoloads for sml-util.el...
Generating autoloads for sml-util.el...done
Saving file /«PKGBUILDDIR»/sml-mode-startup.el...
Wrote /«PKGBUILDDIR»/sml-mode-startup.el
(No changes need to be saved)
mkdir -p /«PKGBUILDDIR»/debian/sml-mode/usr/share/emacs/site-lisp/sml-mode
for f in sml-compat.elc sml-util.elc sml-defs.elc sml-move.elc sml-mode.elc
sml-proc.elc sml-mode-startup.el; do \
cp $f
/«PKGBUILDDIR»/debian/sml-mode/usr/share/emacs/site-lisp/sml-mode/$f ;\
done
makeinfo sml-mode.texi
sml-mode.texi:37: misplaced {
sml-mode.texi:37: misplaced }
sml-mode.texi:37: warning: @center missing argument
sml-mode.texi:38: misplaced {
sml-mode.texi:38: misplaced }
sml-mode.texi:38: warning: @center missing argument
sml-mode.texi:66: warning: multiple @setchapternewpage
make[1]: *** [sml-mode.info] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/09/sml-mode_4.1-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: sml-mode
Source-Version: 5.0-1
We believe that the bug you reported is fixed in the latest version of
sml-mode, 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 712...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Barry deFreese bdefre...@debian.org (supplier of updated sml-mode 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: Wed, 17 Jul 2013 19:01:03 -0400
Source: sml-mode
Binary: sml-mode
Architecture: source all
Version: 5.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Barry deFreese bdefre...@debian.org
Description:
sml-mode - Emacs major mode for editing Standard ML programs
Closes: 681922 710746 712352
Changes:
sml-mode (5.0-1) unstable; urgency=low
.
* QA upload.
* Set maintainer to Debian QA Group packa...@qa.debian.org.
* New upstream release.
+ Refresh existing patches.
+ find_match_stop_at_end_or_beginning_of_buffer.diff -
Update to patch sml-oldindent.el instead of sml-move.el.
+ sml-compat.el removed and so are old
Bug#681922: marked as done (sml-mode: can't be compiled with emacs24)
Your message dated Thu, 18 Jul 2013 00:33:57 + with message-id e1uzcap-0001lv...@franck.debian.org and subject line Bug#681922: fixed in sml-mode 5.0-1 has caused the Debian Bug report #681922, regarding sml-mode: can't be compiled with emacs24 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.) -- 681922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sml-mode Version: 4.1-2 Severity: serious Dear Maintainer, I tried installing sml-mode. Installation failed while it was being compiled for Emacs 24. Output is shown below. Cheers, -Hilko $ sudo apt-get install sml-mode [sudo] password for bengen: Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: sml-mode 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 58.3 kB of archives. After this operation, 258 kB of additional disk space will be used. Get:1 http://localhost/debian/ sid/main sml-mode all 4.1-2 [58.3 kB] Fetched 58.3 kB in 0s (168 kB/s) Selecting previously unselected package sml-mode. (Reading database ... 497625 files and directories currently installed.) Unpacking sml-mode (from .../sml-mode_4.1-2_all.deb) ... Processing triggers for install-info ... install-info: warning: no info dir entry in `/usr/share/info/ocaml.info.gz' Setting up sml-mode (4.1-2) ... Install emacsen-common for emacs Install emacsen-common for emacs23 install/sml-mode: Handling install for emacsen flavor emacs23 Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-compat.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-proc.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-mode-startup.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-move.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-defs.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-mode.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-util.elc Install emacsen-common for emacs24 install/sml-mode: Handling install for emacsen flavor emacs24 Wrote /usr/share/emacs24/site-lisp/sml-mode/sml-compat.elc In toplevel form: sml-proc.el:93:1:Error: Constant symbol `:group' specified in defvar Wrote /usr/share/emacs24/site-lisp/sml-mode/sml-mode-startup.elc In toplevel form: sml-move.el:26:1:Error: Constant symbol `:group' specified in defvar In toplevel form: sml-defs.el:25:1:Error: Constant symbol `:group' specified in defvar In toplevel form: sml-mode.el:73:1:Error: Constant symbol `:group' specified in defvar In toplevel form: sml-util.el:25:1:Error: Constant symbol `:group' specified in defvar ERROR: install script from emacsen-common package failed dpkg: error processing sml-mode (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: sml-mode E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages sml-mode depends on: ii dpkg1.16.7 ii emacsen-common 2.0.3 ii install-info4.13a.dfsg.1-10 sml-mode recommends no packages. sml-mode suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: sml-mode Source-Version: 5.0-1 We believe that the bug you reported is fixed in the latest version of sml-mode, 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 681...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barry deFreese bdefre...@debian.org (supplier of updated sml-mode 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: Wed, 17 Jul 2013 19:01:03 -0400 Source: sml-mode Binary: sml-mode Architecture: source all Version: 5.0-1 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Barry deFreese bdefre...@debian.org Description: sml-mode -
Bug#717216: fusionforge-plugin-authcas: fails to install: PHP Fatal error: require_once(): Failed opening required 'CAS.php'
Package: fusionforge-plugin-authcas Version: 5.2.2+20130717-1 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 fusionforge-plugin-authcas. (Reading database ... 16580 files and directories currently installed.) Unpacking fusionforge-plugin-authcas (from .../fusionforge-plugin-authcas_5.2.2+20130717-1_all.deb) ... Setting up fusionforge-plugin-authcas (5.2.2+20130717-1) ... PHP Warning: require_once(CAS.php): failed to open stream: No such file or directory in /usr/share/gforge/plugins/authcas/include/AuthCASPlugin.class.php on line 25 PHP Fatal error: require_once(): Failed opening required 'CAS.php' (include_path='/usr/share/php-htmlpurifier/library:/etc/fusionforge//custom:/etc/fusionforge/:/usr/share/gforge/common:/usr/share/gforge/www:/usr/share/gforge/plugins:/usr/share/gforge:/usr/share/gforge/www/include:/usr/share/gforge/common/include:.:/usr/share/php:/usr/share/pear') in /usr/share/gforge/plugins/authcas/include/AuthCASPlugin.class.php on line 25 PHP Warning: require_once(CAS.php): failed to open stream: No such file or directory in /usr/share/gforge/plugins/authcas/include/AuthCASPlugin.class.php on line 25 ... PHP Fatal error: require_once(): Failed opening required 'CAS.php' (include_path='/usr/share/php-htmlpurifier/library:/etc/fusionforge//custom:/etc/fusionforge/:/usr/share/gforge/common:/usr/share/gforge/www:/usr/share/gforge/plugins:/usr/share/gforge:/usr/share/gforge/www/include:/usr/share/gforge/common/include:.:/usr/share/php:/usr/share/pear') in /usr/share/gforge/plugins/authcas/include/AuthCASPlugin.class.php on line 25 PHP Warning: require_once(CAS.php): failed to open stream: No such file or directory in /usr/share/gforge/plugins/authcas/include/AuthCASPlugin.class.php on line 25 PHP Fatal error: require_once(): Failed opening required 'CAS.php' (include_path='/usr/share/php-htmlpurifier/library:/etc/fusionforge//custom:/etc/fusionforge/:/usr/share/gforge/common:/usr/share/gforge/www:/usr/share/gforge/plugins:/usr/share/gforge:/usr/share/gforge/www/include:/usr/share/gforge/common/include:.:/usr/share/php:/usr/share/pear') in /usr/share/gforge/plugins/authcas/include/AuthCASPlugin.class.php on line 25 /usr/share/gforge/lib/include.pl did not return a true value at /usr/share/gforge/bin/register-plugin line 13 (#1) (F) A required (or used) file must return a true value to indicate that it compiled correctly and ran its initialization code correctly. It's traditional to end such a file with a 1;, though any true value would do. See require in perlfunc. Uncaught exception from user code: /usr/share/gforge/lib/include.pl did not return a true value at /usr/share/gforge/bin/register-plugin line 13. at /usr/share/gforge/bin/register-plugin line 13 dpkg: error processing fusionforge-plugin-authcas (--configure): subprocess installed post-installation script returned error exit status 255 Errors were encountered while processing: fusionforge-plugin-authcas cheers, Andreas fusionforge-plugin-authcas_5.2.2+20130717-1.log.gz Description: GNU Zip compressed data
Bug#711297: autoconf: FTBFS: texinfo errors
THis is analysed here: http://old.nabble.com/CVS-Texinfo-fails-to-build-the-Autoconf-manual-%28from-git%29-td34167051.html and there is a patch near the bottom of the page, applied to upstream autoconf (in july 2012). We should apply it too or move to a newer autoconf (don't know if this fix is in a released version yet - one would hope so). Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714591: marked as done (FTBFS on mipsel: src/lifeograph.cpp:109:12: error: expected ')' before 'n')
Your message dated Thu, 18 Jul 2013 03:33:34 + with message-id e1uzeye-0005uf...@franck.debian.org and subject line Bug#714591: fixed in lifeograph 0.11.1.dfsg-3 has caused the Debian Bug report #714591, regarding FTBFS on mipsel: src/lifeograph.cpp:109:12: error: expected ')' before 'n' 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.) -- 714591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lifeograph Version: 0.11.1.dfsg-2 Severity: serious lifeograph fails to build on mipsel: g++ -c src/lifeobase.cpp -Wall `pkg-config gtkmm-3.0 enchant --cflags`-DHAVE_CONFIG_H -I./build/include -g -O2 -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -o build/o/lifeobase.o In file included from src/helpers.hpp:28:0, from src/settings.hpp:30, from src/lifeobase.hpp:29, from src/lifeobase.cpp:23: ./build/include/config.h:2:28: warning: missing whitespace after the macro name [enabled by default] g++ -c src/lifeograph.cpp -Wall `pkg-config gtkmm-3.0 enchant --cflags`-DHAVE_CONFIG_H -I./build/include -g -O2 -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -o build/o/lifeograph.o In file included from src/lifeograph.cpp:24:0: ./build/include/config.h:2:28: warning: missing whitespace after the macro name [enabled by default] src/lifeograph.cpp:109:2: error: stray '\' in program src/lifeograph.cpp: In constructor 'LIFEO::Lifeograph::Lifeograph(int, char**)': src/lifeograph.cpp:109:12: error: expected ')' before 'n' make[1]: *** [build/o/lifeograph.o] Error 1 make: *** [build-stamp] Error 2 Full build log is available at https://buildd.debian.org/status/fetch.php?pkg=lifeographarch=mipselver=0.11.1.dfsg-2stamp=1372555106 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: lifeograph Source-Version: 0.11.1.dfsg-3 We believe that the bug you reported is fixed in the latest version of lifeograph, 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. Laszlo Boszormenyi (GCS) g...@debian.org (supplier of updated lifeograph 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: Wed, 17 Jul 2013 21:44:17 +0200 Source: lifeograph Binary: lifeograph Architecture: source amd64 Version: 0.11.1.dfsg-3 Distribution: unstable Urgency: low Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Changed-By: Laszlo Boszormenyi (GCS) g...@debian.org Description: lifeograph - Private digital diary Closes: 714591 Changes: lifeograph (0.11.1.dfsg-3) unstable; urgency=low . * Fix FTBFS on mipsel (closes: #714591). Checksums-Sha1: 7f650654659ad3febef817f889d587d63082a732 1212 lifeograph_0.11.1.dfsg-3.dsc af69878d950a5d7fa1b79e0cda06217f69f025d0 3530 lifeograph_0.11.1.dfsg-3.debian.tar.gz efbddcb254835b181d71e19d45b569a9f5894288 658752 lifeograph_0.11.1.dfsg-3_amd64.deb Checksums-Sha256: 2a52c634f9e071f37fb32292513826ce40310bde610de12df39db7a3a7c605bb 1212 lifeograph_0.11.1.dfsg-3.dsc f2d92eaa6d3dd019cee83fac0b4a3bef20af3c48ecd760737e388c9f3432380f 3530 lifeograph_0.11.1.dfsg-3.debian.tar.gz 44e48f6d72e12b075c42e7c8379be7029ac5375b07b324c637d867ad588c0a7a 658752 lifeograph_0.11.1.dfsg-3_amd64.deb Files: bc129ba34ef9084946aa179cf9381a7f 1212 gnome optional lifeograph_0.11.1.dfsg-3.dsc 565fb02e93c564c30212ca29e18f401c 3530 gnome optional lifeograph_0.11.1.dfsg-3.debian.tar.gz f450474448302646bc870a51ca91d0c2 658752 gnome optional lifeograph_0.11.1.dfsg-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHnXhYACgkQMDatjqUaT93ftQCfcrO4ujDOmWhZVHmqsdTaS3Y7 stwAn2rNlD/MjFky4JCVnW1blCch1G6B =2hGr -END PGP SIGNATUREEnd Message---
Bug#714535: netexpect: FTBFS with wireshark 1.10 (patch)
Hi Adam,
I uploaded to unstable new netexpect packages, and they just got
accepted. Things now build and work with the new Wireshark 1.10
libraries. Hopefully the new packages will propagate to Ubuntu soon.
Cheers,
Eloy Paris.-
netexpect.org
On 07/05/2013 03:14 PM, Adam Conrad wrote:
Package: netexpect
Version: 0.20-3
Followup-For: Bug #714535
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch
In Ubuntu, I've applied the following naive patch to port to the
wireshark 1.10 API. It looks like the _set_unset calls can probably
just go away, as they're setting members that no longer exist.
As for the frame_data_{reset,destroy} mangling, I made a best-effort
guess as to which to use in which situation, but input from someone
more familiar with the source would probably not be a bad plan.
* fix-libwireshark110-build.patch: Track wireshark 1.10 API (closes: #714535)
Thanks for considering the patch.
... Adam
-- System Information:
Debian Release: wheezy/sid
APT prefers saucy-updates
APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10.0-2-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
