Bug#813081: marked as done (lib{, x}32stdc++6-6-dbg, libgccjit-6-doc: fails to upgrade from 'sid' - trying to overwrite /usr/lib{, x}32/debug/libstdc++fs.a, /usr/share/info/libgccjit.info.gz)
Your message dated Sun, 07 Feb 2016 00:08:46 + with message-idand subject line Bug#813081: fixed in gcc-6 6-20160205-1 has caused the Debian Bug report #813081, regarding lib{, x}32stdc++6-6-dbg, libgccjit-6-doc: fails to upgrade from 'sid' - trying to overwrite /usr/lib{, x}32/debug/libstdc++fs.a, /usr/share/info/libgccjit.info.gz 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.) -- 813081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx32stdc++6-6-dbg,lib32stdc++6-6-dbg,libgccjit-6-doc Version: 6-20160122-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libx32stdc++6-6-dbg. Preparing to unpack .../libx32stdc++6-6-dbg_6-20160122-1_amd64.deb ... Unpacking libx32stdc++6-6-dbg (6-20160122-1) ... dpkg: error processing archive /var/cache/apt/archives/libx32stdc++6-6-dbg_6-20160122-1_amd64.deb (--unpack): trying to overwrite '/usr/libx32/debug/libstdc++fs.a', which is also in package libx32stdc++6-5-dbg 5.3.1-7 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for libc-bin (2.21-7) ... Errors were encountered while processing: /var/cache/apt/archives/libx32stdc++6-6-dbg_6-20160122-1_amd64.deb Selecting previously unselected package lib32stdc++6-6-dbg. Preparing to unpack .../lib32stdc++6-6-dbg_6-20160122-1_amd64.deb ... Unpacking lib32stdc++6-6-dbg (6-20160122-1) ... dpkg: error processing archive /var/cache/apt/archives/lib32stdc++6-6-dbg_6-20160122-1_amd64.deb (--unpack): trying to overwrite '/usr/lib32/debug/libstdc++fs.a', which is also in package lib32stdc++6-5-dbg 5.3.1-7 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for libc-bin (2.21-7) ... Errors were encountered while processing: /var/cache/apt/archives/lib32stdc++6-6-dbg_6-20160122-1_amd64.deb Selecting previously unselected package libgccjit-6-doc. Preparing to unpack .../libgccjit-6-doc_6-20160122-1_all.deb ... Unpacking libgccjit-6-doc (6-20160122-1) ... dpkg: error processing archive /var/cache/apt/archives/libgccjit-6-doc_6-20160122-1_all.deb (--unpack): trying to overwrite '/usr/share/info/libgccjit.info.gz', which is also in package libgccjit-5-doc 5.3.1-7 Errors were encountered while processing: dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) /var/cache/apt/archives/libgccjit-6-doc_6-20160122-1_all.deb cheers, Andreas libx32stdc++6-5-dbg=5.3.1-7_libx32stdc++6-6-dbg=6-20160122-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-6 Source-Version: 6-20160205-1 We believe that the bug you reported is fixed in the latest version of gcc-6, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 813...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Feb 2016 18:08:37 +0100 Source: gcc-6 Binary: gcc-6-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-6-dev libgcc4 libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-6-dev lib32gcc1 lib32gcc1-dbg lib32gcc-6-dev libn32gcc1 libn32gcc1-dbg libn32gcc-6-dev libx32gcc1 libx32gcc1-dbg libx32gcc-6-dev gcc-6 gcc-6-multilib gcc-6-test-results gcc-6-plugin-dev gcc-6-hppa64-linux-gnu cpp-6 gcc-6-locales g++-6 g++-6-multilib libgomp1 libgomp1-dbg lib32gomp1 lib32gomp1-dbg lib64gomp1 lib64gomp1-dbg libn32gomp1 libn32gomp1-dbg libx32gomp1 libx32gomp1-dbg libitm1 libitm1-dbg lib32itm1 lib32itm1-dbg
Processed: ogmtools: diff for NMU version 1:1.5-3.1
Processing control commands: > tags 800203 + patch Bug #800203 [src:ogmtools] ogmtools: Please migrate a supported debhelper compat level Added tag(s) patch. > tags 800203 + pending Bug #800203 [src:ogmtools] ogmtools: Please migrate a supported debhelper compat level Added tag(s) pending. -- 800203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#800203: ogmtools: diff for NMU version 1:1.5-3.1
Control: tags 800203 + patch Control: tags 800203 + pending Dear maintainer, I've prepared an NMU for ogmtools (versioned as 1:1.5-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -u ogmtools-1.5/debian/changelog ogmtools-1.5/debian/changelog --- ogmtools-1.5/debian/changelog +++ ogmtools-1.5/debian/changelog @@ -1,3 +1,10 @@ +ogmtools (1:1.5-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Switch to compat level 9. (Closes: #800203) + + -- Sebastian RamacherSat, 06 Feb 2016 22:41:41 +0100 + ogmtools (1:1.5-3) unstable; urgency=low * fix dependency on libdvdread3-dev diff -u ogmtools-1.5/debian/rules ogmtools-1.5/debian/rules --- ogmtools-1.5/debian/rules +++ ogmtools-1.5/debian/rules @@ -5,9 +5,6 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 -# This is the debhelper compatibility version to use. -export DH_COMPAT=3 - # These are used for cross-compiling and for saving the configure script # from having to guess our platform (since we know it already) DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) diff -u ogmtools-1.5/debian/control ogmtools-1.5/debian/control --- ogmtools-1.5/debian/control +++ ogmtools-1.5/debian/control @@ -2,7 +2,7 @@ Section: graphics Priority: optional Maintainer: Marc Leeman -Build-Depends: debhelper (>> 3.0.0), automake, libvorbis-dev (>= 1.0.0-2), libvorbis0a, libdvdread-dev, libogg0, dpatch +Build-Depends: debhelper (>= 9), automake, libvorbis-dev (>= 1.0.0-2), libvorbis0a, libdvdread-dev, libogg0, dpatch Standards-Version: 3.6.0 Package: ogmtools only in patch2: unchanged: --- ogmtools-1.5.orig/debian/compat +++ ogmtools-1.5/debian/compat @@ -0,0 +1 @@ +9 signature.asc Description: PGP signature
Bug#813932: sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices
Source: sunpy Version: 0.6.1-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, sunpy fails to build from source in unstable/amd64: [..] -- new_delt : float New delta between consecutive values. """ if self.t_delt == new_delt: return self factor = self.t_delt / float(new_delt) # The last data-point does not change! new_size = floor((self.shape[1] - 1) * factor + 1) # pylint: disable=E1101 data = ndimage.zoom(self.data, (1, new_size / self.shape[1])) # pylint: disable=E1101 params = self._get_params() params.update({ 'time_axis': np.linspace( self.time_axis[0], > self.time_axis[(new_size - 1) * new_delt / self.t_delt], new_size ), 't_delt': new_delt, }) E IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices sunpy/spectra/spectrogram.py:960: IndexError __ test_combine_freqs __ def test_combine_freqs(): image = np.random.rand(5, 3600) spec = LinearTimeSpectrogram(image, np.linspace(0, image.shape[1] - 1, image.shape[1]), np.array([8, 6, 4, 2, 0]), datetime(2010, 1, 1, 0, 15), datetime(2010, 1, 1, 0, 30), 900, 0.25 ) image = np.random.rand(5, 3600) spec2 = LinearTimeSpectrogram(image, np.linspace(0, image.shape[1] - 1, image.shape[1]), np.array([9, 7, 5, 3, 1]), datetime(2010, 1, 1, 0, 15), datetime(2010, 1, 1, 0, 30), 900, 0.25 ) > comb = LinearTimeSpectrogram.combine_frequencies([spec, spec2]) sunpy/spectra/tests/test_spectrogram.py:575: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ sunpy/spectra/spectrogram.py:1162: in combine_frequencies specs = cls.intersect_time(specs) sunpy/spectra/spectrogram.py:1144: in intersect_time cut = [sp[:, (start - sp.t_init) / delt:] for sp in specs] sunpy/spectra/spectrogram.py:601: in __getitem__ return self._slice(key[0], key[1]) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = y_range = slice(None, None, None), x_range = slice(0.0, None, None) def _slice(self, y_range, x_range): """Return new spectrogram reduced to the values passed as slices. Implementation detail.""" > data = self.data[y_range, x_range] E IndexError: invalid slice sunpy/spectra/spectrogram.py:339: IndexError _ test_intersect_time __ def test_intersect_time(): image = np.random.rand(5, 3600) spec = LinearTimeSpectrogram(image, np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]), np.array([8, 6, 4, 2, 0]), datetime(2010, 1, 1, 0, 15), datetime(2010, 1, 1, 0, 30), 900, 0.25 ) image = np.random.rand(5, 3600) spec2 = LinearTimeSpectrogram(image, np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]), np.array([9, 7, 5, 3, 1]), datetime(2010, 1, 1, 0, 15), datetime(2010, 1, 1, 0, 30), 901, 0.25 ) one, other = LinearTimeSpectrogram.intersect_time( > [spec, spec2] ) sunpy/spectra/tests/test_spectrogram.py:632: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ sunpy/spectra/spectrogram.py:1144: in intersect_time cut = [sp[:, (start - sp.t_init) / delt:] for sp in specs] sunpy/spectra/spectrogram.py:601: in __getitem__ return self._slice(key[0], key[1]) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = y_range = slice(None, None, None), x_range = slice(4.0, None, None) def _slice(self, y_range, x_range): """Return new spectrogram reduced to the values passed as slices. Implementation detail.""" > data = self.data[y_range, x_range] E IndexError: invalid slice sunpy/spectra/spectrogram.py:339: IndexError test_linearize def test_linearize(): image = np.random.rand(5, 900) spec = LinearTimeSpectrogram(image, np.linspace(0, 1 *
Bug#811054: marked as done (obexftp: FTBFS: object.c:39:43: error: parameter 1 ('obex') has incomplete type)
Your message dated Sat, 06 Feb 2016 22:26:16 + with message-idand subject line Bug#811054: fixed in obexftp 0.24-1 has caused the Debian Bug report #811054, regarding obexftp: FTBFS: object.c:39:43: error: parameter 1 ('obex') has incomplete type to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 811054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: obexftp Version: 0.23-6 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, obexftp fails to build from source in unstable/amd64: [..] Making all in obexftp make[3]: Entering directory '/home/lamby/temp/cdt.20160115095516.JItmmLlOx2/obexftp-0.23/obexftp' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../includes -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -W -Wundef -Wmissing-declarations -Wmissing-prototypes -Wall -MT object.lo -MD -MP -MF .deps/object.Tpo -c -o object.lo object.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../includes -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -W -Wundef -Wmissing-declarations -Wmissing-prototypes -Wall -MT object.lo -MD -MP -MF .deps/object.Tpo -c object.c -fPIC -DPIC -o .libs/object.o object.c:39:43: error: parameter 1 ('obex') has incomplete type obex_object_t *obexftp_build_info (obex_t obex, uint32_t conn, uint8_t opcode) ^ object.c: In function 'obexftp_build_info': object.c:39:43: warning: unused parameter 'obex' [-Wunused-parameter] object.c: At top level: object.c:73:42: error: parameter 1 ('obex') has incomplete type obex_object_t *obexftp_build_get (obex_t obex, uint32_t conn, const char *name, const char *type) ^ object.c: In function 'obexftp_build_get': object.c:73:42: warning: unused parameter 'obex' [-Wunused-parameter] object.c: At top level: object.c:125:45: error: parameter 1 ('obex') has incomplete type obex_object_t *obexftp_build_rename (obex_t obex, uint32_t conn, const char *from, const char *to) ^ object.c: In function 'obexftp_build_rename': object.c:125:45: warning: unused parameter 'obex' [-Wunused-parameter] object.c: At top level: object.c:189:42: error: parameter 1 ('obex') has incomplete type obex_object_t *obexftp_build_del (obex_t obex, uint32_t conn, const char *name) ^ object.c: In function 'obexftp_build_del': object.c:189:42: warning: unused parameter 'obex' [-Wunused-parameter] object.c: At top level: object.c:238:46: error: parameter 1 ('obex') has incomplete type obex_object_t *obexftp_build_setpath (obex_t obex, uint32_t conn, const char *name, int create) ^ object.c: In function 'obexftp_build_setpath': object.c:238:46: warning: unused parameter 'obex' [-Wunused-parameter] object.c: At top level: object.c:299:42: error: parameter 1 ('obex') has incomplete type obex_object_t *obexftp_build_put (obex_t obex, uint32_t conn, const char *name, const int size) ^ object.c: In function 'obexftp_build_put': object.c:299:42: warning: unused parameter 'obex' [-Wunused-parameter] Makefile:489: recipe for target 'object.lo' failed make[3]: *** [object.lo] Error 1 make[3]: Leaving directory '/home/lamby/temp/cdt.20160115095516.JItmmLlOx2/obexftp-0.23/obexftp' Makefile:504: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/lamby/temp/cdt.20160115095516.JItmmLlOx2/obexftp-0.23' Makefile:411: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/lamby/temp/cdt.20160115095516.JItmmLlOx2/obexftp-0.23' debian/rules:81: recipe for target 'build-stamp' failed make: *** [build-stamp] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- obexftp.0.23-6.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: obexftp Source-Version: 0.24-1 We
Bug#813951: freefoam: FTBFS with libopenmpi 1.10
Source: freefoam Version: 0.1.0+dfsg+1-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 813128 by -1 Dear maintainer, your package FTBFS while rebuilding against libopenmpi 1.10. https://buildd.debian.org/status/logs.php?pkg=freefoam=0.1.0%2Bdfsg%2B1-3%2Bb1 [ 21%] Building CXX object src/ODE/CMakeFiles/ODE.dir/ODESolvers/SIBS/polyExtrapolate.C.o cd /«BUILDDIR»/freefoam-0.1.0+dfsg+1/obj-x86_64-linux-gnu/src/ODE && /usr/bin/c++ -DDP -DNoRepository -DODE_EXPORTS -Dlinux64 -I/«BUILDDIR»/freefoam-0.1.0+dfsg+1/obj-x86_64-linux-gnu/include -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fpermissive -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/ODE.dir/ODESolvers/SIBS/polyExtrapolate.C.o -c /«BUILDDIR»/freefoam-0.1.0+dfsg+1/src/ODE/ODESolvers/SIBS/polyExtrapolate.C CMakeFiles/ansysToFoam.dir/CMakeFiles/ansysToFoam.C.o:(.rodata._ZTV11yyFlexLexer[_ZTV11yyFlexLexer]+0x68): undefined reference to `yyFlexLexer::yywrap()' collect2: error: ld returned 1 exit status applications/utilities/mesh/conversion/ansysToFoam/CMakeFiles/ansysToFoam.dir/build.make:104: recipe for target 'libexec/FreeFOAM/0.1.0/freefoam-ansysToFoam' failed make[3]: *** [libexec/FreeFOAM/0.1.0/freefoam-ansysToFoam] Error 1 Note that because of the parallel build the error is a bit up in the log. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: freefoam: FTBFS with libopenmpi 1.10
Processing control commands: > block 813128 by -1 Bug #813128 [release.debian.org] transition: openmpi 813128 was blocked by: 813799 813724 813498 813814 813722 813725 813128 was not blocking any bugs. Added blocking bug(s) of 813128: 813951 -- 813128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813128 813951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#769482: marked as done (/usr/bin/pip-3.2: pip 1.1 is insecure, unsupported and does not work with most of python3)
Your message dated Sat, 6 Feb 2016 16:34:01 -0500 with message-id <20160206163401.6f643...@subdivisions.wooz.org> and subject line has caused the Debian Bug report #769482, regarding /usr/bin/pip-3.2: pip 1.1 is insecure, unsupported and does not work with most of python3 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.) -- 769482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pip Version: 1.1-3 Severity: serious File: /usr/bin/pip-3.2 Tags: security Justification: unkkown Dear Maintainer, * What led up to the situation? Tried to upgrade a python package using pip-3.2 (which is pip v1.1) * What exactly did you do (or not do) that was effective (or ineffective)? pip install -U docker-forklift * What was the outcome of this action? Exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 104, in main status = self.run(options, args) File "/usr/lib/python3/dist-packages/pip/commands/install.py", line 245, in run requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle) File "/usr/lib/python3/dist-packages/pip/req.py", line 1014, in prepare_files req_to_install.assert_source_matches_version() File "/usr/lib/python3/dist-packages/pip/req.py", line 359, in assert_source_matches_version version = self.installed_version File "/usr/lib/python3/dist-packages/pip/req.py", line 351, in installed_version return self.pkg_info()['version'] File "/usr/lib/python3/dist-packages/pip/req.py", line 318, in pkg_info data = self.egg_info_data('PKG-INFO') File "/usr/lib/python3/dist-packages/pip/req.py", line 261, in egg_info_data data = fp.read() File "/usr/lib/python3.2/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 6265: ordinal not in range(128) * What outcome did you expect instead? docker-forklift to be upgraded * Notes: https://github.com/kennethreitz/requests/issues/2335 https://github.com/infoxchange/docker-forklift/issues/78 https://security-tracker.debian.org/tracker/CVE-2013-1629 -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3-pip depends on: ii python33.2.3-6 ii python3-pkg-resources 0.6.24-1 ii python3-setuptools 0.6.24-1 ii python3.2 3.2.3-7 Versions of packages python3-pip recommends: ii build-essential 11.5 ii python3-dev 3.2.3-6 python3-pip suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- I'm going to close this bug because newer versions of pip work for me. Besides, docker-forklift now requires pip3 (i.e. Python 3). pgpDEU0htA8y1.pgp Description: OpenPGP digital signature --- End Message ---
Processed: merging 813906 813887
Processing commands for cont...@bugs.debian.org: > merge 813906 813887 Bug #813906 [icedtea-netx] icedtea-netx: Fails to upgrade if openjdk-7-jre-headless is removed: "alternative /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/javaws for javaws not registered; not setting" Bug #813887 [icedtea-netx] icedtea-netx: postinst fails registering javaws alternative for OpenJDK 7 Merged 813887 813906 > thanks Stopping processing here. Please contact me if you need assistance. -- 813887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813887 813906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#786173: marked as pending
tag 786173 pending thanks Hello, Bug #786173 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-peak.rules.git;a=commitdiff;h=535856f --- commit 535856f9a8a08ff1a53051ad12bdceb33925b5ae Author: Daniele TricoliDate: Sat Feb 6 22:58:29 2016 +0100 Update changelog diff --git a/debian/changelog b/debian/changelog index a66bc2a..3616979 100644 --- a/debian/changelog +++ b/debian/changelog @@ -5,11 +5,26 @@ python-peak.rules (0.5a1+r2713-1) UNRELEASED; urgency=low [ Daniele Tricoli ] * New upstream release. + * Replace deprecated dh_pysupport with dh_python2. (Closes: #786173) + * debian/compat +- Bump debhelper compatibility level to 9. * debian/control -- Bumped Standards-Version to 3.9.3 (no changes needed) +- Bump Standards-Version to 3.9.7 (no changes needed). +- Update Vcs fields for git migration. +- Bump debhelper B-D to (>= 9). +- Add X-Python-Version. +- Use secure URI for Vcs-Git. + * debian/copyright +- Update Format URI. +- Fix wildcard-matches-nothing-in-dep5-copyright. +- Use secure URI in Source field. +- Update copyright years. * debian/rules -- Made package build twice in a row. Thanks to Jakub Wilk for - the bug report (Closes: #671424) +- Clean egg-info to build the package twice in a row. Thanks to Jakub Wilk + for the bug report. (Closes: #671424) +- Use mktemp to create GOS_TMP_DIR. + * debian/README.source +- Update. -- Daniele Tricoli Fri, 05 Feb 2016 01:17:55 +0100
Processed: Bug#786173 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 786173 pending Bug #786173 [src:python-peak.rules] python-peak.rules: deprecation of python-support Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 786173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#812969: marked as done (libvmime: FTBFS: net_tls_TLSSession.cpp:120:38: error: 'gnutls_certificate_type_set_priority' was not declared in this scope)
Your message dated Sat, 06 Feb 2016 22:24:12 + with message-idand subject line Bug#812969: fixed in libvmime 0.9.1-5 has caused the Debian Bug report #812969, regarding libvmime: FTBFS: net_tls_TLSSession.cpp:120:38: error: 'gnutls_certificate_type_set_priority' was not declared in this scope 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.) -- 812969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvmime Version: 0.9.1-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, libvmime fails to build from source in unstable/amd64: [..] net_tls_TLSSession.cpp: In constructor 'vmime::net::tls::TLSSession::TLSSession(vmime::utility::ref)': net_tls_TLSSession.cpp:105:24: warning: 'gnutls_session' is deprecated [-Wdeprecated-declarations] m_gnutlsSession = new gnutls_session; ^ In file included from /usr/include/gnutls/gnutls.h:2594:0, from net_tls_TLSSession.cpp:24: /usr/include/gnutls/compat.h:78:26: note: declared here typedef gnutls_session_t gnutls_session _GNUTLS_GCC_ATTR_DEPRECATED; ^ net_tls_TLSSession.cpp:120:38: error: 'gnutls_certificate_type_set_priority' was not declared in this scope (*m_gnutlsSession, certTypePriority); ^ net_tls_TLSSession.cpp:131:68: error: 'gnutls_protocol_set_priority' was not declared in this scope res = gnutls_protocol_set_priority(*m_gnutlsSession, protoPriority); ^ net_tls_TLSSession.cpp:152:61: error: 'gnutls_cipher_set_priority' was not declared in this scope gnutls_cipher_set_priority(*m_gnutlsSession, cipherPriority); ^ net_tls_TLSSession.cpp:157:55: error: 'gnutls_mac_set_priority' was not declared in this scope gnutls_mac_set_priority(*m_gnutlsSession, macPriority); ^ net_tls_TLSSession.cpp:173:53: error: 'gnutls_kx_set_priority' was not declared in this scope gnutls_kx_set_priority(*m_gnutlsSession, kxPriority); ^ net_tls_TLSSession.cpp:184:71: error: 'gnutls_compression_set_priority' was not declared in this scope gnutls_compression_set_priority(*m_gnutlsSession, compressionPriority); ^ Makefile:657: recipe for target 'net_tls_TLSSession.lo' failed make[3]: *** [net_tls_TLSSession.lo] Error 1 make[3]: *** Waiting for unfinished jobs libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include -I.. -D_REENTRANT=1 -D_THREAD_SAFE=1 -I/usr/include/p11-kit-1 -fPIC -DPIC -ansi -pedantic -W -Wall -Wpointer-arith -Wold-style-cast -Wconversion -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -c security_sasl_builtinSASLMechanism.cpp -o security_sasl_builtinSASLMechanism.o >/dev/null 2>&1 libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include -I.. -D_REENTRANT=1 -D_THREAD_SAFE=1 -I/usr/include/p11-kit-1 -fPIC -DPIC -ansi -pedantic -W -Wall -Wpointer-arith -Wold-style-cast -Wconversion -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -c security_sasl_defaultSASLAuthenticator.cpp -o security_sasl_defaultSASLAuthenticator.o >/dev/null 2>&1 In file included from net_tls_TLSSocket.cpp:27:0: ../vmime/net/tls/TLSSocket.hpp:99:88: warning: 'gnutls_transport_ptr' is deprecated [-Wdeprecated-declarations] static ssize_t gnutlsPushFunc(gnutls_transport_ptr trspt, const void* data, size_t len); ^ ../vmime/net/tls/TLSSocket.hpp:100:82: warning: 'gnutls_transport_ptr' is deprecated [-Wdeprecated-declarations] static ssize_t gnutlsPullFunc(gnutls_transport_ptr trspt, void* data, size_t len); ^ In file included from net_tls_TLSSocket.cpp:28:0: ../vmime/net/tls/TLSSession.hpp:80:18: warning: 'gnutls_session' is deprecated [-Wdeprecated-declarations] gnutls_session* m_gnutlsSession; ^ In file included from /usr/include/gnutls/gnutls.h:2594:0, from
Bug#813160: marked as done (hdf-eos5: FTBFS: configure:19095: error: HDF5 was linked with SZIP, but --with-szlib was not given)
Your message dated Sat, 06 Feb 2016 22:23:45 + with message-idand subject line Bug#813160: fixed in hdf-eos5 5.1.15.dfsg.1-6 has caused the Debian Bug report #813160, regarding hdf-eos5: FTBFS: configure:19095: error: HDF5 was linked with SZIP, but --with-szlib was not given 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.) -- 813160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hdf-eos5 Version: 5.1.15.dfsg.1-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, hdf-eos5 fails to build from source in unstable/amd64: [..] configure:19095: error: HDF5 was linked with SZIP, but --with-szlib was not given ## ## ## Cache variables. ## ## ## ac_cv_build=x86_64-pc-linux-gnu ac_cv_c_compiler_gnu=yes ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set=set ac_cv_env_CFLAGS_value='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_HDFEOS5_THREADSAFE -Df2cFortran' ac_cv_env_CPPFLAGS_set=set ac_cv_env_CPPFLAGS_value='-Wdate-time -D_FORTIFY_SOURCE=2' ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_F77_set= ac_cv_env_F77_value= ac_cv_env_FCFLAGS_set=set ac_cv_env_FCFLAGS_value='-g -O2 -fstack-protector-strong' ac_cv_env_FC_set= ac_cv_env_FC_value= ac_cv_env_FFLAGS_set=set ac_cv_env_FFLAGS_value='-g -O2 -fstack-protector-strong' ac_cv_env_LDFLAGS_set=set ac_cv_env_LDFLAGS_value='-Wl,-z,relro -lpthread' ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= ac_cv_env_build_alias_set=set ac_cv_env_build_alias_value=x86_64-linux-gnu ac_cv_env_host_alias_set= ac_cv_env_host_alias_value= ac_cv_env_target_alias_set= ac_cv_env_target_alias_value= ac_cv_fc_compiler_gnu=yes ac_cv_header_dlfcn_h=yes ac_cv_header_hdf5_h=yes ac_cv_header_inttypes_h=yes ac_cv_header_memory_h=yes ac_cv_header_stdc=yes ac_cv_header_stdint_h=yes ac_cv_header_stdlib_h=yes ac_cv_header_string_h=yes ac_cv_header_strings_h=yes ac_cv_header_sys_stat_h=yes ac_cv_header_sys_types_h=yes ac_cv_header_unistd_h=yes ac_cv_header_zlib_h=yes ac_cv_host=x86_64-pc-linux-gnu ac_cv_lib_hdf5_H5Fcreate=yes ac_cv_lib_m_ceil=yes ac_cv_lib_z_compress2=yes ac_cv_objext=o ac_cv_path_EGREP='/bin/grep -E' ac_cv_path_FGREP='/bin/grep -F' ac_cv_path_GREP=/bin/grep ac_cv_path_SED=/bin/sed ac_cv_path_install='/usr/bin/install -c' ac_cv_path_mkdir=/bin/mkdir ac_cv_prog_AWK=mawk ac_cv_prog_CPP='gcc -E' ac_cv_prog_ac_ct_AR=ar ac_cv_prog_ac_ct_CC=gcc ac_cv_prog_ac_ct_FC=gfortran ac_cv_prog_ac_ct_OBJDUMP=objdump ac_cv_prog_ac_ct_RANLIB=ranlib ac_cv_prog_ac_ct_STRIP=strip ac_cv_prog_cc_c89= ac_cv_prog_cc_g=yes ac_cv_prog_fc_g=yes ac_cv_prog_make_make_set=yes ac_cv_sizeof_intp=8 am_cv_CC_dependencies_compiler_type=none am_cv_make_support_nested_variables=yes am_cv_prog_cc_c_o=yes he2_cv_fortran90_compiler=yes he5_cv_32ptr=no he5_cv_f2cFortran_defined=yes he5_cv_hdf5_szip_can_decode=yes he5_cv_hdf5_szip_can_encode=yes lt_cv_ar_at_file=@ lt_cv_archive_cmds_need_lc=no lt_cv_deplibs_check_method=pass_all lt_cv_file_magic_cmd='$MAGIC_CMD' lt_cv_file_magic_test_file= lt_cv_ld_reload_flag=-r lt_cv_nm_interface='BSD nm' lt_cv_objdir=.libs lt_cv_path_LD=/usr/bin/ld lt_cv_path_NM='/usr/bin/nm -B' lt_cv_path_mainfest_tool=no lt_cv_prog_compiler_c_o=yes lt_cv_prog_compiler_c_o_FC=yes lt_cv_prog_compiler_pic='-fPIC -DPIC' lt_cv_prog_compiler_pic_FC=-fPIC lt_cv_prog_compiler_pic_works=yes lt_cv_prog_compiler_pic_works_FC=yes lt_cv_prog_compiler_rtti_exceptions=no lt_cv_prog_compiler_static_works=yes lt_cv_prog_compiler_static_works_FC=yes lt_cv_prog_gnu_ld=yes lt_cv_sharedlib_from_linklib_cmd='printf %s\n' lt_cv_shlibpath_overrides_runpath=no lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p'\'' | sed '\''/ __gnu_lto/d'\''' lt_cv_sys_global_symbol_to_c_name_address='sed -n -e '\''s/^: \([^ ]*\)[ ]*$/ {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) \([^ ]*\)$/ {"\2", (void *) \&\2},/p'\''' lt_cv_sys_global_symbol_to_c_name_address_lib_prefix='sed -n -e '\''s/^: \([^ ]*\)[ ]*$/ {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) \(lib[^ ]*\)$/
Processed: Re: Bug#813799: [Debichem-devel] Bug#813799: cp2k FTBFS with openmpi1.10
Processing control commands: > severity -1 serious Bug #813799 [src:cp2k] cp2k FTBFS with openmpi1.10 Severity set to 'serious' from 'important' > block 813128 by -1 Bug #813128 [release.debian.org] transition: openmpi 813128 was blocked by: 813722 813724 813814 813498 813725 813128 was not blocking any bugs. Added blocking bug(s) of 813128: 813799 -- 813128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813128 813799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813877: alienblaster content is used non-dfsg and legal problematic content.
Package: alienblaster-data Severity: serious Hello. alienblaster content (not code) is used "Red Cross flag". This is "Health item" image. (Restore Player's Health) "Red Cross flag" is non-free, because this image is not freely use. (Violate DFSG) I think that this is misuse, It is violate of law. https://www.icrc.org/applic/ihl/ihl-nat.nsf/a24d1cf3344e99934125673e00508142/57a872a8776b3fc9c12572d700386930/$FILE/The%20Geneva%20Distinctive%20Emblems%20Protection%20Act%20of%202006.pdf http://law.e-gov.go.jp/htmldata/S22/S22HO159.html Thanks. Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1305233
Bug#812796: marked as done (Segfault in tchmttest)
Your message dated Sat, 06 Feb 2016 09:38:37 + with message-idand subject line Bug#812796: fixed in tokyocabinet 1.4.48-6 has caused the Debian Bug report #812796, regarding Segfault in tchmttest 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.) -- 812796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tokyocabinet Version: 1.4.48-4 Severity: serious Tags: sid stretch seen in 20160126 unstable: AA@A01A2A9CA515D7E849493@98@24787308E46B9E6@44B098 (3850) AB3@475D023A21312976ECAA2728AD10C64778CAB06279C468 (3900) AC9AAD2EEE@CEC9124524674647@619B17A@EB85A53@01D832 (3950) 4DACD34D4B742@C0@02C0DA@9848492@C42@37E520E5480B40 (4000) 4E02000@@44331A6C3A845B@1AE8@0CB7DD@D974C048272CB4Makefile:236: recipe for target 'check-hdb' failed make[2]: *** [check-hdb] Segmentation fault make[2]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48' Makefile:166: recipe for target 'check' failed make[1]: *** [check] Error 2 make[1]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48' dh_auto_test: make -j1 check returned exit code 2 debian/rules:9: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 --- End Message --- --- Begin Message --- Source: tokyocabinet Source-Version: 1.4.48-6 We believe that the bug you reported is fixed in the latest version of tokyocabinet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated tokyocabinet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2016 09:49:05 +0100 Source: tokyocabinet Binary: libtokyocabinet9 libtokyocabinet-dev tokyocabinet-doc tokyocabinet-bin Architecture: source amd64 all Version: 1.4.48-6 Distribution: unstable Urgency: medium Maintainer: Tobias Frost Changed-By: Tobias Frost Description: libtokyocabinet-dev - Tokyo Cabinet Database Libraries [development] libtokyocabinet9 - Tokyo Cabinet Database Libraries [runtime] tokyocabinet-bin - Tokyo Cabinet Database Utilities tokyocabinet-doc - Tokyo Cabinet Database Documentation Closes: 812796 Changes: tokyocabinet (1.4.48-6) unstable; urgency=medium . * Enable race-condition detection. Closes: #812796 Checksums-Sha1: 8caa9edde0b8a56339c258b2a10dc604297c28a4 2139 tokyocabinet_1.4.48-6.dsc f4cb9b7f64a1b85aadcefba9fad96f210237f562 15024 tokyocabinet_1.4.48-6.debian.tar.xz efcf074a82bb3cd10c63ce5527987905e5b294ac 454720 tokyocabinet-doc_1.4.48-6_all.deb Checksums-Sha256: 5ffe3ea7c984d5a5a2b25699ba159c96d4b9dc4cd0940fc80f45d1f6e6ac9246 2139 tokyocabinet_1.4.48-6.dsc a1dcac54eecfa239a6f13ab88542f177449bd65abded3e66e2945b71465204b7 15024 tokyocabinet_1.4.48-6.debian.tar.xz f1c1176a94b014f340f66223f0ea11a6db68179a00e06b5f4957888aa0b23f6c 454720 tokyocabinet-doc_1.4.48-6_all.deb Files: 33cef7fabcd1f2bb47bc9b2612a618b5 2139 libs standard tokyocabinet_1.4.48-6.dsc 29be695df49fc28de8fb7e0115399426 15024 libs standard tokyocabinet_1.4.48-6.debian.tar.xz f0cfb323150a3f2344870b6f0403d2c2 454720 doc optional tokyocabinet-doc_1.4.48-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWtbwvAAoJEJFk+h0XvV02UVYQANAi4lictbRN6+l7N1qOEv8c n9ohnZOH6p+q92eM/ee/5YM6ZBoJyEYDS7kTKHj3cz9h0G/5NuaJSFLbpBAqGBpB e99MINVsX7A6XFYGRJPumO3bBXSHwzLF0vSnADRcKs00twUu40sitj13pjjMjjyn hjU1v+LlxmEskWeBVwITdiQPMGYIu30m8hdKRRknAQ0d/RbKiarR61X6tfB8UYwE EGmwXERW9ugMRI1KBpkC2qVKUHZmqKMMhDnTYZhYY4pRQAhfQFPOyxM3RA2r/n/S aEGRcWtEUsnVHFrG6wWbOmN5DS5EcovQPND6mOmvzdOmL7cJflWuEM2uFraWKPtN DnzhlrhHsrfehPokAHlO5+WLVtcgPuofSQuF+D/VFQ90Z88OUtJlBgXcv1q/wvxF Wro5CFpd1+Qbb86ho9xNZPPkp6SvjBe1aqJUnqW1Bh7QNG9W3DsyxAMaIL6Gc8BM ITaJsJmqXRduLMPcVkeOUCiqd67GSTK/swjSWYrQZCzAuoaLYsXt8AucTtJigqSS Otuh4MeEUfBpIa44jLmYp05eOJ66Nq1ifINSEWV6J1ow8q6XCz9IJKZadBNkNJyo x8Xf1C1wGuocrowOf5eqc9Z8YvNC1gb3fTHqWoFfCxFaZtr3b/mahp95lLBp4rDy G2/3dfGlqBGqznxx5rUM =eeIH -END PGP SIGNATURE End Message ---
Bug#801046: 나에게 메일 보내기
-- Android용 myMail 앱에서 보냄
Bug#813875: [Debian-med-packaging] Bug#813875: insighttoolkit4: FTBFS on i386 (member reference base type 'void' is not a structure or union)
Hello, /usr/bin/castxml -o /«PKGBUILDDIR»/BUILD/Wrapping/itkDenseFiniteDifferenceImageFilter.xml [...] /usr/include/i386-linux-gnu/bits/mathinline.h:948:9: error: '(anonymous union at /usr/include/i386-linux-gnu/bits/mathinline.h:948:9)' cannot be defined in a type specifier (union { double __d; int __i[2]; }) {__d: __x}).__i[1] ^ /usr/include/i386-linux-gnu/bits/mathinline.h:948:55: error: member reference base type 'void' is not a structure or union (union { double __d; int __i[2]; }) {__d: __x}).__i[1] As you can see, this is actually a bug in castxml, which is used to parse the files and create XML descriptions of the code as an intermediate step to create Python bindings. CastXML uses LLVM as a backend, hence there may be incompatibilities. Since I'm currently on mobile devices only and don't have my GitHub password, would you please consider filing a bug upstream [1] . They are quite responsive (at least on weekdays). Best, Gert [1] https://github.com/CastXML/CastXML
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 813578 serious Bug #813578 [obexpushd] obexpushd: Please update package name of libopenobex in B-D Severity set to 'serious' from 'important' > block 813100 by 813578 Bug #813100 [release.debian.org] transition: libopenobex 813100 was blocked by: 810331 810773 811054 811300 810521 810562 813100 was not blocking any bugs. Added blocking bug(s) of 813100: 813578 > block 813100 by 813819 Bug #813100 [release.debian.org] transition: libopenobex 813100 was blocked by: 813578 811300 810562 810331 811054 810521 810773 813100 was not blocking any bugs. Added blocking bug(s) of 813100: 813819 > -- Stopping processing here. Please contact me if you need assistance. -- 813100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813100 813578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813880: marked as done (tokyocabinet: testsuite failures on some archs)
Your message dated Sat, 06 Feb 2016 14:26:44 + with message-idand subject line Bug#813880: fixed in tokyocabinet 1.4.48-7 has caused the Debian Bug report #813880, regarding tokyocabinet: testsuite failures on some archs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 813880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tokyocabinet Severity: serious e.g powerpc and s390x are affected by a "metadata error". Investigating already. -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: tokyocabinet Source-Version: 1.4.48-7 We believe that the bug you reported is fixed in the latest version of tokyocabinet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 813...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated tokyocabinet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2016 14:51:35 +0100 Source: tokyocabinet Binary: libtokyocabinet9 libtokyocabinet-dev tokyocabinet-doc tokyocabinet-bin Architecture: source amd64 all Version: 1.4.48-7 Distribution: unstable Urgency: medium Maintainer: Tobias Frost Changed-By: Tobias Frost Description: libtokyocabinet-dev - Tokyo Cabinet Database Libraries [development] libtokyocabinet9 - Tokyo Cabinet Database Libraries [runtime] tokyocabinet-bin - Tokyo Cabinet Database Utilities tokyocabinet-doc - Tokyo Cabinet Database Documentation Closes: 813880 Changes: tokyocabinet (1.4.48-7) unstable; urgency=medium . * Fix testsuite on certain archs: Seems that gcc optimized too much, hinting it that memcpy() might change memory fixes that. (Closes: #813880) Checksums-Sha1: 5d684409b7bcbf8fa653890c64077f9364d0249a 2139 tokyocabinet_1.4.48-7.dsc 40e0dc05d1df830051e0f05da636d13131e0 15404 tokyocabinet_1.4.48-7.debian.tar.xz e1d86238a09be0783b03990c777276616b7eec98 454808 tokyocabinet-doc_1.4.48-7_all.deb Checksums-Sha256: ea350fc496a393a0c99c68054b6072eda013df387d7b846a49a8a0bab98ad457 2139 tokyocabinet_1.4.48-7.dsc 0f4bc36976e1f08cb0911dd842942285fd59d8fa0fbed6d31f62d28e957badd7 15404 tokyocabinet_1.4.48-7.debian.tar.xz 536f8ad2b7ec8f984d9d77c396fd3b41ca6fab5b9c4f0ccb7f0023e1e585ba58 454808 tokyocabinet-doc_1.4.48-7_all.deb Files: 9aefaa28e2809fa35aacfd2cbea1cbd4 2139 libs standard tokyocabinet_1.4.48-7.dsc 49f8aab00461d7517783773dc1575bbc 15404 libs standard tokyocabinet_1.4.48-7.debian.tar.xz 84b0520c71e4e3c2ca102f7f62d73330 454808 doc optional tokyocabinet-doc_1.4.48-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWtfu1AAoJEJFk+h0XvV02aXAP/jGk+cdD0CfdNrzink36swKy qSIGMTigAju4Ewk8LsIxvIA4hWTGL24z9CF7Z/BYzDyNWqjsZCw+IWGRT7zlOZ4m 3hCB4S5khtLKYYqdi/PPa5S+QEyBvyeUnVrP0GPwgNsOpuSJaY8lEuz9bfQXmp+n NP9jKRxRS48Juin9I8Nz1rtPoUG31Z14N6daT9XPVJ3shh7PPqvT+rw5DqESDzL1 zcRDy2HCHxFj2hlTDcKJQmJ2qFp4faUXO9fnCqjf9geF8mItyT/94TwljrCYqkBm TGK3R6vKmzTH9EJszHi7gDEv0/0tTtLjIZQyYpg4kdVR59poMAMYwrVYgZUGkUqs TZDZQl3hJDBKngDVkhRYUWx5/Xby1Q4xWCJhnnyYSXyNY8CE8nIcw35WEcvwv55P zOufK7KkHw+1FLBQ/JqUMzyz4qknCtsh90jkubAXAGPtDjQeGj4V+hC2Wyonc5fn jTKVKUkJYoWvlOd2Y1TNHM17yBx0ss5u9By+ovXeKaKkSvbVBYdhvUbYWpZ4jjUR etQHbp626Mx+rd9cQBl9XUjXhpYpcDaHDz5NTC1S83lnZVEpIevpMp/hJBvfiJJA JvgzsJWDSddpwQKFoj0qEyxerzkH+qeje9OF0irLp3MktP9fVHXmewrRngOFlbel tjSsNFHBzhmqyN42y8RP =KiSu -END PGP SIGNATURE End Message ---
Bug#810521: marked as done (obex-data-server: FTBFS with libopenobex 1.7.1: src/ods-obex.c:408: undefined reference to `OBEX_FindInterfaces')
Your message dated Sat, 06 Feb 2016 14:25:54 + with message-idand subject line Bug#810521: fixed in obex-data-server 0.4.5-1.1 has caused the Debian Bug report #810521, regarding obex-data-server: FTBFS with libopenobex 1.7.1: src/ods-obex.c:408: undefined reference to `OBEX_FindInterfaces' 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.) -- 810521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: obex-data-server Version: 0.4.5-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, obex-data-server fails to build from source in unstable/amd64: [..] gcc -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/dbus-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z,relro -o src/obex-data-server src/ods-bluez.o src/ods-usb.o src/ods-capabilities.o src/ods-common.o src/ods-error.o src/ods-folder-listing.o src/ods-imaging-helpers.o src/ods-main.o src/ods-marshal.o src/ods-manager.o src/ods-logging.o src/ods-obex.o src/ods-server.o src/ods-server-session.o src/ods-session.o -lgobject-2.0 -lglib-2.0 -lgthread-2.0 -pthread -lglib-2.0 -lMagickWand-6.Q16 -lMagickCore-6.Q16 -lusb -ldbus-glib-1 -lgobject-2.0 -lglib-2.0 -ldbus-1 -lbluetooth -lopenobex src/ods-obex.o: In function `ods_obex_setup_usbtransport': /home/lamby/temp/cdt.20160109134239.XEOZMNRa3h/obex-data-server-0.4.5/src/ods-obex.c:408: undefined reference to `OBEX_FindInterfaces' collect2: error: ld returned 1 exit status Makefile:380: recipe for target 'src/obex-data-server' failed make[2]: *** [src/obex-data-server] Error 1 Makefile:263: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/lamby/temp/cdt.20160109134239.XEOZMNRa3h/obex-data-server-0.4.5' /usr/share/cdbs/1/class/makefile.mk:47: recipe for target 'debian/stamp-makefile-build' failed make: *** [debian/stamp-makefile-build] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- obex-data-server.0.4.5-1.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: obex-data-server Source-Version: 0.4.5-1.1 We believe that the bug you reported is fixed in the latest version of obex-data-server, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 810...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated obex-data-server package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2016 13:35:48 + Source: obex-data-server Binary: obex-data-server Architecture: source Version: 0.4.5-1.1 Distribution: unstable Urgency: medium Maintainer: Filippo Giunchedi Changed-By: Mattia Rizzolo Description: obex-data-server - D-Bus service for OBEX client and server side functionality Closes: 810521 Changes: obex-data-server (0.4.5-1.1) unstable; urgency=medium . * Non-maintainer upload. . [ Nobuhiro Iwamatsu ] * Bumped version of libopenobex in B-D to 1.7. * Fix FTBFS with libopenobex2. (Closes: #810521) Add patches/fix_ftbfs_with_libopenobex2.patch. . [ Mattia Rizzolo ] * Add explicit Build-Depends on libusb-dev. Checksums-Sha1:
Processed: merge two libproc-waitstat-perl bugs
Processing commands for cont...@bugs.debian.org: > merge 800243 811260 Bug #800243 [src:libproc-waitstat-perl] libproc-waitstat-perl: Please migrate a supported debhelper compat level Bug #811260 [src:libproc-waitstat-perl] libproc-waitstat-perl: FTBFS: Compatibility levels before 4 are no longer supported (level 3 requested) Added tag(s) stretch and sid. Bug #800243 [src:libproc-waitstat-perl] libproc-waitstat-perl: Please migrate a supported debhelper compat level Marked as found in versions libproc-waitstat-perl/1.00-4.1. Merged 800243 811260 > thanks Stopping processing here. Please contact me if you need assistance. -- 800243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800243 811260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#808858: [gimp] terminate called after throwing an instance of 'std::bad_alloc'
What happens if you remove beignet-opencl-icd?
Bug#809505: marked as done (bt-obex: crash with "Segmentation Fault" when trying to send a file)
Your message dated Sat, 06 Feb 2016 16:19:02 + with message-idand subject line Bug#809505: fixed in bluez-tools 0.2.0~20140808-5 has caused the Debian Bug report #809505, regarding bt-obex: crash with "Segmentation Fault" when trying to send a file 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.) -- 809505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bluez-tools Version: 0.2.0~20140808-4 Severity: grave Tags: patch upstream Justification: renders package unusable Dear Maintainer, While trying to use bt-obex command to exchange file with a mobile phone device, I have faced a number of unexpected Segmentation Faults. I took time to investigate and found the problem in the source, so I have prepared a patch that I have sent to Alexander Orlenko which seems to be the author of the tools, in hope to have it integrated upstream. I have attached the patch of interrest (5th of 5 patches), but be warned that I have made it against Git's latest state, so I am not sure it would apply to the current debian source state. I am adding Sam Morris in copy because he has reported 2 bugs which may be linked to similar issue, so if he has the possibility to test it would be interresting to know if it improves his cases. Regards, Christophe. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) >From 5046c746adbaba3137723a5be38e705f5d29e606 Mon Sep 17 00:00:00 2001 From: Christophe CURIS Date: Thu, 31 Dec 2015 12:03:16 +0100 Subject: [PATCH 5/5] Fix incorrect return value compare In the function obex_client_create_session, when the call to the dbus function would return a NULL pointer then the program would terminate with a "Segmentation Fault" message without further explanation, and it is not sure that in other cases it did behave as expected. Now the bt-obex command properly display the error message when dbus gives one and works in the other case. Signed-off-by: Christophe CURIS --- src/lib/bluez/obex/obex_client.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib/bluez/obex/obex_client.c b/src/lib/bluez/obex/obex_client.c index 02b65bb..2a4f20a 100644 --- a/src/lib/bluez/obex/obex_client.c +++ b/src/lib/bluez/obex/obex_client.c @@ -144,7 +144,7 @@ const gchar *obex_client_create_session(ObexClient *self, const gchar *destinati g_assert(OBEX_CLIENT_IS(self)); const gchar *ret = NULL; GVariant *proxy_ret = g_dbus_proxy_call_sync(self->priv->proxy, "CreateSession", g_variant_new ("(s@a{sv})", destination, args), G_DBUS_CALL_FLAGS_NONE, -1, NULL, error); - if (proxy_ret != NULL) + if (proxy_ret == NULL) return NULL; proxy_ret = g_variant_get_child_value(proxy_ret, 0); ret = g_variant_get_string(proxy_ret, NULL); -- 2.6.4 --- End Message --- --- Begin Message --- Source: bluez-tools Source-Version: 0.2.0~20140808-5 We believe that the bug you reported is fixed in the latest version of bluez-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nobuhiro Iwamatsu (supplier of updated bluez-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Jan 2016 04:55:49 +0900 Source: bluez-tools Binary: bluez-tools Architecture: source amd64 Version: 0.2.0~20140808-5 Distribution: unstable Urgency: medium Maintainer: Debian Bluetooth Maintainers Changed-By: Nobuhiro Iwamatsu Description: bluez-tools - Set of tools to manage Bluetooth devices for linux Closes: 785603 809505 Changes: bluez-tools (0.2.0~20140808-5) unstable; urgency=medium . * Fix crash with
Bug#808858: marked as done ([gimp] terminate called after throwing an instance of 'std::bad_alloc')
Your message dated Sat, 06 Feb 2016 18:31:39 + with message-id
Bug#813718: [Pkg-pascal-devel] Bug#813718: mricron: FTBFS: dialogsx.pas(77, 14) Error: (4054) Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons"
Hi, >So the patch is in mricron, I reassign the bug back to mricron and mark >it such as containing a patch. Gianfranco I suggest you send the patch >upstream as well. unfortunately I'm not the maintainer, and I failed to find the upstream code location/bug tracker. I hope Michael and Yaroslav will fix it and report the patch upstream. thanks for the great help and fix! cheers, Gianfranco
Processed: limit source to php-guzzle, tagging 813568
Processing commands for cont...@bugs.debian.org: > limit source php-guzzle Limiting to bugs with field 'source' containing at least one of 'php-guzzle' Limit currently set to 'source':'php-guzzle' > tags 813568 + pending Bug #813568 [src:php-guzzle] php-guzzle: FTBFS: DefaultCacheStorageTest::testCachesRequests strpos() expects parameter 1 to be string, array given Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 813568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813906: icedtea-netx: Fails to upgrade if openjdk-7-jre-headless is removed: "alternative /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/javaws for javaws not registered; not setting"
Package: icedtea-netx Version: 1.6.2-1 Severity: serious Hi, upgrading icedtea-netx from 1.6.1-4 to 1.6.2-1 while removing all openjdk7 packages (which is allowed according to the dependencies) fails for me as follows: Setting up icedtea-netx:amd64 (1.6.2-1) ... update-alternatives: error: alternative /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/javaws for javaws not registered; not setting dpkg: error processing package icedtea-netx:amd64 (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of icedtea-8-plugin:amd64: icedtea-8-plugin:amd64 depends on icedtea-netx (= 1.6.2-1); however: Package icedtea-netx:amd64 is not configured yet. dpkg: error processing package icedtea-8-plugin:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of icedtea-plugin: icedtea-plugin depends on icedtea-8-plugin; however: Package icedtea-8-plugin:amd64 is not configured yet. dpkg: error processing package icedtea-plugin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: icedtea-netx:amd64 icedtea-8-plugin:amd64 icedtea-plugin -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.6.2-1 ii openjdk-7-jre7u95-2.6.4-1 ii openjdk-8-jre8u72-b15-2 icedtea-netx recommends no packages. icedtea-netx suggests no packages. -- no debconf information
Bug#735573: marked as done (pystatgrab: FTBFS: error: too few arguments to function 'sg_init')
Your message dated Sat, 06 Feb 2016 15:49:36 + with message-idand subject line Bug#812819: Removed package(s) from unstable has caused the Debian Bug report #735573, regarding pystatgrab: FTBFS: error: too few arguments to function 'sg_init' 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.) -- 735573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pystatgrab Version: 0.5-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: sid jessie pystatgrab fails to build against the current version of libstatgrab: | x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c _statgrab.c -o build/temp.linux-x86_64-2.7/_statgrab.o | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_init': | _statgrab.c:350:3: error: too few arguments to function 'sg_init' |__pyx_1 = (sg_init() == 0); |^ | In file included from _statgrab.c:14:0: | /usr/include/statgrab.h:130:11: note: declared here | __sg_public sg_error sg_init(int ignore_init_errors); |^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_set_error': | _statgrab.c:512:3: warning: implicit declaration of function 'sg_set_error' [-Wimplicit-function-declaration] |sg_set_error(__pyx_1,__pyx_2); |^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_set_error_with_errno': | _statgrab.c:540:3: warning: implicit declaration of function 'sg_set_error_with_errno' [-Wimplicit-function-declaration] |sg_set_error_with_errno(__pyx_1,__pyx_2); |^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_get_host_info': | _statgrab.c:701:3: error: too few arguments to function 'sg_get_host_info' |__pyx_v_s = sg_get_host_info(); |^ | In file included from _statgrab.c:14:0: | /usr/include/statgrab.h:168:16: note: declared here | __sg_public sg_host_info *sg_get_host_info(size_t *entries); | ^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_get_cpu_stats': | _statgrab.c:784:3: error: too few arguments to function 'sg_get_cpu_stats' |__pyx_v_s = sg_get_cpu_stats(); |^ | In file included from _statgrab.c:14:0: | /usr/include/statgrab.h:191:16: note: declared here | __sg_public sg_cpu_stats *sg_get_cpu_stats(size_t *entries); | ^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_get_cpu_stats_diff': | _statgrab.c:864:3: error: too few arguments to function 'sg_get_cpu_stats_diff' |__pyx_v_s = sg_get_cpu_stats_diff(); |^ | In file included from _statgrab.c:14:0: | /usr/include/statgrab.h:192:16: note: declared here | __sg_public sg_cpu_stats *sg_get_cpu_stats_diff(size_t *entries); | ^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_get_cpu_percents': | _statgrab.c:946:63: error: expected expression before ')' token |__pyx_v_s = sg_get_cpu_percents(); |^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_get_mem_stats': | _statgrab.c:1027:3: error: too few arguments to function 'sg_get_mem_stats' |__pyx_v_s = sg_get_mem_stats(); |^ | In file included from _statgrab.c:14:0: | /usr/include/statgrab.h:227:16: note: declared here | __sg_public sg_mem_stats *sg_get_mem_stats(size_t *entries); | ^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_get_load_stats': | _statgrab.c:1099:3: error: too few arguments to function 'sg_get_load_stats' |__pyx_v_s = sg_get_load_stats(); |^ | In file included from _statgrab.c:14:0: | /usr/include/statgrab.h:238:17: note: declared here | __sg_public sg_load_stats *sg_get_load_stats(size_t *entries); | ^ | _statgrab.c: In function '__pyx_f_9_statgrab_py_sg_get_user_stats': | _statgrab.c:1167:3: error: too few arguments to function 'sg_get_user_stats' |__pyx_v_s = sg_get_user_stats(); |^ | In file included from _statgrab.c:14:0: | /usr/include/statgrab.h:253:17: note: declared here | __sg_public sg_user_stats *sg_get_user_stats(size_t *entries); | ^ | _statgrab.c:1185:42: error: 'sg_user_stats' has no member named 'name_list' |__pyx_4 = PyString_FromString(__pyx_v_s->name_list); if (!__pyx_4) {__pyx_filename = __pyx_f[0]; __pyx_lineno = 437; goto __pyx_L1;} | ^ | _statgrab.c:1188:37: error: 'sg_user_stats' has no member named 'num_entries' |__pyx_4 = PyInt_FromLong(__pyx_v_s->num_entries);
Bug#786158: marked as done (pystatgrab: deprecation of python-support)
Your message dated Sat, 06 Feb 2016 15:49:36 + with message-idand subject line Bug#812819: Removed package(s) from unstable has caused the Debian Bug report #786158, regarding pystatgrab: deprecation of python-support 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.) -- 786158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pystatgrab Version: 0.5-4 Severity: important User: debian-pyt...@lists.debian.org Usertags: pysupport-deprecation Dear Maintainer, your package either build-depends or depends on the python-support package, or uses dh_pysupport in debian/rules file. python-support has been deprecated for some time, and any package still using it should be migrated to dh_python2 and dh_python3. Instructions on how to migrate packages to dh_python2/dh_python3 can be found on the Debian wiki [0]. An overview of the anatomy of a package using the pybuild and dh_python{2,3} helpers can be found in the Python Module Style Guide [1]. Please test your package thoroughly to make sure the transition to dh_python2/dh_python3 is done correctly and does not cause a negative impact on your package. In particular, please test upgrades from the current jessie and stretch/sid versions of the package. If your package does not yet use Python 3, please consider adding Python 3 support to your package at the same time as updating the build system; the py3k porters can offer assistance with that [2]. [0] https://wiki.debian.org/Python/TransitionToDHPython2 [1] https://wiki.debian.org/Python/LibraryStyleGuide [2] https://wiki.debian.org/Python/Python3Port Thanks! --- End Message --- --- Begin Message --- Version: 0.5-4+rm Dear submitter, as the package pystatgrab has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/812819 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Re: Bug#807074: fbreader: includes files with unclear DFSG-freeness and/or copyright status
Processing control commands: > reopen -1 Bug #807074 {Done: "Eugene V. Lyubimkin"} [fbreader] fbreader: includes files with unclear DFSG-freeness and/or copyright status Bug reopened Ignoring request to alter fixed versions of bug #807074 to the same values previously set -- 807074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809580: marked as done (libdap: FTBFS without networking: getdap tests fail)
Your message dated Sat, 06 Feb 2016 18:19:51 + with message-idand subject line Bug#809580: fixed in libdap 3.15.1-7 has caused the Debian Bug report #809580, regarding libdap: FTBFS without networking: getdap tests fail 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.) -- 809580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdap Version: 3.15.1-5 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build without networking. Most builds are run without networking, and the Policy requires that builds succeed without external resources being available (such as remote websites): ## - ## ## Test results. ## ## - ## All 118 tests were successful. /bin/bash './getdapTest' ## - ## ## libdap 3.15.1 test suite: getdap. ## ## - ## 1: getdap -d http://test.opendap.org/dap/data/nc/fnoc1.nc getdap-testsuite/fnoc1.nc.dds (pass) FAILED (getdapTest.at:34) ## - ## ## Test results. ## ## - ## ERROR: 1 test was run, 1 failed unexpectedly. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libdap.html Ubuntu's builders also run without networking: https://launchpad.net/ubuntu/+source/libdap/3.15.1-5/+build/8342750 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: libdap Source-Version: 3.15.1-7 We believe that the bug you reported is fixed in the latest version of libdap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated libdap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Feb 2016 16:21:36 + Source: libdap Binary: libdap17v5 libdapclient6v5 libdapserver7v5 libdap-bin libdap-dev libdap-doc Architecture: source amd64 all Version: 3.15.1-7 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: libdap-bin - Binaries for the libdap Data Access Protocol library libdap-dev - Development files (headers and static libraries) for libdap libdap-doc - Documentation for the libdap Data Access Protocol library libdap17v5 - Open-source Project for a Network Data Access Protocol library libdapclient6v5 - Client library for the Network Data Access Protocol libdapserver7v5 - Server library for the Network Data Access Protocol Closes: 809580 Changes: libdap (3.15.1-7) unstable; urgency=medium . * Disable more networ, tests. Closes: #809580. Checksums-Sha1: 11d00c3363870060d22b179071df1993f17f3b40 2309 libdap_3.15.1-7.dsc 8a9892e918f85246b097e5957871363f5bf76bd8 9588 libdap_3.15.1-7.debian.tar.xz 64b1ae3c37d4eb92716d57aa273d9f3a3a426c4a 68622 libdap-bin-dbgsym_3.15.1-7_amd64.deb a1675fc0cedb64f4e3db5e341024e67992059c14 107816 libdap-bin_3.15.1-7_amd64.deb 8ae0bdc2e9d9dd2fb5a39b239703a5069af8d7e8 785616 libdap-dev_3.15.1-7_amd64.deb ea2f23639ee5c4e5b28cc3358f911e7a363cf642 97682 libdap-doc_3.15.1-7_all.deb 97bb406ab14040a887d5a12244fad931e7f75e53 4029344 libdap17v5-dbgsym_3.15.1-7_amd64.deb d1ac3550575df8eeff66c17ec9b2ac266a80a271 504396 libdap17v5_3.15.1-7_amd64.deb 3dfcbb4f0b7aab011c592ca58c8353867973cb19 722636 libdapclient6v5-dbgsym_3.15.1-7_amd64.deb f8552826e03497605d450f48ab443082e68f0bc5 178256 libdapclient6v5_3.15.1-7_amd64.deb fae95ea94b0c53fb0b6d2c78cf62bb64baa03bd2 105938 libdapserver7v5-dbgsym_3.15.1-7_amd64.deb 8ecc5f566059987d901d9850951e354411484980 112382 libdapserver7v5_3.15.1-7_amd64.deb Checksums-Sha256: 6d5823ed6e1fc7ca7d5235a13e852422d20080618b405f2334d1d3472fddbaf1 2309 libdap_3.15.1-7.dsc
Processed: Re: [Pkg-pascal-devel] Bug#813718: mricron: FTBFS: dialogsx.pas(77, 14) Error: (4054) Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons"
Processing control commands: > reassign -1 mricron Bug #813718 [fpc] removal of gtk1 causes mricron to FTBFS with 3.0.0 Bug reassigned from package 'fpc' to 'mricron'. No longer marked as found in versions fpc/3.0.0+dfsg-2. Ignoring request to alter fixed versions of bug #813718 to the same values previously set > retitle -1 mricron FTBFS because fpc check got more strict Bug #813718 [mricron] removal of gtk1 causes mricron to FTBFS with 3.0.0 Changed Bug title to 'mricron FTBFS because fpc check got more strict' from 'removal of gtk1 causes mricron to FTBFS with 3.0.0' > tags -1 patch upstream Bug #813718 [mricron] mricron FTBFS because fpc check got more strict Added tag(s) patch and upstream. -- 813718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813718: [Pkg-pascal-devel] Bug#813718: mricron: FTBFS: dialogsx.pas(77, 14) Error: (4054) Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons"
control: reassign -1 mricron control: retitle -1 mricron FTBFS because fpc check got more strict control: tags -1 patch upstream Great Michalis, thanks a lot. On 06-02-16 15:45, Michalis Kamburelis wrote: >> Short story: the patch is attached, it should help:) > > Better take this patch version (spaces, not tabs:). So the patch is in mricron, I reassign the bug back to mricron and mark it such as containing a patch. Gianfranco I suggest you send the patch upstream as well. Paul signature.asc Description: OpenPGP digital signature
Bug#807074: fbreader: includes files with unclear DFSG-freeness and/or copyright status
Control: reopen -1 On Sat, 23 Jan 2016 11:17:49 +0100 Eugene V. Lyubimkin wrote: > On 09.01.2016 12:51, Francesco Poli wrote: > > FTP Masters are often very busy, and in some cases they do not have > > time to reply to queries of this kind. Hence, we should *not* > > interpret their silence as if they were saying that everything is OK. > > > > I am consequently reopening the bug report. > > Francesco, we have a technical disagreement. Re-opening a bug won't change my > opinion. To overrule, please refer to > usual authorities: archive masters or tech-ctte or DAMs. The FTP Masters continue to be silent, but there's a new fact. I've been pointed out that the fbreader package not only includes OASIS files based on ISO files which do not grant permission to modify and only grant a limited permission to copy and distribute (as I originally reported), but also directly includes ISO files under the problematic license. These are the three files fbreader/data/formats/xhtml/*.ent These files are non-free: they do not grant permission to modify (thus failing DFSG#3) and only grant a limited permission to copy and use, restricting the field of endeavor to conforming SGML systems and applications as defined in ISO 8879 (thus failing DFSG#6). As an aside, they are not documented in the debian/copyright file, thus making them harder to spot... While the OASIS files have an unclear legal status, the ISO files are more clearly unfit for Debian main, as stated by FTP Assistant Paul Tagliamonte in: https://lists.debian.org/debian-legal/2015/12/msg0.html I am therefore reopening the bug report. Please investigate and fix the issue. Thanks for your time. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgp8RhakqPCh_.pgp Description: PGP signature
Bug#812655: charybdis: FTFBS against gnutls 3.4 (implicit declaration of function 'gnutls_certificate_client_set_retrieve_function')
On 2016-01-25 Andreas Metzlerwrote: [...] > I have already opened an upstream ticket on > https://github.com/charybdis-ircd/charybdis/issues/123 This is now fixed in upstream GIT. cu Andreas
Bug#813906: icedtea-netx: wrong logic in .postinst
Package: icedtea-netx Version: 1.6.2-1 Followup-For: Bug #813906 Dear Maintainer, I suspect a trouble in .postinst script. Here is my suggest: # 7's priority is higher, but 7 is not installed, set it to 8 if [ $priority7 -gt $priority8 ] && [ ! -f $base7dir/jre/bin/$i ]; then update-alternatives --set $i $base8dir/jre/bin/$i fi # 8's priority is higher, but 8 is not installed, set it to 7 if [ $priority8 -gt $priority7 ] && [ ! -f $base8dir/jre/bin/$i ]; then update-alternatives --set $i $base7dir/jre/bin/$i fi Regards, Patrice -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-trunk-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 Init: systemd (via /run/systemd/system) Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.6.2-1 ii openjdk-7-jre7u95-2.6.4-1 ii openjdk-8-jre8u72-b15-2 icedtea-netx recommends no packages. icedtea-netx suggests no packages. -- no debconf information
Bug#808858: [gimp] terminate called after throwing an instance of 'std::bad_alloc'
On 06.02.2016 19:24, Ari Pollak wrote: > What happens if you remove beignet-opencl-icd? Sorry, forgot to post the update: The issue went away after upgrading Mesa. Philipp
Bug#813970: dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.
Package: dbus Version: 1.10.6-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I cannot purge dbus package on my server: (Læser database ... 104307 filer og kataloger installeret i øjeblikket.) Afinstallerer dbus (1.8.20-0+deb8u1) ... Job for dbus.service canceled. invoke-rc.d: initscript dbus, action "stop" failed. dpkg: fejl under behandling af pakken dbus (--purge): underproces installerede pre-removal-script returnerede afslutningsstatus 1 Der opstod fejl under behandlingen: dbus - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJWtvPYAAoJECx8MUbBoAEhx9QP/AppsKAuduB3uUQumOWKsDy6 HfiY2OupLX7RNyY+1eI60z4Lrqkh0DmO4wmO3InGgW6yJ32mYuTDgv4PcFlXxuNq 8CQuwIv+L46iy+6s0xoZN1Fs5hpaG9/wv7F6FgOLb1c/AE4LlPd2O5OWgDNHZJSy XNEHzlfAJwcO78cnXG6VzzJiokn+oStQLVqvKLxMCLirHFvK28+coyfHaW6rxsf7 ke1X1NbqhuVjvhBa4nygZqwHv3q9KEUpMklzuYobPXJ0f2pAr7O+j9gPBsIg3bvT zQJKZTHYBIqOWyoJ5ZDPkQBpXpzxC4g9FDGdfK4bmvVAK+ORRI4MVzmWZ4C0tLGQ pyEQm9CSBBuEYKYl3hbVfoBmGMfEx7oI8XNhgL1y0ojcF9y2boBFvS+j79UKP6TG s87171B+c5RLtTLa/ul3gU6lDqU5xMPuWtLt0d1pH5yPOC887YduHnBeSIgdBWEM B+R+zqoxN1lX7NOjdX8pK6eXjqLXSi3aStz7t51K7DqMMNGZAXXX+bTkFcLVUHs8 Gu2opmxcf4VcVyaJ7odJ3Ev0ZUT7NUUCnz2MkeWQfrqWUgzIt12nRS4TgAQ/k6Dj +E7LTsKRulMjPDjL4+LDXtL/+BPbHttoWxMA0KDPJyYluJUawdeu4/L0h/dPYyR1 XHm082GrYyU7b4pWR9Db =pTWg -END PGP SIGNATURE-
Bug#739633: marked as done (c-repl depends on libreadline-ruby which no longer exists)
Your message dated Sun, 07 Feb 2016 07:30:56 + with message-idand subject line Bug#813931: Removed package(s) from unstable has caused the Debian Bug report #739633, regarding c-repl depends on libreadline-ruby which no longer exists 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.) -- 739633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreadline-ruby Severity: serious Tags: sid patch Your package depends on libreadline-ruby. A recent version of the libruby package (currently in sid but not yet in jessie) dropped the provides of libreadline-ruby. I brought this up on #debian-ruby (conversation pasted below) and it seems you can just drop the dependency. I notice that libruby seems to have dropped the provides of libreadline-ruby breaking c-repl was this intentional? I can't find any mention of it in the changelog <--snip--> that's part of "Drop Conflicts/Replaces/Provides on obsolete packages that are not even on squeeze anymore " plugwash, ^ so what should c-repl do? change it's dependency to libruby? seeing that it already depends on ruby... probably drop the libreadline-ruby dep --- End Message --- --- Begin Message --- Version: 0.0.20071223-1+rm Dear submitter, as the package c-repl has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/813931 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#813958: trinityrnaseq: FTBFS: cannot access .../trinityrnaseq-examples/...
Source: trinityrnaseq Version: 2.1.1+dfsg-1 Severity: serious Justification: fails to build from source Builds of trinityrnaseq covering only its main architecture-dependent package (notably, on the autobuilders, or with dpkg-buildpackage -B) failed: chmod u+x \ debian/trinityrnaseq/usr/lib/trinityrnaseq/Analysis/DifferentialExpression/pairwise_summaries/class_to_separate_fpkm_matrices.pl \ debian/trinityrnaseq/usr/lib/trinityrnaseq/Analysis/FL_reconstruction_analysis/count_by_expression_quintile.pl \ debian/trinityrnaseq/usr/lib/trinityrnaseq/util/misc/capture_orig_n_unmapped_reads.pl \ debian/trinityrnaseq/usr/lib/trinityrnaseq/util/support_scripts/plugin_install_tests.sh \ debian/trinityrnaseq/usr/lib/trinityrnaseq/util/support_scripts/trinity_install_tests.sh \ debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/__regression_tests/test_GraphFromFasta/runMe.sh \ debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/test_Inchworm/runMe_MPI.sh \ debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/test_Trinity_Assembly/__indiv_ex_sample_derived/ex05/runMe.clean.sh \ debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/test_Trinity_Assembly/__indiv_ex_sample_derived/ex05/runMe.sh chmod: cannot access 'debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/__regression_tests/test_GraphFromFasta/runMe.sh': No such file or directory chmod: cannot access 'debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/test_Inchworm/runMe_MPI.sh': No such file or directory chmod: cannot access 'debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/test_Trinity_Assembly/__indiv_ex_sample_derived/ex05/runMe.clean.sh': No such file or directory chmod: cannot access 'debian/trinityrnaseq-examples/usr/share/trinityrnaseq/sample_data/test_Trinity_Assembly/__indiv_ex_sample_derived/ex05/runMe.sh': No such file or directory debian/rules:42: recipe for target 'override_dh_install' failed Please conditionalize the different portions of this command appropriately. Thanks!
Processed: retitle 813573 to php-horde: CVE-2016-2228: Reflected cross-site scripting in menu bar
Processing commands for cont...@bugs.debian.org: > retitle 813573 php-horde: CVE-2016-2228: Reflected cross-site scripting in > menu bar Bug #813573 {Done: Mathieu Parent} [php-horde] [php-horde] XSS vulnerability in menu bar Changed Bug title to 'php-horde: CVE-2016-2228: Reflected cross-site scripting in menu bar' from '[php-horde] XSS vulnerability in menu bar' > thanks Stopping processing here. Please contact me if you need assistance. -- 813573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813957: edgar: FTBFS: find: 'debian/edgar-data': No such file or directory
Source: edgar Version: 1.21-1 Severity: serious Justification: fails to build from source Builds of edgar covering only its main architecture-dependent package (notably, on the autobuilders, or with dpkg-buildpackage -B) failed: find $(pwd)/debian/edgar-data -name "*.xcf" -exec rm {} \; find: '/«PKGBUILDDIR»/debian/edgar-data': No such file or directory debian/rules:10: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 1 make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules:7: recipe for target 'binary-arch' failed make: *** [binary-arch] Error 2 Please conditionalize this command appropriately. While you're at it, you might want to take out the redundant $(pwd)/ and simplify -exec rm {} \; to -delete. Thanks!
Bug#813880: tokyocabinet: testsuite failures on some archs
Source: tokyocabinet Severity: serious e.g powerpc and s390x are affected by a "metadata error". Investigating already. -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#801413: wheezy: update for polarssl's CVE-2015-5291
Hi, On Fri, Feb 05, 2016 at 08:44:37PM +, James Cowgill wrote: > Hi! > > On Fri, 2016-02-05 at 14:24 +0100, Guido Günther wrote: > > Hi, > > On Mon, Feb 01, 2016 at 09:51:54AM +0100, Sébastien Delafond wrote: > > > On Jan/31, Guido Günther wrote: > > > > Uploaded now. Thanks! > > > > > > Hi Guido, > > > > > > have you looked into fixing the jessie version (1.3.9-2.1) as well ? If > > > not, I'll need to look into it later this week, so that a DSA for > > > CVE-2015-5291 fixes both wheezy and jessie. > > > > Debdiff attached. It's far more intrusive since we also have to deal > > with CVE-2015-8036. > > > > James you alread discussed the best way forward at > > > > > > https://tls.mbed.org/discussions/bug-report-issues/question-about-cve-2015-5291 > > > > with upstream so I'm very interesed in your opinion on this as well. > > Upstream would obviously like Debian to use the point releases of > polarssl, but they broke the ABI in the 1.3 series since 1.3.9 so we > can't use them directly. I had a go at reverting the ABI breaking > changes and I posted my attempt earlier to this bug report, but the > changes I had to make were very intrusive and they'll probably have to > fixed up again every time there is a new release. >From what I read and figured from the Git commits I wonder if we should open CVEs for the other fixes in 1.3.14 too? > I'm beginning to feel like cherry picking the CVE related fixes (like > you've done) is probably the best solution, especially since this has > already taken some time to fix. Yeah, I think we should go ahead an fix these and rather revisit the problem in case we have more issues to fix. > > A few things on the debdiff you just posted: > - The attachment came though in ISO-8859-1 instead of UTF-8 and > lintian didn't like it. Hopefully the file is ok on your machine > though. > - I think the ssl-server-test needs an 'isolation-container' > restriction since it opens TCP ports. Good point, isolation-container restricction added. Cheers, -- Guido
Bug#801413: wheezy: update for polarssl's CVE-2015-5291
On Feb/06, Guido Günther wrote: > > A few things on the debdiff you just posted: > > - The attachment came though in ISO-8859-1 instead of UTF-8 and > > lintian didn't like it. Hopefully the file is ok on your machine > > though. > > - I think the ssl-server-test needs an 'isolation-container' > > restriction since it opens TCP ports. Hi Guido, can I get the updated debdiff ? I'm about to review it. Cheers, --Seb
Bug#810562: marked as done (ircp-tray: FTBFS with libopenobex 1.7.1: src/ircp_server.c:273: undefined reference to `OBEX_UnicodeToChar')
Your message dated Sat, 06 Feb 2016 13:38:13 + with message-idand subject line Bug#810562: fixed in ircp-tray 0.7.6-1.2 has caused the Debian Bug report #810562, regarding ircp-tray: FTBFS with libopenobex 1.7.1: src/ircp_server.c:273: undefined reference to `OBEX_UnicodeToChar' 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.) -- 810562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ircp-tray Version: 0.7.6-1.1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ircp-tray fails to build from source in unstable/amd64: [..] gcc -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -o ircp-tray ircptray.o ircptray_main.o ircptray_trayicon.o ircp_io.o ircp_client.o dirtraverse.o sendfile.o recvfile.o ircp_server.o progresswin.o savefiledlg.o irda_misc.o -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lopenobex -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 ircp_server.o: In function `ircp_srv_setpath': /home/lamby/temp/cdt.20160109213623.zKCqkyfqXu/ircp-tray-0.7.6/src/ircp_server.c:204: undefined reference to `OBEX_UnicodeToChar' ircp_server.o: In function `new_file': /home/lamby/temp/cdt.20160109213623.zKCqkyfqXu/ircp-tray-0.7.6/src/ircp_server.c:273: undefined reference to `OBEX_UnicodeToChar' collect2: error: ld returned 1 exit status Makefile:288: recipe for target 'ircp-tray' failed make[3]: *** [ircp-tray] Error 1 make[3]: Leaving directory '/home/lamby/temp/cdt.20160109213623.zKCqkyfqXu/ircp-tray-0.7.6/src' Makefile:285: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/lamby/temp/cdt.20160109213623.zKCqkyfqXu/ircp-tray-0.7.6' Makefile:223: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/lamby/temp/cdt.20160109213623.zKCqkyfqXu/ircp-tray-0.7.6' dh_auto_build: make -j1 returned exit code 2 debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ircp-tray.0.7.6-1.1.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: ircp-tray Source-Version: 0.7.6-1.2 We believe that the bug you reported is fixed in the latest version of ircp-tray, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 810...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated ircp-tray package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2016 13:31:00 + Source: ircp-tray Binary: ircp-tray Architecture: source Version: 0.7.6-1.2 Distribution: unstable Urgency: medium Maintainer: Devid Antonio Filoni Changed-By: Mattia Rizzolo Description: ircp-tray - IrDA and OBEX wireless file transfer Closes: 743127 810562 Changes: ircp-tray (0.7.6-1.2) unstable; urgency=medium . * Non-maintainer upload. . [ Nobuhiro Iwamatsu ] * Fix build with libopenobex2. (Closes: #810562) Add
Bug#813877: alienblaster content is used non-dfsg and legal problematic content.
Control: tags -1 moreinfo On Sat, 6 Feb 2016 17:51:58 +0900 Kouta Ikematsuwrote: > Package: alienblaster-data > Severity: serious > > Hello. > > alienblaster content (not code) is used "Red Cross flag". > This is "Health item" image. (Restore Player's Health) > > "Red Cross flag" is non-free, because this image is not freely use. (Violate > DFSG) > I think that this is misuse, It is violate of law. > > https://www.icrc.org/applic/ihl/ihl-nat.nsf/a24d1cf3344e99934125673e00508142/57a872a8776b3fc9c12572d700386930/$FILE/The%20Geneva%20Distinctive%20Emblems%20Protection%20Act%20of%202006.pdf > > http://law.e-gov.go.jp/htmldata/S22/S22HO159.html > > Thanks. > > Reference: > > https://bugzilla.redhat.com/show_bug.cgi?id=1305233 Hello, please clarify what image exactly is violating the law. I have looked through all bmp files in alienblaster's images directory but couldn't find the exact same image. There is one image with a red cross but this one is not copyrightable. It is far too common and generic. Please also note that there is a difference between trademark and copyright but currently I don't see a violation of either of them. Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: Re: alienblaster content is used non-dfsg and legal problematic content.
Processing control commands: > tags -1 moreinfo Bug #813877 [alienblaster-data] alienblaster content is used non-dfsg and legal problematic content. Added tag(s) moreinfo. -- 813877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813498: marked as done (scalapack FTBFS with openmpi1.10; patch included)
Your message dated Sat, 06 Feb 2016 13:43:13 + with message-idand subject line Bug#813498: fixed in scalapack 1.8.0-12.2 has caused the Debian Bug report #813498, regarding scalapack FTBFS with openmpi1.10; patch included 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.) -- 813498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scalapack Severity: important Tags: patch Attached is a patch for scalapack to build against openmpi1.10. Note that this really also requires: (1) depend on pkg-config (2) build-depend on mpi-default-dev/openmpi >= 1.10.2 (See #813494) -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -urN scalapack-1.8.0/debian/changelog scalapack-1.8.0.new/debian/changelog --- scalapack-1.8.0/debian/changelog 2015-03-10 09:10:28.0 + +++ scalapack-1.8.0.new/debian/changelog 2016-02-01 19:50:02.115258698 + @@ -1,3 +1,10 @@ +scalapack (1.8.0-12.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix for openmpi1.10 transition: Use pkg-config mpi-fort --libs + + -- Alastair McKinstry Mon, 01 Feb 2016 19:49:43 + + scalapack (1.8.0-12.1) unstable; urgency=medium * Non-maintainer upload. diff -urN scalapack-1.8.0/debian/patches/01_SLmake.inc.patch scalapack-1.8.0.new/debian/patches/01_SLmake.inc.patch --- scalapack-1.8.0/debian/patches/01_SLmake.inc.patch 2011-12-25 18:56:52.0 + +++ scalapack-1.8.0.new/debian/patches/01_SLmake.inc.patch 2016-02-01 19:28:21.720189006 + @@ -9,12 +9,12 @@ +ifeq ($(MPI),openmpi) +USEMPI= -DUsingMpiBlacs +ifeq ($(BUILD),static) -+SMPLIB= -L/usr/lib/openmpi/lib/ -lmpi -lmpi_f77 ++SMPLIB= $$(pkg-config mpi-fort --libs) +BLACSFINIT= /usr/lib/libblacsF77init-openmpi.a +BLACSCINIT= /usr/lib/libblacsCinit-openmpi.a +BLACSLIB = /usr/lib/libblacs-openmpi.a +else -+SMPLIB= -L/usr/lib/openmpi/lib/ -lmpi -lmpi_f77 ++SMPLIB= $$(pkg-config mpi-fort --libs) +BLACSFINIT= -lblacsF77init-openmpi +BLACSCINIT= -lblacsCinit-openmpi +BLACSLIB = -lblacs-openmpi diff -urN scalapack-1.8.0/debian/rules scalapack-1.8.0.new/debian/rules --- scalapack-1.8.0/debian/rules 2015-03-10 09:08:06.0 + +++ scalapack-1.8.0.new/debian/rules 2016-02-01 19:20:30.194770251 + @@ -49,7 +49,7 @@ ar x ../$${i}_openmpi.a ;\ cd .. ;\ gcc -shared -Wl,-soname=lib$$i-openmpi.so.$(version_major) -o \ - lib$$i-openmpi.so.$(version) tmp/*.o -lblas -llapack -lblacsCinit-openmpi -lblacs-openmpi -L/usr/lib/openmpi/lib -lmpi -lmpi_f77 -lgfortran;\ + lib$$i-openmpi.so.$(version) tmp/*.o -lblas -llapack -lblacsCinit-openmpi -lblacs-openmpi $$(pkg-config mpi-fort --libs) -lgfortran;\ ln -snf lib$$i-openmpi.so.$(version) lib$$i-openmpi.so.$(version_major) ;\ ln -snf lib$$i-openmpi.so.$(version_major) lib$$i-openmpi.so ;\ rm tmp/* ;\ --- End Message --- --- Begin Message --- Source: scalapack Source-Version: 1.8.0-12.2 We believe that the bug you reported is fixed in the latest version of scalapack, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 813...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated scalapack package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Feb 2016 14:31:30 + Source: scalapack Binary: libscalapack-openmpi1 libscalapack-mpich1 libscalapack-mpi-dev scalapack-mpi-test libscalapack-pvm1 libscalapack-pvm-dev scalapack-pvm-test scalapack-test-common Architecture: source Version: 1.8.0-12.2 Distribution: unstable Urgency: medium Maintainer: Muammar El Khatib Changed-By: Mattia Rizzolo
Bug#812452: marked as done (python-openstackclient-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc-base/python-openstackclient)
Your message dated Sat, 06 Feb 2016 10:22:24 + with message-idand subject line Bug#812452: fixed in python-openstackclient 2.0.0-3 has caused the Debian Bug report #812452, regarding python-openstackclient-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc-base/python-openstackclient 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.) -- 812452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-openstackclient-doc Version: 2.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python-openstackclient-doc. Preparing to unpack .../python-openstackclient-doc_2.0.0-2_all.deb ... Unpacking python-openstackclient-doc (2.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/python-openstackclient-doc_2.0.0-2_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/python-openstackclient', which is also in package python-openstackclient 1.7.1-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for libc-bin (2.21-6) ... Errors were encountered while processing: /var/cache/apt/archives/python-openstackclient-doc_2.0.0-2_all.deb cheers, Andreas python-openstackclient=1.7.1-1_python-openstackclient-doc=2.0.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-openstackclient Source-Version: 2.0.0-3 We believe that the bug you reported is fixed in the latest version of python-openstackclient, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-openstackclient package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2016 08:46:49 + Source: python-openstackclient Binary: python-openstackclient python3-openstackclient python-openstackclient-doc Architecture: source all Version: 2.0.0-3 Distribution: experimental Urgency: medium Maintainer: PKG OpenStack Changed-By: Thomas Goirand Description: python-openstackclient - OpenStack Command-line Client - Python 2.7 python-openstackclient-doc - OpenStack Command-line Client - doc python3-openstackclient - OpenStack Command-line Client - Python 3.x Closes: 812452 Changes: python-openstackclient (2.0.0-3) experimental; urgency=medium . * Blacklist 3 failed unit tests in Jessie (works in Sid): - test_shell.TestShellCli.test_shell_args_precedence - test_shell.TestShellCliEnv.test_shell_args_precedence_1 - test_shell.TestShellCliEnv.test_shell_args_precedence_2 * Drop python-tuskarclient from build-depends (project is stopped). * Add Breaks+Replaces: python-openstackclient (<< 2.0.0-2~) in python-openstackclient-doc (Closes: #812452). * VCS URLs using HTTPS. Checksums-Sha1: 67b2868df2a1557efe2962b803a818ac5cc5b20f 4331 python-openstackclient_2.0.0-3.dsc 19f49087fc8987fc3a1439ec7d7e924123c02262 45836 python-openstackclient_2.0.0-3.debian.tar.xz 87b79c600e95a93dd54fb68f81d30f3a1e6e73a7 332162 python-openstackclient-doc_2.0.0-3_all.deb ecfad9831a26e1a3f9ce9f607b6bafa029e949eb 183524 python-openstackclient_2.0.0-3_all.deb 3b27e4db5872dc5859c8ffef27f09413f6d0eebf 183660 python3-openstackclient_2.0.0-3_all.deb Checksums-Sha256: f9522aad4af4fc1d8b3f79a5a7531604cbab1345d05116d77498154fba896324 4331 python-openstackclient_2.0.0-3.dsc ee2d2eb440bec3646d270be922413bdf6996c4a35652f75ccfed8327739e56df 45836
Bug#813887: icedtea-netx: postinst fails registering javaws alternative for OpenJDK 7
Package: icedtea-netx Version: 1.6.2-1 Severity: serious Hi, on my dist-upgrade just now: Setting up icedtea-netx:amd64 (1.6.2-1) ... update-alternatives: error: alternative /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/javaws for javaws not registered; not setting dpkg: error processing package icedtea-netx:amd64 (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of icedtea-8-plugin:amd64: icedtea-8-plugin:amd64 depends on icedtea-netx (= 1.6.2-1); however: Package icedtea-netx:amd64 is not configured yet. dpkg: error processing package icedtea-8-plugin:amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: icedtea-netx:amd64 icedtea-8-plugin:amd64 Regards, Rene
Processed: Tagging #813873
Processing commands for cont...@bugs.debian.org: > tags 813873 + fixed-upstream pending Bug #813873 [src:python-mpop] python-mpop: FTBFS: ImportError: No module named eps_format Added tag(s) fixed-upstream and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 813873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813877: marked as done (alienblaster content is used non-dfsg and legal problematic content.)
Your message dated Sat, 6 Feb 2016 13:55:35 +0100 with message-id <56b5ed47.50...@debian.org> and subject line Re: alienblaster content is used non-dfsg and legal problematic content. has caused the Debian Bug report #813877, regarding alienblaster content is used non-dfsg and legal problematic content. 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.) -- 813877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: alienblaster-data Severity: serious Hello. alienblaster content (not code) is used "Red Cross flag". This is "Health item" image. (Restore Player's Health) "Red Cross flag" is non-free, because this image is not freely use. (Violate DFSG) I think that this is misuse, It is violate of law. https://www.icrc.org/applic/ihl/ihl-nat.nsf/a24d1cf3344e99934125673e00508142/57a872a8776b3fc9c12572d700386930/$FILE/The%20Geneva%20Distinctive%20Emblems%20Protection%20Act%20of%202006.pdf http://law.e-gov.go.jp/htmldata/S22/S22HO159.html Thanks. Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1305233 --- End Message --- --- Begin Message --- Am 06.02.2016 um 13:21 schrieb Kouta Ikematsu: > On Sat, 6 Feb 2016 12:26:56 +0100 > Markus Koschanywrote: > >> please clarify what image exactly is violating the law. > > I think that this is violate Geneva Conventions and Geneva Conventions > related law. > > Geneva Conventions is forbids misuse of red cross. > Geneva Conventions related law is same. > > Example: > > USA: > http://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title18-section706a%29=0=prelim > > Japan: http://law.e-gov.go.jp/htmldata/S22/S22HO159.html > > > Thanks. Since you have not specified the image in question, I will assume that you are referring to https://sources.debian.net/data/main/a/alienblaster/1.1.0-9/images/itemHealth.bmp I don't think this image violates the Geneva Conventions or related law because the shape of the red cross is very different and it does not resemble the flag of the ICRC. https://en.wikipedia.org/wiki/File:Flag_of_the_ICRC.svg There is also a huge difference between misusing the red cross in real life, which is indeed a protective sign and misuse is punishable by law, and the use in fantasy games like Alienblaster. I have found three interesting articles [1] [2] [3] and I can see why you think this might be an issue for Debian. But if you carefully read [2], then you will find the following paragraph: "Does this also apply to more fantasy oriented war games? No, the ICRC is talking about video games that simulate real-war situations. It is not suggesting that this apply to games that portray more fictional scenarios such as medieval fantasy or futuristic wars in outer space. A few media reported that certain virtual acts performed by characters in video games could amount to serious violations of the law of armed conflict. Is this correct? No. Serious violations of the laws of war can only be committed in real-life. A person cannot commit a war crime simply by playing a video game." Alienblaster does not simulate real war combat. It is a fantasy sci-fi shooter game and completely unrealistic. Since there are no trademark or copyright violations and no misuse of the original red cross symbol, I am going to close this bug report now. Regards, Markus [1] http://www.redcross.ca/about-us/about-the-canadian-red-cross/red-cross-emblem/it-may-just-be-a-game-to-you-but--it-means-the-world-to-us [2] https://www.icrc.org/eng/resources/documents/film/2013/09-28-ihl-video-games.htm [3] https://en.wikipedia.org/wiki/Emblems_of_the_International_Red_Cross_and_Red_Crescent_Movement signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#813377: marked as done (ocserv: B-D on obsolete package libsystemd-daemon-dev)
Your message dated Sat, 06 Feb 2016 13:40:48 + with message-idand subject line Bug#813377: fixed in ocserv 0.10.11-1 has caused the Debian Bug report #813377, regarding ocserv: B-D on obsolete package libsystemd-daemon-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 813377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocserv Version: 0.10.10-1 Severity: serious Justification: fails to build from source Hi, your package Build-Depends on the obsolete package libsystemd-daemon-dev that is no longer built (nor provided) by src:systemd. Please adjust your package to use libsystemd-dev instead. Andreas --- End Message --- --- Begin Message --- Source: ocserv Source-Version: 0.10.11-1 We believe that the bug you reported is fixed in the latest version of ocserv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 813...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aron Xu (supplier of updated ocserv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2016 03:22:56 +0800 Source: ocserv Binary: ocserv Architecture: source amd64 Version: 0.10.11-1 Distribution: unstable Urgency: medium Maintainer: Aron Xu Changed-By: Aron Xu Description: ocserv - OpenConnect VPN server compatible with Cisco AnyConnect VPN Closes: 813377 Changes: ocserv (0.10.11-1) unstable; urgency=medium . * New upstream bug fix release * d/rules: - Disable parallel building - Make use of dh-systemd * d/control: - Use libsystemd-dev (Closes: #813377) - Add libkrb5-dev and liboath-dev to B-D - std-ver: 3,9.6 -> 3.9.7, no change - Add VCS-* fields - Better tune arch list * Update example configuration, ship as default now Checksums-Sha1: 00d415dc79c885ebbddb8be0e5d944d6aff039a2 1954 ocserv_0.10.11-1.dsc f12dc32f57a2e5c312c835188974ea7613e3ae7b 730128 ocserv_0.10.11.orig.tar.xz 08d780be7301c8fab089028b3301d08d29be5686 61520 ocserv_0.10.11-1.debian.tar.xz f34bde5c32dc585137b38642548759886ebc6ba9 503288 ocserv-dbgsym_0.10.11-1_amd64.deb 6cdacda089e811cb16446b870e9caaf3977d72ba 240562 ocserv_0.10.11-1_amd64.deb Checksums-Sha256: b98885ee7de1c5c5ecd31fab888ec1219f6a719e0d375ac930f3cd6573d85f5c 1954 ocserv_0.10.11-1.dsc ba607ecc377d62e66cecaca73154c97e2ef6609e932250aad2906af46c1f785c 730128 ocserv_0.10.11.orig.tar.xz 90b9a3ecb99336104a8f31bc455a7001737f4e75dacc7b4c723ec39ee62009e4 61520 ocserv_0.10.11-1.debian.tar.xz a72cae54270d80ffc98dc0cb0ed2d21d76191f779233f3c99ca53924172803d4 503288 ocserv-dbgsym_0.10.11-1_amd64.deb 16401a5e835bfba95eec25efb2aeaf2e823bd6d2a947780be3001be5f16969d9 240562 ocserv_0.10.11-1_amd64.deb Files: 30288dafaf60ceb56ec80bf9348c5351 1954 net optional ocserv_0.10.11-1.dsc 7daf9f105b115cd6611a2ac016a29d24 730128 net optional ocserv_0.10.11.orig.tar.xz e067aa7e8ce3f55a39a6232a77f0ecaf 61520 net optional ocserv_0.10.11-1.debian.tar.xz c296168ecae2eb42a85073144136df9c 503288 debug extra ocserv-dbgsym_0.10.11-1_amd64.deb a7022fcf8969a9cbe7dbbb166389d3b5 240562 net optional ocserv_0.10.11-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJWteVNAAoJEPbsVcVkKA0eLyEH/3df8IRiTweb71fQpMcwHiuz 0K1hxS6Jck7cs/PwG2saxpmEI6Rz5slce1iLCPv+YIqYt8EZ84+fjyd7qHwXnEtj 1FSL35sKY8TQ0lWUQzGSb7zLjNrYKqNeucQLKTGNqFU/HodikgkWeqj/jZMk4c+v Uq0zngFL9HFIFwEoNOTuBPfcq1OdcbqJJo2uqadP0NC3G/NFXhWcM4D0lNNiUUm7 OO5yAQrxyw2GBnn4BfGttxDALweBha4sTxCzRz6aPlbMJKyB7giInwCuA+qXCuSD gBWEtLXU1OYKtdzqqsPPPl9FD57li2Ir6ycvrey7G5XF/eAB5AIEkO+o9b4lwvY= =qRHe -END PGP SIGNATURE End Message ---
Bug#812702: marked as done (neutron-lbaas: FTBFS - tests fail with a series of import errors)
Your message dated Sat, 06 Feb 2016 09:35:17 + with message-idand subject line Bug#812702: fixed in neutron-lbaas 1:7.0.2-1 has caused the Debian Bug report #812702, regarding neutron-lbaas: FTBFS - tests fail with a series of import errors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 812702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: neutron-lbaas Version: 2015.1.0-3 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] ===> Testing with python2.7 (python2) + rm -rf .testrepository + testr-python2 init + mktemp -t + TEMP_REZ=/tmp/tmp.xROdclR1LA + PYTHONPATH=/srv/jenkins-slave/workspace/sid-goto-cc-neutron-lbaas/neutron-lbaas-2015.1.0 PYTHON=python2.7 testr-python2 run --subunit neutron_lbaas\.tests\.unit\.(?!(.*test_synchronous_driver.TestHaproxyNSDriver.test_cleanup_name.*|.*test_v2_plugin_driver.TestLBaaSDriver.test_wf_created_on_first_member_creation.*|.*test_v2_plugin_driver.TestLBaaSDriverRestClient.test_flip_servers.*)) + tee /tmp/tmp.xROdclR1LA + subunit2pyunit No handlers could be found for logger "neutron.quota" runnNon-zero exit code (2) from test listing. ing=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./neutron_lbaas/tests/unit} --list --- import errors --- Failed to import test module: neutron_lbaas.tests.unit.agent.test_agent Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in _get_module_from_name __import__(name) File "neutron_lbaas/tests/unit/agent/test_agent.py", line 20, in from neutron_lbaas.agent import agent File "neutron_lbaas/agent/agent.py", line 26, in from neutron.openstack.common import service ImportError: cannot import name service [...] -- Ran 0 tests in 4.718s OK + cat /tmp/tmp.xROdclR1LA + + subunit-filter -s --no-passthrough subunit-stats Total tests: 0 Passed tests: 0 Failed tests: 0 Skipped tests: 0 Seen tags: + rm -f /tmp/tmp.xROdclR1LA + testr-python2 slowest debian/rules:19: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 3 The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael neutron-lbaas-build-log.txt.gz Description: application/gunzip signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: neutron-lbaas Source-Version: 1:7.0.2-1 We believe that the bug you reported is fixed in the latest version of neutron-lbaas, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated neutron-lbaas package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 22 Oct 2015 15:48:15 +0200 Source: neutron-lbaas Binary: python-neutron-lbaas neutron-lbaas-agent Architecture: source all Version: 1:7.0.2-1 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack Changed-By: Thomas Goirand Description: neutron-lbaas-agent - OpenStack virtual network service - lbass agent python-neutron-lbaas - OpenStack virtual network service - Python library Closes: 812702 Changes: neutron-lbaas (1:7.0.2-1) unstable; urgency=medium . * New upstream release (Closes: #812702). * Uploading to unstable. * Added git as build-depends. * Fixed debian/copyright order, holders and years. * Blacklisted some tests:
Bug#801413: wheezy: update for polarssl's CVE-2015-5291
On Sat, Feb 06, 2016 at 11:42:34AM +0100, Sébastien Delafond wrote: > On Feb/06, Guido Günther wrote: > > > A few things on the debdiff you just posted: > > > - The attachment came though in ISO-8859-1 instead of UTF-8 and > > > lintian didn't like it. Hopefully the file is ok on your machine > > > though. > > > - I think the ssl-server-test needs an 'isolation-container' > > > restriction since it opens TCP ports. > > Hi Guido, > > can I get the updated debdiff ? I'm about to review it. Attached. I've trimmed the CC: list a little to reduce the noise. Feel free to readd lists as you see fit. Cheers, -- Guido diff --git a/debian/changelog b/debian/changelog index a0b698f..2952b8f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +polarssl (1.3.9-2.2) jessie-security; urgency=high + + * Non-maintainer upload by the LTS Team. + * Backport pathes for CVE-2015-5291 and CVE-2015-8036 +(Closes: #801413) + * Add simple smoke test + + -- Guido GüntherFri, 05 Feb 2016 13:41:23 +0100 + polarssl (1.3.9-2.1) unstable; urgency=high * Non-maintainer upload. diff --git a/debian/patches/CVE-2015-5291-Added-max-length-checking-of-hostname.patch b/debian/patches/CVE-2015-5291-Added-max-length-checking-of-hostname.patch new file mode 100644 index 000..dd17324 --- /dev/null +++ b/debian/patches/CVE-2015-5291-Added-max-length-checking-of-hostname.patch @@ -0,0 +1,37 @@ +From: Simon Butcher +Date: Tue, 29 Sep 2015 23:27:20 +0100 +Subject: CVE-2015-5291: Added max length checking of hostname + +(cherry picked from commit c988f32adde62a169ba340fee0da15aecd40e76e) +--- + include/polarssl/ssl.h | 2 ++ + library/ssl_tls.c | 3 +++ + 2 files changed, 5 insertions(+) + +diff --git a/include/polarssl/ssl.h b/include/polarssl/ssl.h +index 194e944..2bd66ca 100644 +--- a/include/polarssl/ssl.h b/include/polarssl/ssl.h +@@ -194,6 +194,8 @@ + #endif /* POLARSSL_SSL_PROTO_TLS1_1 */ + #endif /* POLARSSL_SSL_PROTO_TLS1_2 */ + ++#define SSL_MAX_HOST_NAME_LEN 255 /*!< Maximum host name defined in RFC 1035 */ ++ + /* RFC 6066 section 4, see also mfl_code_to_length in ssl_tls.c + * NONE must be zero so that memset()ing structure to zero works */ + #define SSL_MAX_FRAG_LEN_NONE 0 /*!< don't use this extension */ +diff --git a/library/ssl_tls.c b/library/ssl_tls.c +index 5f080de..196f0c9 100644 +--- a/library/ssl_tls.c b/library/ssl_tls.c +@@ -3903,6 +3903,9 @@ int ssl_set_hostname( ssl_context *ssl, const char *hostname ) + if( ssl->hostname_len + 1 == 0 ) + return( POLARSSL_ERR_SSL_BAD_INPUT_DATA ); + ++if( ssl->hostname_len > SSL_MAX_HOST_NAME_LEN ) ++return( POLARSSL_ERR_SSL_BAD_INPUT_DATA ); ++ + ssl->hostname = (unsigned char *) polarssl_malloc( ssl->hostname_len + 1 ); + + if( ssl->hostname == NULL ) diff --git a/debian/patches/CVE-2015-8036-Add-extra-check-before-integer-conversion.patch b/debian/patches/CVE-2015-8036-Add-extra-check-before-integer-conversion.patch new file mode 100644 index 000..2b11b31 --- /dev/null +++ b/debian/patches/CVE-2015-8036-Add-extra-check-before-integer-conversion.patch @@ -0,0 +1,24 @@ +From: =?utf-8?q?Manuel_P=C3=A9gouri=C3=A9-Gonnard?= +Date: Fri, 2 Oct 2015 09:53:52 +0200 +Subject: CVE-2015-8036: Add extra check before integer conversion + +end < p should never happen, but just be extra sure + +(cherry picked from commit f3e6e4badb35760c9a543ee69b7449cb0cd9784b) +--- + library/ssl_cli.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/library/ssl_cli.c b/library/ssl_cli.c +index 7696311..9b4b8a9 100644 +--- a/library/ssl_cli.c b/library/ssl_cli.c +@@ -135,7 +135,7 @@ static void ssl_write_renegotiation_ext( ssl_context *ssl, + + SSL_DEBUG_MSG( 3, ( "client hello, adding renegotiation extension" ) ); + +-if( (size_t)(end - p) < 5 + ssl->verify_data_len ) ++if( end < p || (size_t)(end - p) < 5 + ssl->verify_data_len ) + { + SSL_DEBUG_MSG( 1, ( "buffer too small" ) ); + return; diff --git a/debian/patches/CVE-2015-8036-Added-bounds-checking-for-TLS-extensions.patch b/debian/patches/CVE-2015-8036-Added-bounds-checking-for-TLS-extensions.patch new file mode 100644 index 000..e674cd9 --- /dev/null +++ b/debian/patches/CVE-2015-8036-Added-bounds-checking-for-TLS-extensions.patch @@ -0,0 +1,280 @@ +From: Simon Butcher +Date: Thu, 1 Oct 2015 00:24:36 +0100 +Subject: CVE-2015-8036: Added bounds checking for TLS extensions + +IOTSSL-478 - Added checks to prevent buffer overflows. + +(cherry picked from commit b1e325d6b2bd9c504536fbbd45dce348f0a6c40c) +--- + library/ssl_cli.c | 141 +- + 1 file changed, 128 insertions(+), 13 deletions(-) + +diff --git a/library/ssl_cli.c b/library/ssl_cli.c +index 27abb3e..71e1beb 100644 +--- a/library/ssl_cli.c b/library/ssl_cli.c +@@ -68,6 +68,7 @@ static
Bug#813885: cppo: Missing native libraries
Package: cppo Version: 1.3.1-1 Severity: grave Tags: patch Dear Maintainer, On architectures with OCaml support for native compilation, cppo 1.3.1-1 is missing the native libraries. (They were there in 1.1.2-2.) The patch below fixes this problem (tested on amd64 and ppc64le), I have committed that to the git repository. Cheers, -Hilko diff --git a/debian/rules b/debian/rules index 8d769dc..6339d8a 100755 --- a/debian/rules +++ b/debian/rules @@ -26,4 +26,4 @@ endif .PHONY: override_dh_auto_install override_dh_auto_install: mkdir -p $(OCAMLFIND_DESTDIR) - make install 'BINDIR=$(DESTDIR)/usr/bin' BEST=$(OCAML_BEST) + make install 'BINDIR=$(DESTDIR)/usr/bin'
Bug#813398: opensmtpd: segfaults when relaying email
Thanks for the bug report. Upstream has released a fix, but I'm away from home/without access to my keys until Tuesday. Please feel free to NMU, or I'll deal with it when I get home. Sorry for the delay and best wishes, Ryan
Bug#800243: #800243: libproc-waitstat-perl: Please migrate a supported debhelper compat level
Tags: + patch Dear maintainer, as one of my packages (monotone) depends on libproc-waitstat-perl, I decided to take a look at this issue. Attached a proposal that updates and simplifies the packaging to use debhelper 9. Not strictly a minimalistic change, but a minimalistic approach. Please let me know what you think. Kind Regards Markus Wanner diff -Nru libproc-waitstat-perl-1.00/debian/changelog libproc-waitstat-perl-1.00/debian/changelog --- libproc-waitstat-perl-1.00/debian/changelog 2016-02-06 15:15:57.0 +0100 +++ libproc-waitstat-perl-1.00/debian/changelog 2016-02-06 15:15:48.0 +0100 @@ -1,3 +1,14 @@ +libproc-waitstat-perl (1.00-4.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Bump S-V from 3.5.2 to 3.9.7.0: drop the versioned B-D on perl. + * Set compatibility level v9. Closes: #800243. + * Set source format to 3.0 (quilt). + * Simplify debian/rules by using debhelper. Adjust build dependency +for debhelper. This adds the README to the binary package. + + -- Markus WannerSat, 06 Feb 2016 14:29:04 +0100 + libproc-waitstat-perl (1.00-4.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libproc-waitstat-perl-1.00/debian/compat libproc-waitstat-perl-1.00/debian/compat --- libproc-waitstat-perl-1.00/debian/compat1970-01-01 01:00:00.0 +0100 +++ libproc-waitstat-perl-1.00/debian/compat2016-02-06 14:08:00.0 +0100 @@ -0,0 +1 @@ +9 diff -Nru libproc-waitstat-perl-1.00/debian/control libproc-waitstat-perl-1.00/debian/control --- libproc-waitstat-perl-1.00/debian/control 2016-02-06 15:15:57.0 +0100 +++ libproc-waitstat-perl-1.00/debian/control 2016-02-06 15:10:24.0 +0100 @@ -2,12 +2,12 @@ Section: perl Priority: optional Maintainer: Roderick Schertler -Standards-Version: 3.5.2 -Build-Depends: debhelper (>= 3.0.5), perl (>= 5.6.0-16), libipc-signal-perl +Standards-Version: 3.9.7 +Build-Depends: debhelper (>= 9), libipc-signal-perl Package: libproc-waitstat-perl Architecture: all -Depends: ${perl:Depends}, libipc-signal-perl +Depends: ${perl:Depends}, ${misc:Depends}, libipc-signal-perl Description: interpret and act on wait() status values This Perl module contains functions which are useful for interpreting and acting on wait() status values. diff -Nru libproc-waitstat-perl-1.00/debian/rules libproc-waitstat-perl-1.00/debian/rules --- libproc-waitstat-perl-1.00/debian/rules 2016-02-06 15:15:57.0 +0100 +++ libproc-waitstat-perl-1.00/debian/rules 2016-02-06 14:15:27.0 +0100 @@ -1,73 +1,4 @@ #!/usr/bin/make -f -# $Id: rules,v 1.4 2001-07-31 14:34:41 roderick Exp $ - -dt := debian/libproc-waitstat-perl -prefix = `pwd`/$(dt) -stamp_build:= debian/stamp.build -stamp_install := debian/stamp.install -clean := $(stamp_build) $(stamp_install) - -ifneq "" "$(findstring debug,$(DEB_BUILD_OPTIONS))" -CFLAGS += -g -endif -export DH_COMPAT := 3 -PERL ?= perl - -build: $(stamp_build) -$(stamp_build): - dh_testdir - $(PERL) Makefile.PL INSTALLDIRS=vendor - $(MAKE) OPTIMIZE="-O2 -Wall $(CFLAGS)" - $(MAKE) test - touch $@ - -install: $(stamp_install) -$(stamp_install): $(stamp_build) - dh_testdir - dh_testroot - dh_clean -k - dh_installdirs - $(MAKE) install DESTDIR=$(prefix) - find $(prefix) -depth -type d -print0 | \ - xargs -0r rmdir --ignore-fail-on-non-empty - touch $@ - -clean: - dh_testdir - dh_testroot - [ ! -f Makefile ] || $(MAKE) realclean - dh_clean $(clean) - -binary: binary-indep binary-arch -binary-arch: -binary-indep: $(stamp_install) - dh_testdir - dh_testroot -# dh_installdebconf - dh_installdocs README - dh_installexamples - dh_installmenu -# dh_installlogrotate -# dh_installemacsen -# dh_installpam -# dh_installmime -# dh_installinit - dh_installcron - dh_installman - dh_installinfo -# dh_undocumented - dh_installchangelogs Changes - dh_link - dh_strip - dh_compress - dh_fixperms -# dh_makeshlibs - dh_installdeb - dh_perl - dh_shlibdeps - dh_gencontrol -u -isp - dh_md5sums - dh_builddeb - -.PHONY: build install clean binary-indep binary-arch binary +%: + dh $@ --with-perl diff -Nru libproc-waitstat-perl-1.00/debian/source/format libproc-waitstat-perl-1.00/debian/source/format --- libproc-waitstat-perl-1.00/debian/source/format 1970-01-01 01:00:00.0 +0100 +++ libproc-waitstat-perl-1.00/debian/source/format 2016-02-06 14:19:10.0 +0100 @@ -0,0 +1 @@ +3.0 (quilt) signature.asc Description: OpenPGP digital signature
Bug#813858: gcc-5: [mips] regression: miscompilation caused by -fexpensive-optimizations
I also see something like this for tokyocabinet, see #813880 for an analysis... I see those failures on powerpc, ppc64 and s390x, but not on mips. So this might be indeed a differnt bug as well, but I guess related to optimization. After seeing this bug, I tried -fno-expensive-optimizations on partch.d.o -- and this fixes also the regression I was experiencing. Comparing the buildd-logs, I see it not failing with version gcc-5_5.3.1-7 (https://buildd.debian.org/status/fetch.php?pkg=tokyocabi net=powerpc=1.4.48-5=1453879293) and the last-non-failing one was using gcc-5_5.3.1-4 (https://buildd.debian.org/status/fetch.php?pkg=tokyocab inet=powerpc=1.4.48-4=1451741581) -- tobi
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 812819 ftp.debian.org Bug #812819 [src:pystatgrab] should pystatgrab be removed from Debian? Bug reassigned from package 'src:pystatgrab' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #812819 to the same values previously set Ignoring request to alter fixed versions of bug #812819 to the same values previously set > severity 812819 normal Bug #812819 [ftp.debian.org] should pystatgrab be removed from Debian? Severity set to 'normal' from 'serious' > retitle 812819 RM: pystatgrab -- RoQA; unmaintained, RC-buggy, low popcon Bug #812819 [ftp.debian.org] should pystatgrab be removed from Debian? Changed Bug title to 'RM: pystatgrab -- RoQA; unmaintained, RC-buggy, low popcon' from 'should pystatgrab be removed from Debian?' > -- Stopping processing here. Please contact me if you need assistance. -- 812819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: try again to add tag: patch
Processing commands for cont...@bugs.debian.org: > tags 800243 +patch Bug #800243 [src:libproc-waitstat-perl] libproc-waitstat-perl: Please migrate a supported debhelper compat level Bug #811260 [src:libproc-waitstat-perl] libproc-waitstat-perl: FTBFS: Compatibility levels before 4 are no longer supported (level 3 requested) Added tag(s) patch. Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 800243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800243 811260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813718: [Pkg-pascal-devel] Bug#813718: mricron: FTBFS: dialogsx.pas(77, 14) Error: (4054) Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons"
> Short story: the patch is attached, it should help:) Better take this patch version (spaces, not tabs:). Michalis --- common/dialogsx.pas.orig 2016-02-06 15:20:36.0 +0100 +++ common/dialogsx.pas 2016-02-06 15:43:30.0 +0100 @@ -66,6 +66,36 @@ end; {$ENDIF} +{ Convert our TMsgDlgButtons type to Dialogs.TMsgDlgButtons type + in a type-safe manner. Do not assume that memory layout matches between + - TMsgDlgButtons and Dialogs.TMsgDlgButtons, or + - TMsgDlgBtn and Dialogs.TMsgDlgBtn. +} +function MsgDlgButtonsConvertToStandard( + const Buttons: TMsgDlgButtons): Dialogs.TMsgDlgButtons; +var + B: TMsgDlgBtn; +begin + Result := []; + for B := Low(B) to High(B) do +if B in Buttons then + { convert our TMsgDlgBtn to Dialogs.TMsgDlgBtn type } + case B of +mbYes : Include(Result, Dialogs.mbYes ); +mbNo : Include(Result, Dialogs.mbNo ); +mbOK : Include(Result, Dialogs.mbOK ); +mbCancel : Include(Result, Dialogs.mbCancel ); +mbAbort : Include(Result, Dialogs.mbAbort ); +mbRetry : Include(Result, Dialogs.mbRetry ); +mbIgnore : Include(Result, Dialogs.mbIgnore ); +mbAll : Include(Result, Dialogs.mbAll ); +mbNoToAll : Include(Result, Dialogs.mbNoToAll ); +mbYesToAll: Include(Result, Dialogs.mbYesToAll); +mbHelp: Include(Result, Dialogs.mbHelp); +else raise Exception.Create('Unsupported TMsgDlgBtn value'); + end; +end; + function MsgDlg(const Msg: string; DlgType: TMsgDlgType; Buttons: TMsgDlgButtons; HelpCtx: Longint): Word; {$IFDEF GUI} var @@ -74,7 +104,7 @@ begin lDlgType := Dialogs.TMsgDlgType(DlgType); - lButtons:= Dialogs.TMsgDlgButtons(Buttons); + lButtons:= MsgDlgButtonsConvertToStandard(Buttons); result := MessageDlg(Msg, lDlgType, lButtons,HelpCtx); {$ELSE} begin
Processed: forcibly merging 812371 812369
Processing commands for cont...@bugs.debian.org: > forcemerge 812371 812369 Bug #812371 [rpcbind] nis: NIS is started before rpcbind since rpcbind was migrated to systemd Bug #812369 [rpcbind] rpcbind does not properly provide $portmap needed by /etc/init.d/nis Severity set to 'critical' from 'important' Marked as found in versions rpcbind/0.2.3-0.1. Bug #812371 [rpcbind] nis: NIS is started before rpcbind since rpcbind was migrated to systemd Marked as found in versions rpcbind/0.2.3-0.2. Merged 812369 812371 > thanks Stopping processing here. Please contact me if you need assistance. -- 812369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812369 812371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Making it clearly visible that autodocktools is currently useless
Processing commands for cont...@bugs.debian.org: > severity 783547 grave Bug #783547 [autodocktools] TclError: cannot use geometry manager Severity set to 'grave' from 'important' > severity 767144 grave Bug #767144 [autodocktools] autodocktools: fails to start the GUI Bug #767145 [autodocktools] autodocktools: fails to start the GUI Severity set to 'grave' from 'important' Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 767144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767144 767145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767145 783547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813889: ebtables: Fails to upgrade if /var/lib/ebtables doesn't exist
Package: ebtables Version: 2.0.10.4-3.3 Severity: serious Dear Laurent, Updating ebtables from 2.0.10.4-3 to 2.0.10.4-3.3 fails for me as follows: […] Preparing to unpack .../ebtables_2.0.10.4-3.3_amd64.deb ... Unpacking ebtables (2.0.10.4-3.3) over (2.0.10.4-3) ... […] Setting up ebtables (2.0.10.4-3.3) ... rmdir: failed to remove '/var/lib/ebtables': No such file or directory dpkg: error processing package ebtables (--configure): subprocess installed post-installation script returned error exit status 1 […] Errors were encountered while processing: […] ebtables […] Failed to perform requested operation on package. Trying to recover: […] Setting up ebtables (2.0.10.4-3.3) ... rmdir: failed to remove '/var/lib/ebtables': No such file or directory dpkg: error processing package ebtables (--configure): subprocess installed post-installation script returned error exit status 1 […] Errors were encountered while processing: […] ebtables Downgrading again to 2.0.10.4-3 helps. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ebtables depends on: ii libc6 2.21-7 Versions of packages ebtables recommends: ii iptables 1.6.0-2 ii kmod 22-1 ebtables suggests no packages. -- no debconf information
Bug#813877: Re: alienblaster content is used non-dfsg and legal problematic content.
On Sat, 6 Feb 2016 12:26:56 +0100 Markus Koschanywrote: > please clarify what image exactly is violating the law. I think that this is violate Geneva Conventions and Geneva Conventions related law. Geneva Conventions is forbids misuse of red cross. Geneva Conventions related law is same. Example: USA: http://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title18-section706a%29=0=prelim Japan: http://law.e-gov.go.jp/htmldata/S22/S22HO159.html Thanks.
Bug#801413: wheezy: update for polarssl's CVE-2015-5291
On Feb/06, Guido Günther wrote: > Attached. I've trimmed the CC: list a little to reduce the noise. Feel > free to readd lists as you see fit. All good, please upload. Cheers, --Seb
Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1
On Wed, Feb 3, 2016 at 9:46 PM, Andreas Beckmannwrote: >> What is the best way to fix this? > > Probably reverting the reverted transition, therefore reopening this bug. > > You can drop the v5 suffix once upstream bumps the SOVERSION again and > you have to rename the package anyway. I'm preparing fix, Can anyone look at, https://anonscm.debian.org/cgit/debian-science/packages/lttoolbox.git/commit/?id=a3b07fe80d08de83902971f45aab75701bae8cea and see if it is OK? -- Kartik Mistry | IRC: kart_ {0x1f1f, kartikm}.wordpress.com
Processed: libsyncml: diff for NMU version 0.5.4-2.3
Processing control commands: > tags 794225 + pending Bug #794225 [src:libsyncml] libsyncml: please make the build reproducible (timestamps) Ignoring request to alter tags of bug #794225 to the same tags previously set > tags 811300 + pending Bug #811300 [libsyncml] FTBFS: error: 'OBEX_TRANS_CUST' undeclared Ignoring request to alter tags of bug #811300 to the same tags previously set -- 794225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794225 811300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libsyncml: diff for NMU version 0.5.4-2.3
Processing control commands: > tags 794225 + pending Bug #794225 [src:libsyncml] libsyncml: please make the build reproducible (timestamps) Added tag(s) pending. > tags 811300 + pending Bug #811300 [libsyncml] FTBFS: error: 'OBEX_TRANS_CUST' undeclared Added tag(s) pending. -- 794225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794225 811300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#811300: libsyncml: diff for NMU version 0.5.4-2.3
Control: tags 794225 + pending Control: tags 811300 + pending Dear maintainer, I've prepared an NMU for libsyncml (versioned as 0.5.4-2.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- diffstat for libsyncml_0.5.4-2.2 libsyncml_0.5.4-2.3 debian/patches/fix_build_with_libopenobex2.patch | 53 +++ libsyncml-0.5.4/debian/changelog | 15 ++ libsyncml-0.5.4/debian/control |2 libsyncml-0.5.4/debian/patches/series|1 libsyncml-0.5.4/debian/rules |2 5 files changed, 72 insertions(+), 1 deletion(-) diff -u libsyncml-0.5.4/debian/changelog libsyncml-0.5.4/debian/changelog --- libsyncml-0.5.4/debian/changelog +++ libsyncml-0.5.4/debian/changelog @@ -1,3 +1,18 @@ +libsyncml (0.5.4-2.3) unstable; urgency=medium + + * Non-maintainer upload. + + [ Nobuhiro Iwamatsu ] + * Fix FTBFS with libopenobex2-dev. Closes: #811300 +Add patches/fix_build_with_libopenobex2.patch. + * Change B-D from libopenobex1-dev to libopenobex2-dev. + + [ Maria Valentina Marin ] + * Export environment variable SOURCE_DATE_EPOCH to produce reproducible +timestamps in manpage output. Closes: #794225 + + -- Mattia RizzoloSat, 06 Feb 2016 13:05:59 + + libsyncml (0.5.4-2.2) unstable; urgency=medium * Non-maintainer upload. diff -u libsyncml-0.5.4/debian/control libsyncml-0.5.4/debian/control --- libsyncml-0.5.4/debian/control +++ libsyncml-0.5.4/debian/control @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: Michael Banck -Build-Depends: debhelper (>= 7.0.0), quilt, doxygen, cmake, check, libopenobex1-dev (>= 1.2), libxml2-dev (>= 2.6.16), libglib2.0-dev (>= 2.6.0), libsoup2.4-dev, libwbxml2-dev (>= 0.9.2-2), libxml2-dev +Build-Depends: debhelper (>= 7.0.0), quilt, doxygen, cmake, check, libopenobex2-dev (>= 1.7), libxml2-dev (>= 2.6.16), libglib2.0-dev (>= 2.6.0), libsoup2.4-dev, libwbxml2-dev (>= 0.9.2-2), libxml2-dev Standards-Version: 3.8.3 Package: libsyncml2 diff -u libsyncml-0.5.4/debian/patches/series libsyncml-0.5.4/debian/patches/series --- libsyncml-0.5.4/debian/patches/series +++ libsyncml-0.5.4/debian/patches/series @@ -2,0 +3 @@ +fix_build_with_libopenobex2.patch diff -u libsyncml-0.5.4/debian/rules libsyncml-0.5.4/debian/rules --- libsyncml-0.5.4/debian/rules +++ libsyncml-0.5.4/debian/rules @@ -11,6 +11,8 @@ DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog --count 1 -SDate)" +%s) + CFLAGS = -Wall -g ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 only in patch2: unchanged: --- libsyncml-0.5.4.orig/debian/patches/fix_build_with_libopenobex2.patch +++ libsyncml-0.5.4/debian/patches/fix_build_with_libopenobex2.patch @@ -0,0 +1,53 @@ +Origin: upstream +Bug-Debian: https://bugs.debian.org/811300 +Forwarded: not-yet +Last-Update: <2016-02-01> + +--- libsyncml-0.5.4.orig/libsyncml/transports/obex_client.c libsyncml-0.5.4/libsyncml/transports/obex_client.c +@@ -881,8 +881,8 @@ + + } else if (env->type == SML_TRANSPORT_CONNECTION_TYPE_USB) { + smlTrace(TRACE_INTERNAL, "%s: connecting to usb interface %i", __func__, env->port); +- +- obex_intf_cnt = OBEX_FindInterfaces(env->obexhandle, _intf); ++ ++ obex_intf_cnt = OBEX_EnumerateInterfaces(env->obexhandle); + smlTrace(TRACE_INTERNAL, "%s: found %i interfaces", __func__, obex_intf_cnt); + + if (obex_intf_cnt <= 0) { +only in patch2: +unchanged: +--- libsyncml-0.5.4.orig/tools/syncml-obex-client.c libsyncml-0.5.4/tools/syncml-obex-client.c +@@ -418,7 +418,7 @@ + if (geteuid() != 0) + fprintf(stderr, "Superuser privileges are required to access complete USB information.\n"); + +- interfaces_number = OBEX_FindInterfaces(handle, _intf); ++ interfaces_number = OBEX_EnumerateInterfaces(handle); + printf("Found %d USB OBEX interfaces\n", interfaces_number); + + for (i = 0; i < interfaces_number; i++) +--- libsyncml-0.5.4.orig/libsyncml/transports/obex_client.c libsyncml-0.5.4/libsyncml/transports/obex_client.c +@@ -716,7 +716,7 @@ + env->obexhandle = OBEX_Init(OBEX_TRANS_BLUETOOTH, smlTransportObexClientEvent, 0); + break; + case SML_TRANSPORT_CONNECTION_TYPE_SERIAL: +- env->obexhandle = OBEX_Init(OBEX_TRANS_CUST, smlTransportObexClientEvent, 0); ++ env->obexhandle = OBEX_Init(OBEX_TRANS_CUSTOM, smlTransportObexClientEvent, 0); + break; + case SML_TRANSPORT_CONNECTION_TYPE_USB: +
Bug#813880: tokyocabinet: testsuite failures on some archs
Control: tags -1 pending Ok, before uploading the fix, this error needs some documentation, as this is a quite weird one; and I'm not 100% sure if this not a gcc bug. The bug is in tcfdbloadmeta(), where TC tries to load and parse the meta data. Its bascially always "memcpy some bytes to a temp var, do endianess correction and store result into struct. (The function is quoted below, for easier referncing) gdb'ing into it, it shows that the metadata is correctly loaded in to the buffer (hbuf) but not correctly stored restored. As an example, the failing testcase creates a TC DB with fdb->width = 50; this information is stored in the file with offset=64. Memdump of hbuf shows that the expected value is there... However, fdb->width is 0 after tcfdbloadmeta()... A tatical "volatile" before the local fixes that... I'm not really sure if gcc is allowed to do such optimizations... The func: /* Deserialize meta data from a buffer. `fdb' specifies the fixed-length database object. `hbuf' specifies the buffer. */ static void tcfdbloadmeta(TCFDB *fdb, const char *hbuf){ memcpy(&(fdb->type), hbuf + FDBTYPEOFF, sizeof(fdb->type)); memcpy(&(fdb->flags), hbuf + FDBFLAGSOFF, sizeof(fdb->flags)); volatile uint64_t llnum; // << the volatile is added to fix this. memcpy(, hbuf + FDBRNUMOFF, sizeof(llnum)); fdb->rnum = TCITOHLL(llnum); memcpy(, hbuf + FDBFSIZOFF, sizeof(llnum)); fdb->fsiz = TCITOHLL(llnum); memcpy(, hbuf + FDBWIDTHOFF, sizeof(llnum)); fdb->width = TCITOHLL(llnum); memcpy(, hbuf + FDBLIMSIZOFF, sizeof(llnum)); fdb->limsiz = TCITOHLL(llnum); memcpy(, hbuf + FDBMINOFF, sizeof(llnum)); fdb->min = TCITOHLL(llnum); memcpy(, hbuf + FDBMAXOFF, sizeof(llnum)); fdb->max = TCITOHLL(llnum); } -- tobi
Processed: Re: tokyocabinet: testsuite failures on some archs
Processing control commands: > tags -1 pending Bug #813880 [src:tokyocabinet] tokyocabinet: testsuite failures on some archs Added tag(s) pending. -- 813880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813858: gcc-5: [mips] regression: miscompilation caused by -fexpensive-optimizations
On Sat, 06 Feb 2016 15:37:09 +0100 Tobias Frostwrote: > > I see those failures on powerpc, ppc64 and s390x, but not on mips. > So this might be indeed a differnt bug as well, but I guess related to Ähm, should read: ALSO on mips
Bug#813858: gcc-5: [mips] regression: miscompilation caused by -fexpensive-optimizations
Control: affects -1 tokyocabinet Hi Tobias, On 06.02.2016 15:37, Tobias Frost wrote: > I also see something like this for tokyocabinet, see #813880 for an > analysis... > > I see those failures on powerpc, ppc64 and s390x, but not on mips. Well, 1.4.48-5 and 1.4.48-6 also failed to build on mips [1]. > So this might be indeed a differnt bug as well, but I guess related to > optimization. > > After seeing this bug, I tried -fno-expensive-optimizations on > partch.d.o -- and this fixes also the regression I was experiencing. I tried making the argument of av_bswap32 in my test case volatile and that also fixed the problem. So it seems to me that these really are the same bug. Thus I've added this to the bug metadata. Best regards, Andreas 1: https://buildd.debian.org/status/fetch.php?pkg=tokyocabinet=mips=1.4.48-6=1454770843
Processed: Re: Bug#813858: gcc-5: [mips] regression: miscompilation caused by -fexpensive-optimizations
Processing control commands: > affects -1 tokyocabinet Bug #813858 [gcc-5] gcc-5: [mips] regression: miscompilation caused by -fexpensive-optimizations Added indication that 813858 affects tokyocabinet -- 813858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813718: [Pkg-pascal-devel] Bug#813718: mricron: FTBFS: dialogsx.pas(77, 14) Error: (4054) Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons"
> I can't see where the dialogs unit is getting the TMsgDlgButtons method > or function or procedure or whatever it is called in Pascal from. Short story: the patch is attached, it should help:) Longer explanation: 1. TMsgDlgButtons is a "type". It's a set (which is like a type-safe bitfield in Pascal). Writing "Dialogs.TMsgDlgButtons" means "take TMsgDlgButtons type from Dialogs unit, not from any other unit that may define the same name" --- that's how you deal with multiple used units having the same identifier in Pascal. 2. What happens in this code is a little dirty, as mricron code defines it's own type "TMsgDlgButtons", with the *exact* same memory layout as standard "TMsgDlgButtons" type in "Dialogs" unit. "Dialogs" unit is part of the Lazarus library (LCL). Then the line lButtons:= Dialogs.TMsgDlgButtons(Buttons); converts one type to another. The dirtyness here is that such typecast avoids any type checks, it just assumes that memory layout of both "TMsgDlgButtons" types matches, and that the programmer knows what (s)he is doing:) 3. To make it a little confusing, type names are the same, so you need to be aware how compiler resolves them, and some error messages become unclear. This message from FPC: Illegal type conversion: "TMsgDlgButtons" to "TMsgDlgButtons" actually means that we cannot convert "TMsgDlgButtons as defined in unit dialogsx" to "TMsgDlgButtons as defined in unit Dialogs". Possibly FPC checks got stricter? Which would be a good thing here --- this code is indeed dangerous, it's good that it's prohibited, IMHO. In fact, Lazarus Dialogs.TMsgDlgButtons type did change (there's a new enum mbClose), it only accidentally didn't change the memory layout of TMsgDlgButtons (as mbClose was added at the end). 4. The attached patch just does the type conversion the long (but safe) way. Regards, Michalis --- common/dialogsx.pas.orig 2016-02-06 15:20:36.0 +0100 +++ common/dialogsx.pas 2016-02-06 15:32:45.0 +0100 @@ -66,6 +66,36 @@ end; {$ENDIF} +{ Convert our TMsgDlgButtons type to Dialogs.TMsgDlgButtons type + in a type-safe manner. Do not assume that memory layout matches between + - TMsgDlgButtons and Dialogs.TMsgDlgButtons, or + - TMsgDlgBtn and Dialogs.TMsgDlgBtn. +} +function MsgDlgButtonsConvertToStandard( + const Buttons: TMsgDlgButtons): Dialogs.TMsgDlgButtons; +var + B: TMsgDlgBtn; +begin + Result := []; + for B := Low(B) to High(B) do +if B in Buttons then + { convert our TMsgDlgBtn to Dialogs.TMsgDlgBtn type } + case B of +mbYes : Include(Result, Dialogs.mbYes ); + mbNo : Include(Result, Dialogs.mbNo ); + mbOK : Include(Result, Dialogs.mbOK ); + mbCancel : Include(Result, Dialogs.mbCancel ); + mbAbort : Include(Result, Dialogs.mbAbort ); + mbRetry : Include(Result, Dialogs.mbRetry ); + mbIgnore : Include(Result, Dialogs.mbIgnore ); + mbAll : Include(Result, Dialogs.mbAll ); + mbNoToAll : Include(Result, Dialogs.mbNoToAll ); + mbYesToAll: Include(Result, Dialogs.mbYesToAll); + mbHelp : Include(Result, Dialogs.mbHelp); +else raise Exception.Create('Unsupported TMsgDlgBtn value'); + end; +end; + function MsgDlg(const Msg: string; DlgType: TMsgDlgType; Buttons: TMsgDlgButtons; HelpCtx: Longint): Word; {$IFDEF GUI} var @@ -74,7 +104,7 @@ begin lDlgType := Dialogs.TMsgDlgType(DlgType); - lButtons:= Dialogs.TMsgDlgButtons(Buttons); + lButtons:= MsgDlgButtonsConvertToStandard(Buttons); result := MessageDlg(Msg, lDlgType, lButtons,HelpCtx); {$ELSE} begin
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 801377 serious Bug #801377 [bgfinancas] bgfinancas: build-depends on unmaintained substance library Severity set to 'serious' from 'normal' > -- Stopping processing here. Please contact me if you need assistance. -- 801377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems