Processed: forcemerge 672056 671028
Processing commands for cont...@bugs.debian.org: forcemerge 672056 671028 Bug #672056 [src:xf86-video-glamo] xf86-video-glamo: FTBFS: ../../src/glamo-driver.c:289:7: error: assignment discards 'const' qualifier from pointer target type [-Werror] Bug #671028 [src:xf86-video-glamo] xf86-video-glamo: FTBFS against X server 1.12 Added tag(s) sid, wheezy, and patch. Merged 671028 672056 thanks Stopping processing here. Please contact me if you need assistance. -- 671028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671028 672056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672056 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#669679: Any reason not to upload the fixed package?
Hi, On Wed, May 09, 2012 at 09:46:52PM -0400, Aaron M. Ucko wrote: Andreas Tille ti...@debian.org writes: I wonder whether there is any reason not to upload the fixed package. I had thought Olivier might want to, as the official primary maintainer; I have no problem issuing another team upload if necessary, though. It finally saves time for everybody because I guess on your system a readily builded package is hanging around after you prepared the patch, right? :-) Thanks for asking! Thanks for the patch in any case Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671916: marked as done (quagga and babeld: error when trying to install together)
Your message dated Thu, 10 May 2012 06:18:14 + with message-id e1ssmha-0006sl...@franck.debian.org and subject line Bug#671916: fixed in quagga 0.99.21-2 has caused the Debian Bug report #671916, regarding quagga and babeld: error when trying to install together 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.) -- 671916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: babeld,quagga Version: babeld/1.3.1-1 Version: quagga/0.99.21-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-05-08 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libcap2 quagga babeld Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libcap2. (Reading database ... 10559 files and directories currently installed.) Unpacking libcap2 (from .../libcap2_1%3a2.22-1_amd64.deb) ... Selecting previously unselected package quagga. Unpacking quagga (from .../quagga_0.99.21-1_amd64.deb) ... Selecting previously unselected package babeld. Unpacking babeld (from .../babeld_1.3.1-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/babeld_1.3.1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man8/babeld.8.gz', which is also in package quagga 0.99.21-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/babeld_1.3.1-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/man/man8/babeld.8.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: quagga Source-Version: 0.99.21-2 We believe that the bug you reported is fixed in the latest version of quagga, which is due to be installed in the Debian FTP archive: quagga-dbg_0.99.21-2_amd64.deb to main/q/quagga/quagga-dbg_0.99.21-2_amd64.deb quagga-doc_0.99.21-2_all.deb to main/q/quagga/quagga-doc_0.99.21-2_all.deb quagga_0.99.21-2.debian.tar.gz to main/q/quagga/quagga_0.99.21-2.debian.tar.gz quagga_0.99.21-2.dsc to main/q/quagga/quagga_0.99.21-2.dsc quagga_0.99.21-2_amd64.deb to main/q/quagga/quagga_0.99.21-2_amd64.deb 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 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hammers c...@debian.org (supplier of updated quagga 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 10 May 2012 07:53:01 +0200 Source: quagga Binary: quagga quagga-dbg quagga-doc Architecture: source amd64 all Version: 0.99.21-2 Distribution: unstable Urgency: low Maintainer: Christian Hammers c...@debian.org Changed-By: Christian Hammers c...@debian.org Description:
Bug#671520: marked as done (lxappearance-obconf: FTBFS: undeclared B-D on openbox-dev)
Your message dated Thu, 10 May 2012 06:47:59 + with message-id e1ssnan-0008qu...@franck.debian.org and subject line Bug#671520: fixed in lxappearance-obconf 0.2.0-2 has caused the Debian Bug report #671520, regarding lxappearance-obconf: FTBFS: undeclared B-D on openbox-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.) -- 671520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lxappearance-obconf Version: 0.2.0-1 Severity: serious Justification: fails to build from source Builds of lxappearance-obconf in minimal environments (such as on the autobuilders) are failing: checking for OPENBOX... no configure: error: Package requirements (obrender-3.5 = 3.5 obt-3.5 = 3.5) were not met: No package 'obrender-3.5' found No package 'obt-3.5' found Please declare a build dependency on openbox-dev (= 3.5) and check with pbuilder or the like that no others are missing. Thanks! ---End Message--- ---BeginMessage--- Source: lxappearance-obconf Source-Version: 0.2.0-2 We believe that the bug you reported is fixed in the latest version of lxappearance-obconf, which is due to be installed in the Debian FTP archive: lxappearance-obconf_0.2.0-2.debian.tar.xz to main/l/lxappearance-obconf/lxappearance-obconf_0.2.0-2.debian.tar.xz lxappearance-obconf_0.2.0-2.dsc to main/l/lxappearance-obconf/lxappearance-obconf_0.2.0-2.dsc lxappearance-obconf_0.2.0-2_i386.deb to main/l/lxappearance-obconf/lxappearance-obconf_0.2.0-2_i386.deb 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 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann dan...@debian.org (supplier of updated lxappearance-obconf 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 10 May 2012 08:33:58 +0200 Source: lxappearance-obconf Binary: lxappearance-obconf Architecture: source i386 Version: 0.2.0-2 Distribution: unstable Urgency: low Maintainer: Debian LXDE Maintainers lxde-deb...@lists.lxde.org Changed-By: Daniel Baumann dan...@debian.org Description: lxappearance-obconf - LXDE GTK+ theme switcher (plugin) Closes: 671520 672097 Changes: lxappearance-obconf (0.2.0-2) unstable; urgency=low . * Adding missing build-depends to libimlib2-dev and openbox-dev (Closes: #671520, #672097). Checksums-Sha1: 77ce1c47b80327745db9e026bd03999fe69525c0 1565 lxappearance-obconf_0.2.0-2.dsc 037b096ffd884a48493e9fe40f58dc6ad62ae775 1912 lxappearance-obconf_0.2.0-2.debian.tar.xz 8688ed2e847a5c9ab2b9326c92ccc1218578e640 154822 lxappearance-obconf_0.2.0-2_i386.deb Checksums-Sha256: a706c821561f86d32bc145de16971ebbaaa33350d1cb6b1ec91b23dad94a85e1 1565 lxappearance-obconf_0.2.0-2.dsc 62eff34a6f691da3ea1d4061f4086e5dbcafb95def659c6f87313942388808c3 1912 lxappearance-obconf_0.2.0-2.debian.tar.xz 9f4cb1906dd5d3de2e67e65599363290823ed2387cb279c32e8ffb5bfbffd906 154822 lxappearance-obconf_0.2.0-2_i386.deb Files: e79b74881009690d734ab87c7302c738 1565 x11 optional lxappearance-obconf_0.2.0-2.dsc 4edd229d7f9dfe7f78cfbc452e0ddb8b 1912 x11 optional lxappearance-obconf_0.2.0-2.debian.tar.xz 8d3991311dbf68f59d6ce770925e8cbd 154822 x11 optional lxappearance-obconf_0.2.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk+rYbwACgkQ+C5cwEsrK561OQCcD4fvfVk9uuHQp/Qfrdl/NHXG Z9cAn36VFuuJqlfY2Gj2vSFwwAjb32Bq =QdTc -END PGP SIGNATURE- ---End Message---
Bug#672097: marked as done (lxappearance-obconf: FTBFS: gcc: error: unrecognized option '-V')
Your message dated Thu, 10 May 2012 06:48:00 + with message-id e1ssnao-0008qy...@franck.debian.org and subject line Bug#672097: fixed in lxappearance-obconf 0.2.0-2 has caused the Debian Bug report #672097, regarding lxappearance-obconf: FTBFS: gcc: error: unrecognized option '-V' 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.) -- 672097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lxappearance-obconf Version: 0.2.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc version 4.6.3 (Debian 4.6.3-5) configure:3268: $? = 0 configure:3257: gcc -V 5 gcc: error: unrecognized option '-V' gcc: fatal error: no input files compilation terminated. configure:3268: $? = 4 configure:3257: gcc -qversion 5 gcc: error: unrecognized option '-qversion' gcc: fatal error: no input files compilation terminated. configure:3268: $? = 4 configure:3288: checking whether the C compiler works configure:3310: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c 5 configure:3314: $? = 0 configure:3362: result: yes configure:3365: checking for C compiler default output file name configure:3367: result: a.out configure:3373: checking for suffix of executables configure:3380: gcc -o conftest -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c 5 configure:3384: $? = 0 configure:3406: result: configure:3428: checking whether we are cross compiling configure:3436: gcc -o conftest -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c 5 configure:3440: $? = 0 configure:3447: ./conftest configure:3451: $? = 0 configure:3466: result: no configure:3471: checking for suffix of object files configure:3493: gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.c 5 configure:3497: $? = 0 configure:3518: result: o configure:3522: checking whether we are using the GNU C compiler configure:3541: gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.c 5 configure:3541: $? = 0 configure:3550: result: yes configure:3559: checking whether gcc accepts -g configure:3579: gcc -c -g -D_FORTIFY_SOURCE=2 conftest.c 5 configure:3579: $? = 0 configure:3620: result: yes configure:3637: checking for gcc option to accept ISO C89 configure:3701: gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.c 5 configure:3701: $? = 0 configure:3714: result: none needed configure:3736: checking dependency style of gcc configure:3847: result: none configure:3863: checking whether gcc and cc understand -c and -o together configure:3894: gcc -c conftest.c -o conftest2.o 5 configure:3898: $? = 0 configure:3904: gcc -c conftest.c -o conftest2.o 5 configure:3908: $? = 0 configure:3919: cc -c conftest.c 5 configure:3923: $? = 0 configure:3931: cc -c conftest.c -o conftest2.o 5 configure:3935: $? = 0 configure:3941: cc -c conftest.c -o conftest2.o 5 configure:3945: $? = 0 configure:3963: result: yes configure:3989: checking for an ANSI C-conforming const configure:4054: gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.c 5 configure:4054: $? = 0 configure:4061: result: yes configure:4069: checking for inline configure:4085: gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.c 5 configure:4085: $? = 0 configure:4093: result: inline configure:4145: checking build system type configure:4159: result: x86_64-pc-linux-gnu configure:4179: checking host system type configure:4192: result: x86_64-pc-linux-gnu configure:4233: checking how to print strings configure:4260: result: printf configure:4281: checking for a sed that does not truncate output configure:4345: result: /bin/sed configure:4363: checking for grep that handles long lines and -e configure:4421: result: /bin/grep configure:4426: checking for egrep configure:4488: result: /bin/grep -E
Bug#671998: hugin: FTBFS with gcc 4.7 bug
Cyril Brulebois k...@debian.org (09/05/2012): Looks good so far, except for s390 :/ https://buildd.debian.org/status/package.php?p=huginsuite=experimental FWIW I think we'll go with a temporary removal from testing to let exiv2 migrate ASAP, given it would get entangled with gdal if we waited further. I'll be happy to assist you get it back into testing once its FTBFS is fixed for all release architectures. Mraw, KiBi. signature.asc Description: Digital signature
Bug#672332: hugin - FTBFS: invalid initialization of reference of type 'ptrdiff_t {aka int}'
Source: hugin
Version: 2011.4.0+dfsg-1
Severity: serious
hugin fails to build on s390:
| error: invalid initialization of reference of type 'ptrdiff_t {aka int}'
from expression of type 'long int'
| error: in passing argument 5 of 'void swig::slice_adjust(ptrdiff_t,
ptrdiff_t, ptrdiff_t, size_t, ptrdiff_t, ptrdiff_t, bool)'
Bastian
--
I have never understood the female capacity to avoid a direct answer to
any question.
-- Spock, This Side of Paradise, stardate 3417.3
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672334: linux-container: trying to overwrite '/usr/bin/uptime', which is also in package procps
Package: linux-container Version: 1-6 Severity: grave Justification: renders package unusable Hi, Upgrade from version 1-5 does not work: | Preparing to replace linux-container 1-5 (using .../linux-container_1-6_all.deb) ... | Unpacking replacement linux-container ... | dpkg: error processing /var/cache/apt/archives/linux-container_1-6_all.deb (--unpack): | trying to overwrite '/usr/bin/uptime', which is also in package procps 1:3.3.2-3 | [..] | Processing triggers for install-info ... | Errors were encountered while processing: | /var/cache/apt/archives/linux-container_1-6_all.deb Thanks -- System Information: Debian Release: wheezy/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ro_RO.utf8, LC_CTYPE=ro_RO.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-container depends on: ii debconf [debconf-2.0] 1.5.43 linux-container recommends no packages. Versions of packages linux-container suggests: pn openssh-server none -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672034: widelands: FTBFS: collect2: error: ld returned 1 exit status
found 672034 widelands/1:17~rc2-3 thanks On 10/05/12 at 07:16 +0200, Martin Quinson wrote: Hello, It seems to me that the FTBFS comes from the fact that you used gcc-4.7 to build the package. If so, I'm kinda doubting the need for a tag wheezy since gcc-4.7 is not part of wheezy. Hi, Tags: wheezy sid really means Tags: does not affect stable (unfortunately, there's no such tag). Tagging sid only is dangerous, since this bug will affect wheezy as soon as GCC 4.7 will migrate to wheezy. So we would need to make sure that tags are updated accordingly. This package being part of various transitions and building fine with gcc-4.6, I was wondering if it would be possible to (temporarly?) lowering the bug severity to allow its migration to testing, and the completion of the libboost transition, amongst others. That decision would need to be taken by the release team. However, an easier solution is to mark that bug as affecting the testing version as well (since the migration criteria is no new RC bugs). I've just done that (I did not check that the testing package also fails to build with 4.7, but it seems to be a reasonable bet). Lucas -- 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#672034: widelands: FTBFS: collect2: error: ld returned 1 exit status
Processing commands for cont...@bugs.debian.org: found 672034 widelands/1:17~rc2-3 Bug #672034 [src:widelands] widelands: FTBFS: collect2: error: ld returned 1 exit status Marked as found in versions widelands/1:17~rc2-3. thanks Stopping processing here. Please contact me if you need assistance. -- 672034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672034 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#672335: aptitude: FTBFS in incremental_expression.h
Source: aptitude
Version: 0.6.7
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
g++ -DLOCALEDIR=\/usr/share/locale\ -DHAVE_CONFIG_H -I.
-I../../../../src/generic/apt -I../../.. -I../../..
-I../../../../src/generic/apt -I../../../.. -I../../../../src
-D_FORTIFY_SOURCE=2 -I/usr/include -DHELPDIR=\/usr/share/aptitude\
-DPKGDATADIR=\/usr/share/aptitude\ -g -O2 -fPIE -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security
-I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/lib/cwidget
-I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include
-I/usr/include/tagcoll-2.0.13 -D_REENTRANT -fno-strict-aliasing -Wall
-Werror -c -o aptitude_resolver.o
../../../../src/generic/apt/aptitude_resolver.cc
In file included from
../../../../src/generic/problemresolver/problemresolver.h:55:0,
from ../../../../src/generic/apt/aptitude_resolver.h:32,
from ../../../../src/generic/apt/aptitude_resolver.cc:20:
.../../../../src/generic/problemresolver/incremental_expression.h: In
instantiation of ‘void var_eT::set_value(T) [with T = bool]’:
.../../../../src/generic/problemresolver/problemresolver.h:4010:2: required
from ‘void generic_problem_resolverPackageUniverse::reject_version(const
version, undo_group*) [with PackageUniverse = aptitude_universe;
generic_problem_resolverPackageUniverse::version = aptitude_resolver_version]’
.../../../../src/generic/apt/aptitude_resolver.cc:1363:5: required from here
.../../../../src/generic/problemresolver/incremental_expression.h:536:2: error:
‘signal_value_changed’ was not declared in this scope, and no declarations were
found by argument-dependent lookup at the point of instantiation [-fpermissive]
.../../../../src/generic/problemresolver/incremental_expression.h:536:2: note:
declarations in dependent base ‘expressionbool’ are not found by unqualified
lookup
.../../../../src/generic/problemresolver/incremental_expression.h:536:2: note:
use ‘this-signal_value_changed’ instead
-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude
aptitude version information:
aptitude 0.6.7 compiled at May 5 2012 03:07:17
Compiler: g++ 4.6.3
Compiled against:
apt version 4.12.0
NCurses version 5.9
libsigc++ version: 2.2.10
Ept support enabled.
Gtk+ support disabled.
Qt support disabled.
Current library versions:
NCurses version: ncurses 5.9.20110404
cwidget version: 0.5.16
Apt version: 4.12.0
aptitude linkage:
linux-gate.so.1 = (0xb7717000)
libapt-pkg.so.4.12 = /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
(0xb71b5000)
libncursesw.so.5 = /lib/i386-linux-gnu/libncursesw.so.5 (0xb7183000)
libtinfo.so.5 = /lib/i386-linux-gnu/libtinfo.so.5 (0xb7162000)
libsigc-2.0.so.0 = /usr/lib/libsigc-2.0.so.0 (0xb715d000)
libcwidget.so.3 = /usr/lib/libcwidget.so.3 (0xb705c000)
libept.so.1.0.5.4.12 = /usr/lib/libept.so.1.0.5.4.12 (0xb700c000)
libxapian.so.22 = /usr/lib/sse2/libxapian.so.22 (0xb6e0d000)
libz.so.1 = /usr/lib/i386-linux-gnu/libz.so.1 (0xb6df5000)
libsqlite3.so.0 = /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb6d4d000)
libboost_iostreams.so.1.49.0 = /usr/lib/libboost_iostreams.so.1.49.0
(0xb6d36000)
libpthread.so.0 = /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
(0xb6d1d000)
libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb6c31000)
libm.so.6 = /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb6c0a000)
libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb6bed000)
libc.so.6 = /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb6a9)
libutil.so.1 = /lib/i386-linux-gnu/i686/cmov/libutil.so.1 (0xb6a8c000)
libdl.so.2 = /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb6a88000)
libbz2.so.1.0 = /lib/i386-linux-gnu/libbz2.so.1.0 (0xb6a77000)
libuuid.so.1 = /lib/i386-linux-gnu/libuuid.so.1 (0xb6a71000)
librt.so.1 = /lib/i386-linux-gnu/i686/cmov/librt.so.1 (0xb6a68000)
/lib/ld-linux.so.2 (0xb7718000)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-- no debconf information
From 49b626df6ac253bd2d5ac7c9e1b857c5204f5cd3 Mon Sep 17 00:00:00 2001
From: Adrian Lang m...@adrianlang.de
Date: Thu, 10 May 2012 09:37:13 +0200
Subject: [PATCH] Fix FTBFS
diff --git a/src/generic/problemresolver/incremental_expression.h b/src/generic/problemresolver/incremental_expression.h
index da23520..81334ae 100644
--- a/src/generic/problemresolver/incremental_expression.h
+++ b/src/generic/problemresolver/incremental_expression.h
@@ -533,7 +533,7 @@ public:
{
T old_value = value;
value = new_value;
-
Bug#669949: Still having a problem with no keyboard mouse after upgrade to .24
On Wed, May 09, 2012 at 06:52:52PM -0700, Dean Loros wrote: It looks like this is not fixed in my case. I yes'd all developer changes to Initscripts (thought that might fix things), but I still have no keyboard or mouse--using both as USB3 devices. I can unplug replug them--then both will work normally. What logs do you need to see this? I also have downgraded before this to 22.1 have had normal functions...I don't know if I can downgrade easily with the current version. Only things that seem to be affected are the keyboard mouse. This is odd. It's definitely fixed the problem for myself, which was due to cleaning /run and removing some of the udev state. If you add an exit 0 to the top of /lib/init/bootclean.sh (to disable cleaning), does this prevent the problem? Did you reboot after installing -24? (Since this is a problem which is created at boot) It would be useful to have a copy of the boot logs for 22.1 and 24 so that we can look at any obvious differences. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672100: [Bulk] Bug#672100: presage: FTBFS: profileManagerTest.cpp:86:47: error: 'unlink' was not declared in this scope
Thanks for the bug report and the proposed patch. I plan to upload an updated package that fixes the FTBFS bug to mentors later today. Cheers, - Matteo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636148: marked as done (smarty3: Smarty3 source package does not contain source code)
Your message dated Thu, 10 May 2012 09:18:12 + with message-id e1sspvk-0005d2...@franck.debian.org and subject line Bug#636148: fixed in smarty3 3.1.8-1 has caused the Debian Bug report #636148, regarding smarty3: Smarty3 source package does not contain source code 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.) -- 636148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: smarty3 Version: 3.0.8-1 Severity: normal As far as I can tell, the Smarty3 source package does not actually contain the smarty3 source code. For example, I wrote the file http://smarty-php.googlecode.com/svn/trunk/development/lexer/smarty_internal_configfileparser.y which is the source code for the file http://smarty-php.googlecode.com/svn/trunk/distribution/libs/sysplugins/smarty_internal_templateparser.php which is included in the Debian Smarty3 package. As the GPL states, The “source code” for a work means the preferred form of the work for making modifications to it.. So since the .y files is obviously the preferred form, smarty_internal_configfileparser.y should be distributed in the Debian source package, to be in compliance with the GNU LGPL. Regards, Thue -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages smarty3 depends on: ii php5-cli 5.3.6-13 command-line interpreter for the p smarty3 recommends no packages. smarty3 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: smarty3 Source-Version: 3.1.8-1 We believe that the bug you reported is fixed in the latest version of smarty3, which is due to be installed in the Debian FTP archive: smarty3_3.1.8-1.debian.tar.gz to main/s/smarty3/smarty3_3.1.8-1.debian.tar.gz smarty3_3.1.8-1.dsc to main/s/smarty3/smarty3_3.1.8-1.dsc smarty3_3.1.8-1_all.deb to main/s/smarty3/smarty3_3.1.8-1_all.deb smarty3_3.1.8.orig.tar.gz to main/s/smarty3/smarty3_3.1.8.orig.tar.gz 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 636...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel mike.gabr...@das-netzwerkteam.de (supplier of updated smarty3 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 10 May 2012 10:44:55 +0200 Source: smarty3 Binary: smarty3 Architecture: source all Version: 3.1.8-1 Distribution: experimental Urgency: low Maintainer: Mike Gabriel mike.gabr...@das-netzwerkteam.de Changed-By: Mike Gabriel mike.gabr...@das-netzwerkteam.de Description: smarty3- Template engine for PHP Closes: 636148 657385 668200 Changes: smarty3 (3.1.8-1) experimental; urgency=low . * New upstream release (rev. 4611). * New package maintainer (closes: #668200). * Add watch file (closes: #657385). * Add Vcs-* lines to control file. * Add README.source that explains how we obtain code from upstream SVN. Make sure all upstream source files are shipped with the Debian source package (closes: #636148). Checksums-Sha1: a0649e933eb684c8582dcfd9f6f1c0e257e4e2b4 1893 smarty3_3.1.8-1.dsc 3050e2c5bd0bcc74a69d56f0b21b78550f707236 1637808 smarty3_3.1.8.orig.tar.gz 2b6020fdbf5e20ef1c3bf9b56e4af06ed1343bae 2713 smarty3_3.1.8-1.debian.tar.gz dfe4a9000b303b83b44a33d7631ae68d8494f283 205122 smarty3_3.1.8-1_all.deb Checksums-Sha256: 0c664de66df408bf9ba0129f1d94d4ed9b246e3fceaa2916ed4048a1b63b106c 1893 smarty3_3.1.8-1.dsc 0257a1827e9cb32687dc0726b329987dcc21d9bf161a11ea189e5bc41b53f504 1637808 smarty3_3.1.8.orig.tar.gz 010c2e91c4ba3b2d42b23e573d20d250f96fafb35d10f026653bda21a07c 2713 smarty3_3.1.8-1.debian.tar.gz c7f356c7f3feb8d8bf561954cdbebe4dd10facca664de277287742146734565c 205122 smarty3_3.1.8-1_all.deb Files: cbb8c706e2e96871742fe2c2025bb72d 1893 web optional smarty3_3.1.8-1.dsc c79dff3b5a7250de20093ea7d2bf01b1 1637808 web optional smarty3_3.1.8.orig.tar.gz 6787843d709e3af6e3e746c2cad44393 2713 web
Bug#672348: texlive-xetex: Missing file t3enc.def
Package: texlive-xetex Version: 2011.20120509-1 Severity: grave File: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty xunicode now need t3enc.def from tipa. | (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty | (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty | (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1enc.def) | (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1lmr.fd)) | (/usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty | ! I can't find file `t3enc.def'. As xunicode is included in almost any xelatex file, this needs a depends. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages texlive-xetex depends on: ii dpkg1.16.3 ii tex-common 3.10 ii texlive-base2011.20120424-1 ii texlive-binaries2011.20120410-1 ii texlive-common 2011.20120424-1 ii texlive-latex-base 2011.20120424-1 Versions of packages texlive-xetex recommends: pn lmodern 2.004.1-5 pn tipa none texlive-xetex suggests no packages. Versions of packages tex-common depends on: ii debconf [debconf-2.0] 1.5.42 ii dpkg 1.16.3 ii ucf3.0025+nmu3 Versions of packages tex-common suggests: pn debhelper none Versions of packages texlive-xetex is related to: ii tex-common3.10 ii texlive-binaries 2011.20120410-1 -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 672256 in 5.1.50+svn15410-1, severity of 670982 is serious
Processing commands for cont...@bugs.debian.org:
found 672256 5.1.50+svn15410-1
Bug #672256 [gforge-db-postgresql] gforge-db-postgresql: unowned files after
purge (policy 6.8, 10.8): /etc/postgresql/9.1/main/pg_hba.conf.ucf-old
Marked as found in versions fusionforge/5.1.50+svn15410-1.
severity 670982 serious
Bug #670982 {Done: Keith Packard kei...@debian.org} [fontconfig-config]
fontconfig-config: fail to delete non-empty /var/lib/defoma/fontconfig.d/
Severity set to 'serious' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
670982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670982
672256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672256
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#672353: IPv6 does not work
Package: linux-2.6 Version: 2.6.32-44 Severity: grave Tags: squeeze Hello, Since the upgrade linux-image-2.6.32-5-kirkwood 2.6.32-41squeeze2 - 2.6.32-44, IPv6 is no longer working: $ sudo modprobe ipv6 FATAL: Error inserting ipv6 (/lib/modules/2.6.32-5-kirkwood/kernel/net/ipv6/ipv6.ko): Unknown symbol in module, or unknown parameter (see dmesg) $ dmesg | tail [ 859.528092] ipv6: Unknown symbol sock_queue_err_skb [ 955.738434] ipv6: Unknown symbol sock_queue_err_skb [ 955.823919] ipv6: Unknown symbol sock_queue_err_skb [ 956.146015] ipv6: Unknown symbol sock_queue_err_skb [ 956.231203] ipv6: Unknown symbol sock_queue_err_skb [ 960.375556] ipv6: Unknown symbol sock_queue_err_skb [ 960.483456] ipv6: Unknown symbol sock_queue_err_skb [ 1160.345399] ipv6: Unknown symbol sock_queue_err_skb [ 1160.474001] ipv6: Unknown symbol sock_queue_err_skb [ 1228.298415] ipv6: Unknown symbol sock_queue_err_skb A new ipv6: Unknown symbol sock_queue_err_skb appears each time I try to load the ipv6 module. Cheers, -- Stéphane -- Package-specific info: ** Version: Linux version 2.6.32-5-kirkwood (Debian 2.6.32-39squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Thu Jan 12 01:10:21 UTC 2012 ** Command line: root=/dev/ram initrd=0xa0,0x90 ramdisk=32768 ** Not tainted ** Kernel log: [ 24.095568] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 24.122391] orion-ehci orion-ehci.0: irq 19, io mem 0xf105 [ 24.142379] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 24.142457] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 24.142479] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 24.142502] usb usb1: Product: Marvell Orion EHCI [ 24.142518] usb usb1: Manufacturer: Linux 2.6.32-5-kirkwood ehci_hcd [ 24.142537] usb usb1: SerialNumber: orion-ehci.0 [ 24.143108] usb usb1: configuration #1 chosen from 1 choice [ 24.143435] hub 1-0:1.0: USB hub found [ 24.143508] hub 1-0:1.0: 1 port detected [ 24.442379] ata5: SATA link down (SStatus 0 SControl F300) [ 24.462379] usb 1-1: new high speed USB device using orion-ehci and address 2 [ 24.602397] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 24.613701] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 [ 24.613726] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 24.613747] usb 1-1: Product: USB2.0 Hub [ 24.614279] usb 1-1: configuration #1 chosen from 1 choice [ 24.614860] hub 1-1:1.0: USB hub found [ 24.615203] hub 1-1:1.0: 4 ports detected [ 24.642410] ata1.00: ATA-8: WDC WD10EARS-22Y5B1, 80.00A80, max UDMA/133 [ 24.642439] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 24.682475] ata1.00: configured for UDMA/133 [ 24.682802] scsi 0:0:0:0: Direct-Access ATA WDC WD10EARS-22Y 80.0 PQ: 0 ANSI: 5 [ 25.192394] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 25.232417] ata2.00: ATA-8: WDC WD10EARS-22Y5B1, 80.00A80, max UDMA/133 [ 25.232448] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 25.272470] ata2.00: configured for UDMA/133 [ 25.272786] scsi 1:0:0:0: Direct-Access ATA WDC WD10EARS-22Y 80.0 PQ: 0 ANSI: 5 [ 25.299347] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 25.299386] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 25.299640] sd 0:0:0:0: [sda] Write Protect is off [ 25.299663] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 25.300291] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 25.300935] sda: [ 25.301536] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 25.301572] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 25.301820] sd 1:0:0:0: [sdb] Write Protect is off [ 25.301844] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 25.301948] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 25.302624] sdb: sda1 [ 25.311268] sd 0:0:0:0: [sda] Attached SCSI disk [ 25.315545] sdb1 [ 25.317482] sd 1:0:0:0: [sdb] Attached SCSI disk [ 25.622388] ata3: SATA link down (SStatus 0 SControl 300) [ 25.972385] ata4: SATA link down (SStatus 0 SControl 300) [ 26.322381] ata6: SATA link down (SStatus 0 SControl F300) [ 26.692613] md: raid1 personality registered for level 1 [ 26.751515] md: md0 stopped. [ 26.770724] md: bindsdb1 [ 26.771104] md: bindsda1 [ 26.779526] raid1: raid set md0 active with 2 out of 2 mirrors [ 26.779653] md0: detected capacity change from 0 to 1000202174464 [ 26.783968] md0: unknown partition table [ 27.024226] device-mapper: uevent: version 1.0.3 [ 27.026396] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [ 27.309962] kjournald starting. Commit interval 5 seconds [ 27.310018] EXT3-fs: mounted filesystem with ordered data mode. [ 28.680010] udev[218]: starting version 164 [
Bug#672015: Build issue when building with gcc-4.7
Hi, when building libhmsbeagle using gcc version 4.7 you get a build error which can be easily fixed (see patch in Debian Med SVN[1]) Before I upload a package featuring this patch I would like to clarify something which remains not clear to me. The first thing is that I'm a bit unsure what version you might consider as stable for Debian release. The homepage[2] is featuring version 1.0. However, our watch file (containing the metainformation from where to download the source which needs to point to tagged SVN releases because you are not providing a downloadable source tarball) points to SVN tags[3] and finds version 1.1. So which one is the one you want Debian to distribute? BTW, questions like this will not occure if you would provide versioned a source tarball at the homepage directly. The second issue is about the problem which was discussed in the beginning of this year[4] about SSE support. I have noticed that you seem to have dealt with this but at least if I build not really successfully. I can not build on my amd64 machine if I do not at least add this patch: --- libhmsbeagle-1.1.orig/configure.ac +++ libhmsbeagle-1.1/configure.ac @@ -211,6 +211,9 @@ if test $enable_sse = yes; then SSE_CFLAGS+=-DENABLE_SSE AM_CXXFLAGS=$AM_CXXFLAGS -msse2 +AM_CONDITIONAL(HAVE_SSE2,true) +else +AM_CONDITIONAL(HAVE_SSE2,false) fi # -- Otherwise automake is claimin missing AM_CONDITIONAL statement for HAVE_SSE2. Moreover I think the way you changed libhmsbeagle/CPU/Makefile.am is not sufficiently preventing that the build system tries to build libhmsbeagle-cpu-sse.la on non-Intel architectures. The first line says: lib_LTLIBRARIES=libhmsbeagle-cpu.la libhmsbeagle-cpu-sse.la and thus libhmsbeagle-cpu-sse.la is an unconditional target which is not handled by the HAVE_SSE2 conditional. It might be that the HAVE_SSE2 condition has a completely different purpose than the patch from Debian[5] which was using HAVE_SSE and thus I would like to make sure I have understood things properly first before I upload. Kind regards and thanks for providing libhmsbeagle as Free Software Andreas. [1] http://anonscm.debian.org/viewvc/debian-med/trunk/packages/libhmsbeagle/trunk/debian/patches/gcc-4.7.patch?view=markup [2] http://code.google.com/p/beagle-lib/ [3] http://beagle-lib.googlecode.com/svn/tags/ [4] http://bugs.debian.org/656755 [5] http://anonscm.debian.org/viewvc/debian-med/trunk/packages/libhmsbeagle/trunk/debian/patches/disable_cpu_sse_plugin.patch?revision=9433view=markup -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668314: [calibre] same here, rebuilding fixes the problem
Package: calibre Version: 0.8.49+dfsg-0.1 Same here, just rebuilding the calibre and calibre-bin fixes the problem. Cheers, Bastian --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-2-amd64 Debian Release: wheezy/sid 500 unstableftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-= python2.7 | 2.7.3~rc2-2.1 python-dbus | 1.1.0-1 python-imaging| 1.1.7-4 python-lxml | 2.3.2-1 python-mechanize | 1:0.2.5-2 python-beautifulsoup | 3.2.0-2 python-pkg-resources | 0.6.24-1 python-cssutils (= 0.9.7~) | 0.9.9-1 python-cherrypy3 (= 3.1.1) | 3.2.2-2 python-dateutil | 1.5-1 python-feedparser | 5.0.1-1 python-qt4 (= 4.9.1-3) | 4.9.1-3 python-pyparsing | 1.5.2-2 python-routes | 1.13-1 python-chardet| 2.0.1-2 xdg-utils | 1.1.0~rc1+git20111210-6 imagemagick | 8:6.7.4.0-5 poppler-utils | 0.16.7-3 ttf-liberation| 1.07.2-2 calibre-bin (= 0.8.49+dfsg-0.2) | 0.8.49+dfsg-0.2 Recommends(Version) | Installed ===-+-=== python-dnspython| 1.9.4-1 Package's Suggests field is empty. -- Bastian Venthur http://venthur.de Debian Developer venthur at 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: adding patch-tag
Processing commands for cont...@bugs.debian.org: tags 668314 patch Bug #668314 [calibre] calibre: crash on start - python-sip api change related Bug #671809 [calibre] calibre: Calibre segfaults on startup. likely python-sip related Added tag(s) patch. Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 668314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668314 671809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671809 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#672023: goldencheetah: ftbfs with GCC-4.7
reassign 672023 qwtplot3d merge 672067 672023 affect 672067 goldencheetah thanks hi, At Wed, 09 May 2012 19:55:45 +0900, KURASHIKI Satoru wrote: The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. I confirmed that this FTBFS was reproduced in sid environment, With a quick look, It seems that qwt3d_openglhelper.h should have #include GL/glu.h. # already filed as #665750 and with the change above fix FTBFS. So, I will reassign this bug to qwtplot3d and merge with #665750 later. I do this, and now qwtplot3d has 3 bugs all fixed by same include. #665750 says it occurred by the transition of QT4.8, so I leave it alone, and merge only with #672067. regards, -- KURASHIKI Satoru -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672357: virtualbox-ose-dkms: fails to build kernel module - I found a solution
Package: virtualbox-ose-dkms Version: 3.2.10-dfsg-1 Severity: grave Tags: patch Justification: renders package unusable Virtualbox-ose fails to start a virtualmachine due to lack of virtualbox kernel module. modprobe vboxdrv returns FATAL: module not found. Package virtualbox-ose-dkms was installed but no module was built during the installation. However the package didn't report an error upon installation. I installed virtualbox-ose-source and re-installed virtualbox-ose-dkms. Now virtualbox-ose-dkms really built a module for the kernel and installed it. Virtualbox-ose runs virtual machiens fine. The problem is fixed. I suggest to make virtualbox-ose-source a dependency of virtualbox-ose-dkms (which is a dependency of virtualbox-ose, right?). That should fix the problem. Best regards - unfa. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-ose-dkms depends on: ii dkms 2.1.1.2-5 Dynamic Kernel Module Support Fram virtualbox-ose-dkms recommends no packages. virtualbox-ose-dkms suggests no packages. -- no debconf information -- Tobiasz unfa -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT/MU/P d--- s+:-(--) a? C++(+++)$ ULC+(++)$ !P? L+++$ E? W++$ !N-? !o--? K-? !w-- O? !M-- V? PS++ PE++ !Y+ !PGP+? !t(+) 5? !X !R+ tv b DI+ D+ G e h--- !r y--() --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org:
reassign 672023 qwtplot3d
Bug #672023 [src:goldencheetah] goldencheetah: FTBFS:
qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this
scope
Bug reassigned from package 'src:goldencheetah' to 'qwtplot3d'.
No longer marked as found in versions goldencheetah/2.1-3.
Ignoring request to alter fixed versions of bug #672023 to the same values
previously set
merge 672067 672023
Bug #672067 [src:qwtplot3d] qwtplot3d: FTBFS:
include/qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in
this scope
Unable to merge bugs because:
package of #672023 is 'qwtplot3d' not 'src:qwtplot3d'
Failed to merge 672067: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1c8f9a8)',
'requester', 'Satoru KURASHIKI lur...@gmail.com', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'CAM0xXk-zoJrxYxs7NWeO7Hy5eyZWSmtcWB9jZe1re81a8Rq=d...@mail.gma...',
'request_subject', ...) called at /usr/lib/debbugs/service line 872
eval {...} called at /usr/lib/debbugs/service line 871
affect 672067 goldencheetah
Failed to mark 672067 as affecting package(s): failed to get lock on
/org/bugs.debian.org/spool/lock/672067 -- Unable to lock
/org/bugs.debian.org/spool/lock/672067 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/672067 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579. at
/usr/local/lib/site_perl/Debbugs/Common.pm line 597
Debbugs::Common::filelock('/org/bugs.debian.org/spool/lock/672067')
called at /usr/local/lib/site_perl/Debbugs/Status.pm line 209
Debbugs::Status::read_bug('bug', 672067, 'lock', 1) called at
/usr/local/lib/site_perl/Debbugs/Status.pm line 464
Debbugs::Status::lock_read_all_merged_bugs('bug', 672067) called at
/usr/local/lib/site_perl/Debbugs/Control.pm line 3604
Debbugs::Control::__begin_control('remove', 0, 'add', 1,
'request_replyto', 'Satoru KURASHIKI lur...@gmail.com', 'transcript',
'GLOB(0x1c8f9a8)', 'bug', ...) called at
/usr/local/lib/site_perl/Debbugs/Control.pm line 2533
Debbugs::Control::affects('transcript', 'GLOB(0x1c8f9a8)', 'requester',
'Satoru KURASHIKI lur...@gmail.com', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'CAM0xXk-zoJrxYxs7NWeO7Hy5eyZWSmtcWB9jZe1re81a8Rq=d...@mail.gma...',
'request_subject', ...) called at /usr/lib/debbugs/service line 984
eval {...} called at /usr/lib/debbugs/service line 983
thanks
Stopping processing here.
Please contact me if you need assistance.
--
672023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672023
672067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672067
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#672358: dbus: some machines do not shutdown properly and do not do poweroff
Package: dbus Version: 1.5.12-1 Justification: breaks the whole system Severity: critical Dear Maintainer, I have some desktop, server and notebooks running debian. All machines have nvidia graphic cards and driver are proprietary from nvidia. Until 05/2012 I run debian squeeze on all machines. In 05/2012 I begin update to debian wheezy with fresh install. Kernel used is taken from kernel.org without any patches, configuration is taken from debian experimental. All machines uses kde as window system. With debian wheezy (testing), last dist-upgrade 09.05.2012, on all type of machines, I have got problems with full shutdown by running shutdown -h now or shutdown -hP now on notebook system, which is an Acer Aspire 8930G-944. The system hang on try to kill remaining processes. Desktop system do the shutdown. For I'am using a new kernel on the notebook, I think this may be a kernel/bios problem and I try the typical acpi, etc. kernel options with no success. After this probes I think it maybe a problem with nvidia driver and try several versions, no success. At least I inspect the run level and found that there is no dbus kill link in run level 0 for dbus. I added a link to stop dbus lately after kdm and after adding this kill link the shutdown process finished successfully. Inspecting lsb header of dbus script in /etc/init.d I see that there is no entry for Default-Stop. It seem that the finishing kill on remaining processes at end of shutdown do not stop dbus and related processes. I add a file dbus to /etc/insserv/overrides with content ### BEGIN INIT INFO # Provides: dbus # Required-Start:$remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: D-Bus systemwide message bus # Description: D-Bus is a simple interprocess messaging system, used #for sending messages between applications. ### END INIT INFO It is not clear to me whether this file is honored on update of dbus because I have problems understanding the complex handling of program update-rc.d. Please enter proper stop directives (0 1 6) to lsb header in init script and postinst script to honor this change. Thanks in advance -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.3.5-ksamd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dbus depends on: ii adduser3.113+nmu1 ii libc6 2.13-32 ii libdbus-1-31.5.12-1 ii libexpat1 2.1.0-1 ii libselinux12.1.9-2 ii libsystemd-login0 37-1.1 ii lsb-base 4.1+Debian2 dbus recommends no packages. Versions of packages dbus suggests: ii dbus-x11 1.5.12-1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: reassign 672023 src:qwtplot3d Bug #672023 [qwtplot3d] goldencheetah: FTBFS: qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope Bug reassigned from package 'qwtplot3d' to 'src:qwtplot3d'. Ignoring request to alter found versions of bug #672023 to the same values previously set Ignoring request to alter fixed versions of bug #672023 to the same values previously set merge 672067 672023 Bug #672067 [src:qwtplot3d] qwtplot3d: FTBFS: include/qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope Bug #672023 [src:qwtplot3d] goldencheetah: FTBFS: qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope Marked as found in versions qwtplot3d/0.2.7+svn191-5. Merged 672023 672067 affect 672067 goldencheetah Bug #672067 [src:qwtplot3d] qwtplot3d: FTBFS: include/qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope Bug #672023 [src:qwtplot3d] goldencheetah: FTBFS: qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope Added indication that 672067 affects goldencheetah Added indication that 672023 affects goldencheetah thanks Stopping processing here. Please contact me if you need assistance. -- 672023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672023 672067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672067 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#672357: marked as done (virtualbox-ose-dkms: fails to build kernel module - I found a solution)
Your message dated Thu, 10 May 2012 13:40:03 +0200 with message-id 20120510114003.ga25...@feivel.credativ.lan and subject line Re: [Pkg-virtualbox-devel] Bug#672357: virtualbox-ose-dkms: fails to build kernel module - I found a solution has caused the Debian Bug report #672357, regarding virtualbox-ose-dkms: fails to build kernel module - I found a solution 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.) -- 672357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: virtualbox-ose-dkms Version: 3.2.10-dfsg-1 Severity: grave Tags: patch Justification: renders package unusable Virtualbox-ose fails to start a virtualmachine due to lack of virtualbox kernel module. modprobe vboxdrv returns FATAL: module not found. Package virtualbox-ose-dkms was installed but no module was built during the installation. However the package didn't report an error upon installation. I installed virtualbox-ose-source and re-installed virtualbox-ose-dkms. Now virtualbox-ose-dkms really built a module for the kernel and installed it. Virtualbox-ose runs virtual machiens fine. The problem is fixed. I suggest to make virtualbox-ose-source a dependency of virtualbox-ose-dkms (which is a dependency of virtualbox-ose, right?). That should fix the problem. Best regards - unfa. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-ose-dkms depends on: ii dkms 2.1.1.2-5 Dynamic Kernel Module Support Fram virtualbox-ose-dkms recommends no packages. virtualbox-ose-dkms suggests no packages. -- no debconf information -- Tobiasz unfa -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT/MU/P d--- s+:-(--) a? C++(+++)$ ULC+(++)$ !P? L+++$ E? W++$ !N-? !o--? K-? !w-- O? !M-- V? PS++ PE++ !Y+ !PGP+? !t(+) 5? !X !R+ tv b DI+ D+ G e h--- !r y--() --END GEEK CODE BLOCK-- ---End Message--- ---BeginMessage--- Virtualbox-ose fails to start a virtualmachine due to lack of virtualbox kernel module. modprobe vboxdrv returns FATAL: module not found. Package virtualbox-ose-dkms was installed but no module was built during the installation. However the package didn't report an error upon installation. The reason for this may be that some packages needed for the build were not available, like the correct kernel headers. It's almost impossible to tell what exactly was at fault here. However, it surely is not virtualbox-ose-dkms' fault. I installed virtualbox-ose-source and re-installed virtualbox-ose-dkms. Now virtualbox-ose-dkms really built a module for the kernel and installed it. Virtualbox-ose runs virtual machiens fine. The problem is fixed. I suggest to make virtualbox-ose-source a dependency of virtualbox-ose-dkms (which is a dependency of virtualbox-ose, right?). Why? Just because you installed it does not mean it was part of the solution. In fact the solution was to re-install virtualbox-ose-dkms. This package contains the same sources as virtualbox-ose-source with the only difference being that virtualbox-ose-dkms works with dkms, while virtualbox-ose-source is made for module-assistant. That should fix the problem. No, that won't change anything. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL ---End Message---
Bug#672358: dbus: some machines do not shutdown properly and do not do poweroff
On 10/05/12 11:56, Jürgen Kaiser wrote: With debian wheezy (testing), last dist-upgrade 09.05.2012, on all type of machines, I have got problems with full shutdown by running shutdown -h now or shutdown -hP now [...] At least I inspect the run level and found that there is no dbus kill link in run level 0 for dbus. I added a link to stop dbus lately after kdm and after adding this kill link the shutdown process finished successfully. Please enter proper stop directives (0 1 6) to lsb header in init script and postinst script to honor this change. As far as I understand it, what dbus does (no explicit stop directives) is meant to work, and is correct for anything that doesn't need to do special cleanup during shutdown - having init kill all the remaining processes with a single syscall is more efficient than running shell scripts that kill them individually, leading to a faster shutdown. The change was made back in 1.1.4-1 for runlevels 0 and 6, and 1.2.24-1 for runlevel 1, so dbus was already not killed in those runlevels in squeeze. (anacron, cron, sshd are among other examples of common daemons that don't have an explicit stop runlevel.) This might mean that something has changed in dbus and/or init more recently, such that the way init kills it no longer works? (The same dbus version worked fine last time I rebooted my laptop, though.) Alternatively: what upgrade path did you use on the machine where init stalls waiting for dbus? Did you install wheezy, or install squeeze and upgrade, or what? Depending on the upgrade path you followed, you might have ended up with slightly different configuration. Similarly, did you say you had a similar machine where init *does* kill dbus properly without any intervention from you? If you do, what version of Debian did you originally install on that machine, and what upgrade path did you use there? Kernel used is taken from kernel.org without any patches, configuration is taken from debian experimental. I'd be interested to hear what happens with the packaged Debian kernel (linux-image-3.2.0-2-amd64 from unstable and/or linux-image-3.3.0-trunk-amd64 from experimental), if those can boot on your hardware. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667291: music: diff for NMU version 1.0.7-1.2
tags 667291 + patch
tags 667291 + pending
thanks
Dear maintainer,
I've prepared an NMU for music (versioned as 1.0.7-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u music-1.0.7/debian/changelog music-1.0.7/debian/changelog
--- music-1.0.7/debian/changelog
+++ music-1.0.7/debian/changelog
@@ -1,3 +1,11 @@
+music (1.0.7-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-4.7: add #include unistd.h to
+utils/VisualiseNeurons.cpp (Closes: #667291).
+
+ -- Mònica Ramírez Arceda mon...@debian.org Thu, 10 May 2012 13:40:31 +0200
+
music (1.0.7-1.1) unstable; urgency=low
* Non-maintainer upload.
only in patch2:
unchanged:
--- music-1.0.7.orig/utils/VisualiseNeurons.cpp
+++ music-1.0.7/utils/VisualiseNeurons.cpp
@@ -18,7 +18,7 @@
// VisualiseNeurons.cpp written by Johannes Hjorth, hjo...@nada.kth.se
-
+#include unistd.h
#include VisualiseNeurons.h
void VisualiseNeurons::printHelp() {
Processed: music: diff for NMU version 1.0.7-1.2
Processing commands for cont...@bugs.debian.org: tags 667291 + patch Bug #667291 [music] music: ftbfs with GCC-4.7 Added tag(s) patch. tags 667291 + pending Bug #667291 [music] music: ftbfs with GCC-4.7 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 667291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667291 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: fixed 571634 in 4.1.0~rc6-1
Processing commands for cont...@bugs.debian.org:
fixed 571634 4.1.0~rc6-1
Bug #571634 {Done: Bastian Blank wa...@debian.org} [xen-utils-common]
xen-utils-common vif-common.sh still using --physdev-out, --state
Bug #639942 {Done: Bastian Blank wa...@debian.org} [xen-utils-common] Xen
non-bridged traffic is not supported anymore with bridges
Marked as fixed in versions xen-common/4.1.0~rc6-1; no longer marked as fixed
in versions 4.1.0~rc6-1.
Marked as fixed in versions xen-common/4.1.0~rc6-1; no longer marked as fixed
in versions 4.1.0~rc6-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
571634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571634
639942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639942
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#672099: marked as done (gvfs: FTBFS: gvfsafpvolume.c:1085:3: error: dereferencing pointer to incomplete type)
Your message dated Thu, 10 May 2012 12:18:03 + with message-id e1sssjn-0005r4...@franck.debian.org and subject line Bug#672099: fixed in gvfs 1.12.2-2 has caused the Debian Bug report #672099, regarding gvfs: FTBFS: gvfsafpvolume.c:1085:3: error: dereferencing pointer to incomplete type 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.) -- 672099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gvfs Version: 1.12.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../common -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gnome-keyring-1 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DLIBEXEC_DIR=\/usr/lib/gvfs/\ -DMOUNTABLE_DIR=\/usr/share/gvfs/mounts/\ -DGVFS_LOCALEDIR=\/usr/share/locale\ -DBACKEND_HEADER=gvfsbackendafpbrowse.h -DMAX_JOB_THREADS=1 -DBACKEND_TYPES='afp-server, G_VFS_TYPE_BACKEND_AFP_BROWSE,' -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o gvfsd_afp_browse-gvfsafpvolume.o `test -f 'gvfsafpvolume.c' || echo './'`gvfsafpvolume.c gvfsafpvolume.c: In function 'create_directory_get_filedir_parms_cb': gvfsafpvolume.c:1085:3: error: dereferencing pointer to incomplete type gvfsafpvolume.c:1085:3: error: dereferencing pointer to incomplete type make[5]: *** [gvfsd_afp_browse-gvfsafpvolume.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/gvfs_1.12.2-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: gvfs Source-Version: 1.12.2-2 We believe that the bug you reported is fixed in the latest version of gvfs, which is due to be installed in the Debian FTP archive: gvfs-backends_1.12.2-2_amd64.deb to main/g/gvfs/gvfs-backends_1.12.2-2_amd64.deb gvfs-bin_1.12.2-2_amd64.deb to main/g/gvfs/gvfs-bin_1.12.2-2_amd64.deb gvfs-common_1.12.2-2_all.deb to main/g/gvfs/gvfs-common_1.12.2-2_all.deb gvfs-daemons_1.12.2-2_amd64.deb to main/g/gvfs/gvfs-daemons_1.12.2-2_amd64.deb gvfs-dbg_1.12.2-2_amd64.deb to main/g/gvfs/gvfs-dbg_1.12.2-2_amd64.deb gvfs-fuse_1.12.2-2_amd64.deb to main/g/gvfs/gvfs-fuse_1.12.2-2_amd64.deb gvfs-libs_1.12.2-2_amd64.deb to main/g/gvfs/gvfs-libs_1.12.2-2_amd64.deb gvfs_1.12.2-2.debian.tar.gz to main/g/gvfs/gvfs_1.12.2-2.debian.tar.gz gvfs_1.12.2-2.dsc to main/g/gvfs/gvfs_1.12.2-2.dsc gvfs_1.12.2-2_amd64.deb to main/g/gvfs/gvfs_1.12.2-2_amd64.deb 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 672...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt mp...@debian.org (supplier of updated gvfs 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 08 May 2012 14:21:51 -0700 Source: gvfs Binary: gvfs gvfs-daemons gvfs-libs gvfs-common gvfs-fuse gvfs-backends gvfs-bin gvfs-dbg Architecture: source all amd64 Version: 1.12.2-2 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Martin Pitt mp...@debian.org Description: gvfs - userspace virtual filesystem - GIO module gvfs-backends - userspace virtual filesystem - backends gvfs-bin - userspace virtual filesystem - binaries gvfs-common -
Bug#672357: closed by Michael Meskes mes...@debian.org (Re: [Pkg-virtualbox-devel] Bug#672357: virtualbox-ose-dkms: fails to build kernel module - I found a solution)
From: Michael Meskes mes...@debian.org To: Tobiasz Karoń unf...@gmail.com, 672357-d...@bugs.debian.org Cc: Date: Thu, 10 May 2012 13:40:03 +0200 Subject: Re: [Pkg-virtualbox-devel] Bug#672357: virtualbox-ose-dkms: fails to build kernel module - I found a solution That should fix the problem. No, that won't change anything. In fact - that is what worked for me. I tried re-installing virtualbox-ose-dkms several times to no effect. I have no idea what causes the problem, I now only what fixed it for me. Do you know what is the cause? Do you consider this problem solved? Hoping to not waste your time - unfa -- Wiadomość przekazana dalej -- From: Tobiasz Karoń unf...@gmail.com To: submit sub...@bugs.debian.org Cc: Date: Thu, 10 May 2012 12:47:49 +0200 Subject: virtualbox-ose-dkms: fails to build kernel module - I found a solution Package: virtualbox-ose-dkms Version: 3.2.10-dfsg-1 Severity: grave Tags: patch Justification: renders package unusable Virtualbox-ose fails to start a virtualmachine due to lack of virtualbox kernel module. modprobe vboxdrv returns FATAL: module not found. Package virtualbox-ose-dkms was installed but no module was built during the installation. However the package didn't report an error upon installation. I installed virtualbox-ose-source and re-installed virtualbox-ose-dkms. Now virtualbox-ose-dkms really built a module for the kernel and installed it. Virtualbox-ose runs virtual machiens fine. The problem is fixed. I suggest to make virtualbox-ose-source a dependency of virtualbox-ose-dkms (which is a dependency of virtualbox-ose, right?). That should fix the problem. Best regards - unfa. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-ose-dkms depends on: ii dkms 2.1.1.2-5 Dynamic Kernel Module Support Fram virtualbox-ose-dkms recommends no packages. virtualbox-ose-dkms suggests no packages. -- no debconf information -- Tobiasz unfa -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT/MU/P d--- s+:-(--) a? C++(+++)$ ULC+(++)$ !P? L+++$ E? W++$ !N-? !o--? K-? !w-- O? !M-- V? PS++ PE++ !Y+ !PGP+? !t(+) 5? !X !R+ tv b DI+ D+ G e h--- !r y--() --END GEEK CODE BLOCK-- -- Tobiasz *unfa* -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT/MU/P d--- s+:-(--) a? C++(+++)$ ULC+(++)$ !P? L+++$ E? W++$ !N-? !o--? K-? !w-- O? !M-- V? PS++ PE++ !Y+ !PGP+? !t(+) 5? !X !R+ tv b DI+ D+ G e h--- !r y--() --END GEEK CODE BLOCK--
Processed (with 1 errors): severity of 668868 is serious, forcibly merging 668868 650805
Processing commands for cont...@bugs.debian.org:
severity 668868 serious
Bug #668868 [bitcoind] bitcoind: Assertion failed at startup on mips (big
endian)
Severity set to 'serious' from 'important'
forcemerge 668868 650805
Bug #668868 [bitcoind] bitcoind: Assertion failed at startup on mips (big
endian)
Unable to merge bugs because:
package of #650805 is 'src:bitcoin' not 'bitcoind'
Failed to forcibly merge 668868: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2c526d8)',
'requester', 'Jonas Smedegaard d...@jones.dk', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1336652070-1040-bts...@jones.dk', 'request_subject', ...) called at
/usr/lib/debbugs/service line 887
eval {...} called at /usr/lib/debbugs/service line 886
thanks
Stopping processing here.
Please contact me if you need assistance.
--
650805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650805
668868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668868
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#672353: IPv6 does not work
On Thu, May 10, 2012 at 11:59:10AM +0200, Stéphane Glondu wrote: ** Version: Linux version 2.6.32-5-kirkwood (Debian 2.6.32-39squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Thu Jan 12 01:10:21 UTC 2012 This is not -44. We expect users to reboot after an upgrade. Bastian -- You canna change the laws of physics, Captain; I've got to have thirty minutes! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665750: qwtplot3d: diff for NMU version 0.2.7+svn191-5.1
Dear maintainer,
I've prepared an NMU for qwtplot3d (versioned as 0.2.7+svn191-5.1).
Please consider to update your package (I'm not a DD, so I can't
upload this directly).
regards,
--
KURASHIKI Satoru
diff -Nru qwtplot3d-0.2.7+svn191/debian/changelog
qwtplot3d-0.2.7+svn191/debian/changelog
--- qwtplot3d-0.2.7+svn191/debian/changelog 2011-03-03 19:10:11.0
+0900
+++ qwtplot3d-0.2.7+svn191/debian/changelog 2012-05-10 21:21:33.0
+0900
@@ -1,3 +1,10 @@
+qwtplot3d (0.2.7+svn191-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * apply 04_glu_include.patch to fix FTBFS (Closes: 665750 672067)
+
+ -- KURASHIKI Satoru lur...@gmail.com Thu, 10 May 2012 21:14:42 +0900
+
qwtplot3d (0.2.7+svn191-5) unstable; urgency=low
* Remove qt3 support (Closes: #604380)
diff -Nru qwtplot3d-0.2.7+svn191/debian/patches/04_glu_include.patch
qwtplot3d-0.2.7+svn191/debian/patches/04_glu_include.patch
--- qwtplot3d-0.2.7+svn191/debian/patches/04_glu_include.patch 1970-01-01
09:00:00.0 +0900
+++ qwtplot3d-0.2.7+svn191/debian/patches/04_glu_include.patch 2012-05-10
20:55:43.0 +0900
@@ -0,0 +1,11 @@
+--- qwtplot3d-0.2.7+svn191.orig/include/qwt3d_openglhelper.h
qwtplot3d-0.2.7+svn191/include/qwt3d_openglhelper.h
+@@ -8,6 +8,8 @@
+ #include QtOpenGL/qgl.h
+ #endif
+
++#include GL/glu.h
++
+ namespace Qwt3D
+ {
+
diff -Nru qwtplot3d-0.2.7+svn191/debian/patches/series
qwtplot3d-0.2.7+svn191/debian/patches/series
--- qwtplot3d-0.2.7+svn191/debian/patches/series2011-03-03
19:10:11.0 +0900
+++ qwtplot3d-0.2.7+svn191/debian/patches/series2012-05-10
20:57:53.0 +0900
@@ -1,3 +1,4 @@
01_makefile.patch
02_examples_include.patch
03_fix_ftbs.patch
+04_glu_include.patch
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672348: texlive-xetex: Missing file t3enc.def
On Do, 10 Mai 2012, Bastian Blank wrote:
Package: texlive-xetex
Version: 2011.20120509-1
Severity: grave
File: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty
xunicode now need t3enc.def from tipa.
Indeed ..
(although *grave* I would not say ...)
I fixed that some time ago upstream, but it somehow got lost.
Redoing it.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
CLIXBY (adj.)
Politely rude. Briskly vague. Firmly uninformative.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672034: [Bug 996965] Re: Fail to build on amd64
On Thu, May 10, 2012 at 10:33:37AM -, Jens Beyer (Qcumber-some) wrote: From what I could get from this forum thread: https://bbs.archlinux.org/viewtopic.php?id=138992 it seems that a rebuild of boost libraries with the new compiler (read: gcc-4.7.0) should solve this. Martin, can you confirm if the libboost packages which are used in this build are already built by gcc-4.7.0? It seems to me that the lastest libboost in debian unstable on amd64 were built with gcc-4.6 https://buildd.debian.org/status/fetch.php?pkg=boost1.49arch=ia64ver=1.49.0-3stamp=1336330572 I'm CCing the debian bug for information archival. Thanks investiguating this, Mt. -- Le pointeur est aux données ce que la boucle while est au code. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopening 666597
Processing commands for cont...@bugs.debian.org:
# as the source package still exists lets make this closed when it gets RMed
reopen 666597
Bug #666597 {Done: Rene Engelhard r...@debian.org} [src:texpower] texpower:
FTBFS: !pdfTeX error: pdflatex (file tcrm1200): Font tcrm1200 at 600 not found
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2011.20120509-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
666597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666597
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#672348: marked as done (texlive-xetex: Missing file t3enc.def)
Your message dated Thu, 10 May 2012 21:44:44 +0900
with message-id 2012051012.gd29...@gamma.logic.tuwien.ac.at
and subject line Re: Bug#672348: texlive-xetex: Missing file t3enc.def
has caused the Debian Bug report #672348,
regarding texlive-xetex: Missing file t3enc.def
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.)
--
672348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: texlive-xetex
Version: 2011.20120509-1
Severity: grave
File: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty
xunicode now need t3enc.def from tipa.
| (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
| (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
| (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1enc.def)
| (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1lmr.fd))
| (/usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty
| ! I can't find file `t3enc.def'.
As xunicode is included in almost any xelatex file, this needs a depends.
Bastian
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages texlive-xetex depends on:
ii dpkg1.16.3
ii tex-common 3.10
ii texlive-base2011.20120424-1
ii texlive-binaries2011.20120410-1
ii texlive-common 2011.20120424-1
ii texlive-latex-base 2011.20120424-1
Versions of packages texlive-xetex recommends:
pn lmodern 2.004.1-5
pn tipa none
texlive-xetex suggests no packages.
Versions of packages tex-common depends on:
ii debconf [debconf-2.0] 1.5.42
ii dpkg 1.16.3
ii ucf3.0025+nmu3
Versions of packages tex-common suggests:
pn debhelper none
Versions of packages texlive-xetex is related to:
ii tex-common3.10
ii texlive-binaries 2011.20120410-1
-- debconf information:
tex-common/check_texmf_wrong:
tex-common/check_texmf_missing:
---End Message---
---BeginMessage---
Hi ... once more ...
On Do, 10 Mai 2012, Bastian Blank wrote:
As xunicode is included in almost any xelatex file, this needs a depends.
I disagree. THere is a recommends. You can run xetex without xunicode,
it is not necessary.
Closing this bug ... if you decide not to install recommends, then you
have to live with limitations.
I forgot that there is a recommends already.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
LOUTH (n.)
The sort of man who wears loud check jackets, has a personalised
tankard behind the bar and always gets served before you do.
--- Douglas Adams, The Meaning of Liff
---End Message---
Bug#672348: closed by Norbert Preining prein...@logic.at (Re: Bug#672348: texlive-xetex: Missing file t3enc.def)
reopen 672348 thanks On Thu, May 10, 2012 at 12:48:21PM +, Debian Bug Tracking System wrote: I forgot that there is a recommends already. There is no recommends in Stable, so it is not installed on upgrades. Bastian -- 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#672348 closed by Norbert Preining prein...@logic.at (Re: Bug#672348: texlive-xetex: Missing file t3enc.def)
Processing commands for cont...@bugs.debian.org:
reopen 672348
Bug #672348 {Done: Norbert Preining prein...@logic.at} [texlive-xetex]
texlive-xetex: Missing file t3enc.def
Bug reopened
Ignoring request to alter fixed versions of bug #672348 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
672348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672348
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#672353: marked as done (IPv6 does not work)
Your message dated Thu, 10 May 2012 15:00:30 +0200 with message-id 4fabbbee.30...@debian.org and subject line Re: Bug#672353: IPv6 does not work has caused the Debian Bug report #672353, regarding IPv6 does not work 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.) -- 672353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-44 Severity: grave Tags: squeeze Hello, Since the upgrade linux-image-2.6.32-5-kirkwood 2.6.32-41squeeze2 - 2.6.32-44, IPv6 is no longer working: $ sudo modprobe ipv6 FATAL: Error inserting ipv6 (/lib/modules/2.6.32-5-kirkwood/kernel/net/ipv6/ipv6.ko): Unknown symbol in module, or unknown parameter (see dmesg) $ dmesg | tail [ 859.528092] ipv6: Unknown symbol sock_queue_err_skb [ 955.738434] ipv6: Unknown symbol sock_queue_err_skb [ 955.823919] ipv6: Unknown symbol sock_queue_err_skb [ 956.146015] ipv6: Unknown symbol sock_queue_err_skb [ 956.231203] ipv6: Unknown symbol sock_queue_err_skb [ 960.375556] ipv6: Unknown symbol sock_queue_err_skb [ 960.483456] ipv6: Unknown symbol sock_queue_err_skb [ 1160.345399] ipv6: Unknown symbol sock_queue_err_skb [ 1160.474001] ipv6: Unknown symbol sock_queue_err_skb [ 1228.298415] ipv6: Unknown symbol sock_queue_err_skb A new ipv6: Unknown symbol sock_queue_err_skb appears each time I try to load the ipv6 module. Cheers, -- Stéphane -- Package-specific info: ** Version: Linux version 2.6.32-5-kirkwood (Debian 2.6.32-39squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Thu Jan 12 01:10:21 UTC 2012 ** Command line: root=/dev/ram initrd=0xa0,0x90 ramdisk=32768 ** Not tainted ** Kernel log: [ 24.095568] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 24.122391] orion-ehci orion-ehci.0: irq 19, io mem 0xf105 [ 24.142379] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 24.142457] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 24.142479] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 24.142502] usb usb1: Product: Marvell Orion EHCI [ 24.142518] usb usb1: Manufacturer: Linux 2.6.32-5-kirkwood ehci_hcd [ 24.142537] usb usb1: SerialNumber: orion-ehci.0 [ 24.143108] usb usb1: configuration #1 chosen from 1 choice [ 24.143435] hub 1-0:1.0: USB hub found [ 24.143508] hub 1-0:1.0: 1 port detected [ 24.442379] ata5: SATA link down (SStatus 0 SControl F300) [ 24.462379] usb 1-1: new high speed USB device using orion-ehci and address 2 [ 24.602397] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 24.613701] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 [ 24.613726] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 24.613747] usb 1-1: Product: USB2.0 Hub [ 24.614279] usb 1-1: configuration #1 chosen from 1 choice [ 24.614860] hub 1-1:1.0: USB hub found [ 24.615203] hub 1-1:1.0: 4 ports detected [ 24.642410] ata1.00: ATA-8: WDC WD10EARS-22Y5B1, 80.00A80, max UDMA/133 [ 24.642439] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 24.682475] ata1.00: configured for UDMA/133 [ 24.682802] scsi 0:0:0:0: Direct-Access ATA WDC WD10EARS-22Y 80.0 PQ: 0 ANSI: 5 [ 25.192394] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 25.232417] ata2.00: ATA-8: WDC WD10EARS-22Y5B1, 80.00A80, max UDMA/133 [ 25.232448] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 25.272470] ata2.00: configured for UDMA/133 [ 25.272786] scsi 1:0:0:0: Direct-Access ATA WDC WD10EARS-22Y 80.0 PQ: 0 ANSI: 5 [ 25.299347] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 25.299386] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 25.299640] sd 0:0:0:0: [sda] Write Protect is off [ 25.299663] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 25.300291] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 25.300935] sda: [ 25.301536] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 25.301572] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 25.301820] sd 1:0:0:0: [sdb] Write Protect is off [ 25.301844] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 25.301948] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 25.302624] sdb: sda1 [ 25.311268] sd 0:0:0:0: [sda] Attached SCSI disk [ 25.315545] sdb1 [ 25.317482] sd 1:0:0:0: [sdb] Attached SCSI disk [ 25.622388] ata3: SATA link down (SStatus 0
Bug#672348: closed by Norbert Preining prein...@logic.at (Re: Bug#672348: texlive-xetex: Missing file t3enc.def)
On Do, 10 Mai 2012, Bastian Blank wrote:
There is no recommends in Stable, so it is not installed on upgrades.
H? A dist-upgrade does NOT install recommends (if not disabled
on purpose)???
Is this a joke?
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
`Er, hey Earthman...'
`Arthur,' said Arthur.
`Yeah, could you just sort of keep this robot with you and
guard this end of the passageway. OK?'
What from? You just said there's no
one here.'
`Yeah, well, just for safety, OK?' said Zaphod.
`Whose? Yours or mine?'
--- Arthur drawing the short straw on Magrathea.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 668868 to src:bitcoin, forcibly merging 668868 650805
Processing commands for cont...@bugs.debian.org: reassign 668868 src:bitcoin Bug #668868 [bitcoind] bitcoind: Assertion failed at startup on mips (big endian) Bug reassigned from package 'bitcoind' to 'src:bitcoin'. No longer marked as found in versions bitcoin/0.3.24~dfsg-1. Ignoring request to alter fixed versions of bug #668868 to the same values previously set forcemerge 668868 650805 Bug #668868 [src:bitcoin] bitcoind: Assertion failed at startup on mips (big endian) Bug #668868 [src:bitcoin] bitcoind: Assertion failed at startup on mips (big endian) Marked as found in versions bitcoin/0.4.0-1. Bug #650805 [src:bitcoin] bitcoin: FTBFS: error in script_PushData: check EvalScript(pushdata2Stack, CScript(pushdata2[0], pushdata2[sizeof(pushdata2)]), CTransaction(), 0, 0) failed Added tag(s) patch. Merged 650805 668868 thanks Stopping processing here. Please contact me if you need assistance. -- 650805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650805 668868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668868 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#667114: marked as done (bitcoin: ftbfs with GCC-4.7)
Your message dated Thu, 10 May 2012 13:17:13 + with message-id e1sstf3-0002yv...@franck.debian.org and subject line Bug#667114: fixed in bitcoin 0.6.2.1-1 has caused the Debian Bug report #667114, regarding bitcoin: ftbfs with GCC-4.7 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.) -- 667114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bitcoin Version: 0.5.2-1 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. config_file.hpp:163:13: error: 'to_internal' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/bitcoin_0.5.2-1_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] uint256.h: In instantiation of 'void base_uintBITS::SetHex(const char*) [with unsigned int BITS = 160u]': uint256.h:343:9: required from 'void base_uintBITS::SetHex(const string) [with unsigned int BITS = 160u; std::string = std::basic_stringchar]' uint256.h:450:19: required from here uint256.h:325:9: warning: array subscript has type 'char' [-Wchar-subscripts] uint256.h: In instantiation of 'void base_uintBITS::SetHex(const char*) [with unsigned int BITS = 256u]': uint256.h:343:9: required from 'void base_uintBITS::SetHex(const string) [with unsigned int BITS = 256u; std::string = std::basic_stringchar]' uint256.h:564:19: required from here uint256.h:325:9: warning: array subscript has type 'char' [-Wchar-subscripts] In file included from headers.h:89:0, from util.cpp:5: uint256.h: In instantiation of 'std::string base_uintBITS::GetHex() const [with unsigned int BITS = 256u; std::string = std::basic_stringchar]': uint256.h:348:25: required from 'std::string base_uintBITS::ToString() const [with unsigned int BITS = 256u; std::string = std::basic_stringchar]' uint256.h:641:31: required from here uint256.h:304:22: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] uint256.h: In instantiation of 'base_uintBITS base_uintBITS::operator--() [with unsigned int BITS = 256u; base_uintBITS = base_uint256u]': uint256.h:216:9: required from 'const base_uintBITS base_uintBITS::operator--(int) [with unsigned int BITS = 256u; base_uintBITS = base_uint256u]' uint256.h:642:6: required from here uint256.h:207:9: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] In file included from util.cpp:7:0: /usr/include/boost/program_options/detail/config_file.hpp: In instantiation of 'bool boost::program_options::detail::basic_config_file_iteratorcharT::getline(std::string) [with charT = char; std::string = std::basic_stringchar]': util.cpp:1166:1: required from here /usr/include/boost/program_options/detail/config_file.hpp:163:13: error: 'to_internal' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] In file included from /usr/include/boost/program_options/detail/parsers.hpp:9:0, from /usr/include/boost/program_options/parsers.hpp:265, from util.cpp:8: /usr/include/boost/program_options/detail/convert.hpp:75:34: note: 'templateclass T std::vectorstd::basic_stringchar boost::program_options::to_internal(const std::vectorT)' declared here, later in the translation unit make[1]: *** [obj/nogui/util.o] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»/src' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: bitcoin Source-Version: 0.6.2.1-1 We believe that the bug you reported is fixed in the latest version of bitcoin, which is due to be installed in the Debian FTP archive: bitcoin_0.6.2.1-1.debian.tar.gz to main/b/bitcoin/bitcoin_0.6.2.1-1.debian.tar.gz bitcoin_0.6.2.1-1.dsc to main/b/bitcoin/bitcoin_0.6.2.1-1.dsc
Bug#668868: marked as done (bitcoind: Assertion failed at startup on mips (big endian))
Your message dated Thu, 10 May 2012 13:17:13 +
with message-id e1sstf3-0002z1...@franck.debian.org
and subject line Bug#668868: fixed in bitcoin 0.6.2.1-1
has caused the Debian Bug report #668868,
regarding bitcoind: Assertion failed at startup on mips (big endian)
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.)
--
668868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: bitcoind
Version: 0.3.24~dfsg-1
Severity: important
Tags: patch
The wheezy bitcoind package is completely unusable on mips (big endian).
When starting bitcoind on mips, it immediately fails with the following error:
bitcoind: main.cpp:1545: bool LoadBlockIndex(bool):
Assertion `block.hashMerkleRoot ==
uint256(0x4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b)'
failed.
New versions apparently fail to build from source, most like due to the
test suite being run at build time.[1]
I have filed a wishlist-severity bug[2] against bitcoind asking for
big-endian support. However, that's unlikely to happen any time soon,
because upstream has said that big-endian simply isn't supported and has
probably never worked[3]. I'm attaching a patch that will prevent bitcoind
from being built on big-endian architectures for now, so that the lack of
big-endian support won't prevent new versions from propagating to testing
on little-endian architectures.
Since bitcoind is currently useless on big-endian architectures, a bug
should[4] be filed against ftp.debian.org once this patch is applied,
asking that the old binaries be removed from the following big-endian
architectures: mips powerpc s390 sparc sparc64 hppa powerpcspe.
Cheers,
- Dwayne
[1]
https://buildd.debian.org/status/fetch.php?pkg=bitcoinarch=mipsver=0.6.0-1stamp=1333140761
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668864
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665922
[4] http://www.debian.org/devel/testing (under Why is it sometimes hard to
get Architecture: all packages into 'testing'?)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: mips
Kernel: Linux 2.6.32-5-4kc-malta
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 bitcoind depends on:
ii libboost-filesystem1.46.1 1.46.1-8
ii libboost-program-options1.46.1 1.46.1-8
ii libboost-system1.46.1 1.46.1-8
ii libboost-thread1.46.1 1.46.1-8
ii libc6 2.13-27
ii libcrypto++95.6.1-5
ii libdb5.1++ 5.1.29-1
ii libgcc1 1:4.7.0-1
ii libglib2.0-02.30.2-6
ii libminiupnpc5 1.5-2
ii libssl1.0.0 1.0.1-4
ii libstdc++6 4.7.0-1
ii zlib1g 1:1.2.6.dfsg-2
bitcoind recommends no packages.
Versions of packages bitcoind suggests:
pn db-util none
pn db4.7-util none
pn db4.8-util none
-- no debconf information
From 15017391424f9c29f4ae7e29729cd784a11d598d Mon Sep 17 00:00:00 2001
From: Dwayne C. Litzenberger dl...@dlitz.net
Date: Sun, 15 Apr 2012 01:19:24 -0400
Subject: [PATCH] Only build little-endian architectures
---
debian/control |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 1c83ea7..1ca3f67 100644
--- a/debian/control
+++ b/debian/control
@@ -22,8 +22,11 @@ Homepage: http://www.bitcoin.org/
Vcs-Git: git://git.debian.org/git/collab-maint/bitcoin
Vcs-Browser: http://git.debian.org/?p=collab-maint/bitcoin.git
+# The Architecture section should list all the little-endian architectures.
+# See http://wiki.debian.org/ArchitectureSpecificsMemo for a list.
Package: bitcoind
-Architecture: any
+Architecture: any-alpha any-amd64 any-armel any-armhf any-i386 any-ia64
+ any-mipsel any-sh4
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: ${cdbs:Suggests}
Description: peer-to-peer network based digital currency - daemon
--
1.7.9.5
---End Message---
---BeginMessage---
Source: bitcoin
Source-Version: 0.6.2.1-1
We believe that the bug you reported is fixed in the latest version of
bitcoin, which is due to be installed in the Debian FTP archive:
bitcoin_0.6.2.1-1.debian.tar.gz
to main/b/bitcoin/bitcoin_0.6.2.1-1.debian.tar.gz
bitcoin_0.6.2.1-1.dsc
to main/b/bitcoin/bitcoin_0.6.2.1-1.dsc
bitcoin_0.6.2.1.orig.tar.gz
to
Bug#650805: marked as done (bitcoin: FTBFS: error in script_PushData: check EvalScript(pushdata2Stack, CScript(pushdata2[0], pushdata2[sizeof(pushdata2)]), CTransaction(), 0, 0) failed)
Your message dated Thu, 10 May 2012 13:17:13 + with message-id e1sstf3-0002z1...@franck.debian.org and subject line Bug#668868: fixed in bitcoin 0.6.2.1-1 has caused the Debian Bug report #668868, regarding bitcoin: FTBFS: error in script_PushData: check EvalScript(pushdata2Stack, CScript(pushdata2[0], pushdata2[sizeof(pushdata2)]), CTransaction(), 0, 0) failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 668868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bitcoin Version: 0.4.0-1 Severity: serious Justification: fails to build from source bitcoin FTBFS on big-endian architectures: | touch debian/stamp-makefile-check | src/test_bitcoin | Running 6 test cases... | test/script_tests.cpp(32): error in script_PushData: check EvalScript(pushdata2Stack, CScript(pushdata2[0], pushdata2[sizeof(pushdata2)]), CTransaction(), 0, 0) failed | test/script_tests.cpp(33): error in script_PushData: check pushdata2Stack == directStack failed | test/script_tests.cpp(36): error in script_PushData: check EvalScript(pushdata4Stack, CScript(pushdata4[0], pushdata4[sizeof(pushdata4)]), CTransaction(), 0, 0) failed | test/script_tests.cpp(37): error in script_PushData: check pushdata4Stack == directStack failed | unknown location(0): fatal error in basic_transaction_tests: std::runtime_error: boost::filesystem::create_directory: No such file or directory: /home/buildd/.bitcoin Full build logs: https://buildd.debian.org/status/fetch.php?pkg=bitcoinarch=mipsver=0.4.0-1stamp=1317782082 https://buildd.debian.org/status/fetch.php?pkg=bitcoinarch=powerpcver=0.4.0-1stamp=1317774642 https://buildd.debian.org/status/fetch.php?pkg=bitcoinarch=s390ver=0.4.0-1stamp=1317775176 https://buildd.debian.org/status/fetch.php?pkg=bitcoinarch=sparcver=0.4.0-1stamp=1317776433 -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: bitcoin Source-Version: 0.6.2.1-1 We believe that the bug you reported is fixed in the latest version of bitcoin, which is due to be installed in the Debian FTP archive: bitcoin_0.6.2.1-1.debian.tar.gz to main/b/bitcoin/bitcoin_0.6.2.1-1.debian.tar.gz bitcoin_0.6.2.1-1.dsc to main/b/bitcoin/bitcoin_0.6.2.1-1.dsc bitcoin_0.6.2.1.orig.tar.gz to main/b/bitcoin/bitcoin_0.6.2.1.orig.tar.gz bitcoind_0.6.2.1-1_amd64.deb to main/b/bitcoin/bitcoind_0.6.2.1-1_amd64.deb 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 668...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard d...@jones.dk (supplier of updated bitcoin 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 May 2012 14:09:46 +0200 Source: bitcoin Binary: bitcoind Architecture: source amd64 Version: 0.6.2.1-1 Distribution: unstable Urgency: low Maintainer: Jonas Smedegaard d...@jones.dk Changed-By: Jonas Smedegaard d...@jones.dk Description: bitcoind - peer-to-peer network based digital currency - daemon Closes: 667114 668864 668868 Changes: bitcoin (0.6.2.1-1) unstable; urgency=low . * New upstream release. . * Add -fpermissive to CXXFLAGS to work around build failure with gcc 4.7. Closes: bug#667114. Thanks to Matthias Klose. * Only build on little-endian architectures: Upstream code does not support big-endian. Closes: bug#668868, #668864. Thanks to Dwayne C. Litzenberger. Checksums-Sha1: a3793d91e0a0e607ebc1975ec38947a15c4d 2384 bitcoin_0.6.2.1-1.dsc 50cb50927d745e9c2f295a4e39ae78aa2f96483a 1359499 bitcoin_0.6.2.1.orig.tar.gz 25085f585bd44a686383b1c75f5eb0639275d390 22070 bitcoin_0.6.2.1-1.debian.tar.gz 2dbaec61a2119910db692622734c5a1055c9e187 597980 bitcoind_0.6.2.1-1_amd64.deb Checksums-Sha256: 9d825b021d9e278ee93e388ba645e3d3191f5b83167b915b0466c8f6a9af094f 2384 bitcoin_0.6.2.1-1.dsc 2dfc6c47dd19b386c5308eb3c61e7459fbc918e7e863328b9bc096810f28bc46 1359499 bitcoin_0.6.2.1.orig.tar.gz 796fcb1cc0357296005d433c7de0f5f006811ba73c9230954739d7e320c994f8 22070 bitcoin_0.6.2.1-1.debian.tar.gz 6bee445378920373c2f01400d6b80c82c4d8a5b492eb8ab05450ca42346e9aac 597980 bitcoind_0.6.2.1-1_amd64.deb Files: 763f4ff3f8e407b811b9c8ad71f4969c 2384 utils optional
Bug#670678: marked as done (node-expat: FTBFS on ARM: tests time out)
Your message dated Thu, 10 May 2012 13:19:58 +
with message-id e1ssthi-0003pl...@franck.debian.org
and subject line Bug#670678: fixed in node-expat 1.5.0-2
has caused the Debian Bug report #670678,
regarding node-expat: FTBFS on ARM: tests time out
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.)
--
670678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: node-expat
Version: 1.5.0-1
Severity: serious
Justification: fails to build from source
Builds of node-expat on armel and armhf have both been failing with
test suite timeouts:
NODE_PATH=/.../node-expat-1.5.0/debian/node-node-expat//usr/lib/nodejs node
test.js
timers.js:96
if (!process.listeners('uncaughtException').length) throw e;
^
mRuntime within maximum expected timem
at [object Object].anonymous (/.../node-expat-1.5.0/test.js:243:14)
at [object Object].anonymous (events.js:67:17)
at [object Object].emit (/usr/lib/nodejs/vows.js:236:24)
at [object Object].emit (/.../node-expat-1.5.0/lib/node-expat.js:18:12)
at [object Object].resume (/.../node-expat-1.5.0/lib/node-expat.js:41:24)
at Object._onTimeout (/.../node-expat-1.5.0/test.js:226:6)
at Timer.ontimeout (timers.js:94:19)
make: *** [build/node-node-expat] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
Could you please take a look?
Thanks!
---End Message---
---BeginMessage---
Source: node-expat
Source-Version: 1.5.0-2
We believe that the bug you reported is fixed in the latest version of
node-expat, which is due to be installed in the Debian FTP archive:
node-expat_1.5.0-2.debian.tar.gz
to main/n/node-expat/node-expat_1.5.0-2.debian.tar.gz
node-expat_1.5.0-2.dsc
to main/n/node-expat/node-expat_1.5.0-2.dsc
node-node-expat_1.5.0-2_amd64.deb
to main/n/node-expat/node-node-expat_1.5.0-2_amd64.deb
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 670...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard d...@jones.dk (supplier of updated node-expat 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 10 May 2012 14:42:55 +0200
Source: node-expat
Binary: node-node-expat
Architecture: source amd64
Version: 1.5.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
pkg-javascript-de...@lists.alioth.debian.org
Changed-By: Jonas Smedegaard d...@jones.dk
Description:
node-node-expat - fast XML parser library for Node
Closes: 670678
Changes:
node-expat (1.5.0-2) unstable; urgency=low
.
* Use anonscm.debian.org for Vcs-Browser field.
* Relax timing tolerance of test to avoid failure on slow
architectures.
Closes: bug#670678. Thanks to Aaron M. Ucko.
Checksums-Sha1:
2ee8984aef04e23ac0419f82a957e3fbe24678d3 1996 node-expat_1.5.0-2.dsc
8390da0702df576cf17599ce5fddf0b952fc7628 4396 node-expat_1.5.0-2.debian.tar.gz
455f8113701f0f5cebe880ac3f429771bcb351d3 25966
node-node-expat_1.5.0-2_amd64.deb
Checksums-Sha256:
44c12a606f29a8d10bae49e702fc18c6abe7f32df7cda09b47db286b22e1f260 1996
node-expat_1.5.0-2.dsc
45fada20b9e9816d14aada23bfe57caf1d35e3f9eb14de66bd23bc5a9bac7b35 4396
node-expat_1.5.0-2.debian.tar.gz
c0925abc18b4d24afb529b9b05d5b310bad30dc1e78badbc0f6f67a1198962d2 25966
node-node-expat_1.5.0-2_amd64.deb
Files:
9683343d5de99a827b3b7fd51f841672 1996 web optional node-expat_1.5.0-2.dsc
54f0d4f6588930733797a112bca4bab0 4396 web optional
node-expat_1.5.0-2.debian.tar.gz
0054ee1f22c40c5632cbbe4a32dd4ee2 25966 web optional
node-node-expat_1.5.0-2_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJPq7nPAAoJECx8MUbBoAEhdMcP/joVVLzsw0vReQ5GYu9GyuHb
wXrT62UGu4QlZR5OcFUvA4GFwMmcPsCALqsRUoGKcjJx3sxiDNot2gUt54QAL7Sn
zgqC/PZavIMdq/fvjw5VAf0PE4LgjRGkmT+E3w0WHnfVbra6XHmQRGQni82cD+ar
Qv/8Xez0slVFKpRZo3UFHNSoGPzJ63ix1yfgLaM2iCU8df891JGe4kOePYtOYsXF
TZghy7Q7ESkLtUGJ8yb8dtDnWvtWlFnng+vMKP+GVkG6mHqX549a5dk6mqAi210l
+ynqXn3VeQYeHHUgD3wQoCh+wU1PeOdEVg8IBHWpI71xYxnTodlpUnOmjk9OOdxP
oW/rSwRFpDZw8Vfg061+Gw8pbZGSRW1YfPqCUPQDb/MKx9lpGSJnSktEmZJ5Qok5
Bug#672357: [Pkg-virtualbox-devel] Bug#672357: closed by Michael Meskes mes...@debian.org (Re: Bug#672357: virtualbox-ose-dkms: fails to build kernel module - I found a solution)
On Thu, May 10, 2012 at 02:08:14PM +0200, Tobiasz Karoń wrote: In fact - that is what worked for me. I tried re-installing virtualbox-ose-dkms several times to no effect. But did you remove if first? All the time I've seen this problem, a complete removal and a subsequent re-installation of virtualbox-ose-dkms solved it. I have no idea what causes the problem, I now only what fixed it for me. Again, I strongly believe that installing virtualbox-ose-source did not change anything, this is just coincidence. Do you know what is the cause? Do you consider this problem solved? The cause is outside the virtualbox packages and thus, yes, I consider it solved for virtualbox. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667221: marked as done (kdesvn: ftbfs with GCC-4.7)
Your message dated Thu, 10 May 2012 13:49:40 + with message-id e1sstks-0006ou...@franck.debian.org and subject line Bug#667221: fixed in kdesvn 1.5.5-4.1 has caused the Debian Bug report #667221, regarding kdesvn: ftbfs with GCC-4.7 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.) -- 667221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kdesvn Version: 1.5.5-4 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. maintreewidget.cpp:1292:38: error: 'chdir' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/kdesvn_1.5.5-4_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] /«PKGBUILDDIR»/src/svnfrontend/blamedisplay_impl.cpp: In member function 'virtual void BlameDisplay_impl::setContent(const QString, const AnnotatedFile)': /«PKGBUILDDIR»/src/svnfrontend/blamedisplay_impl.cpp:236:12: warning: variable '_bgColor' set but not used [-Wunused-but-set-variable] /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 56 [ 83%] Building CXX object src/svnfrontend/CMakeFiles/svnfrontend.dir/threadcontextlistenerdata.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/svnfrontend /usr/bin/c++ -D_BSD_SOURCE -DKDE_DEFAULT_DEBUG_AREA=9510 -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -fexceptions -O2 -g -DNDEBUG -DQT_NO_DEBUG -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/svnfrontend -I/«PKGBUILDDIR»/src/svnfrontend -I/«PKGBUILDDIR»/src/svnqt -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR»/src -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src/svnfrontend/fronthelpers -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/svnqt -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/ksvnwidgets -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/ qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/usr/include/apr-1.0 -I/usr/include/subversion-1 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -fPIC -o CMakeFiles/svnfrontend.dir/threadcontextlistenerdata.o -c /«PKGBUILDDIR»/src/svnfrontend/threadcontextlistenerdata.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles [ 83%] Building CXX object src/svnfrontend/CMakeFiles/svnfrontend.dir/fillcachethread.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/svnfrontend /usr/bin/c++ -D_BSD_SOURCE -DKDE_DEFAULT_DEBUG_AREA=9510 -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -fexceptions -O2 -g -DNDEBUG -DQT_NO_DEBUG -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/svnfrontend -I/«PKGBUILDDIR»/src/svnfrontend -I/«PKGBUILDDIR»/src/svnqt -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR»/src -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src/svnfrontend/fronthelpers -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/svnqt -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/ksvnwidgets -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools
Bug#669949: mouse, keyboard sound not working in -24
I'm almost on the way to work (7am my time)...I'll copy the -22.1 bootlog this evening then upgrade to -24 again--copy the bootlog--and then try the exit0...I reboot after every major change to the main system..so the devices do not show up afterwards. Do you want my system specs also? On Wed, May 09, 2012 at 06:52:52PM -0700, Dean Loros wrote: It looks like this is not fixed in my case. I yes'd all developer changes to Initscripts (thought that might fix things), but I still have no keyboard or mouse--using both as USB3 devices. I can unplug replug them--then both will work normally. What logs do you need to see this? I also have downgraded before this to 22.1 have had normal functions...I don't know if I can downgrade easily with the current version. Only things that seem to be affected are the keyboard mouse. This is odd. It's definitely fixed the problem for myself, which was due to cleaning /run and removing some of the udev state. If you add an exit 0 to the top of /lib/init/bootclean.sh (to disable cleaning), does this prevent the problem? Did you reboot after installing -24? (Since this is a problem which is created at boot) It would be useful to have a copy of the boot logs for 22.1 and 24 so that we can look at any obvious differences. Thanks, Roger -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#672358: dbus: some machines do not shutdown properly and do not do poweroff
(Please reply to the bug, not to me - if you just reply to me, other maintainers can't see your reply. Quoting full-text here for the benefit of other maintainers.) On 10/05/12 14:22, Jürgen Kaiser wrote: Am Donnerstag, 10. Mai 2012, 13:48:05 schrieben Sie: As far as I understand it, what dbus does (no explicit stop directives) is meant to work [...] For run level 1 by my personal opinion dbus should be stopped, because I see this run level as pour maintance mode and I need no dbus services in this mode, may be I am wrong here, but this question has a more philosophic nature. /etc/init.d/killprocs is run in runlevel 1, and should kill dbus, as far as I can see; so we shouldn't need to run the script. This might mean that something has changed in dbus and/or init more recently, such that the way init kills it no longer works? (The same dbus version worked fine last time I rebooted my laptop, though.) May be their is a change but that is beyond my time to check. I would also think of changing in basic kernel features called by halt. My squeeze on the notebook I talking about runs until this mature update with kernel 2.6.38. Alternatively: what upgrade path did you use on the machine where init stalls waiting for dbus? I have made bad experience with simple updating a debian system from an old to new version. So generally I do a complete new install process. OK, so you're essentially using a new installation on both machines, and in particular, the /etc on both machines is from wheezy and has not been upgraded from squeeze? -Update from squeeze to wheezy has been done by clearly fresh installation on a fresh partition with debootstrap, partition cleaned before with mkfs.ext4. then manually added packages as I need. - Preparation has been done on desktop system and than, after system is working correct, this installation has been copied using rsync excluding nonstatic dirs like sys, proc, tmp, etc to the notebook and notebook specific changes are added. For Information: I have a lot of machines to care for, so I handle it over years in this way: - trying to have similar hardware (if possible) in processor type and graphic cards to minimalize special configurations - setup debian version on a single machine prepare it - copy this installation to all other machines and make miniaml modifications like hostname, fstab, etc - from this point on all machines run aptitude dist-upgrade periodically avoiding mixing of debian versions Similarly, did you say you had a similar machine where init *does* kill dbus properly without any intervention from you? If you do, what version of Debian did you originally install on that machine, and what upgrade path did you use there? See last remark for debian installation. The desktop system on which I have prepared the system do a shutdown. The notebook system on which prepared system is copied to from desktop system do not shutdown without stopping explicitely dbus. Right, so either the problem is related to one of the changes you made for the notebook, or it's hardware-specific. One remark about my expirience with linux on notebooks: The acpi bios is very often buggy, there is no help from manufactorer and we (running linux) have to live with this situation or do hard work in reenginiering. As I see kernel devoloper do here a hard work and fix a lot. Maybe the whole thing is a bios bug on my notebook invoked by dbus??? I'd be interested to hear what happens with the packaged Debian kernel (linux-image-3.2.0-2-amd64 from unstable and/or linux-image-3.3.0-trunk-amd64 from experimental), if those can boot on your hardware. Sorry but I have spend now some days with get the notebook run with wheezy. I have not enough time to test some other debian kernels. I have send my bug report hoping I could help a little bit to people having similar problems. I see people on Ubuntu 12.04 have problems shutting down notebooks, then add INIT_HALT=POWEROFF to /etc/default/halt and after this modification they have success. It tried it and shutdown process succeded. But I think that this solution is not the right way, because halt then do not a poweroff so different hardware could be enabled after shutdown which is not a good solution if a notebook runs on battery. What is in /etc/default/halt on each of your machines? Are you absolutely sure that adding/removing stop symlinks for dbus, and not changing anything else, made the notebook power off / not power off? Might you have changed something else at the same time, like /etc/default/halt or the difference between shutdown -h and shutdown -hP? (I wouldn't be surprised if halt vs. poweroff matters on certain notebook hardware, but that shouldn't be anything to do with dbus-daemon, which is fundamentally just a message-passing daemon with a Unix socket - it doesn't do anything to hardware-related itself.) S -- To UNSUBSCRIBE,
Bug#672381: CVE-2012-0862
Package: xinetd Severity: grave Tags: security Please see https://bugzilla.redhat.com/show_bug.cgi?id=790940 for details and a proposed patch. 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#671984: [Pkg-haskell-maintainers] Bug#671984: bluetile: FTBFS: build-dependency not installable: libghc-glade-dev
On 08/05/12 at 23:44 +0200, Joachim Breitner wrote: Hi Lucas, I very much appreciate these FTBFS bug reports. Iâm not so sure about FTBFS for unsatisfiable build-dependencies, as these are more often than not a bug in a different package, or just a temporary problem due to rebuilds. My rule of thumb is that I do not file bugs when the same problem appears in many packages, since this is likely not a bug in the independent packages. I know next to nothing about haskell packages, so i might be mistaken here. Also sometimes i'm lazy and i assume that filing a bug against a package will get attention, and someone will investigate and reassign to the correct package. a suggestion: is there a chance that your tool can also close these bugs once the problem has disappeared? then these temporary problems do not require additional work on the maintainer side? I check for obsolete bugs (bugs I filed that are still open while the package now builds) from time to time, but it's a manual process. Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667200: marked as done (hexxagon: ftbfs with GCC-4.7)
Your message dated Thu, 10 May 2012 14:51:06 + with message-id e1ssuhu-0008pn...@franck.debian.org and subject line Bug#667200: fixed in hexxagon 1.0pl1-3.1 has caused the Debian Bug report #667200, regarding hexxagon: ftbfs with GCC-4.7 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.) -- 667200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: hexxagon Version: 1.0pl1-3 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. gtkhexxagonboard.cpp:141:17: error: redeclaration of 'int x' The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/hexxagon_1.0pl1-3_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] else rm -f .deps/gtkhexxagonboardedit.Tpo; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src -pthread -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atk-1.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/cairomm-1.0 -I/usr/lib/cairomm-1.0/include -DIMAGE_INSTALL_DIR=\/usr/share/hexxagon/images/\ -O2 -MT gtkaboutwindow.o -MD -MP -MF .deps/gtkaboutwindow. Tpo \ -c -o gtkaboutwindow.o `test -f 'gtkaboutwindow.cpp' || echo './'`gtkaboutwindow.cpp; \ then mv -f .deps/gtkaboutwindow.Tpo .deps/gtkaboutwindow.Po; \ else rm -f .deps/gtkaboutwindow.Tpo; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src -pthread -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atk-1.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/cairomm-1.0 -I/usr/lib/cairomm-1.0/include -DIMAGE_INSTALL_DIR=\/usr/share/hexxagon/images/\ -O2 -MT gamemodel.o -MD -MP -MF .deps/gamemodel.Tpo \ -c -o gamemodel.o `test -f 'gamemodel.cpp' || echo './'`gamemodel.cpp; \ then mv -f .deps/gamemodel.Tpo .deps/gamemodel.Po; \ else rm -f .deps/gamemodel.Tpo; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src -pthread -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atk-1.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/sigc++-2.0
Bug#667233: marked as done (kvpnc: ftbfs with GCC-4.7)
Your message dated Thu, 10 May 2012 14:52:47 + with message-id e1ssujx-6b...@franck.debian.org and subject line Bug#667233: fixed in kvpnc 0.9.6a-2.1 has caused the Debian Bug report #667233, regarding kvpnc: ftbfs with GCC-4.7 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.) -- 667233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kvpnc Version: 0.9.6a-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. kvpnc.cpp:4809:35: error: 'usleep' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/kvpnc_0.9.6a-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::ipsecStarted(int, QProcess::ExitStatus)': /«PKGBUILDDIR»/src/kvpnc.cpp:18979:12: error: 'sleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::startStopIpsec(bool, bool)': /«PKGBUILDDIR»/src/kvpnc.cpp:19120:23: error: 'usleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::start_ipsec_initiate()': /«PKGBUILDDIR»/src/kvpnc.cpp:19160:12: error: 'sleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::doAddRemoveVirtualIp(QString)': /«PKGBUILDDIR»/src/kvpnc.cpp:19337:16: error: 'usleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::startStopOpenl2tp(bool, bool)': /«PKGBUILDDIR»/src/kvpnc.cpp:19405:19: error: 'usleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp:19430:23: error: 'usleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::executeCommandAfterConnect()': /«PKGBUILDDIR»/src/kvpnc.cpp:19675:15: error: 'usleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::start_l2tpd()': /«PKGBUILDDIR»/src/kvpnc.cpp:21624:20: error: 'sleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp:21711:16: error: 'sleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::checkL2tpPppUp()': /«PKGBUILDDIR»/src/kvpnc.cpp:21804:29: error: 'sleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp:21832:28: error: 'sleep' was not declared in this scope /«PKGBUILDDIR»/src/kvpnc.cpp: In member function 'void KVpnc::waitForFinished(QProcess*, int, QString)': /«PKGBUILDDIR»/src/kvpnc.cpp:22046:21: error: 'usleep' was not declared in this scope make[3]: *** [src/CMakeFiles/kvpnc_bin.dir/kvpnc.o] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make[2]: *** [src/CMakeFiles/kvpnc_bin.dir/all] Error 2 make[1]: *** [all] Error 2 dh_auto_build: make -j1 returned exit code 2 make[2]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make[1]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: kvpnc Source-Version: 0.9.6a-2.1 We believe that the bug you reported is fixed in the latest version of kvpnc, which is due to be installed in the Debian FTP archive: kvpnc-data_0.9.6a-2.1_all.deb to main/k/kvpnc/kvpnc-data_0.9.6a-2.1_all.deb kvpnc-dbg_0.9.6a-2.1_amd64.deb to main/k/kvpnc/kvpnc-dbg_0.9.6a-2.1_amd64.deb kvpnc_0.9.6a-2.1.debian.tar.gz to main/k/kvpnc/kvpnc_0.9.6a-2.1.debian.tar.gz kvpnc_0.9.6a-2.1.dsc to main/k/kvpnc/kvpnc_0.9.6a-2.1.dsc kvpnc_0.9.6a-2.1_amd64.deb to main/k/kvpnc/kvpnc_0.9.6a-2.1_amd64.deb 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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor
Bug#650060: snort: FTBFS with multiarch libmysqlclient-dev (now [...]
Hi there, Javier Fernández-Sanguino Peña j...@computer.org wrote: It does not seem to be the same bug (or the patch provided does not apply and fix this bug). The version of libmysqlclient-dev currently available in unstable (version 5.1.62-1) does not provide the '--variable=pkglibdir' option (i.e. it is not recognised for mysql_config). FYI, Version in unstable is now 5.5.23-2, which is multiarch. Best regards, -- Marcos Marado -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672335: (no subject)
retitle FTBFS with g++ 4.7
thanks
More new warnings in g++ 4.7, fixes are attached.
Regards,
Adrian
From f14a272b49a6f4b5c7a68b20c93c0894c267ec0c Mon Sep 17 00:00:00 2001
From: Adrian Lang m...@adrianlang.de
Date: Thu, 10 May 2012 16:58:16 +0200
Subject: [PATCH] Fix build with g++ 4.7
---
src/generic/apt/aptitude_resolver.h |2 ++
src/generic/problemresolver/incremental_expression.h |2 +-
src/generic/util/dynamic_list_collection.h |6 +++---
src/generic/util/dynamic_list_impl.h |6 +++---
4 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/src/generic/apt/aptitude_resolver.h b/src/generic/apt/aptitude_resolver.h
index f2fa566..6270d80 100644
--- a/src/generic/apt/aptitude_resolver.h
+++ b/src/generic/apt/aptitude_resolver.h
@@ -450,6 +450,8 @@ public:
aptitudeDepCache *cache,
pkgPolicy *_policy);
+ virtual ~aptitude_resolver() {}
+
/** \brief Return \b true if the given version will break a hold or
* install a forbidden version.
*/
diff --git a/src/generic/problemresolver/incremental_expression.h b/src/generic/problemresolver/incremental_expression.h
index da23520..81334ae 100644
--- a/src/generic/problemresolver/incremental_expression.h
+++ b/src/generic/problemresolver/incremental_expression.h
@@ -533,7 +533,7 @@ public:
{
T old_value = value;
value = new_value;
- signal_value_changed(old_value, new_value);
+ this-signal_value_changed(old_value, new_value);
}
}
diff --git a/src/generic/util/dynamic_list_collection.h b/src/generic/util/dynamic_list_collection.h
index 5539369..50ecc48 100644
--- a/src/generic/util/dynamic_list_collection.h
+++ b/src/generic/util/dynamic_list_collection.h
@@ -254,7 +254,7 @@ namespace aptitude
const std::size_t insert_idx = insert_location - concrete_view.begin();
concrete_view.insert(insert_location, cell(list, idx, value));
- signal_inserted(value, insert_idx);
+ this-signal_inserted(value, insert_idx);
}
templatetypename T
@@ -316,7 +316,7 @@ namespace aptitude
// removal BEFORE removing it!
const std::size_t remove_idx = remove_location - concrete_view.begin();
concrete_view.erase(remove_location);
- signal_removed(value, remove_idx);
+ this-signal_removed(value, remove_idx);
}
}
@@ -412,7 +412,7 @@ namespace aptitude
relocate_target = to_location;
concrete_view.relocate(relocate_target, from_location);
- signal_moved(value, from_idx, to_idx);
+ this-signal_moved(value, from_idx, to_idx);
}
templatetypename T
diff --git a/src/generic/util/dynamic_list_impl.h b/src/generic/util/dynamic_list_impl.h
index 6b0b8bc..90edc0f 100644
--- a/src/generic/util/dynamic_list_impl.h
+++ b/src/generic/util/dynamic_list_impl.h
@@ -91,7 +91,7 @@ namespace aptitude
void dynamic_list_implT::insert(const T t, std::size_t position)
{
entries.insert(entries.begin() + position, t);
- signal_inserted(t, position);
+ this-signal_inserted(t, position);
}
templatetypename T
@@ -99,7 +99,7 @@ namespace aptitude
{
T val = entries[position];
entries.erase(entries.begin() + position);
- signal_removed(val, position);
+ this-signal_removed(val, position);
}
templatetypename T
@@ -129,7 +129,7 @@ namespace aptitude
const std::size_t idx_to_delete = to from ? from + 1 : from;
entries.erase(entries.begin() + idx_to_delete);
- signal_moved(val, from, to);
+ this-signal_moved(val, from, to);
}
}
}
--
1.7.10
signature.asc
Description: PGP signature
Bug#672348: texlive-xetex: Missing file t3enc.def
severity 672348 normal
tags 672348 + pending
thanks
On Do, 10 Mai 2012, Bastian Blank wrote:
Severity: grave
Let us check the definition of grave because I have some time to spare,
not to be taken too serious, though, I am under the influence of a very
good Sake:
makes the package in question unusable or mostly so,
or causes data loss,
or introduces a security hole allowing access to the accounts of users
who use the package.
obviously point 2 and 3 does not apply. Now let us look at the usabillity.
As xunicode is included in almost any xelatex file, this needs a depends.
Interesting, not in mine. Furthermore, checking how many of the files
in texlive-xetex actually use xunicode:
./tex/xelatex/fontwrap/fontwrap.sty:\usepackage{xunicode}
./tex/xelatex/philokalia/philokalia.sty:\RequirePackage{xunicode}
./tex/xelatex/fontbook/fontbook.sty:\RequirePackage{xunicode}
./tex/xelatex/xecyr/xecyr.sty:\RequirePackage{xunicode}
While the not using it are:
realscripts.sty, xltxtra.sty, arabxetex.sty, unisugar.sty,
mathspec.sty, xecolor.sty, xeCJK.sty, fixlatvian.sty,
xepersian.sty, xeindex.sty
H.
unusable or mostly so
...
no, adjusting severity.
Good night.
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
WIVENHOE (n.)
The cry of alacrity with which a sprightly eighty-year-old breaks the
ice on the lake when going for a swim on Christmas Eve.
--- Douglas Adams, The Meaning of Liff
--
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#672348: texlive-xetex: Missing file t3enc.def
Processing commands for cont...@bugs.debian.org: severity 672348 normal Bug #672348 [texlive-xetex] texlive-xetex: Missing file t3enc.def Severity set to 'normal' from 'grave' tags 672348 + pending Bug #672348 [texlive-xetex] texlive-xetex: Missing file t3enc.def Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 672348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672348 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#672056: xf86-video-glamo: FTBFS: ../../src/glamo-driver.c:289:7: error: assignment discards 'const' qualifier from pointer target type [-Werror]
On 10.05.2012 07:55, Gilles Filippini wrote:
Matthias Klose a écrit , Le 10/05/2012 02:50:
tags 672056 + patch
thanks
uploaded to delayed/2, part of the xorg transition.
Where is the patch?
sorry, now attached
diff -Nru xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/changelog
xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/changelog
--- xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/changelog
2011-06-04 23:15:14.0 +0200
+++ xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/changelog
2012-05-10 02:20:10.0 +0200
@@ -1,3 +1,10 @@
+xf86-video-glamo (0.0.0+20100630.git16af3c00-3.1) unstable; urgency=low
+
+ * Non maintainer upload.
+ * Fix build failure with GCC 4.7. Closes: #672056.
+
+ -- Matthias Klose d...@debian.org Thu, 10 May 2012 00:18:15 +
+
xf86-video-glamo (0.0.0+20100630.git16af3c00-3) unstable; urgency=low
* Source format: 3.0 (quilt)
diff -Nru
xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/ftbfs-gcc-4.7.diff
xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/ftbfs-gcc-4.7.diff
---
xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/ftbfs-gcc-4.7.diff
1970-01-01 01:00:00.0 +0100
+++
xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/ftbfs-gcc-4.7.diff
2012-05-10 02:46:14.0 +0200
@@ -0,0 +1,22 @@
+Index: xf86-video-glamo-0.0.0+20100630.git16af3c00/src/glamo-driver.c
+===
+--- xf86-video-glamo-0.0.0+20100630.git16af3c00.orig/src/glamo-driver.c
2012-05-10 00:44:53.528657805 +
xf86-video-glamo-0.0.0+20100630.git16af3c00/src/glamo-driver.c
2012-05-10 00:46:09.364659518 +
+@@ -286,7 +286,7 @@
+
+ for (i = 0; i numDevSections; i++) {
+
+- dev = xf86FindOptionValue(devSections[i]-options, Device);
++ dev = (char *) xf86FindOptionValue(devSections[i]-options,
Device);
+ if (fbdevHWProbe(NULL, dev, NULL)) {
+ int entity;
+ pScrn = NULL;
+@@ -430,7 +430,7 @@
+
+ pGlamo-pEnt = xf86GetEntityInfo(pScrn-entityList[0]);
+
+-fb_device = xf86FindOptionValue(pGlamo-pEnt-device-options, Device);
++fb_device = (char *) xf86FindOptionValue(pGlamo-pEnt-device-options,
Device);
+
+ /* open device */
+ if (!fbdevHWInit(pScrn, NULL, fb_device))
diff -Nru xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/series
xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/series
--- xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/series
2011-06-04 23:14:43.0 +0200
+++ xf86-video-glamo-0.0.0+20100630.git16af3c00/debian/patches/series
2012-05-10 02:45:09.0 +0200
@@ -1 +1,2 @@
03-force-kms-off-v2.patch
+ftbfs-gcc-4.7.diff
Bug#667205: marked as done (icedove: ftbfs with GCC-4.7)
Your message dated Thu, 10 May 2012 15:22:56 + with message-id e1ssvci-0004i8...@franck.debian.org and subject line Bug#667205: fixed in icedove 10.0.4-1 has caused the Debian Bug report #667205, regarding icedove: ftbfs with GCC-4.7 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.) -- 667205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: icedove Version: 10.0.3-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. file_util.cc:228:35: error: 'ftruncate' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/icedove_10.0.3-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] file_path.cc c++ -o file_path.o -c -I../../dist/stl_wrappers -I../../dist/system_wrappers -include ../../config/gcc_hidden.h -DMOZILLA_INTERNAL_API -D_IMPL_NS_COM -DEXPORT_XPT_API -DEXPORT_XPTC_API -D_IMPL_NS_GFX -D_IMPL_NS_WIDGET -DIMPL_XREAPI -DIMPL_NS_NET -DIMPL_THEBES -DMOZ_THUNDERBIRD=1 -DOSTYPE=\Linux2.6\ -DOSARCH=Linux -DEXCLUDE_SKIA_DEPENDENCIES -DOS_LINUX=1 -DOS_POSIX=1 -I../../dist -I../../ipc/chromium/src -I../../ipc/glue -I../../ipc/ipdl/_ipdlheaders -I. -I. -I../../dist/include -I../../dist/include/nsprpub -I/usr/include/nspr -I/usr/include/nss -I/usr/include -I/usr/include -fPIC -D_FORTIFY_SOURCE=2 -fno-rtti -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -Wno-long-long -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -fno-exceptions -fno-strict-aliasing -pthread -ffunction-sections -f data-sections -pipe -DNDEBUG -DTRIMMED -g -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gtk-unix-print-2.0 -Os -freorder-blocks -fomit-frame-pointer -D_FORTIFY_SOURCE=2 -DMOZILLA_CLIENT -include ../../mozilla-config.h -MD -MF .deps/file_path.pp /«PKGBUILDDIR»/mozilla/ipc/chromium/src/base/file_path.cc In file included from ../../ipc/chromium/src/base/basictypes.h:389:0, from ../../ipc/chromium/src/base/file_path.h:70, from /«PKGBUILDDIR»/mozilla/ipc/chromium/src/base/file_path.cc:7: ../../dist/include/nscore.h:407:2: warning: #warning icedove SDK was configured with 2-byte wchar_t, but now building without [-Wcpp] file_util.cc c++ -o file_util.o -c -I../../dist/stl_wrappers -I../../dist/system_wrappers -include ../../config/gcc_hidden.h -DMOZILLA_INTERNAL_API -D_IMPL_NS_COM -DEXPORT_XPT_API -DEXPORT_XPTC_API -D_IMPL_NS_GFX -D_IMPL_NS_WIDGET -DIMPL_XREAPI -DIMPL_NS_NET -DIMPL_THEBES -DMOZ_THUNDERBIRD=1 -DOSTYPE=\Linux2.6\ -DOSARCH=Linux -DEXCLUDE_SKIA_DEPENDENCIES -DOS_LINUX=1 -DOS_POSIX=1 -I../../dist -I../../ipc/chromium/src -I../../ipc/glue -I../../ipc/ipdl/_ipdlheaders -I. -I. -I../../dist/include -I../../dist/include/nsprpub -I/usr/include/nspr -I/usr/include/nss -I/usr/include -I/usr/include -fPIC -D_FORTIFY_SOURCE=2 -fno-rtti -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -Wno-long-long -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -fno-exceptions -fno-strict-aliasing -pthread -ffunction-sections -f data-sections -pipe -DNDEBUG -DTRIMMED -g -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0
Bug#667129: cb2bib: ftbfs with GCC-4.7
tags 667129 + pending patch thanks Hi Filippo I have updated cb2bib with the patch from Cyril Brulebois in the debian-science git repository. It fixes a RC bugs (FTBFS with gcc 4.7). Regards, Salvatore signature.asc Description: Digital signature
Processed: Re: Bug#667129: cb2bib: ftbfs with GCC-4.7
Processing commands for cont...@bugs.debian.org: tags 667129 + pending patch Bug #667129 [cb2bib] cb2bib: ftbfs with GCC-4.7 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 667129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667129 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: severity of 653119 is serious
Processing commands for cont...@bugs.debian.org: # makes lxappearance-obconf FTBFS on *amd64 severity 653119 serious Bug #653119 [openbox-dev] openbox-dev: Wrong .so symlink Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 653119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653119 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#666367: marked as done (eterm: FTBFS: make: *** debian/build: No such file or directory. Stop.)
Your message dated Thu, 10 May 2012 16:03:05 + with message-id e1ssvpz-0006wq...@franck.debian.org and subject line Bug#666367: fixed in eterm 0.9.5-5 has caused the Debian Bug report #666367, regarding eterm: FTBFS: make: *** debian/build: No such file or directory. Stop. 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.) -- 666367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: eterm Version: 0.9.5-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch /usr/bin/make -f debian/rules -C debian/build install USE_BUILD_DIR=TRUE make: *** debian/build: No such file or directory. Stop. make: *** [install] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/eterm_0.9.5-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: eterm Source-Version: 0.9.5-5 We believe that the bug you reported is fixed in the latest version of eterm, which is due to be installed in the Debian FTP archive: eterm_0.9.5-5.diff.gz to main/e/eterm/eterm_0.9.5-5.diff.gz eterm_0.9.5-5.dsc to main/e/eterm/eterm_0.9.5-5.dsc eterm_0.9.5-5_amd64.deb to main/e/eterm/eterm_0.9.5-5_amd64.deb 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 666...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca e...@debian.org (supplier of updated eterm 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 10 May 2012 15:30:12 + Source: eterm Binary: eterm Architecture: source amd64 Version: 0.9.5-5 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Emanuele Rocca e...@debian.org Description: eterm - Enlightened Terminal Emulator Closes: 666367 Changes: eterm (0.9.5-5) unstable; urgency=low . * QA upload. * Provide build-arch target in debian/builddir.mk to fix FTBFS. (Closes: #666367). Checksums-Sha1: 084a3c27b41da3727b2444627847bd902f246f0c 1166 eterm_0.9.5-5.dsc 9e206588aebb044c89c64b3660d575813388373a 11692 eterm_0.9.5-5.diff.gz b31643500dc80712817c670a7a09ffdd3aad03a2 463338 eterm_0.9.5-5_amd64.deb Checksums-Sha256: 487cfc999df731c59253f5b06375dc766abd7a3b10b1884b945bdbd1b2802e71 1166 eterm_0.9.5-5.dsc 049138a2068fa20adcb7ded49521bc6fa9aee9dc3987eb6bf3d4cc0c49e72dc3 11692 eterm_0.9.5-5.diff.gz 335727bdf3ee44f0612b3e88eea40f9eb7a880696cacf2584cb0cdaef97f1b27 463338 eterm_0.9.5-5_amd64.deb Files: 96defcc53a73f15b0e0b747f7b481bf5 1166 x11 optional eterm_0.9.5-5.dsc 44daec3ad488f7287d899c5c8f3e09de 11692 x11 optional eterm_0.9.5-5.diff.gz c1e930ea41cd376c557a30c7fd1416d7 463338 x11 optional eterm_0.9.5-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk+r5PQACgkQC6DuA+rxm2ADywCfbV2SGW2tHBEtl+zPZMJEKCjA TGoAnjCiQ/kxaW3P9nH06fwcyix2fMK0 =y779 -END PGP SIGNATURE- ---End Message---
Processed: Re: Bug#637394: w3-dtd-mathml: /etc/xml/catalog doesn't contain a reference to the MathML DTD
Processing commands for cont...@bugs.debian.org: found 637394 2.0.0.0-3 Bug #637394 [w3-dtd-mathml] w3-dtd-mathml: /etc/xml/catalog doesn't contain a reference to the MathML DTD Marked as found in versions w3-dtd-mathml/2.0.0.0-3. severity 637394 serious Bug #637394 [w3-dtd-mathml] w3-dtd-mathml: /etc/xml/catalog doesn't contain a reference to the MathML DTD Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 637394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637394 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#672353: IPv6 does not work
On Thu, 2012-05-10 at 14:35 +0200, Bastian Blank wrote: On Thu, May 10, 2012 at 11:59:10AM +0200, Stéphane Glondu wrote: ** Version: Linux version 2.6.32-5-kirkwood (Debian 2.6.32-39squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Thu Jan 12 01:10:21 UTC 2012 This is not -44. We expect users to reboot after an upgrade. Bastian Possibly Stéphane has rebooted but flash-kernel didn't run (#656877). Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Bug#635923: ghdl: FTBFS: features.h:323:26: error: bits/predefs.h: No such file or directory
tags 635923 patch thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: ghdl: FTBFS: features.h:323:26: error: bits/predefs.h: No such file or directory
Processing commands for cont...@bugs.debian.org: tags 635923 patch Bug #635923 [src:ghdl] ghdl: FTBFS: features.h:323:26: error: bits/predefs.h: No such file or directory Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 635923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635923 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#669553: criticalmass: FTBFS: configure: error: libpng is needed
tags 669553 patch thanks
Processed: criticalmass: FTBFS: configure: error: libpng is needed
Processing commands for cont...@bugs.debian.org: tags 669553 patch Bug #669553 [src:criticalmass] criticalmass: FTBFS: configure: error: libpng is needed Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 669553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669553 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#667409: marked as done (vdr-plugin-live: ftbfs with GCC-4.7)
Your message dated Thu, 10 May 2012 18:36:45 +0200 with message-id 4fabee9d.8040...@debian.org and subject line Re: vdr-plugin-live: ftbfs with GCC-4.7 has caused the Debian Bug report #667409, regarding vdr-plugin-live: ftbfs with GCC-4.7 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.) -- 667409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: vdr-plugin-live Version: 0.2.0+git20120114-3 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. smartptr.h:252:13: error: 'destroy' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/vdr-plugin-live_0.2.0+git20120114-3_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] menu.ecpp:21:3: required from here /usr/include/cxxtools/smartptr.h:252:13: error: 'destroy' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] /usr/include/cxxtools/smartptr.h:252:13: note: declarations in dependent base 'cxxtools::DefaultDestroyPolicytnt::Object' are not found by unqualified lookup /usr/include/cxxtools/smartptr.h:252:13: note: use 'this-destroy' instead In file included from /usr/include/tnt/scope.h:35:0, from /usr/include/tnt/ecpp.h:34, from menu.cpp:6: /usr/include/tnt/object.h: In instantiation of 'tnt::PointerObjectdata_type, destroyPolicy::~PointerObject() [with data_type = std::basic_stringchar; destroyPolicy = cxxtools::DefaultDestroyPolicy]': menu.ecpp:125:1: required from here /usr/include/tnt/object.h:60:11: error: 'destroy' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] /usr/include/tnt/object.h:60:11: note: declarations in dependent base 'cxxtools::DefaultDestroyPolicystd::basic_stringchar ' are not found by unqualified lookup /usr/include/tnt/object.h:60:11: note: use 'this-destroy' instead /usr/include/tnt/object.h: In instantiation of 'tnt::PointerObjectdata_type, destroyPolicy::~PointerObject() [with data_type = vdrlive::TimerConflictNotifier; destroyPolicy = cxxtools::DefaultDestroyPolicy]': menu.ecpp:125:1: required from here /usr/include/tnt/object.h:60:11: error: 'destroy' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] /usr/include/tnt/object.h:60:11: note: declarations in dependent base 'cxxtools::DefaultDestroyPolicyvdrlive::TimerConflictNotifier' are not found by unqualified lookup /usr/include/tnt/object.h:60:11: note: use 'this-destroy' instead /usr/include/tnt/object.h: In instantiation of 'tnt::PointerObjectdata_type, destroyPolicy::~PointerObject() [with data_type = bool; destroyPolicy = cxxtools::DefaultDestroyPolicy]': menu.ecpp:125:1: required from here /usr/include/tnt/object.h:60:11: error: 'destroy' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] /usr/include/tnt/object.h:60:11: note: declarations in dependent base 'cxxtools::DefaultDestroyPolicybool' are not found by unqualified lookup /usr/include/tnt/object.h:60:11: note: use 'this-destroy' instead make[3]: *** [menu.o] Error 1 make[3]: Leaving directory `/«BUILDDIR»/vdr-plugin-live-0.2.0+git20120114/pages' make[2]: *** [pages] Error 2 dh_auto_build: make -j1 all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale returned exit code 2 make[2]: Leaving directory `/«BUILDDIR»/vdr-plugin-live-0.2.0+git20120114' make[1]: *** [override_dh_auto_build] Error 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- now builds with the fixed build dependencies ---End Message---
Bug#669525: bumprace: FTBFS: configure: error: Your system is missing libjpeg!
tags 669525 patch thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bumprace: FTBFS: configure: error: Your system is missing libjpeg!
Processing commands for cont...@bugs.debian.org: tags 669525 patch Bug #669525 [src:bumprace] bumprace: FTBFS: configure: error: Your system is missing libjpeg! Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 669525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669525 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#669519: luola: FTBFS: configure: error: libz is needed
tags 669519 patch thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667423: xorp: ftbfs with GCC-4.7
ifeq ($(GXXVERSION),4.7) CXXFLAGS += -Wno-error=cast-qual endif building with -Wno-error=cast-qual let's the build get until g++ -o obj/x86_64-unknown-linux-gnu/fea/mfea_mrouter.os -c -Wno-error=cast-qual -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. fea/mfea_mrouter.cc fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::add_multicast_vif(uint32_t)': fea/mfea_mrouter.cc:1325:28: error: cannot bind packed field 'vc_ng.vifctl_ng::vif' to 'vifctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::delete_multicast_vif(uint32_t)': fea/mfea_mrouter.cc:1449:28: error: cannot bind packed field 'vc_ng.vifctl_ng::vif' to 'vifctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::add_mfc(const IPvX, const IPvX, uint32_t, uint8_t*, uint8_t*, const IPvX)': fea/mfea_mrouter.cc:1582:28: error: cannot bind packed field 'mc_ng.mfcctl_ng::mfc' to 'mfcctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::delete_mfc(const IPvX, const IPvX)': fea/mfea_mrouter.cc:1710:28: error: cannot bind packed field 'mc_ng.mfcctl_ng::mfc' to 'mfcctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::get_sg_count(const IPvX, const IPvX, SgCount)': fea/mfea_mrouter.cc:2316:43: error: cannot bind packed field 'sgreq_ng.sioc_sg_req_ng::req' to 'sioc_sg_req' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::get_vif_count(uint32_t, VifCount)': fea/mfea_mrouter.cc:2431:42: error: cannot bind packed field 'vreq_ng.sioc_vif_req_ng::vif' to 'sioc_vif_req' scons: *** [obj/x86_64-unknown-linux-gnu/fea/mfea_mrouter.os] Error 1 scons: building terminated because of errors. make: *** [build-arch-stamp] Error 2 please forward the issue upstream. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: luola: FTBFS: configure: error: libz is needed
Processing commands for cont...@bugs.debian.org: tags 669519 patch Bug #669519 [src:luola] luola: FTBFS: configure: error: libz is needed Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 669519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669519 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#672056: xf86-video-glamo: FTBFS: ../../src/glamo-driver.c:289:7: error: assignment discards 'const' qualifier from pointer target type [-Werror]
Matthias Klose a écrit , Le 10/05/2012 17:23: On 10.05.2012 07:55, Gilles Filippini wrote: Matthias Klose a écrit , Le 10/05/2012 02:50: tags 672056 + patch thanks uploaded to delayed/2, part of the xorg transition. Where is the patch? sorry, now attached np. That's fine (same as mine). Thanks, _g. signature.asc Description: OpenPGP digital signature
Bug#670066: Bug #670066 python-openturns is unusable
Hi, Freeze is approaching, is there any news on version 1.0? Or do we need to fix open bugs and release with 0.15? -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671998: hugin: FTBFS with gcc 4.7 bug
On 2012-05-10 Cyril Brulebois k...@debian.org wrote: Cyril Brulebois k...@debian.org (09/05/2012): Looks good so far, except for s390 :/ https://buildd.debian.org/status/package.php?p=huginsuite=experimental FWIW I think we'll go with a temporary removal from testing to let exiv2 migrate ASAP, given it would get entangled with gdal if we waited further. I'll be happy to assist you get it back into testing once its FTBFS is fixed for all release architectures. Hello, Thanks for the heads up. I have forwarded the s390 issue to hugin-ptx. http://groups.google.com/group/hugin-ptx/browse_thread/thread/cf1c9b63f0eb4bf9 cu andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 672332 is forwarded to http://groups.google.com/group/hugin-ptx/browse_thread/thread/cf1c9b63f0eb4bf9
Processing commands for cont...@bugs.debian.org:
forwarded 672332
http://groups.google.com/group/hugin-ptx/browse_thread/thread/cf1c9b63f0eb4bf9
Bug #672332 [src:hugin] hugin - FTBFS: invalid initialization of reference of
type 'ptrdiff_t {aka int}'
Set Bug forwarded-to-address to
'http://groups.google.com/group/hugin-ptx/browse_thread/thread/cf1c9b63f0eb4bf9'.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
672332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672332
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#672393: missing dependency on php-net-smtp
Package: php-mail Version: 1.2.0 Severity: serious Hi, Just a not to myself so I wont forget to upload: php-mail needs to depends: on php-net-smtp. For others who will read this, please do not NMU, this is a known issue, and it's already fixed in our Git, I'm just waiting for phpunit to be ready, so the package can be uploaded together with the unit tests at build time (which is already in our Git, but can't be uploaded to SID, since phpunit isn't in SID yet). Cheers, Thomas -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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#667129: cb2bib: ftbfs with GCC-4.7
Greetings, On Thu, May 10, 2012 at 05:45:49PM +0200, Salvatore Bonaccorso wrote: tags 667129 + pending patch thanks Hi Filippo I have updated cb2bib with the patch from Cyril Brulebois in the debian-science git repository. It fixes a RC bugs (FTBFS with gcc 4.7). Thank you very much indeed, and to Matthias Klose d...@debian.org and Cyril Brulebois k...@debian.org for handling that bug (with a patch) that somehow escaped my radar. I am handling that bug right away. All the best, Filippo -- Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu Researcher at CNRS and Debian Developer lopi...@debian.org Author of ``massXpert'' at http://www.massxpert.org Photographer at http://filippo.rusconi.free.fr/fineartphotoblog signature.asc Description: Digital signature
Bug#671919: [Python-modules-team] Bug#671919: python-sip: segfault in python-sip in use with calibre
Once again with english error messages: Building package with apt-get build-dep python-sip apt-get source --compile python-sip works, no problems Starting calibre with gdb: gdb /usr/bin/python2.7 (gdb) run /usr/bin/calibre Starting program: /usr/bin/python2.7 /usr/bin/calibre [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. Python Exception class 'gdb.error' There is no member named ma_mask.: createClassType (client=client@entry=0x7fffe2decea0, ctd=ctd@entry=0x7fffe2ded020, mod_dict=mod_dict@entry=) at /tmp/sip4-4.13.2/siplib/siplib.c:5502 5502Py_INCREF(st); (gdb) where Python Exception class 'gdb.error' There is no member named ma_mask.: #0 createClassType (client=client@entry=0x7fffe2decea0, ctd=ctd@entry=0x7fffe2ded020, mod_dict=mod_dict@entry=) at /tmp/sip4-4.13.2/siplib/siplib.c:5502 Python Exception class 'gdb.error' There is no member named ma_mask.: #1 0x722f6f31 in sip_api_init_module (client=0x7fffe2decea0, mod_dict=) at /tmp/sip4-4.13.2/siplib/siplib.c:1396 #2 0x7fffe2bdf9f7 in initpictureflow () from /usr/lib/calibre/calibre/plugins/pictureflow.so #3 0x004a2ac4 in _PyImport_LoadDynamicModule () #4 0x0041f47b in import_submodule.39130 () #5 0x0043caff in load_next.39135 () #6 0x0041fd44 in import_module_level.isra.3.39156 () #7 0x0050917b in builtin___import__.32811 () #8 0x004eaa3b in PyEval_EvalFrameEx () #9 0x004f1db0 in PyEval_EvalCodeEx () #10 0x004eafd8 in PyEval_EvalFrameEx () #11 0x004eb222 in PyEval_EvalFrameEx () #12 0x004f1db0 in PyEval_EvalCodeEx () #13 0x004f2e00 in function_call.15047 () #14 0x0044a176 in PyObject_Call () #15 0x0047cc7a in instancemethod_call.8523 () #16 0x0044a176 in PyObject_Call () #17 0x004dd7b7 in call_method.25480 () #18 0x004ebd03 in PyEval_EvalFrameEx () #19 0x004f1db0 in PyEval_EvalCodeEx () #20 0x004d8d98 in PyImport_ExecCodeModuleEx () #21 0x0041ea88 in load_source_module.39076 () #22 0x0041f47b in import_submodule.39130 () #23 0x0043caff in load_next.39135 () #24 0x0041ff01 in import_module_level.isra.3.39156 () #25 0x0050917b in builtin___import__.32811 () #26 0x0044a176 in PyObject_Call () #27 0x0044c666 in PyEval_CallObjectWithKeywords () #28 0x004ed1f3 in PyEval_EvalFrameEx () #29 0x004f1db0 in PyEval_EvalCodeEx () #30 0x004d8d98 in PyImport_ExecCodeModuleEx () #31 0x0041ea88 in load_source_module.39076 () #32 0x0041f47b in import_submodule.39130 () #33 0x0043caff in load_next.39135 () #34 0x0041ff01 in import_module_level.isra.3.39156 () #35 0x0050917b in builtin___import__.32811 () #36 0x0044a176 in PyObject_Call () #37 0x0044c666 in PyEval_CallObjectWithKeywords () #38 0x004ed1f3 in PyEval_EvalFrameEx () #39 0x004eb222 in PyEval_EvalFrameEx () #40 0x004f1db0 in PyEval_EvalCodeEx () #41 0x004eafd8 in PyEval_EvalFrameEx () #42 0x004f1db0 in PyEval_EvalCodeEx () #43 0x004d980d in PyRun_FileExFlags () #44 0x004d9a96 in PyRun_SimpleFileExFlags () #45 0x004da39e in Py_Main () #46 0x76977ead in __libc_start_main (main=optimized out, argc=optimized out, ubp_av=optimized out, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe2c8) at libc-start.c:228 #47 0x0041e131 in _start () Next suggestet try: Rebuild calibre apt-get build-dep calibre apt-get source --compile calibre = build failed, log is attached. I will open another bug for calibre, because build is failing without any message, but the first problem still exists. I think the lib should never crash, even the call may be wrong. With regards Tom Reading package lists... Building dependency tree... Reading state information... NOTICE: 'calibre' packaging is maintained in the 'Bzr' version control system at: https://code.launchpad.net/~calibre-packagers/calibre/debian Please use: bzr get https://code.launchpad.net/~calibre-packagers/calibre/debian to retrieve the latest (possibly unreleased) updates to the package. Need to get 24.2 MB of source archives. Get:1 http://ftp.de.debian.org/debian/ sid/main calibre 0.8.49+dfsg-0.1 (dsc) [1,763 B] Get:2 http://ftp.de.debian.org/debian/ sid/main calibre 0.8.49+dfsg-0.1 (tar) [24.2 MB] Get:3 http://ftp.de.debian.org/debian/ sid/main calibre 0.8.49+dfsg-0.1 (diff) [21.0 kB] dpkg-source: info: extracting calibre in calibre-0.8.49+dfsg dpkg-source: info: unpacking calibre_0.8.49+dfsg.orig.tar.xz dpkg-source: info: unpacking calibre_0.8.49+dfsg-0.1.debian.tar.gz dpkg-source: info: applying no_updates_dialog.patch dpkg-source: info: applying manpages-installation.patch
Bug#651791: marked as done (Fails to build against Linux 3.1)
Your message dated Thu, 10 May 2012 18:17:17 + with message-id e1ssxvr-00032a...@franck.debian.org and subject line Bug#672384: Removed package(s) from unstable has caused the Debian Bug report #651791, regarding Fails to build against Linux 3.1 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.) -- 651791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: line6-usb-source Version: 0.8.0+svn551-1 Severity: grave These modules fail to build against Linux 3.1: make[2]: Entering directory `/usr/src/linux-headers-3.1.0-1-amd64' /usr/src/linux-headers-3.1.0-1-common/arch/x86/Makefile:81: stack protector enabled but no compiler support CC [M] /usr/src/modules/line6-usb/audio.o CC [M] /usr/src/modules/line6-usb/capture.o /usr/src/modules/line6-usb/capture.c: In function \u2018snd_line6_capture_hw_params\u2019: /usr/src/modules/line6-usb/capture.c:272:2: error: implicit declaration of function \u2018kmalloc\u2019 [-Werror=implicit-function-declaration] /usr/src/modules/line6-usb/capture.c:272:22: warning: assignment makes pointer from integer without a cast [enabled by default] cc1: some warnings being treated as errors make[5]: *** [/usr/src/modules/line6-usb/capture.o] Error 1 make[4]: *** [_module_/usr/src/modules/line6-usb] Error 2 make[3]: *** [sub-make] Error 2 make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-3.1.0-1-amd64' This particular error is due to missing inclusion of linux/slab.h, which was probably being included indirectly in previous kernel versions. Ben. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages line6-usb-source depends on: ii bzip2 1.0.6-1 ii debhelper 8.9.11 ii module-assistant 0.11.4 line6-usb-source recommends no packages. line6-usb-source suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 0.8.0+svn551-1+rm Dear submitter, as the package line6-usb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/672384 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#512354: marked as done (libggzcore-dev: API change: ggzcore_server_list_rooms)
Your message dated Thu, 10 May 2012 18:18:48 + with message-id e1ssxwu-0003cp...@franck.debian.org and subject line Bug#654355: Removed package(s) from unstable has caused the Debian Bug report #512354, regarding libggzcore-dev: API change: ggzcore_server_list_rooms 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.) -- 512354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libggzcore-dev Version: 0.99.5~pre1-1 Severity: serious The prototype has changed from int ggzcore_server_list_rooms(GGZServer *server, const int type, const char verbose) in 0.0.14.1-1 to int ggzcore_server_list_rooms(GGZServer *server, const char verbose) in 0.99.5~pre1-1. man/ggzcore_h.3 still refers to the former interface. If this API change was intentional, the documentation needs to be corrected, and the soname (and package name for libggzcore) needs to be bumped. I believe the same applies to ggzcore_room_list_tables(). ---End Message--- ---BeginMessage--- Version: 0.0.14.1-1.1+rm Dear submitter, as the package ggz-client-libs has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/654355 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ---End Message---
Bug#658893: marked as done (Call-time pass-by-reference has been removed from php5 (= 5.4))
Your message dated Thu, 10 May 2012 18:20:03 +
with message-id e1ssxy7-0003hz...@franck.debian.org
and subject line Bug#672227: Removed package(s) from unstable
has caused the Debian Bug report #658893,
regarding Call-time pass-by-reference has been removed from php5 (= 5.4)
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.)
--
658893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lwat
Version: 0.17-4.2
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php54
Dear maintainer,
package lwat currently fails to parse correctly with
PHP 5.4 with following error(s):
PHP Parse error: syntax error, unexpected '$base' (T_VARIABLE) in
/usr/share/doc/lwat/examples/dummy-config.php on line 10
Errors parsing /usr/share/doc/lwat/examples/dummy-config.php
PHP Fatal error: Call-time pass-by-reference has been removed in
/usr/share/lwat/web/import.php on line 102
Errors parsing /usr/share/lwat/web/import.php
These error were generated by php in the lint mode. To reproduce
please install php5-cli and run:
dpkg -L lwat | grep -E .php[54]? | xargs -i php -l {}
PHP 5.4 is planned to be included in wheezy, as such, this bug might
become RC if not fixed before 5.4 is uploaded to sid.
Thanks,
--
Ondřej Surý ond...@debian.org
-- System Information:
Debian Release: 6.0.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-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
---End Message---
---BeginMessage---
Version: 0.17-4.2+rm
Dear submitter,
as the package lwat has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/672227
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.
Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)
---End Message---
Bug#672001: marked as done (unalz: FTBFS: UnAlz.cpp:1910:49: error: cannot convert 'const z_crc_t* {aka const unsigned int*}' to 'const long unsigned int*' in initialization)
Your message dated Thu, 10 May 2012 18:20:32 +
with message-id e1ssxya-0003rj...@franck.debian.org
and subject line Bug#672001: fixed in unalz 0.65-2
has caused the Debian Bug report #672001,
regarding unalz: FTBFS: UnAlz.cpp:1910:49: error: cannot convert 'const
z_crc_t* {aka const unsigned int*}' to 'const long unsigned int*' in
initialization
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.)
--
672001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: unalz
Version: 0.65-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
g++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -Wall -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-D_FORTIFY_SOURCE=2 -c -o UnAlz.o UnAlz.cpp
UnAlz.cpp: In member function 'BOOL
UNALZ::CUnAlz::ExtractDeflate2(UNALZ::CUnAlz::SExtractDest*,
UNALZ::SAlzLocalFileHeader)':
UnAlz.cpp:1356:8: warning: unused variable 'nInBufSize' [-Wunused-variable]
UnAlz.cpp:1357:8: warning: unused variable 'nOutBufSize' [-Wunused-variable]
UnAlz.cpp:1359:8: warning: unused variable 'flush' [-Wunused-variable]
UnAlz.cpp: In member function 'BOOL UNALZ::CUnAlz::FSeek(long long int)':
UnAlz.cpp:1584:7: warning: variable 'remainHigh' set but not used
[-Wunused-but-set-variable]
UnAlz.cpp: In member function 'UINT32 UNALZ::CUnAlz::CRC32(UINT32, BYTE)':
UnAlz.cpp:1910:49: error: cannot convert 'const z_crc_t* {aka const unsigned
int*}' to 'const long unsigned int*' in initialization
make[1]: *** [UnAlz.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/05/08/unalz_0.65-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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
---End Message---
---BeginMessage---
Source: unalz
Source-Version: 0.65-2
We believe that the bug you reported is fixed in the latest version of
unalz, which is due to be installed in the Debian FTP archive:
unalz_0.65-2.debian.tar.gz
to main/u/unalz/unalz_0.65-2.debian.tar.gz
unalz_0.65-2.dsc
to main/u/unalz/unalz_0.65-2.dsc
unalz_0.65-2_i386.deb
to main/u/unalz/unalz_0.65-2_i386.deb
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 672...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Changwoo Ryu cw...@debian.org (supplier of updated unalz 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 11 May 2012 02:55:06 +0900
Source: unalz
Binary: unalz
Architecture: source i386
Version: 0.65-2
Distribution: unstable
Urgency: low
Maintainer: Changwoo Ryu cw...@debian.org
Changed-By: Changwoo Ryu cw...@debian.org
Description:
unalz - De-archiver for .alz files
Closes: 672001
Changes:
unalz (0.65-2) unstable; urgency=low
.
* Use source format 3.0 (quilt) and debhelper 7
* Standards-Version: 3.9.3
* Fix FTBFS with GCC 4.7 (Closes: #672001)
* Build with the optimize build flag
- according to the policy 4.9.
Checksums-Sha1:
616e5f47de7016e9ee4d6b7619560aad2b411941 1218 unalz_0.65-2.dsc
179e9c6f83be64a58da6b9d0a006f6c9b44fd5a4 7365 unalz_0.65-2.debian.tar.gz
f6e6bc826f214d16f6e60dfe732b847f5a8d319e 26550 unalz_0.65-2_i386.deb
Checksums-Sha256:
f0b42230d127aa9082eb9d55c6811868045140397a03f79ebb7102853e4a06f4 1218
unalz_0.65-2.dsc
f9465594d7a0d9edb3aeeeb48a2d0ca6b052e956ca98d6722ba4187ca8db0437 7365
unalz_0.65-2.debian.tar.gz
2332e9b1aa623f1d936c0a74d8d3ee5f802c4389674ae81d2b3bfd4c7b1bf484 26550
unalz_0.65-2_i386.deb
Files:
84bf348729772c2d35d9ba3713789d1d 1218 utils optional unalz_0.65-2.dsc
b8d44e82eb29aa65ec3f1c2ab9293645 7365 utils optional unalz_0.65-2.debian.tar.gz
942da12441e87376a7648f7ab0455ed7 26550 utils optional unalz_0.65-2_i386.deb
-BEGIN PGP SIGNATURE-
Bug#667423: xorp fails to build from source with GCC 4.7
see http://bugs.debian.org/667423 g++ -o obj/x86_64-unknown-linux-gnu/fea/data_plane/ifconfig/ifconfig_get_netlink_socket.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. fea/data_plane/ifconfig/ifconfig_get_netlink_socket.cc fea/data_plane/ifconfig/ifconfig_get_netlink_socket.cc: In static member function 'static int IfConfigGetNetlinkSocket::parse_buffer_netlink_socket(IfConfig, IfTree, const std::vectorunsigned char, bool, int)': fea/data_plane/ifconfig/ifconfig_get_netlink_socket.cc:283:9: error: cast from type 'const nlmsghdr*' to type 'char*' casts away qualifiers [-Werror=cast-qual] fea/data_plane/ifconfig/ifconfig_get_netlink_socket.cc:284:21: error: cast from type 'const nlmsghdr*' to type 'char*' casts away qualifiers [-Werror=cast-qual] cc1plus: all warnings being treated as errors you can work around this by building with -Wno-error=cast-qual. then the build fails with: g++ -o obj/x86_64-unknown-linux-gnu/fea/mfea_mrouter.os -c -Wno-error=cast-qual -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. fea/mfea_mrouter.cc fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::add_multicast_vif(uint32_t)': fea/mfea_mrouter.cc:1325:28: error: cannot bind packed field 'vc_ng.vifctl_ng::vif' to 'vifctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::delete_multicast_vif(uint32_t)': fea/mfea_mrouter.cc:1449:28: error: cannot bind packed field 'vc_ng.vifctl_ng::vif' to 'vifctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::add_mfc(const IPvX, const IPvX, uint32_t, uint8_t*, uint8_t*, const IPvX)': fea/mfea_mrouter.cc:1582:28: error: cannot bind packed field 'mc_ng.mfcctl_ng::mfc' to 'mfcctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::delete_mfc(const IPvX, const IPvX)': fea/mfea_mrouter.cc:1710:28: error: cannot bind packed field 'mc_ng.mfcctl_ng::mfc' to 'mfcctl' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::get_sg_count(const IPvX, const IPvX, SgCount)': fea/mfea_mrouter.cc:2316:43: error: cannot bind packed field 'sgreq_ng.sioc_sg_req_ng::req' to 'sioc_sg_req' fea/mfea_mrouter.cc: In member function 'int MfeaMrouter::get_vif_count(uint32_t, VifCount)': fea/mfea_mrouter.cc:2431:42: error: cannot bind packed field 'vreq_ng.sioc_vif_req_ng::vif' to 'sioc_vif_req' scons: *** [obj/x86_64-unknown-linux-gnu/fea/mfea_mrouter.os] Error 1 scons: building terminated because of errors. any advice? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668868: bitcoind: Assertion failed at startup on mips (big endian)
* Dwayne C. Litzenberger dl...@dlitz.net, 2012-04-15, 04:07: -Architecture: any +Architecture: any-alpha any-amd64 any-armel any-armhf any-i386 any-ia64 + any-mipsel any-sh4 There are no architectures matching any-armel or any-armhf. You want any-arm instead (which matches both armel and armhf). -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662788: marked as done (kde-style-skulpture: FTBFS against multiarch Qt 4.8)
Your message dated Thu, 10 May 2012 14:19:11 -0400 with message-id e5391b9d-5553-45dc-b734-f38b99e1c...@email.android.com and subject line Package has been removed has caused the Debian Bug report #662788, regarding kde-style-skulpture: FTBFS against multiarch Qt 4.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 662788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kde-style-skulpture Version: 0.2.0-1 Tags: patch experimental Severity: serious User: debian-qt-...@lists.debian.org Usertags: qt48-transition Hi, Your package fails to build against the multiarch enabled Qt 4.8. I'm attaching a patch that adjusts the install path of the Qt plugin. Regards, Felix diff -u kde-style-skulpture-0.2.0/debian/kde-style-skulpture.install kde-style-skulpture-0.2.0/debian/kde-style-skulpture.install --- kde-style-skulpture-0.2.0/debian/kde-style-skulpture.install +++ kde-style-skulpture-0.2.0/debian/kde-style-skulpture.install @@ -1,4 +1,4 @@ -usr/lib/qt4/plugins/styles/libskulpture.so +usr/lib/*/qt4/plugins/styles/libskulpture.so usr/share/kde4/apps/color-schemes/SkulptureChocolate.colors usr/share/kde4/apps/color-schemes/SkulptureIce.colors usr/share/kde4/apps/color-schemes/SkulptureMint.colors ---End Message--- ---BeginMessage--- ---End Message---
Processed: Re: sinfo: ftbfs with GCC-4.7
Processing commands for cont...@bugs.debian.org: tags 667374 + patch Bug #667374 [sinfo] sinfo: ftbfs with GCC-4.7 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 667374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667374 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#667374: sinfo: ftbfs with GCC-4.7
tags 667374 + patch thanks uploaded to delayed/5, part of the boost transition diff -Nru sinfo-0.0.42/debian/changelog sinfo-0.0.42/debian/changelog --- sinfo-0.0.42/debian/changelog 2012-05-10 20:31:49.0 +0200 +++ sinfo-0.0.42/debian/changelog 2012-05-10 20:31:50.0 +0200 @@ -1,3 +1,10 @@ +sinfo (0.0.42-1.1) unstable; urgency=low + + * Non maintainer upload. + * Work around build failure with GCC 4.7. Closes: #667374. + + -- Matthias Klose d...@debian.org Thu, 10 May 2012 20:24:14 +0200 + sinfo (0.0.42-1) unstable; urgency=low * [d36ccf5] Imported Upstream version 0.0.42 diff -Nru sinfo-0.0.42/debian/rules sinfo-0.0.42/debian/rules --- sinfo-0.0.42/debian/rules 2012-05-10 20:31:49.0 +0200 +++ sinfo-0.0.42/debian/rules 2012-05-10 20:31:50.0 +0200 @@ -17,13 +17,9 @@ DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) -CFLAGS = -Wall -g +CFLAGS = $(shell dpkg-buildflags --get CFLAGS) +CXXFLAGS = $(shell dpkg-buildflags --get CXXFLAGS) -fpermissive -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) - CFLAGS += -O0 -else - CFLAGS += -O2 -endif ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) INSTALL_PROGRAM += -s endif @@ -31,6 +27,7 @@ config.status: configure dh_testdir # Add here commands to configure the package. + CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) \ ./configure --host=$(DEB_HOST_GNU_TYPE)\ --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr \
Bug#666882: Wheezy automatic signing key
reassign 666882 debian-archive-keyring thanks The new key has been created, see the following discussion: https://lists.debian.org/debian-devel-announce/2012/05/msg0.html Reassigning as requested. -- 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#666882: Wheezy automatic signing key
Processing commands for cont...@bugs.debian.org: reassign 666882 debian-archive-keyring Bug #666882 [ftp.debian.org] Wheezy automatic signing key Bug reassigned from package 'ftp.debian.org' to 'debian-archive-keyring'. Ignoring request to alter found versions of bug #666882 to the same values previously set Ignoring request to alter fixed versions of bug #666882 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 666882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666882 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#667827: marked as done (libgdf: FTBFS (make[1]: *** [override_dh_auto_install] Error 1))
Your message dated Thu, 10 May 2012 18:50:21 +
with message-id e1ssyrr-0006v3...@franck.debian.org
and subject line Bug#667827: fixed in libgdf 0.1.2-2
has caused the Debian Bug report #667827,
regarding libgdf: FTBFS (make[1]: *** [override_dh_auto_install] Error 1)
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.)
--
667827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libgdf
Version: 0.1.2-1
Severity: serious
Tags: wheezy sid
Hi,
libgdf FTBFS when binNMUed for the boost 1.49 transition. From the
amd64 build log:
-- Removed runtime path from
/build/buildd-libgdf_0.1.2-1+b1-amd64-W7GIHx/libgdf-0.1.2/debian/tmp/usr/bin/gdf_merger
make[2]: Leaving directory
`/build/buildd-libgdf_0.1.2-1+b1-amd64-W7GIHx/libgdf-0.1.2/obj-x86_64-linux-gnu'
: # Install Octave bindings
mkdir -p
debian/octave-gdf/usr/lib/x86_64-linux-gnu/octave/site/oct/x86_64-pc-linux-gnu
install matlab/*.mex
debian/octave-gdf/usr/lib/x86_64-linux-gnu/octave/site/oct/x86_64-pc-linux-gnu
[ -e /usr/bin/octave-depends ] octave-depends -poctave-gdf
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory
`/build/buildd-libgdf_0.1.2-1+b1-amd64-W7GIHx/libgdf-0.1.2'
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit
status 2
Full logs available via
https://buildd.debian.org/status/package.php?p=libgdfsuite=sid
Regards,
Adam
---End Message---
---BeginMessage---
Source: libgdf
Source-Version: 0.1.2-2
We believe that the bug you reported is fixed in the latest version of
libgdf, which is due to be installed in the Debian FTP archive:
gdf-tools_0.1.2-2_amd64.deb
to main/libg/libgdf/gdf-tools_0.1.2-2_amd64.deb
libgdf-dev_0.1.2-2_amd64.deb
to main/libg/libgdf/libgdf-dev_0.1.2-2_amd64.deb
libgdf0-dbg_0.1.2-2_amd64.deb
to main/libg/libgdf/libgdf0-dbg_0.1.2-2_amd64.deb
libgdf0_0.1.2-2_amd64.deb
to main/libg/libgdf/libgdf0_0.1.2-2_amd64.deb
libgdf_0.1.2-2.debian.tar.gz
to main/libg/libgdf/libgdf_0.1.2-2.debian.tar.gz
libgdf_0.1.2-2.dsc
to main/libg/libgdf/libgdf_0.1.2-2.dsc
matlab-gdf_0.1.2-2_all.deb
to contrib/libg/libgdf/matlab-gdf_0.1.2-2_all.deb
octave-gdf_0.1.2-2_amd64.deb
to main/libg/libgdf/octave-gdf_0.1.2-2_amd64.deb
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 667...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yaroslav Halchenko deb...@onerussian.com (supplier of updated libgdf 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 May 2012 09:16:11 -0400
Source: libgdf
Binary: libgdf0 libgdf0-dbg libgdf-dev gdf-tools octave-gdf matlab-gdf
Architecture: source amd64 all
Version: 0.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team t...@neuro.debian.net
Changed-By: Yaroslav Halchenko deb...@onerussian.com
Description:
gdf-tools - IO library for the GDF -- helper tools
libgdf-dev - IO library for the GDF -- development library
libgdf0- IO library for the GDF (general dataformat for biosignals)
libgdf0-dbg - IO library for the GDF -- debug symbols
matlab-gdf - IO library for the GDF -- Matlab interface
octave-gdf - IO library for the GDF -- Octave interface
Closes: 666894 667827
Changes:
libgdf (0.1.2-2) unstable; urgency=medium
.
[ Yaroslav Halchenko ]
* debian/rules:
- Manually provide octave:Depends=octave if octave-depends is not
present (Closes: #667827). This solution (over just adding octave
into Depends) is chosen for backportability to Debian squeeze
* Above and below changes by Rafael (THANK YOU) to address FTBFS due
to deprecation of octave-depends (Closes: #666894)
.
[ Rafael Laboissiere ]
* debian/rules:
- Use directly the octave-config script in order to get the
installation path for the *.mex files
* debian/octave-gdf.docs: New debhelper file for installing the
gdf_{reader,writer}.m files, which contain actually just the
documentation for the *.mex files
* debian/octave-gdf.examples: New debhelper file for installing the
provided examples
Checksums-Sha1:
077f7806013c25de240a900503cf0f8bacb2eba6 1651
Bug#672397: merkaartor FTBFS due to a g++-4.7 issue in boost headers
Package: libboost1.49-dev Version: 1.49.0-3 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 Hi, after applying http://goo.gl/89Kk8 merkaartor ftbfs with g++-4.7 due to a bug in the boost headers: g++ -c -m64 -pipe -I/usr/include/gdal -O2 -Wall -W -D_REENTRANT -DQT_WEBKIT -DRELEASE -DVERSION=0.17 -DREVISION= -DNDEBUG -DUSE_LIBPROXY -DUSE_WEBKIT -D_TTY_POSIX_ -DUSE_GPS -DUSE_GPSD_LIB -DPLUGINS_DIR=/usr/lib/merkaartor/plugins -DSHARE_DIR=/usr/share/merkaartor -DTRANSDIR_MERKAARTOR=/usr/share/merkaartor/translations -DTRANSDIR_SYSTEM=/usr/share/qt4/translations/ -DGEOIMAGE -DUSE_ZBAR -DUSE_GDAL -DUSE_PROJ -DWORLD_SHP=/usr/share/merkaartor/world_background.osb -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_SVG_LIB -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtWebKit -I/usr/include/qt4 -I../3rdparty/qtsingleapplication-2.6_1-opensource/src -I../3rdparty/qttoolbardialog-2.2_1-opensource/src -I../include -I../interfaces -I../include/builtin-ggl -I. -IRender -Iqextserialport - IGPS -INameFinder -IPaintStyle -IPaintStyle -IFeatures -ILayers -IPreferences -ISync -ICommands -IInteractions -IDocks -IImportExport -ITools -ITagTemplate -I. -I. -o ImportExportOsmBin.o ImportExport/ImportExportOsmBin.cpp In file included from /usr/include/boost/intrusive_ptr.hpp:16:0, from Features/Feature.h:12, from ImportExport/../ImportExport/ImportExportOsmBin.h:15, from ImportExport/ImportExportOsmBin.cpp:17: /usr/include/boost/smart_ptr/intrusive_ptr.hpp: In instantiation of 'boost::intrusive_ptrT::intrusive_ptr(T*, bool) [with T = Feature]': ImportExport/ImportExportOsmBin.cpp:130:60: required from here /usr/include/boost/smart_ptr/intrusive_ptr.hpp:67:34: error: 'intrusive_ptr_add_ref' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] In file included from ImportExport/../ImportExport/ImportExportOsmBin.h:15:0, from ImportExport/ImportExportOsmBin.cpp:17: Features/Feature.h:348:21: note: 'void boost::intrusive_ptr_add_ref(Feature*)' declared here, later in the translation unit In file included from /usr/include/boost/intrusive_ptr.hpp:16:0, from Features/Feature.h:12, from ImportExport/../ImportExport/ImportExportOsmBin.h:15, from ImportExport/ImportExportOsmBin.cpp:17: /usr/include/boost/smart_ptr/intrusive_ptr.hpp: In instantiation of 'boost::intrusive_ptrT::~intrusive_ptr() [with T = Feature]': ImportExport/ImportExportOsmBin.cpp:130:60: required from here /usr/include/boost/smart_ptr/intrusive_ptr.hpp:96:23: error: 'intrusive_ptr_release' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] In file included from ImportExport/../ImportExport/ImportExportOsmBin.h:15:0, from ImportExport/ImportExportOsmBin.cpp:17: Features/Feature.h:349:21: note: 'void boost::intrusive_ptr_release(Feature*)' declared here, later in the translation unit In file included from /usr/include/boost/intrusive_ptr.hpp:16:0, from Features/Feature.h:12, from ImportExport/../ImportExport/ImportExportOsmBin.h:15, from ImportExport/ImportExportOsmBin.cpp:17: /usr/include/boost/smart_ptr/intrusive_ptr.hpp: In instantiation of 'boost::intrusive_ptrT::intrusive_ptr(const boost::intrusive_ptrT) [with T = Feature; boost::intrusive_ptrT = boost::intrusive_ptrFeature]': /usr/include/qt4/QtCore/qlist.h:372:58: required from 'void QListT::node_construct(QListT::Node*, const T) [with T = boost::intrusive_ptrFeature]' /usr/include/qt4/QtCore/qlist.h:512:13: required from 'void QListT::append(const T) [with T = boost::intrusive_ptrFeature]' ImportExport/ImportExportOsmBin.cpp:131:35: required from here /usr/include/boost/smart_ptr/intrusive_ptr.hpp:91:23: error: 'intrusive_ptr_add_ref' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] In file included from ImportExport/../ImportExport/ImportExportOsmBin.h:15:0, from ImportExport/ImportExportOsmBin.cpp:17: Features/Feature.h:348:21: note: 'void boost::intrusive_ptr_add_ref(Feature*)' declared here, later in the translation unit make[2]: *** [ImportExportOsmBin.o] Error 1 Building with g+=-4.6 works well Thanks for fixing :) Cheers, Bernd -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale:
Processed: tags 672393 pending
Processing commands for cont...@bugs.debian.org: tags 672393 pending Bug #672393 [php-mail] missing dependency on php-net-smtp Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 672393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672393 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: block 667275 with 672397
Processing commands for cont...@bugs.debian.org: block 667275 with 672397 Bug #667275 [merkaartor] merkaartor: ftbfs with GCC-4.7 667275 was not blocked by any bugs. 667275 was not blocking any bugs. Added blocking bug(s) of 667275: 672397 thanks Stopping processing here. Please contact me if you need assistance. -- 667275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667275 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
