Bug#677460: libmeep-mpich2-dev and libmeep-lam4-dev: error when trying to install together
Package: libmeep-lam4-dev,libmeep-mpich2-dev Version: libmeep-lam4-dev/1.1.1-8 Version: libmeep-mpich2-dev/1.1.1-8 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-14 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! libgomp1 libfftw3-3 libquadmath0 libgfortran3 libblas3 libblas3gf libcr0 libgsl0ldbl liblapack3 liblapack3gf libharminv2 libmpich2-3 libhdf5-mpich2-7 libmeep-lam4-6 libmeep-lam4-dev libmeep-mpich2-6 libmeep-mpich2-dev Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libgomp1:amd64. (Reading database ... 10690 files and directories currently installed.) Unpacking libgomp1:amd64 (from .../libgomp1_4.7.0-13_amd64.deb) ... Selecting previously unselected package libfftw3-3:amd64. Unpacking libfftw3-3:amd64 (from .../libfftw3-3_3.3.2-3_amd64.deb) ... Selecting previously unselected package libquadmath0:amd64. Unpacking libquadmath0:amd64 (from .../libquadmath0_4.7.0-13_amd64.deb) ... Selecting previously unselected package libgfortran3:amd64. Unpacking libgfortran3:amd64 (from .../libgfortran3_4.7.0-13_amd64.deb) ... Selecting previously unselected package libblas3. Unpacking libblas3 (from .../libblas3_1.2.20110419-3_amd64.deb) ... Selecting previously unselected package libblas3gf. Unpacking libblas3gf (from .../libblas3gf_1.2.20110419-3_amd64.deb) ... Selecting previously unselected package libcr0. Unpacking libcr0 (from .../libcr0_0.8.4-2_amd64.deb) ... Selecting previously unselected package libgsl0ldbl. Unpacking libgsl0ldbl (from .../libgsl0ldbl_1.15+dfsg-1_amd64.deb) ... Selecting previously unselected package liblapack3. Unpacking liblapack3 (from .../liblapack3_3.4.1-1_amd64.deb) ... Selecting previously unselected package liblapack3gf. Unpacking liblapack3gf (from .../liblapack3gf_3.4.1-1_amd64.deb) ... Selecting previously unselected package libharminv2. Unpacking libharminv2 (from .../libharminv2_1.3.1-8_amd64.deb) ... Selecting previously unselected package libmpich2-3. Unpacking libmpich2-3 (from .../libmpich2-3_1.4.1-4_amd64.deb) ... Selecting previously unselected package libhdf5-mpich2-7. Unpacking libhdf5-mpich2-7 (from .../libhdf5-mpich2-7_1.8.8-9_amd64.deb) ... Selecting previously unselected package libmeep-lam4-6. Unpacking libmeep-lam4-6 (from .../libmeep-lam4-6_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-lam4-dev. Unpacking libmeep-lam4-dev (from .../libmeep-lam4-dev_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-mpich2-6. Unpacking libmeep-mpich2-6 (from .../libmeep-mpich2-6_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-mpich2-dev. Unpacking libmeep-mpich2-dev (from .../libmeep-mpich2-dev_1.1.1-8_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_amd64.deb (--unpack): trying to overwrite '/usr/include/meep.hpp', which is also in package libmeep-lam4-dev 1.1.1-8 Errors were encountered while processing: /var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_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/include/meep.hpp This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677461: liblapack-doc-man and libblas-doc: error when trying to install together
Package: libblas-doc,liblapack-doc-man Version: libblas-doc/1.2.20110419-3 Version: liblapack-doc-man/3.4.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-14 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! libblas-doc liblapack-doc-man Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libblas-doc. (Reading database ... 10690 files and directories currently installed.) Unpacking libblas-doc (from .../libblas-doc_1.2.20110419-3_all.deb) ... Selecting previously unselected package liblapack-doc-man. Unpacking liblapack-doc-man (from .../liblapack-doc-man_3.4.1-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/liblapack-doc-man_3.4.1-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/ctrsm.3.gz', which is also in package libblas-doc 1.2.20110419-3 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/liblapack-doc-man_3.4.1-1_all.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/man3/cgbmv.3.gz /usr/share/man/man3/cgemm.3.gz /usr/share/man/man3/cgemv.3.gz /usr/share/man/man3/cgerc.3.gz /usr/share/man/man3/cgeru.3.gz /usr/share/man/man3/chbmv.3.gz /usr/share/man/man3/chemm.3.gz /usr/share/man/man3/chemv.3.gz /usr/share/man/man3/cher.3.gz /usr/share/man/man3/cher2.3.gz /usr/share/man/man3/cher2k.3.gz /usr/share/man/man3/cherk.3.gz /usr/share/man/man3/chpmv.3.gz /usr/share/man/man3/chpr.3.gz /usr/share/man/man3/chpr2.3.gz /usr/share/man/man3/cscal.3.gz /usr/share/man/man3/csymm.3.gz /usr/share/man/man3/csyr2k.3.gz /usr/share/man/man3/csyrk.3.gz /usr/share/man/man3/ctbmv.3.gz /usr/share/man/man3/ctbsv.3.gz /usr/share/man/man3/ctpmv.3.gz /usr/share/man/man3/ctpsv.3.gz /usr/share/man/man3/ctrmm.3.gz /usr/share/man/man3/ctrmv.3.gz /usr/share/man/man3/ctrsm.3.gz /usr/share/man/man3/ctrsv.3.gz /usr/share/man/man3/dcabs1.3.gz /usr/share/man/man3/dgbmv.3.gz /usr/share/man/man3/dgemm.3.gz /usr/share/man/man3/dgemv.3.gz /usr/share/man/man3/dger.3.gz /usr/share/man/man3/dsbmv.3.gz /usr/share/man/man3/dspmv.3.gz /usr/share/man/man3/dspr.3.gz /usr/share/man/man3/dspr2.3.gz /usr/share/man/man3/dsymm.3.gz /usr/share/man/man3/dsymv.3.gz /usr/share/man/man3/dsyr.3.gz /usr/share/man/man3/dsyr2.3.gz /usr/share/man/man3/dsyr2k.3.gz /usr/share/man/man3/dsyrk.3.gz /usr/share/man/man3/dtbmv.3.gz /usr/share/man/man3/dtbsv.3.gz /usr/share/man/man3/dtpmv.3.gz /usr/share/man/man3/dtpsv.3.gz /usr/share/man/man3/dtrmm.3.gz /usr/share/man/man3/dtrmv.3.gz /usr/share/man/man3/dtrsm.3.gz /usr/share/man/man3/dtrsv.3.gz /usr/share/man/man3/lsame.3.gz /usr/share/man/man3/sgbmv.3.gz /usr/share/man/man3/sgemm.3.gz /usr/share/man/man3/sgemv.3.gz /usr/share/man/man3/sger.3.gz /usr/share/man/man3/ssbmv.3.gz /usr/share/man/man3/sspmv.3.gz /usr/share/man/man3/sspr.3.gz /usr/share/man/man3/sspr2.3.gz /usr/share/man/man3/ssymm.3.gz /usr/share/man/man3/ssymv.3.gz /usr/share/man/man3/ssyr.3.gz /usr/share/man/man3/ssyr2.3.gz /usr/share/man/man3/ssyr2k.3.gz /usr/share/man/man3/ssyrk.3.gz /usr/share/man/man3/stbmv.3.gz /usr/share/man/man3/stbsv.3.gz /usr/share/man/man3/stpmv.3.gz /usr/share/man/man3/stpsv.3.gz /usr/share/man/man3/strmm.3.gz /usr/share/man/man3/strmv.3.gz /usr/share/man/man3/strsm.3.gz /usr/share/man/man3/strsv.3.gz /usr/share/man/man3/xerbla.3.gz /usr/share/man/man3/zgbmv.3.gz /usr/share/man/man3/zgemm.3.gz /usr/share/man/man3/zgemv.3.gz /usr/share/man/man3/zgerc.3.gz /usr/share/man/man3/zgeru.3.gz /usr/share/man/man3/zhbmv.3.gz /usr/share/man/man3/zhemm.3.gz /usr/share/man/man3/zhemv.3.gz /usr/share/man/man3/zher.3.gz /usr/share/man/man3/zher2.3.gz /usr/share/man/man3/zher2k.3.gz /usr/share/man/man3/zherk.3.gz /usr/share/man/man3/zhpmv.3.gz
Bug#677462: libmeep-mpich2-dev and libmeep-mpi-default-dev: error when trying to install together
Package: libmeep-mpi-default-dev,libmeep-mpich2-dev Version: libmeep-mpi-default-dev/1.1.1-8 Version: libmeep-mpich2-dev/1.1.1-8 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-14 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! libgomp1 libfftw3-3 libquadmath0 libgfortran3 libblas3 libblas3gf libcr0 libgsl0ldbl liblapack3 liblapack3gf libharminv2 libmpich2-3 libhdf5-mpich2-7 libmeep-mpi-default6 libmeep-mpi-default-dev libmeep-mpich2-6 libmeep-mpich2-dev Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libgomp1:amd64. (Reading database ... 10690 files and directories currently installed.) Unpacking libgomp1:amd64 (from .../libgomp1_4.7.0-13_amd64.deb) ... Selecting previously unselected package libfftw3-3:amd64. Unpacking libfftw3-3:amd64 (from .../libfftw3-3_3.3.2-3_amd64.deb) ... Selecting previously unselected package libquadmath0:amd64. Unpacking libquadmath0:amd64 (from .../libquadmath0_4.7.0-13_amd64.deb) ... Selecting previously unselected package libgfortran3:amd64. Unpacking libgfortran3:amd64 (from .../libgfortran3_4.7.0-13_amd64.deb) ... Selecting previously unselected package libblas3. Unpacking libblas3 (from .../libblas3_1.2.20110419-3_amd64.deb) ... Selecting previously unselected package libblas3gf. Unpacking libblas3gf (from .../libblas3gf_1.2.20110419-3_amd64.deb) ... Selecting previously unselected package libcr0. Unpacking libcr0 (from .../libcr0_0.8.4-2_amd64.deb) ... Selecting previously unselected package libgsl0ldbl. Unpacking libgsl0ldbl (from .../libgsl0ldbl_1.15+dfsg-1_amd64.deb) ... Selecting previously unselected package liblapack3. Unpacking liblapack3 (from .../liblapack3_3.4.1-1_amd64.deb) ... Selecting previously unselected package liblapack3gf. Unpacking liblapack3gf (from .../liblapack3gf_3.4.1-1_amd64.deb) ... Selecting previously unselected package libharminv2. Unpacking libharminv2 (from .../libharminv2_1.3.1-8_amd64.deb) ... Selecting previously unselected package libmpich2-3. Unpacking libmpich2-3 (from .../libmpich2-3_1.4.1-4_amd64.deb) ... Selecting previously unselected package libhdf5-mpich2-7. Unpacking libhdf5-mpich2-7 (from .../libhdf5-mpich2-7_1.8.8-9_amd64.deb) ... Selecting previously unselected package libmeep-mpi-default6. Unpacking libmeep-mpi-default6 (from .../libmeep-mpi-default6_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-mpi-default-dev. Unpacking libmeep-mpi-default-dev (from .../libmeep-mpi-default-dev_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-mpich2-6. Unpacking libmeep-mpich2-6 (from .../libmeep-mpich2-6_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-mpich2-dev. Unpacking libmeep-mpich2-dev (from .../libmeep-mpich2-dev_1.1.1-8_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_amd64.deb (--unpack): trying to overwrite '/usr/include/meep.hpp', which is also in package libmeep-mpi-default-dev 1.1.1-8 Errors were encountered while processing: /var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_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/include/meep.hpp This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674098: marked as done (polyorb: FTBFS - test suite errors (varying by architecture))
Your message dated Thu, 14 Jun 2012 06:03:39 + with message-id e1sf39f-0002mj...@franck.debian.org and subject line Bug#674098: fixed in polyorb 2.8~20110207-4 has caused the Debian Bug report #674098, regarding polyorb: FTBFS - test suite errors (varying by architecture) 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.) -- 674098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: polyorb Version: 2.8~20110207-2 Severity: serious Justification: fails to build from source Builds of polyorb have been failing with test suite errors, whose details vary by architecture (and perhaps by chance): https://buildd.debian.org/status/logs.php?pkg=polyorbver=2.8%7E20110207-2 Specifically, CORBA_MIOP_0 fails on i386, ALL_TYPES6 fails on ia64, and gnatpython appears not to support powerpc. Could you please take a look? Thanks! -- ERRORCORBA_MIOP_0 DIFF:unexpected output ERROR--- expected +++ output @@ -0,0 +1,12 @@ +Running client ../examples/corba/send/send (config=miop.conf) +server ../examples/corba/send/listener (config=miop.conf) +IOR:0100180049444c3a546573742f436f6e74726f6c6c65723a312e320064000101020010003139342e3137372e3231312e3230340006bb1b002f303030303030303134546238376231656430313239303733666400010001001c0001000100010101000200010101000201010003004f50410110003139342e3137372e3231312e32303400cdd81b002f303030303030303134546238376231656430313239303733666400 +RUN: POLYORB_CONF=miop.conf /build/buildd-polyorb_2.8~20110207-2-i386-71kndT/polyorb-2.8~20110207/testsuite/../testsuite/../examples/corba/send/send IOR:0100180049444c3a546573742f436f6e74726f6c6c65723a312e320064000101020010003139342e3137372e3231312e3230340006bb1b002f303030303030303134546238376231656430313239303733666400010001001c0001000100010101000200010101000201010003004f50410110003139342e3137372e3231312e32303400cdd81b002f303030303030303134546238376231656430313239303733666400 +== Begin test CORBA/MIOP == +Sending CORBA.String: PASSED +Sending CORBA.Long..: PASSED +Previous tests went OK on the server side...: FAILED +Calling function with return value raised an exception..: PASSED +Shut down server(s).: PASSED +END TESTS...: FAILED +TEST FAILED INFO Aborting: file test_failed has been found -- ERRORALL_TYPES_6DIFF:unexpected output ERROR--- expected +++ output @@ -0,0 +1,123 @@ +Running client ../examples/corba/all_types/client (config=giop_1_1.conf) +server ../examples/corba/all_types/server (config=giop_1_1.conf) +IOR:0100120049444c3a616c6c5f74797065733a312e32005c00010102000a003132372e302e302e3100359d1b002f303030303030303131543861616438646338313239303739306100010001001c0001000100010101000200010101000201010003004f503c0001010e003139322e32352e3230362e363300f6ec1b002f303030303030303131543861616438646338313239303739306100 +RUN: POLYORB_CONF=giop_1_1.conf /build/buildd-polyorb_2.8~20110207-2-ia64-vOBjGF/polyorb-2.8~20110207/testsuite/../testsuite/../examples/corba/all_types/client IOR:0100120049444c3a616c6c5f74797065733a312e32005c00010102000a003132372e302e302e3100359d1b002f303030303030303131543861616438646338313239303739306100010001001c0001000100010101000200010101000201010003004f503c0001010e003139322e32352e3230362e363300f6ec1b002f303030303030303131543861616438646338313239303739306100 +== Begin test CORBA Types == [...] +test bounded wide string: PASSED +Execution terminated by unhandled exception +Exception name: ALL_TYPES.MY_EXCEPTION +Message: PO_Exc_Occ 1 +Call stack traceback locations: +0x40639f0c 0x400554ec 0x4063a63c 0x4038f42c 0x4038f9dc +Running ../examples/corba/all_types/client local (config=giop_1_1.conf) +== Begin test CORBA Types == +polyorb.utils.configuration_file: giop_1_1.conf is not a regular file [...] +test
Bug#676747: marked as done (polyorb: FTBFS: tests failed)
Your message dated Thu, 14 Jun 2012 06:03:39 + with message-id e1sf39f-0002mm...@franck.debian.org and subject line Bug#676747: fixed in polyorb 2.8~20110207-4 has caused the Debian Bug report #676747, regarding polyorb: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 676747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: polyorb Version: 2.8~20110207-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120609 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»' cd testsuite ./testsuite.py --abort-file=test_failed --diffs --testsuite-src-dir=/«PKGBUILDDIR»/testsuite INFO CORE_SYNC_POLICIES_0 OK: INFO DYNAMIC_DICT_0 OK: INFO URI_ENCODING_0 OK: INFO INIT_1 OK: INFO INIT_3 OK: INFO INIT_2 OK: INFO INIT_0 OK: INFO INIT_4 OK: INFO CHAINED_LIST_0 OK: INFO RANDOM_0 OK: INFO POA_0 OK: INFO TASK_0 OK: INFO TASK_1 OK: INFO TASK_2 OK: INFO TASK_3 OK: INFO FIXED_0OK: INFO OA_1 OK: INFO OA_0 OK: INFO TIME_0 OK: INFO NAMING_0 OK: INFO IR_0 OK: INFO CORBA_RANDOM_0 OK: INFO CORBA_RANDOM_1 OK: INFO POLYORB_CORE_2 OK: INFO POLYORB_CORE_3 OK: INFO POLYORB_CORE_1 OK: INFO POLYORB_CORE_0 OK: INFO ALL_FUNCTIONS_0OK: INFO ALL_FUNCTIONS_1UOK: INFO ALL_FUNCTIONS_4OK: INFO ALL_FUNCTIONS_5OK: INFO ALL_FUNCTIONS_6OK: INFO ECHO_7 OK: INFO ECHO_5 OK: INFO ECHO_0 OK: INFO ECHO_2 OK: INFO ECHO_1 OK: INFO ECHO_4 OK: INFO ECHO_6 OK: INFO ECHO_3 OK: INFO ALL_TYPES_6OK: INFO ALL_TYPES_0OK: INFO ALL_TYPES_1UOK: INFO ALL_TYPES_7OK: INFO ALL_TYPES_5OK: INFO CORBA_MIOP_0 OK: INFO MOMA_1 UOK: INFO MOMA_0 UOK: INFO CODE_SETS_1OK: INFO CODE_SETS_0OK: INFO CORBA_BENCHS_0 OK: INFO OBJECT_0 OK: INFO SHUTDOWN_0 OK: INFO CORBA_PERFORMANCE_0UOK: INFO CORBA_HARNESS_1OK: ERRORCORBA_HARNESS_3DIFF:unexpected output ERROR--- expected +++ output @@ -0,0 +1,12 @@ +Running client corba/harness/client (config=) +server corba/harness/server_thread_per_session (config=) +IOR:0100100049444c3a4861726e6573733a312e3200610102000d0031302e32382e3230352e3437a7c91b002f303030303030303131546430646333636338313239356438636300010001001c0001000100010101000200010101000201010003004f503c0001010d0031302e32382e3230352e34375eb41b002f303030303030303131546430646333636338313239356438636300 +RUN: /«PKGBUILDDIR»/testsuite/../testsuite/corba/harness/client IOR:0100100049444c3a4861726e6573733a312e3200610102000d0031302e32382e3230352e3437a7c91b002f303030303030303131546430646333636338313239356438636300010001001c0001000100010101000200010101000201010003004f503c0001010d0031302e32382e3230352e34375eb41b002f303030303030303131546430646333636338313239356438636300 +== Begin test Harness == +test not nil reference..:
Bug#676372: marked as done (API breakage)
Your message dated Thu, 14 Jun 2012 08:55:08 +0200
with message-id 20120614065508.ga18...@wavehammer.waldi.eu.org
and subject line Re: Bug#676372: API breakage
has caused the Debian Bug report #676372,
regarding API breakage
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.)
--
676372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libdebian-installer4
Version: 0.80
Severity: serious
File: /usr/lib/libdebian-installer.so.4
At some point between squeeze and wheezy the declaration of
di_release_file.sum has changed from char * to char **. This breaks
the API making it impossible to compile software (e.g. cdebootstrap)
for stable and testing/unstable without ugly hacks. For example in
cdebootstrap the following code is needed:
if (sizeof(item-sum[0]) == sizeof(char*)) {
if (item-sum[1])
return check_sum (target, sha1sum, (const char*)(intptr_t)item-sum[1],
buf_name);
if (item-sum[0])
return check_sum (target, md5sum, (const char*)(intptr_t)item-sum[0],
buf_name);
} else {
return check_sum (target, md5sum, (const char*)item-sum,
buf_name);
}
This is an API and ABI breakage requiring a rename to
libdebian-installter5[-dev].
Alternatively change the declaration of struct di_release_file to
struct di_release_file
{
union
{
char *filename; /** filename */
di_rstring key; /** @internal */
};
unsigned int size;/** size */
char *sum;/** checksum, currently md5 or
sha */
char *sums[2]; /** checksums, currently md5
and sha1 */
};
filling both sum and sums.
It would be nice to also have some define declared so sources can
check if di_release_file.sums is available. Something simpler than
having to compare the LIBDI_VERSION like
#define DEBIAN_INSTALLER__RELEASE_MULTISUM 1
#define DEBIAN_INSTALLER__RELEASE_SUM0 md5
#define DEBIAN_INSTALLER__RELEASE_SUM1 sha1
MfG
Goswin
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages libdebian-installer4 depends on:
ii libc6 2.13-32
libdebian-installer4 recommends no packages.
libdebian-installer4 suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
On Wed, Jun 06, 2012 at 04:22:11PM +0200, Goswin von Brederlow wrote:
This is an API and ABI breakage requiring a rename to
libdebian-installter5[-dev].
This is only an API breakage and I will not do anything about it.
Bastian
--
What kind of love is that? Not to be loved; never to have shown love.
-- Commissioner Nancy Hedford, Metamorphosis,
stardate 3219.8
---End Message---
Bug#677467: gnucash is built with all patches reverted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Source: gnucash Version: 1:2.4.10-3 Severity: serious Am 13.06.2012 22:49, schrieb Sébastien Villemot: with the upload of libaqbanking 5.0.24-1 I broke the gnucash package. Hence I uploaded gnucash 1:2.4.10-3 with the changes currently in our Git repository. I just realized that something went wrong there. There is a file called debian/patches/debian-changes-1:2.4.10-3 that sneaked into the source package, while not being in git. This patch basically reverts several of the other patches (FTBFS on Hurd, missing manpages). Micha: do you confirm that this is a mistake? If yes, we should just upload a version 1:2.4.10-4 just like that in git, and preferably before 1:2.4.10-3 hits testing. This is indeed a bug. So, let's track it in the bug tracker (done) with severity serious, so it will prevent testing migration immediately. I will take care of fixing it as soon as possible. Regards, Micha -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJP2ZAWAAoJEOpsprlRuFE5KoMP/05Yl+FPP+CnHjIjxm92ovLM FagwAjnPSVfQbmdnjMbAzTCdUjcEXATFRLSV4s0xbvBzHyvDwjHxh9AJeL5v9ldg wmqdtfXtVOm0R414sCY94OsZbC0OAS+8VfKFbjizvSJz0tCyBghwcwpzMdf435+k 6ymRSsbcxtHhzt3766gejZX8iqhgd5/2hBwOHoR82xcPGE9tFVl+SUSYku0vfCbE G95Pvevcmrrq0WHtS08XauP7E/wrgA35TcCyHd0nhPDKbYx++FoQG5LAK6hbZ3zg bgXca7HI0Y00drUEX7EVgrJzSK8CuR5HW9Kpd/iQ7zn5wpKy6JHraooamY+gl5S+ dzCBI0KO3sLTzCN7Xg7eW9/YD57XOdwrXtxomsuOTC11b39lEm9H5B6kNbnCUZxN U9D1O6GvCL7p+x5e6K1qVpWzTDkKG9V64GZERaaGKMsfRSffgBeqRgHRDLopF9BS JvTfZFLVtqOYSotLoznoKSagFcgMJPI6qaMDRN3Gwenmmg3O3VRTKII2fAkV0x1c Rci0YIcQLQikizhrbQf9vHKp5ZJEGnMM4jYB0ad6GsWNMy6oWyMDLBxEI6MuSBl3 41UgRL1r1+hjILPhosjHYkYt++0I8gGPrZap5j+qrQMBCgBM2tlohhC6CspEe0+5 TCllMb/kKn7oZVSXUHX+ =OPhl -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#672842: goffice: binNMUs are not installable
Processing commands for cont...@bugs.debian.org: severity 672842 serious Bug #672842 [goffice] goffice: binNMUs are not installable Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 672842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672842 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#674504: About debian bugs #674504
On Tue, Jun 12, 2012 at 10:10 AM, Mehdi Abaakouk sil...@sileht.net wrote: Hi swift-im maintainers, You have recently uploaded a new package swift-im and introduced a small issue, but unfortunately marked as serious and RC by debian policy bots. So, to quickly solve this issue, we need to rename the binary swift to swift-im And to save your time, please find attached a proposed patch to solve this issue. Thanks very much - we fixed the problem upstream and have a new package due to be uploaded shortly. /K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Thursday 14 June 08:03:11 UTC 2012 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: a href=http://packages.qa.debian.org/wine-unstable;wine-unstable/a tags 677317 + pending Bug #677317 [src:wine-unstable] Maintainer address bounces Added tag(s) pending. # Source package in NEW: php-cas tags 495542 + pending Bug #495542 [wnpp] ITP: php-cas -- Central Authentication Service client library in php Added tag(s) pending. # Source package in NEW: r-bioc-biocgenerics tags 677311 + pending Bug #677311 [wnpp] ITP: r-bioc-biocgenerics -- generic functions for Bioconductor Added tag(s) pending. # Source package in NEW: xserver-xorg-video-modesetting tags 677425 + pending Bug #677425 [wnpp] ITP: xserver-xorg-video-modesetting -- X.Org X server -- Generic modesetting driver Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 495542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495542 677311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677311 677317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677317 677425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677425 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#676885: marked as done (libatlas3-base: Illegal instruction in dgetrf)
Your message dated Thu, 14 Jun 2012 09:02:16 +
with message-id e1sf5ww-0004mi...@franck.debian.org
and subject line Bug#676885: fixed in atlas 3.8.4-7
has caused the Debian Bug report #676885,
regarding libatlas3-base: Illegal instruction in dgetrf
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.)
--
676885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libatlas3-base
Version: 3.8.4-6
Severity: grave
Justification: renders package unusable
I have a Core2 machine that doesn't have the latest FMA4 instructions. My
understanding that the libatlas3-base package from unstable shouldn't be doing
anything fancy and potentially cpu-specific unless the user rebuilds this
package themselves. I have the following trivial program:
#include stdio.h
int dgetrf_(int *m, int *n, double *a, int *lda, int *ipiv, int *info);
int main(void)
{
int three = 3;
int ipiv[3];
int info;
double A[9] = {1,2,5,2,3,4,5,4,3};
dgetrf_(three, three, A, three,
ipiv, info);
printf(info: %d\n, info);
return 0;
}
Session that shows the issue, with some useful diagnostics:
dima@shorty:/tmp$ gcc-4.7 -llapack -o tst tst.c
dima@shorty:/tmp$ ./tst
zsh: illegal hardware instruction (core dumped) ./tst
dima@shorty:/tmp$ ldd tst
linux-vdso.so.1 = (0x7fff3bbff000)
liblapack.so.3 = /usr/lib/liblapack.so.3 (0x7f3ff4f8e000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f3ff4c07000)
libblas.so.3 = /usr/lib/libblas.so.3 (0x7f3ff453d000)
libgfortran.so.3 = /usr/lib/x86_64-linux-gnu/libgfortran.so.3
(0x7f3ff4227000)
libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f3ff4011000)
libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f3ff3df4000)
libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f3ff3b72000)
/lib64/ld-linux-x86-64.so.2 (0x7f3ff5caf000)
libquadmath.so.0 = /usr/lib/x86_64-linux-gnu/libquadmath.so.0
(0x7f3ff393d000)
dima@shorty:/tmp$ update-alternatives --display liblapack.so.3
liblapack.so.3 - auto mode
link currently points to /usr/lib/atlas-base/atlas/liblapack.so.3
/usr/lib/atlas-base/atlas/liblapack.so.3 - priority 35
slave liblapack.so.3gf: /usr/lib/atlas-base/atlas/liblapack.so.3
/usr/lib/lapack/liblapack.so.3 - priority 10
slave liblapack.so.3gf: /usr/lib/lapack/liblapack.so.3
Current 'best' version is '/usr/lib/atlas-base/atlas/liblapack.so.3'.
dima@shorty:/tmp$ dpkg -S /usr/lib/atlas-base/atlas/liblapack.so.3
libatlas3-base: /usr/lib/atlas-base/atlas/liblapack.so.3
dima@shorty:/tmp$ dpkg -l libatlas3-base
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Description
+++-===-===-==
ii libatlas3-base 3.8.4-6 Automatically Tuned Linear
Algebra Software, generic shared
dima@shorty:/tmp$ gdb tst core
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /tmp/tst...(no debugging symbols found)...done.
[New LWP 30474]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by `./tst'.
Program terminated with signal 4, Illegal instruction.
#0 0x7fa03d281bb7 in ATL_dgetrfC () from /usr/lib/liblapack.so.3
(gdb) disass
Dump of assembler code for function ATL_dgetrfC:
0x7fa03d281950 +0: mov%rbx,-0x30(%rsp)
0x7fa03d281955 +5: mov%rbp,-0x28(%rsp)
..
0x7fa03d281bb3 +611: lea(%r12,%rax,8),%rbx
= 0x7fa03d281bb7 +615: vmovsd (%rbx),%xmm1
0x7fa03d281bbb +619: vucomisd 0x996ced(%rip),%xmm1#
0x7fa03dc188b0
0x7fa03d281bc3 +627: mov0x38(%rsp),%r10d
..
dima@shorty:/tmp$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family
Processed: Re: Bug#676874: ghc fails to configure after install (update-alternatives priority out of range)
Processing commands for cont...@bugs.debian.org: severity 676970 serious Bug #676970 [ghc] ghc: update-alternatives priority out of range Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 676970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676970 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#676970: Bug#676874: ghc fails to configure after install (update-alternatives priority out of range)
Dear Cyril, Am Donnerstag, den 14.06.2012, 11:04 +0200 schrieb Cyril Brulebois: severity 676970 serious thanks Jonathan Nieder jrnie...@gmail.com (10/06/2012): Cloning and assigning to ghc. If the way ABI is tracked in ghc is causing valid bugs to be thrown away, that's a problem, in my opinion. Indeed. And since the package isn't installable right now, bumping severity to serious. I’m really not sure what this is about. Who is throwing bugs away (and what does that mean anyways to throw a bug away?)? All I am saying is that at this point of the release cycle, I am very reluctant to do an upload of GHC. I’m sure those of the release team who currently manage the transition will agree that it would be unwise now. I am not saying that I won’t fix GHC (or rather, adjust GHC to changed semantics in dpkg) at all; quite contrary I did announce that I’ll do it on the next upload. It there a deeper misunderstanding here? An in case this bug now hinders the migration that mehdi set up for today: I think this bug can be ignored for wheezy right now, as the dpkg version in wheezy does _not_ make ghc fail to install. We just should make sure that before dpkg 1.16.4 it is turned the error into a warning, e.g. 676874 is closed. (Doesn’t this make 676874 RC?) That fix is required anyways as wheezy’s dpkg needs to be able to install packages from squeeze. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#677479: [fabric] paramiko incompatiblity
Processing commands for cont...@bugs.debian.org: severity 677479 serious Bug #677479 [fabric] [fabric] paramiko incompatiblity Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 677479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677479 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#677485: auto-multiple-choice-common: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2)
Package: auto-multiple-choice-common Version: 1.1.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails As putting files into /usr/local is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. From the attached log (scroll to the bottom...): 0m53.8s ERROR: FAIL: Package purging left files on system: /usr/local/share/texmf/not owned /usr/local/share/texmf/ls-Rnot owned This problem is usually caused by running mktexlsr (or texhash) without path arguments from a maintainer script. The recommende solution is to switch to use dh_installtex and have this generate most (or perhaps even all) of the maintainer scripts content. Otherwise run mktexlsr with the tree as argument where the package installs its files, which is usually mktexlsr /usr/share/texmf Please have a look at the Debian-TeX-Policy (in the tex-common package) for the current practice of handling TeX packages. For further TeX packaging related questions contact debian-tex-ma...@lists.debian.org cheers, Andreas auto-multiple-choice-common_1.1.0-2.log.gz Description: GNU Zip compressed data
Bug#677486: Multiple security issues
Package: openjdk-7 Severity: grave Tags: security Multiple security issues have been fixed in the latest Java update round: http://www.oracle.com/technetwork/topics/security/javacpujun2012-1515912.html#PatchTable 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#677487: Multiple security issues
Package: openjdk-6 Version: Multiple security issues Severity: grave Tags: security Multiple security issues have been fixed in the latest Java update round: http://www.oracle.com/technetwork/topics/security/javacpujun2012-1515912.html#PatchTable 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#676970: Bug#676874: ghc fails to configure after install (update-alternatives priority out of range)
Hi, Am Donnerstag, den 14.06.2012, 11:20 +0200 schrieb Joachim Breitner: An in case this bug now hinders the migration that mehdi set up for today: I think this bug can be ignored for wheezy right now, as the dpkg version in wheezy does _not_ make ghc fail to install. I adjusted the version range of this bug to historic reality, so that britney knows that migrating ghc does not introduce new bugs. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#627944: python-pyhyphen: doesn't work out-of-the-box with hyphen-* packages
Followup-For: Bug #627944 Package: python-pyhyphen Version: 1.0~beta1-2 This bug happens in my system too. Even loading another hyphen dictionary (e.g., it) leads to the same error. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages python-pyhyphen depends on: ii libc6 2.13-33 ii python 2.7.3~rc2-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 python-pyhyphen recommends no packages. python-pyhyphen suggests no packages. -- no debconf information -- Alberto Quattrini Li -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677494: sh: 1: file: not found
Package: ohcount Version: 3.0.0-6 Severity: serious Justification: Policy 3.5 Hi, It appears that «ohcount» package is missing a dependency on «file»: | sh: 1: file: not found The package was installed in a clean wheezy chroot. (it might be nice to push the segfault patch in squeeze) Thanks -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') 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 Versions of packages ohcount depends on: ii libc62.13-33 ii libdifflcs-ruby 1.1.3-1 ii libpcre3 1:8.30-5 ii ruby 4.9 ii ruby-diff-lcs [libdifflcs-ruby] 1.1.3-1 ii ruby1.8 [ruby] 1.8.7.358-4 ohcount recommends no packages. Versions of packages ohcount suggests: pn ohcount-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677499: chromium: Crashes often when entering text in the URL bar
Package: chromium Version: 20.0.1132.21~r139451-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, * What led up to the situation? Entering any text into the URL bar of Chromium, Chromium crashes completely. Not every time, but way too often per day. * What exactly did you do (or not do) that was effective (or ineffective)? Just started entering text in the URL bar. * What was the outcome of this action? Crash. * What outcome did you expect instead? To have it working. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-4.dmz.1-liquorix-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 20.0.1132.21~r139451-3 ii gconf-service 3.2.5-1 ii libasound2 1.0.25-3 ii libatk1.0-0 2.4.0-2 ii libbz2-1.0 1.0.6-3 ii libc6 2.13-33 ii libcairo2 1.12.2-2 ii libcups21.5.3-1 ii libdbus-1-3 1.6.0-1 ii libevent-2.0-5 2.0.19-stable-3 ii libexpat1 2.1.0-1 ii libflac81.2.1-6 ii libfontconfig1 2.9.0-6 ii libfreetype62.4.9-1 ii libgcc1 1:4.7.0-12 ii libgconf-2-43.2.5-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgnome-keyring0 3.4.1-1 ii libgtk2.0-0 2.24.10-1 ii libjpeg88d-1 ii libnspr42:4.9-3 ii libnss3 2:3.13.4-3 ii libnss3-1d 2:3.13.4-3 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-3 ii libspeex1 1.2~rc1-6 ii libstdc++6 4.7.0-12 ii libudev0175-3.1 ii libwebp20.1.3-3 ii libx11-62:1.4.99.901-2 ii libxcomposite1 1:0.4.3-2 ii libxext62:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.8.0+dfsg1-3 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-12+b1 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zlib1g 1:1.2.7.dfsg-11 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670413: marked as done (samba4: fails to install: ProvisioningError: Existing smb.conf does not have a [netlogon] share, but you are configuring a DC.)
Your message dated Thu, 14 Jun 2012 11:18:21 + with message-id e1sf84d-0006lb...@franck.debian.org and subject line Bug#670413: fixed in samba4 4.0.0~beta1+dfsg1-1 has caused the Debian Bug report #670413, regarding samba4: fails to install: ProvisioningError: Existing smb.conf does not have a [netlogon] share, but you are configuring a DC. 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.) -- 670413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: samba4 Version: 4.0.0~alpha19+dfsg1-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package samba4. (Reading database ... 8688 files and directories currently installed.) Unpacking samba4 (from .../samba4_4.0.0~alpha19+dfsg1-6_amd64.deb) ... Setting up samba4 (4.0.0~alpha19+dfsg1-6) ... Administrator password will be set randomly! Unknown parameter encountered: max log size Ignoring unknown parameter max log size Unknown parameter encountered: syslog Ignoring unknown parameter syslog Unknown parameter encountered: unix password sync Ignoring unknown parameter unix password sync Unknown parameter encountered: passwd program Ignoring unknown parameter passwd program Unknown parameter encountered: pam password change Ignoring unknown parameter pam password change Unknown parameter encountered: valid users Ignoring unknown parameter valid users Unknown parameter encountered: guest ok Ignoring unknown parameter guest ok Unknown parameter encountered: guest ok Ignoring unknown parameter guest ok Unknown parameter encountered: max log size Ignoring unknown parameter max log size Unknown parameter encountered: syslog Ignoring unknown parameter syslog Unknown parameter encountered: unix password sync Ignoring unknown parameter unix password sync Unknown parameter encountered: passwd program Ignoring unknown parameter passwd program Unknown parameter encountered: pam password change Ignoring unknown parameter pam password change Unknown parameter encountered: valid users Ignoring unknown parameter valid users Unknown parameter encountered: guest ok Ignoring unknown parameter guest ok Unknown parameter encountered: guest ok Ignoring unknown parameter guest ok Looking up IPv4 addresses Looking up IPv6 addresses No IPv6 address will be assigned Setting up share.ldb Setting up secrets.ldb Setting up the registry Setting up the privileges database Setting up idmap db Setting up SAM db Setting up sam.ldb partitions and settings Setting up sam.ldb rootDSE Pre-loading the Samba 4 and AD schema ProvisioningError: Existing smb.conf does not have a [netlogon] share, but you are configuring a DC. Please either remove /etc/samba/smb.conf or see the template at /usr/share/samba/setup/provision.smb.conf.dc dpkg: error processing samba4 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: samba4 cheers, Andreas samba4_4.0.0~alpha19+dfsg1-6.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: samba4 Source-Version: 4.0.0~beta1+dfsg1-1 We believe that the bug you reported is fixed in the latest version of samba4, which is due to be installed in the Debian FTP archive: libdcerpc-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc-dev_4.0.0~beta1+dfsg1-1_amd64.deb libdcerpc-server-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc-server-dev_4.0.0~beta1+dfsg1-1_amd64.deb libdcerpc-server0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc-server0_4.0.0~beta1+dfsg1-1_amd64.deb libdcerpc0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc0_4.0.0~beta1+dfsg1-1_amd64.deb libgensec-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libgensec-dev_4.0.0~beta1+dfsg1-1_amd64.deb libgensec0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libgensec0_4.0.0~beta1+dfsg1-1_amd64.deb libndr-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libndr-dev_4.0.0~beta1+dfsg1-1_amd64.deb libndr-standard-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libndr-standard-dev_4.0.0~beta1+dfsg1-1_amd64.deb libndr-standard0_4.0.0~beta1+dfsg1-1_amd64.deb to
Bug#674918: marked as done (samba4: FTBFS on amd64)
Your message dated Thu, 14 Jun 2012 11:18:21 + with message-id e1sf84d-0006lh...@franck.debian.org and subject line Bug#674918: fixed in samba4 4.0.0~beta1+dfsg1-1 has caused the Debian Bug report #674918, regarding samba4: FTBFS on amd64 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.) -- 674918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: samba4 Severity: serious Version: 4.0.0~alpha19+dfsg1-7 The current version of samba4 doesn't build anymore. It fails to configure with the following error: Checking for system hx509 : not found Checking for header hx509.h : no ERROR: System library hx509 of version 0.0.0 not found, and bundling disabled This problems seems to be caused by the latest version of heimdal. /usr/include/heimdal/rfc2459_asn1.h includes a reference to config.h, which doesn't exist. The version in testing is fine. Diff between both versions: --- x/usr/include/heimdal/rfc2459_asn1.h2012-03-29 02:09:09.0 +0200 +++ /usr/include/heimdal/rfc2459_asn1.h 2012-05-03 20:56:44.0 +0200 @@ -4,6 +4,9 @@ #ifndef __rfc2459_asn1_h__ #define __rfc2459_asn1_h__ +#ifdef HAVE_CONFIG_H +#include config.h +#endif #include stddef.h #include time.h Ivo ---End Message--- ---BeginMessage--- Source: samba4 Source-Version: 4.0.0~beta1+dfsg1-1 We believe that the bug you reported is fixed in the latest version of samba4, which is due to be installed in the Debian FTP archive: libdcerpc-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc-dev_4.0.0~beta1+dfsg1-1_amd64.deb libdcerpc-server-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc-server-dev_4.0.0~beta1+dfsg1-1_amd64.deb libdcerpc-server0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc-server0_4.0.0~beta1+dfsg1-1_amd64.deb libdcerpc0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libdcerpc0_4.0.0~beta1+dfsg1-1_amd64.deb libgensec-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libgensec-dev_4.0.0~beta1+dfsg1-1_amd64.deb libgensec0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libgensec0_4.0.0~beta1+dfsg1-1_amd64.deb libndr-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libndr-dev_4.0.0~beta1+dfsg1-1_amd64.deb libndr-standard-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libndr-standard-dev_4.0.0~beta1+dfsg1-1_amd64.deb libndr-standard0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libndr-standard0_4.0.0~beta1+dfsg1-1_amd64.deb libndr0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libndr0_4.0.0~beta1+dfsg1-1_amd64.deb libparse-pidl-perl_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libparse-pidl-perl_4.0.0~beta1+dfsg1-1_amd64.deb libregistry-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libregistry-dev_4.0.0~beta1+dfsg1-1_amd64.deb libregistry0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libregistry0_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-credentials-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-credentials-dev_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-credentials0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-credentials0_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-hostconfig-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-hostconfig-dev_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-hostconfig0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-hostconfig0_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-policy-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-policy-dev_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-policy0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-policy0_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-util-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-util-dev_4.0.0~beta1+dfsg1-1_amd64.deb libsamba-util0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamba-util0_4.0.0~beta1+dfsg1-1_amd64.deb libsamdb-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamdb-dev_4.0.0~beta1+dfsg1-1_amd64.deb libsamdb0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsamdb0_4.0.0~beta1+dfsg1-1_amd64.deb libsmbclient-raw-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsmbclient-raw-dev_4.0.0~beta1+dfsg1-1_amd64.deb libsmbclient-raw0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libsmbclient-raw0_4.0.0~beta1+dfsg1-1_amd64.deb libtorture-dev_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libtorture-dev_4.0.0~beta1+dfsg1-1_amd64.deb libtorture0_4.0.0~beta1+dfsg1-1_amd64.deb to main/s/samba4/libtorture0_4.0.0~beta1+dfsg1-1_amd64.deb python-samba_4.0.0~beta1+dfsg1-1_amd64.deb to
Processed: found 676094 in 3.3.1-1
Processing commands for cont...@bugs.debian.org: found 676094 3.3.1-1 Bug #676094 [src:geos] geos: FTBFS: geos_wrap.cxx:856:18: fatal error: ruby.h: No such file or directory Marked as found in versions geos/3.3.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 676094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676094 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#676970: ghc fails to configure after install (update-alternatives priority out of range)
Joachim Breitner wrote: I’m really not sure what this is about. Who is throwing bugs away (and what does that mean anyways to throw a bug away?)? Sorry, my comment was very cryptic. I don't think any malice was intended or anything --- I am guessing you simply forgot to clone bug 676874 before reassigning it to dpkg. But your explanation when doing so didn't say I am making this change in ghc in the next upload. I had no idea that you were making that change in ghc in the next upload, so I cloned and reassigned back as a reminder. No opinion about the severity here. Another bug that gave the impression of being rejected for transition reasons is bug 673081: | I’d rather like to be able to transition the current set of Haskell | packages to testing first and then, if there is time before the freeze, | tackle this bug. For that, the severity needs to be lowered, though, as | otherwise nothing will migrate. That is not what severities are meant to signify. Sorry for the confusion, and hoping that clarifies, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677499: chromium: Crashes often when entering text in the URL bar
forcemerge 676636 677499 quit Hi John, John Louis wrote: Entering any text into the URL bar of Chromium, Chromium crashes completely. Not every time, but way too often per day. Thanks for reporting. Fixed in 20.0.1132.27~r140692-2, hopefully. I highly recommend apt-listbugs so you can be warned about the next such serious bug before installing. Sorry for the trouble and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: chromium: Crashes often when entering text in the URL bar
Processing commands for cont...@bugs.debian.org:
forcemerge 676636 677499
Bug #676636 {Done: Giuseppe Iuculano iucul...@debian.org} [chromium] segfault
repeatedly when using the omnibox (in sqlite code?)
Bug #677499 [chromium] chromium: Crashes often when entering text in the URL bar
Set Bug forwarded-to-address to 'http://crbug.com/122525'.
Severity set to 'serious' from 'grave'
Marked Bug as done
Marked as fixed in versions chromium-browser/20.0.1132.27~r140692-2.
Marked as found in versions chromium-browser/20.0.1132.27~r140692-1.
Added tag(s) upstream and patch.
Merged 676636 677499
quit
Stopping processing here.
Please contact me if you need assistance.
--
676636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676636
677499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677499
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#676970: ghc fails to configure after install (update-alternatives priority out of range)
Joachim Breitner wrote: An in case this bug now hinders the migration that mehdi set up for today: The severity does seem inflated. Luckily it doesn't hinder migration since it is not a new bug (debbugs shows the version in testing as already affected). [...] (Doesn’t this make 676874 RC?) I think so, yes. Though it seems both will be fixed so soon that it is hard for me to care much. Thanks again and sorry for the fuss. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627944: python-pyhyphen: doesn't work out-of-the-box with hyphen-* packages
The only way to make it works is to modify the code, for correct pointing to the correct hyphen dictionaries path and files. Specifically, in config.py, you should modify 1: default_dict_path = u'$path' - default_dict_path = u'/usr/share/hyphen' basically the correct path pointing to the directory where hyphen dictionaries are and in __init__.py 129: else: file_name = language - else: file_name = u'/hyph_' + language + u'.dic' If you want, I can provide you a patch to solve the problem in the package. I don't know if this is an upstream problem, as every OS handles differently the directories where hyphen dictionaries are stored and it is not said that environment variables, first of all, contain such a path, and secondly, are the same in every OS. Alberto Quattrini Li On Thu, Jun 14, 2012 at 11:53 AM, Alberto Quattrini Li alberto.quattrin...@gmail.com wrote: Followup-For: Bug #627944 Package: python-pyhyphen Version: 1.0~beta1-2 This bug happens in my system too. Even loading another hyphen dictionary (e.g., it) leads to the same error. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages python-pyhyphen depends on: ii libc6 2.13-33 ii python 2.7.3~rc2-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 python-pyhyphen recommends no packages. python-pyhyphen suggests no packages. -- no debconf information -- Alberto Quattrini Li -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650806: Pending fixes for bugs in the libperl5i-perl package
tag 650806 + pending thanks Some bugs in the libperl5i-perl package are closed in revision 8019128693e5625b88614e64fd8623c3334c3d53 in branch 'master' by Dominique Dumont The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libperl5i-perl.git;a=commitdiff;h=8019128 Commit message: test: work around mips issue (Closes: #650806) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libperl5i-perl package
Processing commands for cont...@bugs.debian.org: tag 650806 + pending Bug #650806 [src:libperl5i-perl] libperl5i-perl: FTBFS on mips: Failed test 'No autoflush' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 650806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650806 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#675863: accountsservice: makes gdm-simple-greeter crash
Should this bug be marked fixed in version 0.6.21-4 if this is same bug as #673185 ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555168: [Traduc] Bug#555168: Unclear license situation for (e)glibc locales provided by you
Le Mer 13 juin 2012 06:53, Christian PERRIER a écrit : Quoting Helge Kreutzmann (deb...@helgefjell.de): Hello, you are listed as contact person/author of the following locale: fr_FR I think Keld Simonsen's name is mentioned as the locale was based on one he wrote. tra...@traduc.org is a collective address (see http://traduc.org). Adding the internal organisational list to the CC field so that representatives of the traduc.org can give a stance in name of the organization. PS: coucou, traduc.org..:-)...Bon, en gros, vous avez sûrement compris mais c'est vrai qu'il y a une action en cours actuellement, dans Debian, pour clarifier la licence des locales où celle-ci n'est pas claire. Je n'ai évidemment aucun doute sur les intentions de traduc.org par rapport à la locale fr_FR (utiliser une licence libre), mais il faut que quelqu'un confirme cela, évidemment. Ce serait quand même un peu ballot que Debian retire la locale française de la libc. Je serais largement au chomage..:-) The fr_FR was taken over by traduc.org in March 2008, and the update of this file have been discussed on the traduc mail list from January to March 2008 (http://listes.traduc.org/pipermail/traduc/). At that time, the license was not discussed, as we were under the impression this file was part of the glibc and distributed under the same license. The original author of this file is Keld Jørn Simonsen. Provided that Keld Jørn Simonsen agree with this, we would be very happy to see this file officially put under a Free license. Using the same license as the glibc would be fine for us. Hope that helps. Best Regards. -- Jean-Philippe Guérard http://tigreraye.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677202: biber packages version 0.9.9+git2012426-3 is beta and requires beta version of biblatex
Dear all, In a hope to accelerate the process I have uploaded my packages of biber and biblatex, together with the existing ones in this github repo. https://github.com/mtelleria/biber-biblatex-debian-packaging There you can find, with their respective tags, the upstream and full dirs of: biber 0.9.9 biber 1.0beta (the same as the one existing in Sid but with the correct version number). biblatex 1.7 biblatex 2.0beta There might be some lintian errors left but I think that they could be dealt with later. Regards, Miguel On Thu, 14 Jun 2012 08:26:56 +0800 Danai SAE-HAN wrote: (Adding the Perl group in CC.) Hi I am currently in Beijing but return home this Sunday. I think downgrading biber is the best option. If that is too late, I am open to support a NMU. Sorry for the inconvenience. BR -- (O-O) ---oOO-(_)-OOo- Miguel TELLERIA DE ESTEBAN http://www.mtelleria.com Email: miguel at mtelleria.com Tel GSM: +34 650 801098 Tel Fix: +34 942 280174 Miembro de http://www.linuca.orgMembre du http://www.bxlug.be ¿Usuario captivo o libre?http://www.obtengalinux.org/windows/ Free or captive user?http://www.getgnulinux.org/windows/ --- signature.asc Description: PGP signature
Bug#676970: [Pkg-haskell-maintainers] Bug#676970: ghc fails to configure after install (update-alternatives priority out of range)
Hi, Am Donnerstag, den 14.06.2012, 06:29 -0500 schrieb Jonathan Nieder: Joachim Breitner wrote: An in case this bug now hinders the migration that mehdi set up for today: The severity does seem inflated. Luckily it doesn't hinder migration since it is not a new bug (debbugs shows the version in testing as already affected). [...] (Doesn’t this make 676874 RC?) I think so, yes. Though it seems both will be fixed so soon that it is hard for me to care much. Thanks again and sorry for the fuss. thanks for the clarification and I’m glad that we do agree after all :-) Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#677516: gnome-shell-timer: Does not work with Gnome Shell 3.4
Package: gnome-shell-timer Version: 0.0.20120103+gitc7b8d8f-1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The extension refuses to load under Gnome Shell 3.4, because it is marked as compatible with Gnome 3.2 only. The fix seems as simple as this upstream commit: https://github.com/olebowle/gnome-shell-timer/commit/bde3fd2492c847113f200a7485864c5a7916f56e Thanks for your work, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell-timer depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-1 ii gnome-shell 3.4.1-5 ii python 2.7.2-10 gnome-shell-timer recommends no packages. gnome-shell-timer suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637622: config file modifiable by users in /var/lib/dtc
I think this is rather debatable. Perhaps some of the config files could be replaced by things like apache2/conf.d sections that calculated things from the dtc database but it wouldn't be as simple to debug. However, I think there is one file which is troublesome here. I think most users should modify /var/lib/dtc/etc/quotawarnmsg to add some customisation (like the name of the server owner maybe) that makes it easier to distinguish a real warning from a phishing attack. When /var/lib/dtc/etc/quotawarnmsg is emailed, it does not use the header or signature from /etc/dtc/ so it is rather for users to dismiss or attackers to spoof. Could that one be moved to /etc/dtc, please? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/ -- 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#677431: Symbol's function definition is void: --post-body--70277
Processing commands for cont...@bugs.debian.org: severity 677431 wishlist Bug #677431 [w3m-el-snapshot] Symbol's function definition is void: --post-body--70277 Severity set to 'wishlist' from 'grave' tags 677431 + pending Bug #677431 [w3m-el-snapshot] Symbol's function definition is void: --post-body--70277 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 677431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677431 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: Re: ruby-activerecord-3.2: CVE-2012-2660 unsafe query generation risk in Ruby on Rails when Active Record is used
Processing commands for cont...@bugs.debian.org: severity 675429 grave Bug #675429 [ruby-activerecord-3.2] ruby-activerecord-3.2: CVE-2012-2660 unsafe query generation risk in Ruby on Rails when Active Record is used Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 675429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675429 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: Reassigning #612439 (lvm2: lvconvert --merge breaks Logical Volumes) to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 612439 linux-2.6 2.6.32-45 Bug #612439 [lvm2] lvconvert --merge breaks Logical Volumes Bug reassigned from package 'lvm2' to 'linux-2.6'. No longer marked as found in versions lvm2/2.02.66-5. Ignoring request to alter fixed versions of bug #612439 to the same values previously set Bug #612439 [linux-2.6] lvconvert --merge breaks Logical Volumes There is no source info for the package 'linux-2.6' at version '2.6.32-45' with architecture '' Unable to make a source version for version '2.6.32-45' Marked as found in versions 2.6.32-45. severity 612439 grave Bug #612439 [linux-2.6] lvconvert --merge breaks Logical Volumes Severity set to 'grave' from 'normal' kthxbye Stopping processing here. Please contact me if you need assistance. -- 612439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612439 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#676342: marked as done (freemedforms-emr: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/freemedforms/sql/account/insurances_fr_FR.csv)
Your message dated Thu, 14 Jun 2012 14:47:56 + with message-id e1sfbl2-0003wv...@franck.debian.org and subject line Bug#676342: fixed in freemedforms-project 0.7.4-2 has caused the Debian Bug report #676342, regarding freemedforms-emr: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/freemedforms/sql/account/insurances_fr_FR.csv 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.) -- 676342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: freemedforms-emr Version: 0.7.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite files that are owned by other packages without declaring a Breaks/Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace freemedforms-freedata 0.7.1-1 (using .../freemedforms-freedata_0.7.4-1_all.deb) ... Unpacking replacement freemedforms-freedata ... dpkg: error processing /var/cache/apt/archives/freemedforms-freedata_0.7.4-1_all.deb (--unpack): trying to overwrite '/usr/share/freemedforms/sql/account/insurances_fr_FR.csv', which is also in package freemedforms-emr-resources 0.7.1-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas freemedforms-emr_0.7.4-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: freemedforms-project Source-Version: 0.7.4-2 We believe that the bug you reported is fixed in the latest version of freemedforms-project, which is due to be installed in the Debian FTP archive: freeaccount_0.7.4-2_amd64.deb to main/f/freemedforms-project/freeaccount_0.7.4-2_amd64.deb freediams-doc-en_0.7.4-2_all.deb to main/f/freemedforms-project/freediams-doc-en_0.7.4-2_all.deb freediams-doc-fr_0.7.4-2_all.deb to main/f/freemedforms-project/freediams-doc-fr_0.7.4-2_all.deb freediams_0.7.4-2_amd64.deb to main/f/freemedforms-project/freediams_0.7.4-2_amd64.deb freemedforms-common-resources_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-common-resources_0.7.4-2_all.deb freemedforms-emr-doc-en_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-emr-doc-en_0.7.4-2_all.deb freemedforms-emr-doc-fr_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-emr-doc-fr_0.7.4-2_all.deb freemedforms-emr-resources_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-emr-resources_0.7.4-2_all.deb freemedforms-emr_0.7.4-2_amd64.deb to main/f/freemedforms-project/freemedforms-emr_0.7.4-2_amd64.deb freemedforms-freedata_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-freedata_0.7.4-2_all.deb freemedforms-i18n_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-i18n_0.7.4-2_all.deb freemedforms-libs_0.7.4-2_amd64.deb to main/f/freemedforms-project/freemedforms-libs_0.7.4-2_amd64.deb freemedforms-project_0.7.4-2.debian.tar.gz to main/f/freemedforms-project/freemedforms-project_0.7.4-2.debian.tar.gz freemedforms-project_0.7.4-2.dsc to main/f/freemedforms-project/freemedforms-project_0.7.4-2.dsc freemedforms-project_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-project_0.7.4-2_all.deb freemedforms-theme_0.7.4-2_all.deb to main/f/freemedforms-project/freemedforms-theme_0.7.4-2_all.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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated freemedforms-project 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, 14 Jun 2012 15:18:52 +0200 Source: freemedforms-project Binary: freemedforms-project freemedforms-theme freemedforms-i18n freemedforms-common-resources freemedforms-emr-resources freemedforms-freedata freemedforms-emr-doc-en freemedforms-emr-doc-fr freediams-doc-en freediams-doc-fr freemedforms-libs freemedforms-emr freediams freeaccount Architecture: source all
Processed: tagging 451628
Processing commands for cont...@bugs.debian.org: #these tags look bogus now tags 451628 - lenny sid Bug #451628 [ftp.debian.org] Packages might enter the archive from security without source Bug #497178 [ftp.debian.org] ftp.debian.org: Should not accept changes not including orig not in archive Removed tag(s) sid and lenny. Removed tag(s) sid and lenny. thanks Stopping processing here. Please contact me if you need assistance. -- 451628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451628 497178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497178 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#650806: marked as done (libperl5i-perl: FTBFS on mips: Failed test 'No autoflush')
Your message dated Thu, 14 Jun 2012 15:47:10 + with message-id e1sfcgm-0007yj...@franck.debian.org and subject line Bug#650806: fixed in libperl5i-perl 2.9.1-2 has caused the Debian Bug report #650806, regarding libperl5i-perl: FTBFS on mips: Failed test 'No autoflush' 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.) -- 650806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libperl5i-perl Version: 2.9.0-1 Severity: serious Justification: fails to build from source User: debian-m...@lists.debian.org Usertags: mips libperl5i-perl FTBFS on mips: |dh_auto_test | cc -I/usr/lib/perl/5.14/CORE -fPIC -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -o bin/perl5i.o bin/perl5i.c | cc -fstack-protector -L/usr/local/lib -o bin/perl5i bin/perl5i.o | t/ARGV.t . ok | t/ARGV_twice.t ... ok | t/CLASS.t ok | | # Failed test 'No autoflush' | # at t/Child.t line 93. | # Looks like you failed 1 test of 19. | t/Child.t | Dubious, test returned 1 (wstat 256, 0x100) | Failed 1/19 subtests | t/English.t .. ok | t/File-stat.t ok | t/List-MoreUtils/all.t ... ok | t/List-MoreUtils/any.t ... ok | t/List-MoreUtils/false.t . ok | t/List-MoreUtils/mesh.t .. ok | t/List-MoreUtils/minmax.t ok | t/List-MoreUtils/none.t .. ok | t/List-MoreUtils/true.t .. ok | t/List-MoreUtils/uniq.t .. ok | t/List-Util/first.t .. ok | t/List-Util/max.t ok | t/List-Util/maxstr.t . ok | t/List-Util/min.t ok | t/List-Util/minstr.t . ok | t/List-Util/reduce.t . ok | t/List-Util/shuffle.t ok | t/List-Util/sum.t ok | t/Meta/ISA.t . ok | t/Meta/checksum.t ok | t/Meta/class.t ... ok | t/Meta/id.t .. ok | t/Meta/is-equal.t ok | t/Meta/linear_isa.t .. ok | t/Meta/methods.t . ok | t/Meta/reftype.t . ok | t/Meta/super.t ... ok | t/Meta/symbol_table.t ok | t/Want.t . ok | t/alias.t ok | t/autobox.t .. ok | t/autodie.t .. ok | t/autovivification.t . ok | t/caller.t ... ok | t/can.t .. ok | t/capture.t .. ok | t/carp.t . ok | t/center.t ... ok | t/chdir.t ok | t/command_line_wrapper.t . ok | t/commify.t .. ok | t/datetime.t . ok | t/die.t .. ok | t/diff.t . ok | t/dump/array.t ... ok | t/dump/code.t ok | t/dump/hash.t ok | t/dump/obj.t . ok | t/dump/scalar.t .. ok | t/each.t . ok | t/equal.t ok | t/everything_is_an_object.t .. ok | t/flip.t . ok | t/foreach.t .. ok | t/github164.t ok | t/grep.t . ok | t/hash-diff.t ok | t/hash-intersect.t ... ok | t/hash-merge.t ... ok | t/intersect.t ok | t/io-handle.t ok | t/is_module_name.t ... ok | t/lexical.t .. ok | t/list-trim.t ok | t/list.t . ok | t/load_together.t ok | t/map.t .. ok | t/method_leaking.t ... ok | t/modern_perl.t .. ok | t/module2path.t .. ok | t/no_indirect.t .. ok | t/number.t ... ok | t/perl5i.t ... ok | t/require.t .. ok | t/require_message.t .. ok | t/say.t .. ok | t/scalar.t ... ok | t/signature.t ok | t/signatures.t ... ok | t/taint.t ok | t/time_compat.t .. ok | t/true.t . ok | t/try-tiny.t . ok | t/uniq.t . ok | t/utf8.t . ok | t/version_0/00_compile.t . ok | t/version_1/00_compile.t . ok | t/vs_listmoreutils.t . ok | t/wrap.t . ok | t/y2038.t ok | | Test Summary Report | --- | t/Child.t (Wstat: 256 Tests:
Bug#677221: marked as done (xen: Xen PV privilege escalation (CVE-2012-0217))
Your message dated Thu, 14 Jun 2012 15:48:51 + with message-id e1sfchz-00087z...@franck.debian.org and subject line Bug#677221: fixed in xen 4.1.3~rc1+hg-20120614.a9c0a89c08f2-1 has caused the Debian Bug report #677221, regarding xen: Xen PV privilege escalation (CVE-2012-0217) 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.) -- 677221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xen Version: 4.1.2-2 Severity: critical Tags: security Justification: allows PV domains to escape into the dom0 context Hi, I realize you're most likely pretty well aware of that problem already, but Debian's Xen versions are vulnerable to a PV privilege escalation [1]. The issue is tracked as CVE-2012-0217 and public as of today. Therefore I am filing this bug for coordination and traceability. Please update the packages and consider a security update for Squeeze. [1] http://lists.xen.org/archives/html/xen-devel/2012-06/msg00670.html -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-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--- Source: xen Source-Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-1 We believe that the bug you reported is fixed in the latest version of xen, which is due to be installed in the Debian FTP archive: libxen-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxen-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxen-ocaml-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-ocaml-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxen-ocaml_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-ocaml_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxenstore3.0_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxenstore3.0_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb xen-docs-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_all.deb to main/x/xen/xen-docs-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_all.deb xen-hypervisor-4.1-amd64_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/xen-hypervisor-4.1-amd64_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb xen-utils-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/xen-utils-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb xen-utils-common_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_all.deb to main/x/xen/xen-utils-common_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_all.deb xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1.debian.tar.gz to main/x/xen/xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1.debian.tar.gz xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1.dsc to main/x/xen/xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1.dsc xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2.orig-qemu.tar.gz to main/x/xen/xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2.orig-qemu.tar.gz xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2.orig.tar.gz to main/x/xen/xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2.orig.tar.gz xenstore-utils_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/xenstore-utils_4.1.3~rc1+hg-20120614.a9c0a89c08f2-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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank wa...@debian.org (supplier of updated xen 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, 14 Jun 2012 17:06:25 +0200 Source: xen Binary: xen-docs-4.1 libxen-4.1 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.1 xen-hypervisor-4.1-amd64 xen-hypervisor-4.1-i386 Architecture: source amd64 all Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-1 Distribution: unstable Urgency: low Maintainer: Debian Xen Team pkg-xen-de...@lists.alioth.debian.org Changed-By: Bastian Blank wa...@debian.org Description: libxen-4.1 - Public libs for Xen libxen-dev - Public headers and libs
Bug#676728: digikam: FTBFS: parse.hpp:155:9: internal compiler error: Segmentation fault
Hi, I think this was also due to GCC PR c++/26155 and fixed in gcc-4.7 4.7.0-13. After that version becomes available on the i386 buildds, please could it be given back for rebuild? Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Processed (with 1 errors): Re: Bug#675325: iipimage: iipsrv.conf file is configured to use mod_fastcgi
Processing commands for cont...@bugs.debian.org: severity 675325 grave Bug #675325 [iipimage] iipimage: iipsrv.conf file is configured to use mod_fastcgi Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 675325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675325 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#677199: marked as done (w3c-dtd-xhtml: please rebuild to fix your copy of #477751)
Your message dated Thu, 14 Jun 2012 16:03:00 + with message-id e1sfcvg-000120...@franck.debian.org and subject line Bug#677199: fixed in w3c-dtd-xhtml 1.2-4 has caused the Debian Bug report #677199, regarding w3c-dtd-xhtml: please rebuild to fix your copy of #477751 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.) -- 677199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: w3c-dtd-xhtml Severity: serious Dear maintainer(s) of w3c-dtd-xhtml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut ---End Message--- ---BeginMessage--- Source: w3c-dtd-xhtml Source-Version: 1.2-4 We believe that the bug you reported is fixed in the latest version of w3c-dtd-xhtml, which is due to be installed in the Debian FTP archive: w3c-dtd-xhtml_1.2-4.dsc to main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.2-4.dsc w3c-dtd-xhtml_1.2-4.tar.gz to main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.2-4.tar.gz w3c-dtd-xhtml_1.2-4_all.deb to main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.2-4_all.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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas Bamber nicho...@periapt.co.uk (supplier of updated w3c-dtd-xhtml 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, 14 Jun 2012 16:03:59 +0100 Source: w3c-dtd-xhtml Binary: w3c-dtd-xhtml Architecture: source all Version: 1.2-4 Distribution: unstable Urgency: low Maintainer: Nicholas Bamber nicho...@periapt.co.uk Changed-By: Nicholas Bamber nicho...@periapt.co.uk Description: w3c-dtd-xhtml - W3C eXtensible HyperText Markup Language (XHTML) DTD Closes: 615360 677199 Changes: w3c-dtd-xhtml (1.2-4) unstable; urgency=low . * Set minimum version of debhelper (Closes: #677199) * Fixed home page field again (Closes: #615360) Checksums-Sha1: 7267957fc515e559d6b00c3b92ab219be6921b2a 1488 w3c-dtd-xhtml_1.2-4.dsc 939e37989ba0784d1ea16939aa73e91e483c78fb 996374 w3c-dtd-xhtml_1.2-4.tar.gz 014d61ca308f4b2498c5db23092a5b05224ee1f6 92540 w3c-dtd-xhtml_1.2-4_all.deb Checksums-Sha256: 7815cf36d1787b215e1e6d4dc4a5f93ce9255c736b36513b97ed03a3cd75d3d3 1488 w3c-dtd-xhtml_1.2-4.dsc 0c1f141fb60d1179f5f2d891dd2f779384804bc014f65952a59e9f0fd10d2eef 996374 w3c-dtd-xhtml_1.2-4.tar.gz 79958678128ab9421790eb039c0f18844ea934819e8cec3069e9149f3b0526e6 92540 w3c-dtd-xhtml_1.2-4_all.deb Files: 28ce2d814ca1f09db2fd0354bd7b7163 1488 text optional w3c-dtd-xhtml_1.2-4.dsc d3db352dfad893889771432cb3b10637 996374 text optional w3c-dtd-xhtml_1.2-4.tar.gz 1e37bf6bf8666f25475c5fdf85ffdc97 92540 text optional w3c-dtd-xhtml_1.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP2f2QAAoJELbE2bY7/+c887QQAK/q5kxt+LKaTiJf65/vdlWn hRMP91ykVcrv4KraXgrnzRlAIm7JQr4KYg7Bysg2xmQECsC2UfKUQOiUy5nnxz9W 4+kUU+oKjbqD4mVcsfTdRxqwKJf+4pcy/3Ep105ZKf9CAWYdMpGD5EoGumGpRQy2 ElHOL6IIdNh4ce6mKE5j8CzLeg3CSKibKWCWuD1fBysBDLexuYGrzptExgKjtDCf
Bug#675325: iipimage: iipsrv.conf file is configured to use mod_fastcgi
It looks fine. Perhaps mod_fcgid has not been enabled in /etc/apache2/conf-enabled/ ? --- http://iipimage.sourceforge.net --- On 06/14/2012 05:51 PM, Mathieu Malaterre wrote: tags 675325 grave thanks On Thu, Jun 14, 2012 at 5:27 PM, Ruven ru...@users.sourceforge.net wrote: So your previous error is no longer happening?: Syntax error on line 16 of /etc/apache2/mods-enabled/iipsrv.conf: Invalid command 'FcgidInitialEnv', perhaps misspelled or defined by a module not included in the server configuration Action 'configtest' failed. The Apache error log may have more information. failed! I messed up the installation on my side. I was using libapache2-mod-fastcgi on my test server instead of libapache2-mod-fcgid. It appears that I cannot get iipsrv to work with libapache2-mod-fcgid. Here is my conf: $ apt-cache policy libapache2-mod-fcgid libapache2-mod-fcgid: Installed: 1:2.3.6-1+squeeze1 Candidate: 1:2.3.6-1+squeeze1 Version table: *** 1:2.3.6-1+squeeze1 0 500 http://mirror.ovh.net/debian/ squeeze/main amd64 Packages 500 http://security.debian.org/ squeeze/updates/main amd64 Packages 100 /var/lib/dpkg/status And: $ sudo /etc/init.d/apache2 restart Syntax error on line 16 of /etc/apache2/mods-enabled/iipsrv.conf: Invalid command 'FcgidInitialEnv', perhaps misspelled or defined by a module not included in the server configuration Action 'configtest' failed. The Apache error log may have more information. failed! $ cat /etc/apache2/mods-enabled/iipsrv.conf # Create a directory for the iipsrv binary ScriptAlias /iipsrv/ /usr/lib/iipimage-server/ # Set the options on that directory Directory /iipsrv/ AllowOverride None Options None Order allow,deny Allow from all # Set the module handler AddHandler fcgid-script .fcgi /Directory # Set our environment variables for the IIP server FcgidInitialEnv VERBOSITY 1 FcgidInitialEnv LOGFILE /var/log/iipsrv.log FcgidInitialEnv MAX_IMAGE_CACHE_SIZE 10 FcgidInitialEnv JPEG_QUALITY 90 FcgidInitialEnv MAX_CVT 5000 FcgidInitialEnv MEMCACHED_SERVERS localhost # Define the idle timeout as unlimited and the number of # processes we want FcgidIdleTimeout 0 FcgidMaxClassProcessesPerClass 1 Do you see anything wrong ? Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675842: webkitkde: FTBFS[kfreebsd]: symbol changes
Hi, This package isn't up to date, and is orphaned. However, we are working on it to upload a new version, but we are currently searching for a sponsor. You can follow our work on mentors.debian.net : http://mentors.debian.net/package/webkitkde and we manage the packaging on a repository on alioth : http://anonscm.debian.org/gitweb/?p=pkg-kde/kde-extras/webkitkde.git Cheers, Adrien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677293: marked as done (rawtherapee: FTBFS when not building (arch-all) -data package)
Your message dated Thu, 14 Jun 2012 16:19:19 +
with message-id e1sfclt-0001iu...@franck.debian.org
and subject line Bug#677293: fixed in rawtherapee 4.0.9-2
has caused the Debian Bug report #677293,
regarding rawtherapee: FTBFS when not building (arch-all) -data package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
677293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: rawtherapee
Version: 4.0.9-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of rawtherapee building only its architecture-dependent main
package (as on the autobuilders) fail:
rm
/.../rawtherapee-4.0.9/debian/rawtherapee-data/usr/share/rawtherapee/languages/LICENSE
rm: cannot remove
`/.../rawtherapee-4.0.9/debian/rawtherapee-data/usr/share/rawtherapee/languages/LICENSE':
No such file or directory
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory `/.../rawtherapee-4.0.9'
make: *** [binary-arch] Error 2
Could you please operate on rawtherapee-data only when it actually
exists? BTW, I'd also suggest sticking to relative paths when
possible; using $(CURDIR) or the equivalent just clutters output.
Thanks!
---End Message---
---BeginMessage---
Source: rawtherapee
Source-Version: 4.0.9-2
We believe that the bug you reported is fixed in the latest version of
rawtherapee, which is due to be installed in the Debian FTP archive:
rawtherapee-data_4.0.9-2_all.deb
to main/r/rawtherapee/rawtherapee-data_4.0.9-2_all.deb
rawtherapee_4.0.9-2.debian.tar.gz
to main/r/rawtherapee/rawtherapee_4.0.9-2.debian.tar.gz
rawtherapee_4.0.9-2.dsc
to main/r/rawtherapee/rawtherapee_4.0.9-2.dsc
rawtherapee_4.0.9-2_amd64.deb
to main/r/rawtherapee/rawtherapee_4.0.9-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 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Philip Rinn ri...@gmx.net (supplier of updated rawtherapee 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: Wed, 13 June 2012 20:01:54 +0100
Source: rawtherapee
Binary: rawtherapee rawtherapee-data
Architecture: source amd64 all
Version: 4.0.9-2
Distribution: unstable
Urgency: low
Maintainer: Philip Rinn ri...@gmx.net
Changed-By: Philip Rinn ri...@gmx.net
Description:
rawtherapee - Free RAW converter and digital photo processing software
rawtherapee-data - Free RAW converter and digital photo processing software
(data fi
Closes: 677293
Changes:
rawtherapee (4.0.9-2) unstable; urgency=low
.
* Fix build failures (closes: #677293):
- use override_dh_install-{arch,indep} in debian/rules
* Add patch debian/patches/02-fix_color_artifacts.patch:
- fix color artifacts (from upstream)
Checksums-Sha1:
9b8032bed551d1a638e3a63a46cb6eec6246760e 1951 rawtherapee_4.0.9-2.dsc
3810e7ab67fe5be94bd8604cd8ff4097a07cfc0a 9137 rawtherapee_4.0.9-2.debian.tar.gz
4e90ac0f052ae39007bd30589b4de4aecb5e9270 2785346 rawtherapee_4.0.9-2_amd64.deb
a28af402c11f4785995d985a037a33252d3bdb42 7164454
rawtherapee-data_4.0.9-2_all.deb
Checksums-Sha256:
0143a9a5e613f462d8ef39b592b85ebc78dc0001d09577c73811c52fe737b57c 1951
rawtherapee_4.0.9-2.dsc
2feb2389c2e6db85610fa5e64e48d5d97687da1b7ed1904f5a65c874345dcf52 9137
rawtherapee_4.0.9-2.debian.tar.gz
87883558df8625d194befb57849c545fb0479fea2ed353d01d5cd013921a07a0 2785346
rawtherapee_4.0.9-2_amd64.deb
3184383ab613f0428bbd5ac29d934aa48273f82a7fed6a822273fcfd26481e73 7164454
rawtherapee-data_4.0.9-2_all.deb
Files:
aead4e14af72b6c3904072336de88ea6 1951 graphics optional rawtherapee_4.0.9-2.dsc
af52f69c50fd6c0a4eb49f52bc2c4d39 9137 graphics optional
rawtherapee_4.0.9-2.debian.tar.gz
228bcbcd80f289e91834abbae940c58f 2785346 graphics optional
rawtherapee_4.0.9-2_amd64.deb
11506ada921724e504602787dd22a7b9 7164454 graphics optional
rawtherapee-data_4.0.9-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJP2gzOAAoJEBPAtWZ6OLCwm6kP/iYVqDljOO+fx6MGj3oXSdox
Q1/yBjNUjIkhJR20prFwybFpedRigMV1fQIFDjB9UZ8KWLJHh19qIwmZhpASy6OL
90tlmedeOubk7A+YfMEAqZyqBa9bip5M6YlqIC8flOtJTb06HlLRW64itJghAk6h
Bug#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
On Fri, Jun 8, 2012 at 6:17 PM, Philipp Kern wrote: On Sat, Jun 09, 2012 at 04:36:40AM +0800, Aron Xu wrote: Does this mean M-A:same packages should be prevented from being binNMUed, but only source upload can be accepted? You cannot deprive the Release Team of this tool. Also multiarch bugs are IMHO at most important, not serious. Possibly we could allow one last sourceful upload when the transitions all settled, but it would again increase the review load on the release team. IMHO it's on the if it works, fine, if not, sorry about that part of the list, given that it was finalized so late, with that critical piece missing. Wouldn't the ideal solution be non-architecture-specific changelogs? So, a normal binnmu changelog looks like this now: package (version) sid; urgency=low * Binary-only non-maintainer upload for amd64; no source changes. -- amd64 Builddd Daemon (barber) buildd_amd64-bar...@buildd.debian.org Tue, 05 Jun 2012 16:33:05 + which could be changed to something like this instead: package (version) sid; urgency=low * Binary-only non-maintainer upload; no source changes. -- Debian Release Team debian-rele...@lists.debian.org Tue, 05 Jun 2012 16:33:05 + or some other appropriate binnmu mailing address. This would also mean rebuilding all of the other architectures for multi-arch same packages so that they all get the same changelog. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package accountsservice
Processing commands for cont...@bugs.debian.org:
#
# bts-link upstream status pull for source package accountsservice
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was
bts-link-de...@lists.alioth.debian.org).
# remote status report for #674419 (http://bugs.debian.org/674419)
# Bug title: gnome-shell: segfaults in libaccountservice
# * https://bugs.freedesktop.org/show_bug.cgi?id=50112
# * remote status changed: NEW - RESOLVED
# * remote resolution changed: (?) - FIXED
# * closed upstream
tags 674419 + fixed-upstream
Bug #674419 [libaccountsservice0] gnome-shell: segfaults in libaccountservice
Bug #673185 {Done: Alessio Treglia ales...@debian.org} [libaccountsservice0]
gnome-shell: segfault in libaccountsservice.so.0.0.0
Bug #673211 [libaccountsservice0] gnome-shell: segfault in
libaccountsservice.so.0.0.0
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
usertags 674419 - status-NEW
Bug#674419: gnome-shell: segfaults in libaccountservice
Usertags were: status-NEW.
Usertags are now: .
usertags 674419 + status-RESOLVED resolution-FIXED
Bug#674419: gnome-shell: segfaults in libaccountservice
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
# remote status report for #674419 (http://bugs.debian.org/674419)
# Bug title: gnome-shell: segfaults in libaccountservice
# * https://bugs.freedesktop.org/show_bug.cgi?id=50112
# * remote status changed: NEW - RESOLVED
# * remote resolution changed: (?) - FIXED
# * closed upstream
tags 674419 + fixed-upstream
Bug #674419 [libaccountsservice0] gnome-shell: segfaults in libaccountservice
Bug #673185 {Done: Alessio Treglia ales...@debian.org} [libaccountsservice0]
gnome-shell: segfault in libaccountsservice.so.0.0.0
Bug #673211 [libaccountsservice0] gnome-shell: segfault in
libaccountsservice.so.0.0.0
Ignoring request to alter tags of bug #674419 to the same tags previously set
Ignoring request to alter tags of bug #673185 to the same tags previously set
Ignoring request to alter tags of bug #673211 to the same tags previously set
usertags 674419 - status-NEW
Bug#674419: gnome-shell: segfaults in libaccountservice
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: status-RESOLVED resolution-FIXED.
usertags 674419 + status-RESOLVED resolution-FIXED
Bug#674419: gnome-shell: segfaults in libaccountservice
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: status-RESOLVED resolution-FIXED.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
673185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673185
673211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673211
674419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674419
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: [bts-link] source package src:gnome-menus
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:gnome-menus # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #676566 (http://bugs.debian.org/676566) # Bug title: alacarte broken # * http://bugzilla.gnome.org/show_bug.cgi?id=677344 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 676566 + fixed-upstream Bug #676566 [src:gnome-menus] alacarte broken Added tag(s) fixed-upstream. usertags 676566 + status-RESOLVED resolution-FIXED Bug#676566: alacarte broken There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 676566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676566 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#677535: Unwanted soname change
Package: libept1.4.12 Version: 1.0.7 Severity: grave mnencia@greygoo:~/prj/health-check/data-reporter (master *)$ aptitude aptitude: error while loading shared libraries: libept.so.1.0.5.4.12: cannot open shared object file: No such file or directory mnencia@greygoo:~/prj/health-check/data-reporter (master *)$ dpkg -L libept1.4.12 | grep usr/lib /usr/lib /usr/lib/libept.so.1.0.7.4.12 I think this come from a wrong string replace across the project (as the current version is 1.0.7) Commit: http://anonscm.debian.org/gitweb/?p=debtags/libept.git;a=blobdiff;f=CMakeLists.txt;h=7c0c72d90f1c73ad4a960e2892cdd1a5cdbc0d42;hp=1154891d1a335c11f16c3f959d5903c5597f7805;hb=7d4383bd070a53e6c679fe189c9f15fdb7b1dcef;hpb=d456f52d160a5eb97488dd4720cd5e646349845d Regards Marco -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libept1.4.12 depends on: ii libapt-pkg4.12 0.9.6 ii libc6 2.13-33 ii libgcc1 1:4.7.0-13 ii libstdc++6 4.7.0-13 ii libxapian22 1.2.10-2 ii zlib1g 1:1.2.7.dfsg-11 libept1.4.12 recommends no packages. libept1.4.12 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
Michael Gilbert mgilb...@debian.org (14/06/2012): package (version) sid; urgency=low * Binary-only non-maintainer upload; no source changes. -- Debian Release Team debian-rele...@lists.debian.org Tue, 05 Jun 2012 16:33:05 + or some other appropriate binnmu mailing address. This would also mean rebuilding all of the other architectures for multi-arch same packages so that they all get the same changelog. No, binNMUs numbers can be different, along with timestamps (even with: “wb nmu foo . ALL . -m 'Rebuild for foo.'”, architectures are processed one after each other). Also, reasons can be different. Mraw, KiBi. signature.asc Description: Digital signature
Bug#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
On Thu, Jun 14, 2012 at 12:40 PM, Cyril Brulebois wrote: Michael Gilbert mgilb...@debian.org (14/06/2012): package (version) sid; urgency=low * Binary-only non-maintainer upload; no source changes. -- Debian Release Team debian-rele...@lists.debian.org Tue, 05 Jun 2012 16:33:05 + or some other appropriate binnmu mailing address. This would also mean rebuilding all of the other architectures for multi-arch same packages so that they all get the same changelog. No, binNMUs numbers can be different, along with timestamps (even with: “wb nmu foo . ALL . -m 'Rebuild for foo.'”, architectures are processed one after each other). Also, reasons can be different. Right, I imagine it will involving reworking of quite a few steps in the process, and again this would be only for 'multi-arch: same'. So, instead of the buildd (or wherever that is done now) creating the changelog/timestamp, instead create one 'multi-arch: same' changelog before passing it off to the buildds, and then after the build is done, replace the automatically architecture-specific changelog with the 'multi-arch: same' one. The reason for rebuilding a 'multi-arch: same' package by definition should be for the same reason on all architectures, right? Non 'multi-arch: same' binnmus would not need to change. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
On Thu, Jun 14, 2012 at 12:25:42 -0400, Michael Gilbert wrote: Wouldn't the ideal solution be non-architecture-specific changelogs? No, that would be very much non-ideal. One should be able to schedule binNMUs for a subset of archs, and one shouldn't have to look up whether a package builds m-a:same binaries. This has been said a few times already, please drop this thread if you're just going to repeat old shot-down ideas. Thanks, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677543: guake: missing python-xdg dependency
package: guake version: 0.4.3-1 severity: serious Hi, guake fails to run when the python-xdg is not installed: $ guake Traceback (most recent call last): File /usr/bin/guake, line 35, in module from xdg.DesktopEntry import DesktopEntry ImportError: No module named xdg.DesktopEntry -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#677541: aptitude depends upon libept - will not run
Processing commands for cont...@bugs.debian.org:
reassign 677541 libept1.4.12 1.0.7
Bug #677541 [aptitude] aptitude depends upon libept - will not run
Bug reassigned from package 'aptitude' to 'libept1.4.12'.
No longer marked as found in versions aptitude/0.6.8-1.
Ignoring request to alter fixed versions of bug #677541 to the same values
previously set
Bug #677541 [libept1.4.12] aptitude depends upon libept - will not run
Marked as found in versions libept/1.0.7.
merge 677535 677541
Bug #677535 [libept1.4.12] Unwanted soname change
Unable to merge bugs because:
severity of #677541 is 'normal' not 'grave'
Failed to merge 677535: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x30fffd8)',
'requester', 'Sven Joachim svenj...@gmx.de', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '87wr39u6wu@turtle.gmx.de',
'request_subject', ...) called at /usr/lib/debbugs/service line 872
eval {...} called at /usr/lib/debbugs/service line 871
thanks
Stopping processing here.
Please contact me if you need assistance.
--
677535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677535
677541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677541
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: try harder
Processing commands for cont...@bugs.debian.org: forcemerge 677535 677541 Bug #677535 [libept1.4.12] Unwanted soname change Bug #677541 [libept1.4.12] aptitude depends upon libept - will not run Severity set to 'grave' from 'normal' Merged 677535 677541 thanks Stopping processing here. Please contact me if you need assistance. -- 677535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677535 677541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677541 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: affects 677541
Processing commands for cont...@bugs.debian.org: affects 677541 aptitude Bug #677541 [libept1.4.12] aptitude depends upon libept - will not run Bug #677535 [libept1.4.12] Unwanted soname change Added indication that 677541 affects aptitude Added indication that 677535 affects aptitude thanks Stopping processing here. Please contact me if you need assistance. -- 677535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677535 677541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677541 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#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
On Thu, Jun 14, 2012 at 1:07 PM, Julien Cristau jcris...@debian.org wrote: On Thu, Jun 14, 2012 at 12:25:42 -0400, Michael Gilbert wrote: Wouldn't the ideal solution be non-architecture-specific changelogs? No, that would be very much non-ideal. One should be able to schedule binNMUs for a subset of archs, I did not suggest that. Anyway, maybe this will be a bit clearer. Let's say an existing package is at version +b1 on amd64, and it needs to get a binnmu, then a +b2 package is built on amd64, its changelog is taken and stuffed it into all of the other 'Multi-Arch: same' +b1 packages, which are now called +b2, and all of them uploaded. Those other architectures didn't undergo a rebuild, but nevertheless, they got new packages. Then lets say a +b3 is needed on i386, then the same is done, and the 'Multi-arch: same' amd64 package (and others) get stuffed with the i386 +b3 changes (which includes the prior amd64 +b2 changelog). and one shouldn't have to look up whether a package builds m-a:same binaries. This is a new special case that will need to be handled somehow, right? Look-ups are not that expensive; although admittedly the time spent writing the infrastructure supporting may not be. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677543: marked as done (guake: missing python-xdg dependency)
Your message dated Thu, 14 Jun 2012 18:02:41 + with message-id e1sfenv-00029n...@franck.debian.org and subject line Bug#677543: fixed in guake 0.4.3-2 has caused the Debian Bug report #677543, regarding guake: missing python-xdg dependency 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.) -- 677543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: guake version: 0.4.3-1 severity: serious Hi, guake fails to run when the python-xdg is not installed: $ guake Traceback (most recent call last): File /usr/bin/guake, line 35, in module from xdg.DesktopEntry import DesktopEntry ImportError: No module named xdg.DesktopEntry ---End Message--- ---BeginMessage--- Source: guake Source-Version: 0.4.3-2 We believe that the bug you reported is fixed in the latest version of guake, which is due to be installed in the Debian FTP archive: guake_0.4.3-2.debian.tar.gz to main/g/guake/guake_0.4.3-2.debian.tar.gz guake_0.4.3-2.dsc to main/g/guake/guake_0.4.3-2.dsc guake_0.4.3-2_i386.deb to main/g/guake/guake_0.4.3-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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru sylves...@debian.org (supplier of updated guake 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, 08 Jun 2012 13:46:04 +0200 Source: guake Binary: guake Architecture: source i386 Version: 0.4.3-2 Distribution: unstable Urgency: low Maintainer: Sylvestre Ledru sylves...@debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: guake - Drop-down terminal for GNOME Desktop Environment Closes: 669588 676629 677543 Changes: guake (0.4.3-2) unstable; urgency=low . * Missing dependency on python-xdg (Closes: #676629, #677543) * Update of the homepage (Closes: #669588) Checksums-Sha1: cba86218203c82299347ce77ffd257a11d1dd3b3 1297 guake_0.4.3-2.dsc d043066037e197a4a62572c2bf40f8a65e5d46c8 4981 guake_0.4.3-2.debian.tar.gz ae2ee6d0b5045dad282c4be50e1ff071fcb6f1e5 123046 guake_0.4.3-2_i386.deb Checksums-Sha256: 515db3316253cb9ed3f556894011641639599b8ffdc2c230ce467b5bf6c09c93 1297 guake_0.4.3-2.dsc 29fc866a34ff68a4295221d60d076572782925a077ac40b22f8d0c0db6d0d714 4981 guake_0.4.3-2.debian.tar.gz 740098970e2bd48886d797fc298440ef5e3036de2ac7b42ae4c0782b346379ce 123046 guake_0.4.3-2_i386.deb Files: 82a4a53a3c389a87523d880c16b0204a 1297 x11 optional guake_0.4.3-2.dsc df950a5ba405039c8cbfdc6e19b04e55 4981 x11 optional guake_0.4.3-2.debian.tar.gz 7bc65e573bc2b4b531a89d1b375e749a 123046 x11 optional guake_0.4.3-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/aJEQACgkQiOXXM92JlhBiuACeMAI4r0+2lgnfcwhyZaernKc4 /msAn2Hpdpyar4Cv9isQG8gu947mq8OC =IVQ8 -END PGP SIGNATURE- ---End Message---
Bug#676686: tag as pending
tag 676686 + pending thanks I've uploaded the fix for libxml2 just now, will upload libxslt very soon. -- 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
Processed: tag as pending
Processing commands for cont...@bugs.debian.org: tag 676686 + pending Bug #676686 [libxslt1.1] libxslt1.1: libxslt1.1 binNMU broke multi-arch installability Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 676686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676686 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#677552: dkim-filter: libdkim does not get the correcty DNS entry
Package: dkim-filter Version: 2.8.2.dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable dkim-filter project is replaced by opendkim as written on sourceforge. This package should not be shipped in Wheezy ! In fact I get this error in mail.log which prevents any user of gmail.com to send a message to any user in my domain. Jun 9 19:01:18 www postfix/smtpd[9019]: 1D2F0804C2: client=mail-gg0-f169.google.com[209.85.161.169] Jun 9 19:01:18 www postfix/cleanup[9017]: 1D2F0804C2: message-id=cakokwmqdpwcm6fhfoitg+eyshn2crxyd6jefx5zd8meftrv...@mail.gmail.com Jun 9 19:01:18 www dkim-filter[18528]: 1D2F0804C2: dkim_eoh(): internal error from libdkim: ar_addquery() for `20120113._domainkey.gmail.com' failed Jun 9 19:01:18 www postfix/cleanup[9017]: 1D2F0804C2: milter-reject: END-OF-MESSAGE from mail-gg0-f169.google.com[209.85.161.169]: 4.7.1 Service unava -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dkim-filter depends on: ii adduser3.112+nmu2add and remove users and groups ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libdb4.7 4.7.25-9 Berkeley v4.7 Database Libraries [ ii libmilter1.0.1 8.14.3-9.4Sendmail Mail Filter API (Milter) ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries dkim-filter recommends no packages. dkim-filter suggests no packages. -- Configuration Files: /etc/default/dkim-filter changed [not included] /etc/dkim-filter.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Aptitude-devel] Bug#677548: aptitude: linked against nonexisting libept.so.1.0.5.4.12
Processing commands for cont...@bugs.debian.org: reassign 677548 libept1.4.12 1.0.7 Bug #677548 [aptitude] aptitude: linked against nonexisting libept.so.1.0.5.4.12 Bug reassigned from package 'aptitude' to 'libept1.4.12'. No longer marked as found in versions aptitude/0.6.8-1. Ignoring request to alter fixed versions of bug #677548 to the same values previously set Bug #677548 [libept1.4.12] aptitude: linked against nonexisting libept.so.1.0.5.4.12 Marked as found in versions libept/1.0.7. forcemerge 677535 677548 Bug #677535 [libept1.4.12] Unwanted soname change Bug #677541 [libept1.4.12] aptitude depends upon libept - will not run Bug #677548 [libept1.4.12] aptitude: linked against nonexisting libept.so.1.0.5.4.12 Severity set to 'grave' from 'important' Added indication that 677548 affects aptitude Bug #677541 [libept1.4.12] aptitude depends upon libept - will not run Merged 677535 677541 677548 kthxbye Stopping processing here. Please contact me if you need assistance. -- 677535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677535 677541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677541 677548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677548 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#653312: marked as done (tahoe-lafs: Error on building from source: aborting due to unexpected upstream changes)
Your message dated Thu, 14 Jun 2012 18:49:52 +
with message-id e1sff7a-0005ii...@franck.debian.org
and subject line Bug#653312: fixed in tahoe-lafs 1.9.1-1
has caused the Debian Bug report #653312,
regarding tahoe-lafs: Error on building from source: aborting due to unexpected
upstream changes
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.)
--
653312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: tahoe-lafs
Version: 1.8.3-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
While building tahoe-lafs from source dpkg-source returns an error. It don't
happens the first time I build it, but if I rerun dpkg-buildpackage again the
package don't builds.
Here you have the console log:
[meskio@hermes:tahoe-lafs-1.8.3]$ dpkg-buildpackage -rfakeroot
dpkg-buildpackage: source package tahoe-lafs
dpkg-buildpackage: source version 1.8.3-2
dpkg-buildpackage: source changed by Micah Anderson mi...@debian.org
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build tahoe-lafs-1.8.3
fakeroot debian/rules clean
rm -f build-*
dh_testdir
dh_testroot
python setup.py clean
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution
option: 'versionfiles'
warnings.warn(msg)
running clean
rm -rf build
find . -name *\.py[co] -exec rm -f {} \;
dh_clean
dpkg-source -b tahoe-lafs-1.8.3
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building tahoe-lafs using existing
./tahoe-lafs_1.8.3.orig.tar.gz
dpkg-source: warning: file
tahoe-lafs-1.8.3/src/allmydata_tahoe.egg-info/SOURCES.txt has no final newline
(either original or modified version)
dpkg-source: info: local changes detected, the modified files are:
tahoe-lafs-1.8.3/src/allmydata_tahoe.egg-info/SOURCES.txt
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-source: error: aborting due to unexpected upstream changes, see
/tmp/tahoe-lafs_1.8.3-2.diff.q8v7Mt
dpkg-buildpackage: error: dpkg-source -b tahoe-lafs-1.8.3 gave error exit
status 2
---End Message---
---BeginMessage---
Source: tahoe-lafs
Source-Version: 1.9.1-1
We believe that the bug you reported is fixed in the latest version of
tahoe-lafs, which is due to be installed in the Debian FTP archive:
tahoe-lafs_1.9.1-1.debian.tar.gz
to main/t/tahoe-lafs/tahoe-lafs_1.9.1-1.debian.tar.gz
tahoe-lafs_1.9.1-1.dsc
to main/t/tahoe-lafs/tahoe-lafs_1.9.1-1.dsc
tahoe-lafs_1.9.1-1_all.deb
to main/t/tahoe-lafs/tahoe-lafs_1.9.1-1_all.deb
tahoe-lafs_1.9.1.orig.tar.gz
to main/t/tahoe-lafs/tahoe-lafs_1.9.1.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 653...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Micah Anderson mi...@debian.org (supplier of updated tahoe-lafs 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: Tue, 12 Jun 2012 09:35:12 +0200
Source: tahoe-lafs
Binary: tahoe-lafs
Architecture: source all
Version: 1.9.1-1
Distribution: unstable
Urgency: high
Maintainer: Bert Agaz berta...@ptitcanardnoir.org
Changed-By: Micah Anderson mi...@debian.org
Description:
tahoe-lafs - Secure distributed filesystem
Closes: 652002 652106 653312
Changes:
tahoe-lafs (1.9.1-1) unstable; urgency=high
.
[ Bert Agaz ]
* New upstream release (Closes: #652002).
* Set urgency to high due to RC bug fix.
* Update debian/patches/.
* Install munin plugin configuration as examples (Closes: #652106).
* Remove old deps version numbers from debian/control.
* Update debian/copyright to follow DEP-5.
* Bump debian standard version to 3.9.3.
* Add manpage.
* Switch to dh_python2.
* Bump debian/compat.
* Fix setuptools egg_info mess with upstream sources. (Closes: #653312)
Checksums-Sha1:
acbdaf3f39e202bd3959c48f9e872216b9e401e1 1954 tahoe-lafs_1.9.1-1.dsc
4d2f4f1a9be29fc95ba943c32cbd14568d73d3a3 1355980 tahoe-lafs_1.9.1.orig.tar.gz
18bb343887b06ae83ace7852d0b15affdbba218c 13214 tahoe-lafs_1.9.1-1.debian.tar.gz
684080b50f1e199cdf9a8c3f4cae631cd4295e48 1222826 tahoe-lafs_1.9.1-1_all.deb
Checksums-Sha256:
Bug#677541: marked as done (aptitude depends upon libept - will not run)
Your message dated Thu, 14 Jun 2012 19:03:08 + with message-id e1sffk0-0007o4...@franck.debian.org and subject line Bug#677535: fixed in libept 1.0.8 has caused the Debian Bug report #677535, regarding aptitude depends upon libept - will not run 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.) -- 677535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: aptitude Version: 0.6.8-1 Severity: grave Release: Unstable Today's upgrade installed libept1.4.12 with /usr/lib/libept.so.1.0.7.4.12. So now, aptitude: error while loading shared libraries: libept.so.1.0.5.4.12: cannot open shared object file: No such file or directory James ---End Message--- ---BeginMessage--- Source: libept Source-Version: 1.0.8 We believe that the bug you reported is fixed in the latest version of libept, which is due to be installed in the Debian FTP archive: ept-cache_1.0.8_all.deb to main/libe/libept/ept-cache_1.0.8_all.deb libept-dev_1.0.8_amd64.deb to main/libe/libept/libept-dev_1.0.8_amd64.deb libept1.4.12_1.0.8_amd64.deb to main/libe/libept/libept1.4.12_1.0.8_amd64.deb libept_1.0.8.dsc to main/libe/libept/libept_1.0.8.dsc libept_1.0.8.tar.gz to main/libe/libept/libept_1.0.8.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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Enrico Zini enr...@debian.org (supplier of updated libept 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, 14 Jun 2012 20:32:47 +0200 Source: libept Binary: libept-dev libept1.4.12 ept-cache Architecture: source all amd64 Version: 1.0.8 Distribution: unstable Urgency: low Maintainer: Enrico Zini enr...@debian.org Changed-By: Enrico Zini enr...@debian.org Description: ept-cache - Obsolete commandline tool to search the package archive libept-dev - High-level library for managing Debian package information libept1.4.12 - High-level library for managing Debian package information Closes: 677532 677535 677536 Changes: libept (1.0.8) unstable; urgency=low . * Applied Julien Cristau's patch to avoid unnecessary soname bumps. Closes: #677532, #677535, #677536 Checksums-Sha1: a09df592182292bd38b1ed5da4b90d3b6539bf6d 1862 libept_1.0.8.dsc 594d67d857c3e66aa917f8623b9fae5b6294ac8e 2665011 libept_1.0.8.tar.gz 35b530d9693444be59d3156991730a22e6a1b882 14744 ept-cache_1.0.8_all.deb 64193b7bee00db3230792c4b0edc6e88eca1917f 693836 libept-dev_1.0.8_amd64.deb 5952dcdc8e5ae2d39a87ca9ace6c657f6e1ec0b5 207114 libept1.4.12_1.0.8_amd64.deb Checksums-Sha256: b043fc337ef7d1b5cc7b0f0ee4143fccd83fd3304c0e1a70afab804a01c57379 1862 libept_1.0.8.dsc 9dc3e1e8092769b9cbc545918efab01efbc388103874844d4e56e04d00b6ae4b 2665011 libept_1.0.8.tar.gz 4d51d5f683b2678b4fc8fead896c6a624ebbce7427b9f0dac73e79293a43ab3c 14744 ept-cache_1.0.8_all.deb c5c7d2c0ef5346d6937712e934b117506b804ca1258e4b350179e77483270893 693836 libept-dev_1.0.8_amd64.deb 34eb924974bda85cd8ee8f4631fb6b3c0966df655730c2ad477dfae54852f82f 207114 libept1.4.12_1.0.8_amd64.deb Files: 694400453efeb75cbde6271712ced127 1862 libdevel important libept_1.0.8.dsc d6e17d06aaefd496b8b3f4a83a0069e0 2665011 libdevel important libept_1.0.8.tar.gz 74489683130b93b038bffc165a3b2ed7 14744 misc important ept-cache_1.0.8_all.deb ab94318a86e118ff4cffd7281cd4ccb3 693836 libdevel important libept-dev_1.0.8_amd64.deb 0b4c556b965139716ab643b4f1bd7d1e 207114 libs important libept1.4.12_1.0.8_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP2jMmAAoJEDEBgAUJBeQMRp4P/3gQ4PQEnrpiu1666A1FApmM +WjqxP4ca7PSKiqDfsdacCoPqm6l1LzowXephuxsuLcQE09Tt77TD9SRCeYMQJ1N sKiL6TNnQiRcxDiEsEXg2lJKz8EQuAHmnVqYZvUJ9aox2Jv/avcSLKqzNYgz6+H3 DNqaev3zWNNyUidhaezqVrjgC5XgsbE7Gn9xuoUSYytNHsJwcTmQSGhnfauvHfwT vmWV+j98I2iuxGv+6tanZLoX13XRQTFv/RpZ/5L0TkHZy1FTr/nF+SLx3Fx4OdEp fodpgtWMP1QlxfgpvJjrixjx5hXjxROYl4XqXNBjJftzJ1gi2XrOXXHtYhtlEUA4 gqxk8itczIhRSRub1C+GBfNdP13F9cq947k7oSUv45nIqcmCZbVxRA+R3SeSEvcP 20cCDMJbrxJVoyDYxvXz6NBPziOCFmcCxTrh56VkXIDSlj9h4PKbCYHPcg67bSlT 9lNjMtG8w7cCjd8+xVXKoShc1mQ4eBKYLbXlo23x22KaeVt6DxALAluI5vgw3mkt
Bug#677535: marked as done (Unwanted soname change)
Your message dated Thu, 14 Jun 2012 19:03:08 + with message-id e1sffk0-0007o4...@franck.debian.org and subject line Bug#677535: fixed in libept 1.0.8 has caused the Debian Bug report #677535, regarding Unwanted soname change 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.) -- 677535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libept1.4.12 Version: 1.0.7 Severity: grave mnencia@greygoo:~/prj/health-check/data-reporter (master *)$ aptitude aptitude: error while loading shared libraries: libept.so.1.0.5.4.12: cannot open shared object file: No such file or directory mnencia@greygoo:~/prj/health-check/data-reporter (master *)$ dpkg -L libept1.4.12 | grep usr/lib /usr/lib /usr/lib/libept.so.1.0.7.4.12 I think this come from a wrong string replace across the project (as the current version is 1.0.7) Commit: http://anonscm.debian.org/gitweb/?p=debtags/libept.git;a=blobdiff;f=CMakeLists.txt;h=7c0c72d90f1c73ad4a960e2892cdd1a5cdbc0d42;hp=1154891d1a335c11f16c3f959d5903c5597f7805;hb=7d4383bd070a53e6c679fe189c9f15fdb7b1dcef;hpb=d456f52d160a5eb97488dd4720cd5e646349845d Regards Marco -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libept1.4.12 depends on: ii libapt-pkg4.12 0.9.6 ii libc6 2.13-33 ii libgcc1 1:4.7.0-13 ii libstdc++6 4.7.0-13 ii libxapian22 1.2.10-2 ii zlib1g 1:1.2.7.dfsg-11 libept1.4.12 recommends no packages. libept1.4.12 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: libept Source-Version: 1.0.8 We believe that the bug you reported is fixed in the latest version of libept, which is due to be installed in the Debian FTP archive: ept-cache_1.0.8_all.deb to main/libe/libept/ept-cache_1.0.8_all.deb libept-dev_1.0.8_amd64.deb to main/libe/libept/libept-dev_1.0.8_amd64.deb libept1.4.12_1.0.8_amd64.deb to main/libe/libept/libept1.4.12_1.0.8_amd64.deb libept_1.0.8.dsc to main/libe/libept/libept_1.0.8.dsc libept_1.0.8.tar.gz to main/libe/libept/libept_1.0.8.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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Enrico Zini enr...@debian.org (supplier of updated libept 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, 14 Jun 2012 20:32:47 +0200 Source: libept Binary: libept-dev libept1.4.12 ept-cache Architecture: source all amd64 Version: 1.0.8 Distribution: unstable Urgency: low Maintainer: Enrico Zini enr...@debian.org Changed-By: Enrico Zini enr...@debian.org Description: ept-cache - Obsolete commandline tool to search the package archive libept-dev - High-level library for managing Debian package information libept1.4.12 - High-level library for managing Debian package information Closes: 677532 677535 677536 Changes: libept (1.0.8) unstable; urgency=low . * Applied Julien Cristau's patch to avoid unnecessary soname bumps. Closes: #677532, #677535, #677536 Checksums-Sha1: a09df592182292bd38b1ed5da4b90d3b6539bf6d 1862 libept_1.0.8.dsc 594d67d857c3e66aa917f8623b9fae5b6294ac8e 2665011 libept_1.0.8.tar.gz 35b530d9693444be59d3156991730a22e6a1b882 14744 ept-cache_1.0.8_all.deb 64193b7bee00db3230792c4b0edc6e88eca1917f 693836 libept-dev_1.0.8_amd64.deb 5952dcdc8e5ae2d39a87ca9ace6c657f6e1ec0b5 207114 libept1.4.12_1.0.8_amd64.deb Checksums-Sha256: b043fc337ef7d1b5cc7b0f0ee4143fccd83fd3304c0e1a70afab804a01c57379 1862 libept_1.0.8.dsc 9dc3e1e8092769b9cbc545918efab01efbc388103874844d4e56e04d00b6ae4b 2665011 libept_1.0.8.tar.gz 4d51d5f683b2678b4fc8fead896c6a624ebbce7427b9f0dac73e79293a43ab3c 14744 ept-cache_1.0.8_all.deb c5c7d2c0ef5346d6937712e934b117506b804ca1258e4b350179e77483270893 693836 libept-dev_1.0.8_amd64.deb 34eb924974bda85cd8ee8f4631fb6b3c0966df655730c2ad477dfae54852f82f 207114 libept1.4.12_1.0.8_amd64.deb
Bug#677548: marked as done (aptitude: linked against nonexisting libept.so.1.0.5.4.12)
Your message dated Thu, 14 Jun 2012 19:03:08 + with message-id e1sffk0-0007o4...@franck.debian.org and subject line Bug#677535: fixed in libept 1.0.8 has caused the Debian Bug report #677535, regarding aptitude: linked against nonexisting libept.so.1.0.5.4.12 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.) -- 677535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: aptitude Version: 0.6.8-1 Severity: important Dear Maintainer, aptitude is linked against an unavailable libept version. -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude linkage: linux-vdso.so.1 = (0x7fff6b525000) libapt-pkg.so.4.12 = /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x7f0e7d859000) libncursesw.so.5 = /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f0e7d629000) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f0e7d3ff000) libsigc-2.0.so.0 = /usr/lib/libsigc-2.0.so.0 (0x7f0e7d1fa000) libcwidget.so.3 = /usr/lib/libcwidget.so.3 (0x7f0e7cefa000) libept.so.1.0.5.4.12 = not found libxapian.so.22 = /usr/lib/libxapian.so.22 (0x7f0e7cb13000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f0e7c8fc000) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f0e7c65) libboost_iostreams.so.1.49.0 = /usr/lib/libboost_iostreams.so.1.49.0 (0x7f0e7c437000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0e7c21b000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f0e7bf13000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f0e7bc91000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f0e7ba7b000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f0e7b6f3000) libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7f0e7b4f) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0e7b2ec000) libbz2.so.1.0 = /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7f0e7b0db000) libuuid.so.1 = /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f0e7aed6000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f0e7accd000) /lib64/ld-linux-x86-64.so.2 (0x7f0e7e1fc000) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages aptitude depends on: ii aptitude-common 0.6.8-1 ii libapt-pkg4.120.9.6 ii libboost-iostreams1.49.0 1.49.0-3 ii libc6 2.13-33 ii libcwidget3 0.5.16-3.3 ii libept1.4.12 1.0.7 ii libgcc1 1:4.7.0-13 ii libncursesw5 5.9-8 ii libsigc++-2.0-0c2a2.2.10-0.1 ii libsqlite3-0 3.7.13-1 ii libstdc++64.7.0-13 ii libtinfo5 5.9-8 ii libxapian22 1.2.10-2 ii zlib1g1:1.2.7.dfsg-11 Versions of packages aptitude recommends: ii apt-xapian-index0.45 ii aptitude-doc-en [aptitude-doc] 0.6.8-1 ii libparse-debianchangelog-perl 1.2.0-1 ii sensible-utils 0.0.7 Versions of packages aptitude suggests: ii debtags 1.9.1 ii tasksel 3.09 -- no debconf information ---End Message--- ---BeginMessage--- Source: libept Source-Version: 1.0.8 We believe that the bug you reported is fixed in the latest version of libept, which is due to be installed in the Debian FTP archive: ept-cache_1.0.8_all.deb to main/libe/libept/ept-cache_1.0.8_all.deb libept-dev_1.0.8_amd64.deb to main/libe/libept/libept-dev_1.0.8_amd64.deb libept1.4.12_1.0.8_amd64.deb to main/libe/libept/libept1.4.12_1.0.8_amd64.deb libept_1.0.8.dsc to main/libe/libept/libept_1.0.8.dsc libept_1.0.8.tar.gz to main/libe/libept/libept_1.0.8.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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Enrico Zini enr...@debian.org (supplier of updated libept package) (This message was
Processed: reassign 677461 to liblapack-doc-man, tagging 677461
Processing commands for cont...@bugs.debian.org: reassign 677461 liblapack-doc-man 3.4.1-1 Bug #677461 [libblas-doc,liblapack-doc-man] liblapack-doc-man and libblas-doc: error when trying to install together Bug reassigned from package 'libblas-doc,liblapack-doc-man' to 'liblapack-doc-man'. Ignoring request to alter found versions of bug #677461 to the same values previously set Ignoring request to alter fixed versions of bug #677461 to the same values previously set Bug #677461 [liblapack-doc-man] liblapack-doc-man and libblas-doc: error when trying to install together Marked as found in versions lapack/3.4.1-1. tags 677461 + pending Bug #677461 [liblapack-doc-man] liblapack-doc-man and libblas-doc: error when trying to install together Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 677461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677461 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#664925: marked as done (viruskiller: FTBFS: src/pak.cpp:134:16: error: cannot convert 'FILE* {aka _IO_FILE*}' to 'gzFile' for argument '1' to 'int gzclose(gzFile)')
Your message dated Thu, 14 Jun 2012 19:06:28 +
with message-id e1sffne-0007cq...@franck.debian.org
and subject line Bug#664925: fixed in viruskiller 1.03-1+dfsg1-1
has caused the Debian Bug report #664925,
regarding viruskiller: FTBFS: src/pak.cpp:134:16: error: cannot convert 'FILE*
{aka _IO_FILE*}' to 'gzFile' for argument '1' to 'int gzclose(gzFile)'
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.)
--
664925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: viruskiller
Version: 1.0-1.dfsg.1-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120321 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++ `sdl-config --cflags` -DVERSION=1.0 -DRELEASE=1 -DUSEPAK=1
-DPAKNAME=\viruskiller.pak\ -DPAKLOCATION=\/usr/share/games/viruskiller/\
-DSAFEDIR=\/tmp/\ -DUNIX
-DGAMEPLAYMANUAL=\/usr/share/doc/viruskiller/manual.html\ -Wall -c
src/pak.cpp
src/pak.cpp: In function 'void recurseDirectory(char*)':
src/pak.cpp:134:16: error: cannot convert 'FILE* {aka _IO_FILE*}' to 'gzFile'
for argument '1' to 'int gzclose(gzFile)'
src/pak.cpp:166:16: error: cannot convert 'FILE* {aka _IO_FILE*}' to 'gzFile'
for argument '1' to 'int gzclose(gzFile)'
make[2]: *** [pak.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/21/viruskiller_1.0-1.dfsg.1-2.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: viruskiller
Source-Version: 1.03-1+dfsg1-1
We believe that the bug you reported is fixed in the latest version of
viruskiller, which is due to be installed in the Debian FTP archive:
viruskiller_1.03-1+dfsg1-1.debian.tar.xz
to main/v/viruskiller/viruskiller_1.03-1+dfsg1-1.debian.tar.xz
viruskiller_1.03-1+dfsg1-1.dsc
to main/v/viruskiller/viruskiller_1.03-1+dfsg1-1.dsc
viruskiller_1.03-1+dfsg1-1_kfreebsd-amd64.deb
to main/v/viruskiller/viruskiller_1.03-1+dfsg1-1_kfreebsd-amd64.deb
viruskiller_1.03-1+dfsg1.orig.tar.gz
to main/v/viruskiller/viruskiller_1.03-1+dfsg1.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 664...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stephen M. Webb stephen.w...@bregmasoft.ca (supplier of updated viruskiller
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, 12 Apr 2012 15:45:58 -0400
Source: viruskiller
Binary: viruskiller
Architecture: source kfreebsd-amd64
Version: 1.03-1+dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
Changed-By: Stephen M. Webb stephen.w...@bregmasoft.ca
Description:
viruskiller - Game about viruses invading your computer
Closes: 617955 664925
Changes:
viruskiller (1.03-1+dfsg1-1) unstable; urgency=low
.
* Merged new upstream 1.03-1 (closes: #617955)
* debian/rules: adjusted for changed build targets
* debian/control: added myself as uploader, ran wrap-and-sort
* added a build depndency on libsdl-net1.2-dev
* fixed a FTBFS due to wrong call (closes: #664925)
* bumped Standards-Version to 3.9.3
- debian/copyright: updated Format to Version 1.0 of the specification
Checksums-Sha1:
d04a9bc2c26f8a202dc01f066b380771bf86f001 1823 viruskiller_1.03-1+dfsg1-1.dsc
33d69916774c0e285206da8087f276a0dd868cce 2524407
viruskiller_1.03-1+dfsg1.orig.tar.gz
0b38ee6cf2ab5148083cacfebc2845fc04b1907b 7104
viruskiller_1.03-1+dfsg1-1.debian.tar.xz
7e4104135f3cfca26d50145c8c87cff85d59face 2411934
viruskiller_1.03-1+dfsg1-1_kfreebsd-amd64.deb
Checksums-Sha256:
fa18a9309865ecfc47bc18056330112c02c49747026630d3004da30a2fb0957d 1823
viruskiller_1.03-1+dfsg1-1.dsc
b2861cfabbd799f885bcfbb3cbca88b08246eb5734e0a6f44dabcd0a1858ae4d 2524407
Bug#555168: [Traduc] Bug#555168: Unclear license situation for (e)glibc locales provided by you
Hello Jean-Philippe, On Thu, Jun 14, 2012 at 02:29:23PM +0200, Jean-Philippe Guérard wrote: At that time, the license was not discussed, as we were under the impression this file was part of the glibc and distributed under the same license. The original author of this file is Keld Jørn Simonsen. Provided that Keld Jørn Simonsen agree with this, we would be very happy to see this file officially put under a Free license. Using the same license as the glibc would be fine for us. Do you have a working e-mail address of Keld? The one listed in the files no longer works. Hope that helps. Yes, definitly. Hopefully Keld can be contacted, this would solve many other problematic locales as well. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Processed: Re: Bug#669522: coinor-cbc: FTBFS: make[3]: *** No rule to make target `/usr/lib/libCgl.la', needed by `cbc'. Stop.
Processing commands for cont...@bugs.debian.org: tags 669522 patch Bug #669522 [src:coinor-cbc] coinor-cbc: FTBFS: make[3]: *** No rule to make target `/usr/lib/libCgl.la', needed by `cbc'. Stop. Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 669522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669522 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#669522: coinor-cbc: FTBFS: make[3]: *** No rule to make target `/usr/lib/libCgl.la', needed by `cbc'. Stop.
tags 669522 patch thanks Lucas Nussbaum lu...@lucas-nussbaum.net writes: During a rebuild of all packages in sid, your package failed to build on amd64. It should build fine with the attached patch. It was caused by libCgl.la no longer being shipped by coinor-libcgl-dev (see #633173). Vincent diff -Nru coinor-cbc-2.5.0/debian/changelog coinor-cbc-2.5.0/debian/changelog --- coinor-cbc-2.5.0/debian/changelog 2011-12-21 21:37:09.0 +0100 +++ coinor-cbc-2.5.0/debian/changelog 2012-06-14 20:52:23.0 +0200 @@ -1,3 +1,11 @@ +coinor-cbc (2.5.0-2.4) unstable; urgency=low + + * Non-maintainer upload. + * patches/Makefile.diff: .la files are no longer shipped by some -dev +libraries. Link against them using -l instead. (Closes: #669522) + + -- Vincent Legout vleg...@debian.org Thu, 14 Jun 2012 20:50:26 +0200 + coinor-cbc (2.5.0-2.3) unstable; urgency=low * Non-maintainer upload. diff -Nru coinor-cbc-2.5.0/debian/patches/Makefile.diff coinor-cbc-2.5.0/debian/patches/Makefile.diff --- coinor-cbc-2.5.0/debian/patches/Makefile.diff 2009-09-24 15:52:59.0 +0200 +++ coinor-cbc-2.5.0/debian/patches/Makefile.diff 2012-06-14 20:36:09.0 +0200 @@ -1,7 +1,7 @@ -Index: coinor-cbc-2.3.1/Cbc/src/Makefile.in +Index: coinor-cbc-2.5.0/Cbc/src/Makefile.in === coinor-cbc-2.3.1.orig/Cbc/src/Makefile.in 2009-07-28 14:38:50.0 +0200 -+++ coinor-cbc-2.3.1/Cbc/src/Makefile.in 2009-09-24 15:43:37.0 +0200 +--- coinor-cbc-2.5.0.orig/Cbc/src/Makefile.in 2012-06-14 20:31:14.694313988 +0200 coinor-cbc-2.5.0/Cbc/src/Makefile.in 2012-06-14 20:36:01.774321892 +0200 @@ -59,7 +59,7 @@ @COIN_HAS_CLP_TRUE@ -I`$(CYGPATH_W) $(OSISRCDIR)/src/OsiClp` \ @COIN_HAS_CLP_TRUE@ -I`$(CYGPATH_W) $(CLPOBJDIR)/inc` @@ -17,8 +17,8 @@ -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@am__append_10 = $(OSIOBJDIR)/src/OsiClp/libOsiClp.la \ -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@ $(CLPOBJDIR)/src/libClp.la -+@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@am__append_10 = /usr/lib/libOsiClp.la \ -+@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@ /usr/lib/libClp.la ++@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@am__append_10 = -lOsiClp \ ++@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@ -lClp -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@am__append_11 = `cat $(CLPOBJDIR)/clp_addlibs.txt` +@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_CLP_TRUE@am__append_11 = -lClp @@ -31,8 +31,8 @@ -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@am__append_15 = $(OSIOBJDIR)/src/OsiDylp/libOsiDylp.la \ -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@ $(DYLPOBJDIR)/src/Dylp/libDylp.la -+@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@am__append_15 = /usr/lib/libOsiDylp.la \ -+@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@ /usr/lib/libDylp.la ++@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@am__append_15 = -lOsiDylp \ ++@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@ -lDylp -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@am__append_16 = `cat $(DYLPOBJDIR)/dylp_addlibs.txt` +@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_DYLP_TRUE@am__append_16 = -lDylp @@ -44,7 +44,7 @@ @CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_SYMPHONY_TRUE@ -I`$(CYGPATH_W) $(OSISRCDIR)/src/OsiSym` -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_SYMPHONY_TRUE@am__append_28 = $(OSIOBJDIR)/src/OsiSym/libOsiSym.la \ -+@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_SYMPHONY_TRUE@am__append_28 = /usr/lib/libOsiSym.la \ ++@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_SYMPHONY_TRUE@am__append_28 = -lOsiSym \ @CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_SYMPHONY_TRUE@ $(SYMPHONYOBJDIR)/src/libSym.la @CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_SYMPHONY_TRUE@am__append_29 = `cat $(SYMPHONYOBJDIR)/sym_addlibs.txt` @@ -53,15 +53,15 @@ -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@am__append_31 = $(OSIOBJDIR)/src/OsiVol/libOsiVol.la \ -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@ $(VOLOBJDIR)/src/libVol.la -+@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@am__append_31 = /usr/lib/libOsiVol.la \ -+@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@ /usr/lib/libVol.la ++@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@am__append_31 = -lOsiVol \ ++@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@ -lVol -@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@am__append_32 = `cat $(VOLOBJDIR)/vol_addlibs.txt` +@CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_VOL_TRUE@am__append_32 = -lVol @CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_XPR_TRUE@am__append_33 = -I`$(CYGPATH_W) $(XPRINCDIR)` \ @CBC_BUILD_CBC_GENERIC_TRUE@@COIN_HAS_XPR_TRUE@ -I`$(CYGPATH_W) $(OSISRCDIR)/src/OsiXpr` -@@ -190,11 +190,11 @@ +@@ -204,11 +204,11 @@ @COIN_HAS_ASL_TRUE@@COIN_HAS_CLP_TRUE@am__DEPENDENCIES_3 = \ @COIN_HAS_ASL_TRUE@@COIN_HAS_CLP_TRUE@ $(am__DEPENDENCIES_2) @COIN_HAS_CLP_TRUE@cbc_DEPENDENCIES = libCbcSolver.la libCbc.la \ @@ -70,27 +70,27 @@ -@COIN_HAS_CLP_TRUE@ $(OSIOBJDIR)/src/libOsi.la \ -@COIN_HAS_CLP_TRUE@
Bug#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
On Thu, Jun 14, 2012 at 01:59:25PM -0400, Michael Gilbert wrote: I did not suggest that. Anyway, maybe this will be a bit clearer. Let's say an existing package is at version +b1 on amd64, and it needs to get a binnmu, then a +b2 package is built on amd64, its changelog is taken and stuffed it into all of the other 'Multi-Arch: same' +b1 packages, which are now called +b2, and all of them uploaded. For various reasons you cannot do that without a rebuild. (Hint: Files must not change, new versions have their versions in various fields.) Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#555168: [Traduc] Bug#555168: Unclear license situation for (e)glibc locales provided by you
Quoting Helge Kreutzmann (deb...@helgefjell.de): Hello Jean-Philippe, On Thu, Jun 14, 2012 at 02:29:23PM +0200, Jean-Philippe Guérard wrote: At that time, the license was not discussed, as we were under the impression this file was part of the glibc and distributed under the same license. The original author of this file is Keld Jørn Simonsen. Provided that Keld Jørn Simonsen agree with this, we would be very happy to see this file officially put under a Free license. Using the same license as the glibc would be fine for us. Do you have a working e-mail address of Keld? The one listed in the files no longer works. Jean-Philippe added k...@keldix.com to the CC field so I guess that might be what's needed. signature.asc Description: Digital signature
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Thursday 14 June 20:03:26 UTC 2012 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: libio-html-perl tags 677531 + pending Bug #677531 [wnpp] ITP: libio-html-perl -- open an HTML file with automatic charset detection Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/narval;narval/a tags 642650 + pending Bug #642650 [src:narval] narval: FTBFS: unsatisfiable build-dependencies: gnat, libpolyorb1-dev, libaws2.7-dev, libaws-bin Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 642650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642650 677531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677531 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#672842: goffice: binNMUs are not installable
Hi,
Am 14.06.2012 09:22, schrieb Micha Lenk:
We have binNMUed goffice on hurd-i386, and it is now uninstallable:
This is actually a Debian policy violation and hence I just raised the
severity to serious. It also makes other packages (e.g. gnucash) unable
to build due to uninstallable build dependencies.
I just prepared an NMU to fix the package, that I am going to upload
just now. You can find the resulting debdiff output attached.
Regards,
Micha
diff -Nru goffice-0.8.17/debian/changelog goffice-0.8.17/debian/changelog
--- goffice-0.8.17/debian/changelog 2012-04-09 00:44:03.0 +0200
+++ goffice-0.8.17/debian/changelog 2012-06-14 21:21:25.0 +0200
@@ -1,3 +1,12 @@
+goffice (0.8.17-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Make package binNMU safe by using ${source:Version} instead of
+${binary:Version} in dependency on libgoffice-0.8-8-common (closes:
+#672842). Thanks to Pino Toscano (pino) for providing the patch.
+
+ -- Micha Lenk mi...@debian.org Thu, 14 Jun 2012 21:18:08 +0200
+
goffice (0.8.17-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru goffice-0.8.17/debian/control goffice-0.8.17/debian/control
--- goffice-0.8.17/debian/control 2012-04-09 00:44:03.0 +0200
+++ goffice-0.8.17/debian/control 2012-06-14 21:17:33.0 +0200
@@ -46,7 +46,7 @@
Architecture: any
Breaks: libgoffice-0-8
Replaces: libgoffice-0-8
-Depends: ${shlibs:Depends}, libgoffice-0.8-8-common (= ${binary:Version}),
${misc:Depends}
+Depends: ${shlibs:Depends}, libgoffice-0.8-8-common (= ${source:Version}),
${misc:Depends}
Description: Document centric objects library - runtime files
GOffice is a library of document centric objects and utilities building on
top of GLib and Gtk+.
Processed: severity of 663539 is important, tagging 663539
Processing commands for cont...@bugs.debian.org: severity 663539 important Bug #663539 [ekiga] ekiga crash SIP SetUpConnection( BAD ENCODING ) Severity set to 'important' from 'grave' tags 663539 + upstream moreinfo unreproducible Bug #663539 [ekiga] ekiga crash SIP SetUpConnection( BAD ENCODING ) Added tag(s) unreproducible, upstream, and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 663539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663539 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#665234: libpoe-component-client-mpd-perl: FTBFS: tests hang
Hi, gregor herrmann wrote (09 Jun 2012 22:27:44 GMT) : Yup, still FBTFS: No answer from upstream so far. This is a leaf package, very low popcon. In addition, I don't know anything to POE, so I won't try to fix this. Ryan, looks like (#517953) you uploaded it for your own needs, do you still use it? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Reassess severity
Processing commands for cont...@bugs.debian.org: severity 636874 grave Bug #636874 [gnome-shell] gnome-shell: random characters are missing Severity set to 'grave' from 'important' thanks, Unknown command or malformed arguments to command. According to [1]: Unknown command or malformed arguments to command. grave Unknown command or malformed arguments to command. makes the package in question unusable or mostly so, or causes data Unknown command or malformed arguments to command. loss, or introduces a security hole allowing access to the accounts of Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 636874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636874 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#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability
On Thu, Jun 14, 2012 at 3:43 PM, Philipp Kern wrote:
On Thu, Jun 14, 2012 at 01:59:25PM -0400, Michael Gilbert wrote:
I did not suggest that. Anyway, maybe this will be a bit clearer.
Let's say an existing package is at version +b1 on amd64, and it needs
to get a binnmu, then a +b2 package is built on amd64, its changelog
is taken and stuffed it into all of the other 'Multi-Arch: same' +b1
packages, which are now called +b2, and all of them uploaded.
For various reasons you cannot do that without a rebuild. (Hint: Files must
not
change, new versions have their versions in various fields.)
Right, there is that additional complexity, but even so I think it
could be made to work.
dpkg-gencontrol could be used to update the Version and any
${binary:Version} fields in the control file. Also, the package's
md5sums could be regenerated to include the hash for the new
changelog.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672842: marked as done (goffice: binNMUs are not installable)
Your message dated Thu, 14 Jun 2012 21:37:52 +
with message-id e1sfhjk-0007um...@franck.debian.org
and subject line Bug#672842: fixed in goffice 0.8.17-1.2
has caused the Debian Bug report #672842,
regarding goffice: binNMUs are not installable
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.)
--
672842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: goffice
Version: 0.8.17-1.1
Severity: important
Hello,
We have binNMUed goffice on hurd-i386, and it is now uninstallable:
libgoffice-0.8-8 : Depends: libgoffice-0.8-8-common (= 0.8.17-1.1+b1) but
0.8.17-1.1 is to be installed
Some tweaks with the version is probably needed to make it work.
Samuel
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
Samuel Thibault samuel.thiba...@fnac.net
J'ai un gros problème: j'ai cet exercice à rendre demain lundi, mais ma
TI 89 ne sait pas le faire...
Est-ce que quelqu'un pourrait m'aider??
-+- OD In Guide du Neuneu Usenet : Comment ça ! Il faut réfléchir ?-+-
---End Message---
---BeginMessage---
Source: goffice
Source-Version: 0.8.17-1.2
We believe that the bug you reported is fixed in the latest version of
goffice, which is due to be installed in the Debian FTP archive:
goffice_0.8.17-1.2.debian.tar.gz
to main/g/goffice/goffice_0.8.17-1.2.debian.tar.gz
goffice_0.8.17-1.2.dsc
to main/g/goffice/goffice_0.8.17-1.2.dsc
libgoffice-0.8-8-common_0.8.17-1.2_all.deb
to main/g/goffice/libgoffice-0.8-8-common_0.8.17-1.2_all.deb
libgoffice-0.8-8_0.8.17-1.2_i386.deb
to main/g/goffice/libgoffice-0.8-8_0.8.17-1.2_i386.deb
libgoffice-0.8-dev_0.8.17-1.2_i386.deb
to main/g/goffice/libgoffice-0.8-dev_0.8.17-1.2_i386.deb
libgoffice-dbg_0.8.17-1.2_i386.deb
to main/g/goffice/libgoffice-dbg_0.8.17-1.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.
Micha Lenk mi...@debian.org (supplier of updated goffice 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, 14 Jun 2012 21:18:08 +0200
Source: goffice
Binary: libgoffice-0.8-dev libgoffice-dbg libgoffice-0.8-8
libgoffice-0.8-8-common
Architecture: source all i386
Version: 0.8.17-1.2
Distribution: unstable
Urgency: low
Maintainer: J.H.M. Dassen (Ray) jdas...@debian.org
Changed-By: Micha Lenk mi...@debian.org
Description:
libgoffice-0.8-8 - Document centric objects library - runtime files
libgoffice-0.8-8-common - Document centric objects library - common files
libgoffice-0.8-dev - Document centric objects library - runtime files
libgoffice-dbg - Document centric objects library - debugging files
Closes: 672842
Changes:
goffice (0.8.17-1.2) unstable; urgency=low
.
* Non-maintainer upload.
* Make package binNMU safe by using ${source:Version} instead of
${binary:Version} in dependency on libgoffice-0.8-8-common (closes:
#672842). Thanks to Pino Toscano (pino) for providing the patch.
Checksums-Sha1:
96fa0115fd56120c26f6d9e964deabc4c776e5ce 2383 goffice_0.8.17-1.2.dsc
d8bab697c7d64449bbf168ab159cd20eae393c20 20665 goffice_0.8.17-1.2.debian.tar.gz
1d47933d9f3beb6ce6ed324d788a29de3fd71052 1321802
libgoffice-0.8-8-common_0.8.17-1.2_all.deb
93229aff09141c0c17e58f87e045da0a62db4874 1221502
libgoffice-0.8-dev_0.8.17-1.2_i386.deb
1baf6add950bd15447057883b1af48b7b3a015ad 2240470
libgoffice-dbg_0.8.17-1.2_i386.deb
817775c5d79a203eede934bbaa81f84b63f23221 1785534
libgoffice-0.8-8_0.8.17-1.2_i386.deb
Checksums-Sha256:
fc2f0778ab33ba55f0f10b06b7d4fdec815aae1911f9ef546626e7c28629953a 2383
goffice_0.8.17-1.2.dsc
c8131eadedba3f381cfc8939fe4dd9f748c7a640255706a10a423316e30f288b 20665
goffice_0.8.17-1.2.debian.tar.gz
121959b6775ef2c0976c365c1bfa680b79e3311722d9bf7f78a462cabf1cdf61 1321802
libgoffice-0.8-8-common_0.8.17-1.2_all.deb
484df7df13f64889fc89bd7c0e55b66be4b46cc61dbdc940e9633fc8137f73dc
Bug#667737: marked as done (libnet-server-perl: no IPv4 server when binding to localhost)
Your message dated Thu, 14 Jun 2012 21:41:20 + with message-id e1sfhn6-0007ml...@franck.debian.org and subject line Bug#667737: fixed in libnet-server-perl 2.005-1 has caused the Debian Bug report #667737, regarding libnet-server-perl: no IPv4 server when binding to localhost 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.) -- 667737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: librpc-xml-perl Version: 0.76-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120331 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' /usr/bin/perl etc/make_method --base=lib/Apache/RPC/status /usr/bin/perl etc/make_method --base=methods/identity /usr/bin/perl etc/make_method --base=methods/introspection /usr/bin/perl etc/make_method --base=methods/listMethods /usr/bin/perl etc/make_method --base=methods/methodHelp /usr/bin/perl etc/make_method --base=methods/methodSignature /usr/bin/perl etc/make_method --base=methods/multicall /usr/bin/perl etc/make_method --base=methods/status cp methods/status.xpl blib/lib/RPC/XML/status.xpl cp lib/Apache/RPC/Status.pm blib/lib/Apache/RPC/Status.pm cp methods/methodHelp.xpl blib/lib/RPC/XML/methodHelp.xpl cp lib/RPC/XML/Procedure.pm blib/lib/RPC/XML/Procedure.pm cp methods/introspection.xpl blib/lib/RPC/XML/introspection.xpl cp lib/RPC/XML/Parser/XMLLibXML.pm blib/lib/RPC/XML/Parser/XMLLibXML.pm cp lib/RPC/XML/Parser.pm blib/lib/RPC/XML/Parser.pm cp methods/identity.xpl blib/lib/RPC/XML/identity.xpl cp lib/RPC/XML/Server.pm blib/lib/RPC/XML/Server.pm cp lib/Apache/RPC/Server.pm blib/lib/Apache/RPC/Server.pm cp methods/multicall.xpl blib/lib/RPC/XML/multicall.xpl cp lib/Apache/RPC/status.xpl blib/lib/Apache/RPC/status.xpl cp lib/RPC/XML.pm blib/lib/RPC/XML.pm cp methods/listMethods.xpl blib/lib/RPC/XML/listMethods.xpl cp lib/RPC/XML/Client.pm blib/lib/RPC/XML/Client.pm cp methods/methodSignature.xpl blib/lib/RPC/XML/methodSignature.xpl cp lib/RPC/XML/ParserFactory.pm blib/lib/RPC/XML/ParserFactory.pm cp lib/RPC/XML/Parser/XMLParser.pm blib/lib/RPC/XML/Parser/XMLParser.pm cp etc/make_method blib/script/make_method /usr/bin/perl -MExtUtils::MY -e 'MY-fixin(shift)' -- blib/script/make_method PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00_load.t . ok t/10_data.t . ok t/11_base64_fh.t ok t/12_nil.t .. ok t/13_no_deep_recursion.t ok t/14_datetime_iso8601.t . ok t/15_serialize.t ok t/20_xml_parser.t ... ok t/21_xml_libxml.t ... ok t/25_parser_negative.t .. ok t/29_parserfactory.t ok t/30_method.t ... ok t/35_namespaces.t ... ok t/40_server.t ... ok t/40_server_xmllibxml.t . ok t/41_server_hang.t .. ok t/50_client.t ... ok t/51_client_with_host_header.t .. ok # Failed test 'system.identity matches $srv-product_tokens' # at t/60_net_server.t line 60. # got: undef # expected: 'RPC::XML::Server/1.68' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 68. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 80. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 90. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned HASH ref' # at t/60_net_server.t line 100. # got: '' # expected: 'HASH' # Failed test 'system.methodHelp returned correct string' # at t/60_net_server.t line 110. # got: undef # expected: 'Return the server name and version as a string' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 116. # got: '' # expected: 'ARRAY' # Failed test 'system.methodHelp (bad arg) response isa RPC::XML::fault' # at t/60_net_server.t line 127. # system.methodHelp (bad arg) response isn't a 'RPC::XML::fault' it's a '' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 136. # got: '' #
Bug#636874: Reassess severity
severity 636874 important thanks On 14.06.2012 23:19, Abou Al Montacir wrote: severity 636874 grave thanks, According to [1]: grave 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. Here gnome3 is no more usable on my system as most characters and icons are gone and launching any application becomes a guess party especially when you start the system and do not have any shell open. Adding the fact that using alt+f2 hangs the system once over tow trials, I think that the grave severity is fully justified. Nope, important is the right severity. This bug seems to only affects a small percentage of users and is most likely hardware/driver/X related and not a gnome-shell problem at all. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#636874: Reassess severity
Processing commands for cont...@bugs.debian.org: severity 636874 important Bug #636874 [gnome-shell] gnome-shell: random characters are missing Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 636874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636874 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#677565: msva-perl: Insecure dependency in socket while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 80
Package: msva-perl Version: 0.8-2 Severity: grave $ cat $HOME/.monkeysphere/monkeysphere.conf USE_VALIDATION_AGENT=true KEYSERVER=keys.indymedia.org $ . $HOME/.monkeysphere/monkeysphere.conf $ msva-perl Use of uninitialized value $loglevel in lc at /usr/share/perl5/Crypt/Monkeysphere/MSVA/Logger.pm line 91. Insecure dependency in socket while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 80. zsh: exit 255 msva-perl This might be related to upgrading libnet-server-perl to 2.005-1. (Removing the -T flag in /usr/bin/msva-perl = the second error message is replaced with: 2 sockets open; should have been 1. zsh: exit 10msva-perl This may be due to the new Net::Server binding to both IPv4 and IPv6. ) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677467: marked as done (gnucash is built with all patches reverted)
Your message dated Thu, 14 Jun 2012 22:02:56 + with message-id e1sfi80-0001sj...@franck.debian.org and subject line Bug#677467: fixed in gnucash 1:2.4.10-4 has caused the Debian Bug report #677467, regarding gnucash is built with all patches reverted 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.) -- 677467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Source: gnucash Version: 1:2.4.10-3 Severity: serious Am 13.06.2012 22:49, schrieb Sébastien Villemot: with the upload of libaqbanking 5.0.24-1 I broke the gnucash package. Hence I uploaded gnucash 1:2.4.10-3 with the changes currently in our Git repository. I just realized that something went wrong there. There is a file called debian/patches/debian-changes-1:2.4.10-3 that sneaked into the source package, while not being in git. This patch basically reverts several of the other patches (FTBFS on Hurd, missing manpages). Micha: do you confirm that this is a mistake? If yes, we should just upload a version 1:2.4.10-4 just like that in git, and preferably before 1:2.4.10-3 hits testing. This is indeed a bug. So, let's track it in the bug tracker (done) with severity serious, so it will prevent testing migration immediately. I will take care of fixing it as soon as possible. Regards, Micha -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJP2ZAWAAoJEOpsprlRuFE5KoMP/05Yl+FPP+CnHjIjxm92ovLM FagwAjnPSVfQbmdnjMbAzTCdUjcEXATFRLSV4s0xbvBzHyvDwjHxh9AJeL5v9ldg wmqdtfXtVOm0R414sCY94OsZbC0OAS+8VfKFbjizvSJz0tCyBghwcwpzMdf435+k 6ymRSsbcxtHhzt3766gejZX8iqhgd5/2hBwOHoR82xcPGE9tFVl+SUSYku0vfCbE G95Pvevcmrrq0WHtS08XauP7E/wrgA35TcCyHd0nhPDKbYx++FoQG5LAK6hbZ3zg bgXca7HI0Y00drUEX7EVgrJzSK8CuR5HW9Kpd/iQ7zn5wpKy6JHraooamY+gl5S+ dzCBI0KO3sLTzCN7Xg7eW9/YD57XOdwrXtxomsuOTC11b39lEm9H5B6kNbnCUZxN U9D1O6GvCL7p+x5e6K1qVpWzTDkKG9V64GZERaaGKMsfRSffgBeqRgHRDLopF9BS JvTfZFLVtqOYSotLoznoKSagFcgMJPI6qaMDRN3Gwenmmg3O3VRTKII2fAkV0x1c Rci0YIcQLQikizhrbQf9vHKp5ZJEGnMM4jYB0ad6GsWNMy6oWyMDLBxEI6MuSBl3 41UgRL1r1+hjILPhosjHYkYt++0I8gGPrZap5j+qrQMBCgBM2tlohhC6CspEe0+5 TCllMb/kKn7oZVSXUHX+ =OPhl -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: gnucash Source-Version: 1:2.4.10-4 We believe that the bug you reported is fixed in the latest version of gnucash, which is due to be installed in the Debian FTP archive: gnucash-common_2.4.10-4_all.deb to main/g/gnucash/gnucash-common_2.4.10-4_all.deb gnucash-dbg_2.4.10-4_i386.deb to main/g/gnucash/gnucash-dbg_2.4.10-4_i386.deb gnucash_2.4.10-4.debian.tar.gz to main/g/gnucash/gnucash_2.4.10-4.debian.tar.gz gnucash_2.4.10-4.dsc to main/g/gnucash/gnucash_2.4.10-4.dsc gnucash_2.4.10-4_i386.deb to main/g/gnucash/gnucash_2.4.10-4_i386.deb python-gnucash_2.4.10-4_i386.deb to main/g/gnucash/python-gnucash_2.4.10-4_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 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Micha Lenk mi...@debian.org (supplier of updated gnucash 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, 14 Jun 2012 22:52:30 +0200 Source: gnucash Binary: gnucash gnucash-dbg gnucash-common python-gnucash Architecture: source i386 all Version: 1:2.4.10-4 Distribution: unstable Urgency: low Maintainer: Sébastien Villemot sebastien.ville...@ens.fr Changed-By: Micha Lenk mi...@debian.org Description: gnucash- personal and small-business financial-accounting software gnucash-common - common files for the financial-accounting software Gnucash gnucash-dbg - debugging symbols for the accounting software Gnucash python-gnucash - Gnucash interface for Python Closes: 677467 Changes: gnucash (1:2.4.10-4) unstable; urgency=low . * Remove accidentally sneaked-in patch debian-changes-1:2.4.10-3 that reverted all or most of the intended patches (closes: #677467). Thanks to Sébastien Villemot for realizing and reporting it. Checksums-Sha1: 7974f53cd93d476b36225ec231b80ccd74745f98 2416 gnucash_2.4.10-4.dsc
Bug#639466: marked as done (bacula: Please move to postgresql-9.1)
Your message dated Thu, 14 Jun 2012 22:17:17 +
with message-id e1sfilt-0002zy...@franck.debian.org
and subject line Bug#639466: fixed in bacula 5.2.6+dfsg-1
has caused the Debian Bug report #639466,
regarding bacula: Please move to postgresql-9.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.)
--
639466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: bacula
Severity: important
Version: 5.0.3-1
User: mp...@debian.org
Usertags: psql-8.4-deprecation
Hello,
as announced recently [1] we want to move Debian unstable/testing to
postgresql-9.1 and drop postgresql-8.4 and -9.0 completely. bacula is
one of the remaining reverse dependencies of -8.4.
Please rebuild this package against postgresql-server-dev-9.1 instead
of -8.4, or consider just using postgresql-server-dev-all.
While you are at it, please also clean up the dependencies to use the
metapackages:
-Depends: bacula-director-common (= ${binary:Version}), dbconfig-common (=
1.8.19), postgresql-client (= 7.4) | postgresql-client-8.4, ${shlibs:Depends},
bacula-common-pgsql (= ${binary:Version}), ${misc:Depends}
+Depends: bacula-director-common (= ${binary:Version}), dbconfig-common (=
1.8.19), postgresql-client (= 7.4), ${shlibs:Depends}, bacula-common-pgsql (=
${binary:Version}), ${misc:Depends}
-Recommends: postgresql-8.4 | postgresql-8.3 | postgresql-8.2 | postgresql-8.1
| postgresql-8.0 | postgresql (= 7.4)
+Recommends: postgresql (= 7.4)
Thanks for considering,
Martin
[1]
http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2011-August/000570.html
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: bacula
Source-Version: 5.2.6+dfsg-1
We believe that the bug you reported is fixed in the latest version of
bacula, which is due to be installed in the Debian FTP archive:
bacula-client_5.2.6+dfsg-1_all.deb
to main/b/bacula/bacula-client_5.2.6+dfsg-1_all.deb
bacula-common-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-mysql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-mysql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-mysql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-mysql_5.2.6+dfsg-1_amd64.deb
bacula-common-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-pgsql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-pgsql_5.2.6+dfsg-1_amd64.deb
bacula-common-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-sqlite3_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-sqlite3_5.2.6+dfsg-1_amd64.deb
bacula-common_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common_5.2.6+dfsg-1_amd64.deb
bacula-console-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console-dbg_5.2.6+dfsg-1_amd64.deb
bacula-console-qt-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console-qt-dbg_5.2.6+dfsg-1_amd64.deb
bacula-console-qt_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console-qt_5.2.6+dfsg-1_amd64.deb
bacula-console_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console_5.2.6+dfsg-1_amd64.deb
bacula-director-common-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-common-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-common_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-common_5.2.6+dfsg-1_amd64.deb
bacula-director-mysql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-mysql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-mysql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-mysql_5.2.6+dfsg-1_amd64.deb
bacula-director-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-pgsql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-pgsql_5.2.6+dfsg-1_amd64.deb
bacula-director-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-sqlite3_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-sqlite3_5.2.6+dfsg-1_amd64.deb
bacula-fd-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-fd-dbg_5.2.6+dfsg-1_amd64.deb
bacula-fd_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-fd_5.2.6+dfsg-1_amd64.deb
bacula-sd-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-dbg_5.2.6+dfsg-1_amd64.deb
Bug#658326: marked as done (bacula: sha implimentation is non-free)
Your message dated Thu, 14 Jun 2012 22:17:17 +
with message-id e1sfilt-0002zn...@franck.debian.org
and subject line Bug#658326: fixed in bacula 5.2.6+dfsg-1
has caused the Debian Bug report #658326,
regarding bacula: sha implimentation is non-free
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.)
--
658326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: bacula
Severity: serious
Justification: DFSG violation
User: gnewsense-...@nongnu.org
Usertags: gnewsense libreplanet
Hi,
The sha1 implimentation shipped in stable and oldstable appears to be
taken directly from the RFC, with dfsg incompatible licence statements.
The affected files are src/lib/sha1.{h,c}
thanks,
kk
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: bacula
Source-Version: 5.2.6+dfsg-1
We believe that the bug you reported is fixed in the latest version of
bacula, which is due to be installed in the Debian FTP archive:
bacula-client_5.2.6+dfsg-1_all.deb
to main/b/bacula/bacula-client_5.2.6+dfsg-1_all.deb
bacula-common-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-mysql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-mysql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-mysql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-mysql_5.2.6+dfsg-1_amd64.deb
bacula-common-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-pgsql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-pgsql_5.2.6+dfsg-1_amd64.deb
bacula-common-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
bacula-common-sqlite3_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common-sqlite3_5.2.6+dfsg-1_amd64.deb
bacula-common_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-common_5.2.6+dfsg-1_amd64.deb
bacula-console-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console-dbg_5.2.6+dfsg-1_amd64.deb
bacula-console-qt-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console-qt-dbg_5.2.6+dfsg-1_amd64.deb
bacula-console-qt_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console-qt_5.2.6+dfsg-1_amd64.deb
bacula-console_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-console_5.2.6+dfsg-1_amd64.deb
bacula-director-common-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-common-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-common_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-common_5.2.6+dfsg-1_amd64.deb
bacula-director-mysql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-mysql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-mysql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-mysql_5.2.6+dfsg-1_amd64.deb
bacula-director-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-pgsql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-pgsql_5.2.6+dfsg-1_amd64.deb
bacula-director-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
bacula-director-sqlite3_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-director-sqlite3_5.2.6+dfsg-1_amd64.deb
bacula-fd-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-fd-dbg_5.2.6+dfsg-1_amd64.deb
bacula-fd_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-fd_5.2.6+dfsg-1_amd64.deb
bacula-sd-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-dbg_5.2.6+dfsg-1_amd64.deb
bacula-sd-mysql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-mysql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-sd-mysql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-mysql_5.2.6+dfsg-1_amd64.deb
bacula-sd-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-pgsql-dbg_5.2.6+dfsg-1_amd64.deb
bacula-sd-pgsql_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-pgsql_5.2.6+dfsg-1_amd64.deb
bacula-sd-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
bacula-sd-sqlite3_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd-sqlite3_5.2.6+dfsg-1_amd64.deb
bacula-sd_5.2.6+dfsg-1_amd64.deb
to main/b/bacula/bacula-sd_5.2.6+dfsg-1_amd64.deb
bacula-server_5.2.6+dfsg-1_all.deb
to main/b/bacula/bacula-server_5.2.6+dfsg-1_all.deb
Bug#672765: marked as done (FTBFS: Cannot find libmysqlclient following multi-arch conversion)
Your message dated Thu, 14 Jun 2012 22:17:17 + with message-id e1sfilt-000307...@franck.debian.org and subject line Bug#672765: fixed in bacula 5.2.6+dfsg-1 has caused the Debian Bug report #672765, regarding FTBFS: Cannot find libmysqlclient following multi-arch conversion 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.) -- 672765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:bacula Version: 5.0.3+dfsg-0.1 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) autoconf/bacula-macros/db.m4 looks for libmysqlclient_r.so in various directories, but never in the multi-arch installation directory. As a result, it doesn't link libacsql properly and the various executables then fail to link: ... Linking bacula-dir ... /tmp/buildd/bacula-5.0.3+dfsg/debian/tmp-build-mysql/libtool --silent --tag=CXX --mode=link /usr/lib/ccache/i486-linux-gnu-g++ -L../lib -L../cats -L../findlib -o bacula-dir dird.o admin.o authenticate.o autoprune.o backup.o bsr.o catreq.o dir_plugins.o dird_conf.o expand.o fd_cmds.o getmsg.o inc_conf.o job.o jobq.o migrate.o mountreq.o msgchan.o next_vol.o newvol.o pythondir.o recycle.o restore.o run_conf.o scheduler.o ua_acl.o ua_cmds.o ua_dotcmds.o ua_query.o ua_input.o ua_label.o ua_output.o ua_prune.o ua_purge.o ua_restore.o ua_run.o ua_select.o ua_server.o ua_status.o ua_tree.o ua_update.o vbackup.o verify.o \ -lbacfind -lbacsql -lbacpy -lbaccfg -lbac -lm -lpthread -ldl -lutil -lm -lpython2.7 -lutil -lrt-lpthread -ldl \ -lwrap -lssl -lcrypto /tmp/buildd/bacula-5.0.3+dfsg/debian/tmp-build-mysql/src/cats/.libs/libbacsql.so: undefined reference to `mysql_fetch_field' ... Ben. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-2-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 ---End Message--- ---BeginMessage--- Source: bacula Source-Version: 5.2.6+dfsg-1 We believe that the bug you reported is fixed in the latest version of bacula, which is due to be installed in the Debian FTP archive: bacula-client_5.2.6+dfsg-1_all.deb to main/b/bacula/bacula-client_5.2.6+dfsg-1_all.deb bacula-common-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common-dbg_5.2.6+dfsg-1_amd64.deb bacula-common-mysql-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common-mysql-dbg_5.2.6+dfsg-1_amd64.deb bacula-common-mysql_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common-mysql_5.2.6+dfsg-1_amd64.deb bacula-common-pgsql-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common-pgsql-dbg_5.2.6+dfsg-1_amd64.deb bacula-common-pgsql_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common-pgsql_5.2.6+dfsg-1_amd64.deb bacula-common-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb bacula-common-sqlite3_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common-sqlite3_5.2.6+dfsg-1_amd64.deb bacula-common_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-common_5.2.6+dfsg-1_amd64.deb bacula-console-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-console-dbg_5.2.6+dfsg-1_amd64.deb bacula-console-qt-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-console-qt-dbg_5.2.6+dfsg-1_amd64.deb bacula-console-qt_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-console-qt_5.2.6+dfsg-1_amd64.deb bacula-console_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-console_5.2.6+dfsg-1_amd64.deb bacula-director-common-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-director-common-dbg_5.2.6+dfsg-1_amd64.deb bacula-director-common_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-director-common_5.2.6+dfsg-1_amd64.deb bacula-director-mysql-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-director-mysql-dbg_5.2.6+dfsg-1_amd64.deb bacula-director-mysql_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-director-mysql_5.2.6+dfsg-1_amd64.deb bacula-director-pgsql-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-director-pgsql-dbg_5.2.6+dfsg-1_amd64.deb bacula-director-pgsql_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-director-pgsql_5.2.6+dfsg-1_amd64.deb bacula-director-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb to main/b/bacula/bacula-director-sqlite3-dbg_5.2.6+dfsg-1_amd64.deb
Bug#676827: veromix: Not installable concurrently with python3
This bug has been fixed upstream and a package is waiting on mentors[1] for my sponsor (which is very busy) to upload it. Thx for the report [1] http://mentors.debian.net/package/veromix -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677572: racoon: fails to install: missing Depends: adduser
Package: racoon Version: 1:0.8.0-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package racoon. (Reading database ... 8457 files and directories currently installed.) Unpacking racoon (from .../racoon_1%3a0.8.0-11_amd64.deb) ... Setting up racoon (1:0.8.0-11) ... /var/lib/dpkg/info/racoon.postinst: 44: /var/lib/dpkg/info/racoon.postinst: adduser: not found dpkg: error processing racoon (--configure): subprocess installed post-installation script returned error exit status 127 cheers, Andreas racoon_1:0.8.0-11.log.gz Description: GNU Zip compressed data
Bug#677573: libcomedi0: fails to install: missing Depends: adduser
Package: libcomedi0 Version: 0.10.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package libcomedi0. (Reading database ... 6880 files and directories currently installed.) Unpacking libcomedi0 (from .../libcomedi0_0.10.0-1_amd64.deb) ... Setting up libcomedi0 (0.10.0-1) ... creating iocard group... /var/lib/dpkg/info/libcomedi0.postinst: 11: /var/lib/dpkg/info/libcomedi0.postinst: addgroup: not found dpkg: error processing libcomedi0 (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: libcomedi0 cheers, Andreas libcomedi0_0.10.0-1.log.gz Description: GNU Zip compressed data
Bug#665234: libpoe-component-client-mpd-perl: FTBFS: tests hang
On Thu, Jun 14, 2012 at 11:14:10PM +0200, intrigeri wrote: Ryan, looks like (#517953) you uploaded it for your own needs, do you still use it? No, I do not use POE anymore, feel free to RM this if needed. -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677575: rawtherapee-data: fails to upgrade from squeeze - trying to overwrite /usr/share/rawtherapee/themes/25-Gray-Purple.gtkrc
Package: rawtherapee,rawtherapee-data Version: 4.0.9-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'wheezy' fails because it tries to overwrite other packages files without declaring a replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package rawtherapee-data. Unpacking rawtherapee-data (from .../rawtherapee-data_4.0.9-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/rawtherapee-data_4.0.9-1_all.deb (--unpack): trying to overwrite '/usr/share/rawtherapee/themes/25-Gray-Purple.gtkrc', which is also in package rawtherapee 3.0.0~dfsg1-1.1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas rawtherapee_4.0.9-1.log.gz Description: GNU Zip compressed data
Bug#677577: libghc-hsx-dev: fails to upgrade from squeeze - trying to overwrite /usr/bin/trhsx
Package: libghc-hsx-dev Version: 0.9.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks/Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libghc-hsx-dev. Unpacking libghc-hsx-dev (from .../libghc-hsx-dev_0.9.1-2+b2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libghc-hsx-dev_0.9.1-2+b2_amd64.deb (--unpack): trying to overwrite '/usr/bin/trhsx', which is also in package libghc6-hsx-dev 0.7.0-1+b1 cheers, Andreas libghc6-happstack-prof_1:7.log.gz Description: GNU Zip compressed data
Processed: affects 656354, affects 670292, found 670292 in tuareg-mode/1:2.0.6-1, found 672176 in 2-1
Processing commands for cont...@bugs.debian.org:
affects 656354 + update-notifier
Bug #656354 [update-notifier-common] update-notifier-kde: unowned files after
purge (policy 6.8, 10.8)
Bug #606623 [update-notifier-common] update-notifier: owned and unowned files
after purge (policy 6.8 + 10.7.3)
Bug #668712 [update-notifier-common] update-notifier-kde: unowned files after
purge (policy 6.8, 10.8)
Added indication that 656354 affects update-notifier
Added indication that 606623 affects update-notifier
Added indication that 668712 affects update-notifier
affects 670292 + xemacs21-support tuareg-mode
Bug #670292
[xemacs21-gnome-mule,xemacs21-gnome-nomule,xemacs21-gnome-mule-canna-wnn]
xemacs21-gnome-{, no-}mule{, -canna-wnn}: fails to upgrade from squeeze:
apt-get dist-upgrade hangs forever
Added indication that 670292 affects xemacs21-support and tuareg-mode
found 670292 tuareg-mode/1:2.0.6-1
Bug #670292
[xemacs21-gnome-mule,xemacs21-gnome-nomule,xemacs21-gnome-mule-canna-wnn]
xemacs21-gnome-{, no-}mule{, -canna-wnn}: fails to upgrade from squeeze:
apt-get dist-upgrade hangs forever
Marked as found in versions tuareg-mode/1:2.0.6-1.
found 672176 2-1
Bug #672176 [linux-container] leaves uptime diversion after removal
Marked as found in versions linux-container/2-1.
affects 677577 + libghc6-happstack-prof libghc6-happstack-dev
Bug #677577 [libghc-hsx-dev] libghc-hsx-dev: fails to upgrade from squeeze -
trying to overwrite /usr/bin/trhsx
Added indication that 677577 affects libghc6-happstack-prof and
libghc6-happstack-dev
thanks
Stopping processing here.
Please contact me if you need assistance.
--
606623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606623
656354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656354
668712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668712
670292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670292
672176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672176
677577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677577
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
