Processed: Merging duplicates
Processing commands for cont...@bugs.debian.org: > forcemerge 925967 92 Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: Kernel 4.19.0-4 stucks blank screen before starting SDDM or any Login Manager Bug #92 [src:linux] linux-image-4.19.0-4-amd64: Display manager fails to start or display anything on IvyBridge with linux-image-4.19.0-4-amd64 Severity set to 'critical' from 'important' Merged 92 925967 > End of message, stopping processing here. Please contact me if you need assistance. -- 92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92 925967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925967: Solved
On Wed, 24 Apr 2019 14:12:51 -0300 leandroe...@gmail.com wrote: > I solved the problem by copying the file /usr/share/doc/xserver-xorg- > video-intel/xorg.conf to the directory /etc/X11/ I confirm this workaround does work.
Bug#926304: marked as done (freecad: autopkgtest regression)
Your message dated Sun, 28 Apr 2019 00:48:42 + with message-id and subject line Bug#926304: fixed in freecad 0.18.1+dfsg1-2 has caused the Debian Bug report #926304, regarding freecad: autopkgtest regression 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.) -- 926304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freecad Version: 0.18+dfsg1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 0.18+dfsg1-1, freecad has been failing its own autopkgtests [1] with the following error: TestFem (unittest.loader._FailedTest) ... ERROR Regards Graham [1] https://ci.debian.net/packages/f/freecad/unstable/amd64/ --- End Message --- --- Begin Message --- Source: freecad Source-Version: 0.18.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of freecad, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Kremitzki (supplier of updated freecad 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: Sat, 27 Apr 2019 19:06:02 -0500 Source: freecad Architecture: source Version: 0.18.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kurt Kremitzki Closes: 926251 926304 Changes: freecad (0.18.1+dfsg1-2) unstable; urgency=medium . * [5cd3fce] Add missing pyside2 deps * [fd92cc2] Fix breaks+replaces relations (Closes: #926251) * [c61fe87] Add upstream bugfixing patch * [f95e30a] Fix FEM autopkgtest (Closes: #926304 #920535) Checksums-Sha1: d487252c6aeaea79cd6eb22a19dd483079510024 3563 freecad_0.18.1+dfsg1-2.dsc 4a995f4da37c02d451c044abcb652d5ce88baec3 31068 freecad_0.18.1+dfsg1-2.debian.tar.xz 664543f746cf97ce7aa657b24838fed5cd397205 31291 freecad_0.18.1+dfsg1-2_source.buildinfo Checksums-Sha256: 6b1feac5c5f16b689f457b0090ddc60702dcb4149604664b5bb5ed02ad84bc6a 3563 freecad_0.18.1+dfsg1-2.dsc 80beab6ad9bb2b02b2d398e6ca91e2c946817f06edf56351d28616980137f0df 31068 freecad_0.18.1+dfsg1-2.debian.tar.xz aaa1279f6f2ef6e27d34f8ff81904683c837e907f6dba280e5b2d8e4089e0fea 31291 freecad_0.18.1+dfsg1-2_source.buildinfo Files: b4e09dd701d5280377e19c4fc002afe1 3563 science optional freecad_0.18.1+dfsg1-2.dsc de5e84dba5e9b4c7d16b5735ed8adb2a 31068 science optional freecad_0.18.1+dfsg1-2.debian.tar.xz a12c59ce9385d1fa2c099f7d00403c31 31291 science optional freecad_0.18.1+dfsg1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAlzE9GQRHGt1cnRAa3dr LnN5c3RlbXMACgkQKUghB0bfc8BzpxAAgCmxMWE01tzxoh6gWYgMIMEn9dlNov/Z bZCCd8leuPdlbeHWr8Rr8SShrPlr8yRS+0f5rfIgl63864mJUJ6uVUd0fmImbFTp GwAW3zJ78UWHRbpu5mhHKkSpazBvdPUmZvNR0Ww1vHknZF8O80/L+kyrZ/4Ev/dR tFBPo8xmB1JH4T5Ji3+i2QHb245te95WmXL7krBMj6k4k5zD6DgPTCP4wUdehkPi YBaVdkyQVQPuoNhRC8zMAs+8p/XvrbEdL3sBkT3wzwvCtnwY6Ib9wqcUw427R83r R1mDdfJ+CV+TuG3fusCKvcyjO0mbpEiCjFsI7vIZNUveXXebmqzvofOBbOXmhjwx y1LFt1yaBYjgzKwZ365Y5YEB2i8ida5P2k4yxIpKb8l7TvkLgTDB+XhviXQTPZt0 bDHfzDkXJ2SstFDHWkb1O4x1PWYYIH7w6TZOKlFV1ahhabDlOz4FZv6TafmF5q0Q mZ3i+8q+l45jHgDAgs8eLiUVM/gHncf0owtYS7Og3r6M86eWgqIgxK5LdP0zqkvY /xXDUspI/+pKuwLBrRZrZgSlBJJS/BjmEsU9mEi+BRxofF21Tt/n7ypgM75Mr16A WHxWgKLHfZE7KeILi/My5I70rYU3Dl84kyB41DY8aifib/Y1HFS7ZTM5hIN4wrsd YQtOfUbzOuA= =CL2y -END PGP SIGNATURE End Message ---
Bug#926251: marked as done (freecad-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/freecad.1.gz)
Your message dated Sun, 28 Apr 2019 00:48:42 + with message-id and subject line Bug#926251: fixed in freecad 0.18.1+dfsg1-2 has caused the Debian Bug report #926251, regarding freecad-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/freecad.1.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 926251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freecad-common Version: 0.18+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../freecad-common_0.18+dfsg1-1_all.deb ... Unpacking freecad-common (0.18+dfsg1-1) over (0.18~pre1+dfsg1-5) ... dpkg: error processing archive /var/cache/apt/archives/freecad-common_0.18+dfsg1-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/freecad.1.gz', which is also in package freecad-python2 0.18~pre1+dfsg1-5 Errors were encountered while processing: /var/cache/apt/archives/freecad-common_0.18+dfsg1-1_all.deb freecad-common currently has Replaces: freecad (<< 0.18~), freecad-python2 (<< 0.18~) Conflicts: freecad (<< 0.18~), freecad-python2 (<< 0.18~) Breaks: freecad (<< 0.18~), freecad-python2 (<< 0.18~) which does not cover the version in testing. (<< 0.18) should do. Also having both Breaks and Conflicts on the same is redundant. You most likely don't need the Conflicts, the Breaks should be sufficient (and simplify the upgrade path for apt). cheers, Andreas freecad-python2=0.18~pre1+dfsg1-5_freecad-common=0.18+dfsg1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: freecad Source-Version: 0.18.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of freecad, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Kremitzki (supplier of updated freecad 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: Sat, 27 Apr 2019 19:06:02 -0500 Source: freecad Architecture: source Version: 0.18.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kurt Kremitzki Closes: 926251 926304 Changes: freecad (0.18.1+dfsg1-2) unstable; urgency=medium . * [5cd3fce] Add missing pyside2 deps * [fd92cc2] Fix breaks+replaces relations (Closes: #926251) * [c61fe87] Add upstream bugfixing patch * [f95e30a] Fix FEM autopkgtest (Closes: #926304 #920535) Checksums-Sha1: d487252c6aeaea79cd6eb22a19dd483079510024 3563 freecad_0.18.1+dfsg1-2.dsc 4a995f4da37c02d451c044abcb652d5ce88baec3 31068 freecad_0.18.1+dfsg1-2.debian.tar.xz 664543f746cf97ce7aa657b24838fed5cd397205 31291 freecad_0.18.1+dfsg1-2_source.buildinfo Checksums-Sha256: 6b1feac5c5f16b689f457b0090ddc60702dcb4149604664b5bb5ed02ad84bc6a 3563 freecad_0.18.1+dfsg1-2.dsc 80beab6ad9bb2b02b2d398e6ca91e2c946817f06edf56351d28616980137f0df 31068 freecad_0.18.1+dfsg1-2.debian.tar.xz aaa1279f6f2ef6e27d34f8ff81904683c837e907f6dba280e5b2d8e4089e0fea 31291 freecad_0.18.1+dfsg1-2_source.buildinfo Files: b4e09dd701d5280377e19c4fc002afe1 3563 science optional freecad_0.18.1+dfsg1-2.dsc de5e84dba5e9b4c7d16b5735ed8adb2a 31068 science optional freecad_0.18.1+dfsg1-2.debian.tar.xz a12c59ce9385d1fa2c099f7d00403c31 31291 science optional freecad_0.18.1+dfsg1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAlzE9GQRHGt1cnRAa3dr LnN5c3RlbXMACgkQKUghB0bfc8BzpxAAgCmxMWE01tzxoh6gWYgMIMEn9dlNov/Z bZCCd8leuPdlbeHWr8Rr8SShrPlr8yRS+0f5rfIgl63864mJUJ6uVUd0fmImbFTp
Bug#788721: firefox-esr: Some sources are misssing
Hi all, We had the privilege to hold the Toronto BSP in the Mozilla offices here, and our host (in CC) was kind enough to take a quick look at this issue with the Firefox package. He told me to CC him so that he could look into the issue. So to summarize for Will: there's a release-critical bug filed against Firefox in Debian right now, which is fully visible here: https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no=788721 The problem is that the Firefox source code bundles copies of compiled of Javascript files that are missing the source version. In Debian that's considered a copyright issue as compiled Javascript files are like compiled binaries and not sufficient to work on as source code. We need to find where that source is, in other words, for those files. Jonas created a short list of the affected files, below. We'd be really grateful if you could take a look at this. Thanks! A. -- It will be a great day when our schools get all the money they need and the air force has to hold a bake sale to buy a bomber. - Unknown On 2019-04-07 12:01:39, Jonas Smedegaard wrote: > control: reassign 788721 firefox-esr > control: retitle 788721 firefox-esr: Some sources are missing > > This bug affects firefox-esr in testing: > > At least these non-source files are still problematic: > > js/src/octane/typescript-input.js > js/src/octane/box2d.js > third_party/python/mock-1.0.0/html/_static/underscore.js > third_party/python/mock-1.0.0/html/_static/jquery.js > browser/components/translation/cld2/cld-worker.js > browser/extensions/pocket/content/panels/js/vendor/jquery.tokeninput.min.js > browser/extensions/pocket/content/panels/js/vendor/jquery-2.1.1.min.js > layout/mathml/tests/stretchy-and-large-operators.js > > Other of the previously reported files may still be relevant as well, > and possibly additional files are similarly problematic (indicated by > doing a "find -name '*.min.js'" without examining further). > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#926802: marked as done (ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function))
Your message dated Sat, 27 Apr 2019 22:33:20 +
with message-id
and subject line Bug#926802: fixed in ipywidgets 6.0.0-4
has caused the Debian Bug report #926802,
regarding ipywidgets: FTBFS (TypeError:
path.scope.getBindings(...).hasOwnProperty is not a function)
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.)
--
926802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipywidgets
Version: 6.0.0-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure
I: pybuild base:217: python2.7 setup.py config
running config
I: pybuild base:217: python3.7 setup.py config
running config
dh_auto_configure -- -d ./widgetsnbextension
I: pybuild base:217: python2.7 setup.py config
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
I: pybuild base:217: python3.7 setup.py config
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
make[1]: Leaving directory '/<>'
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make -C debian -f fakewebpack.mk all
make[2]: Entering directory '/<>/debian'
/usr/bin/make -f "fakewebpack-prep-unpacked.mk" all
make[3]: Entering directory '/<>/debian'
cd "fakewebpack-unpacked/phosphor/" && tsc --moduleResolution Classic --project
src
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && NODE_PATH=../..
fakewebpack-helpers/css-loader-pack.py <
"fakewebpack-unpacked/phosphor/styles/base.css.real" >
"fakewebpack-unpacked/phosphor/styles/base.css"
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && m4 -DNODE_PATH=../..
-DCSS_INPUT=./base.css "fakewebpack-helpers/style-loader.js.m4" >
"fakewebpack-unpacked/phosphor/styles/base.css?f74d"
printf "module.exports = $(cat
"fakewebpack-unpacked/jupyter-js-widgets/package.json.real");" >
"fakewebpack-unpacked/jupyter-js-widgets/package.json"
cd "fakewebpack-unpacked/jupyter-js-widgets/" && tsc --moduleResolution Classic
--project src
mkdir -p "fakewebpack-unpacked/jupyter-js-widgets/css/"
cd ../jupyter-js-widgets/css && cat widgets.css | \
sed -e '/@import ".\/labvariables.css"/{r ./labvariables.css'"${NLD}"'}' \
-e '/@import ".\/widgets-base.css"/{r ./widgets-base.css'"${NLD}"'}' | \
sed -e '/@import ".\/materialcolors.css"/{r ./materialcolors.css'"${NLD}"'}' >
/<>/debian/"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css.real"
mkdir -p "fakewebpack-unpacked/jupyter-js-widgets/css/" && NODE_PATH=../..
fakewebpack-helpers/css-loader-pack.py <
"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css.real" >
"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css"
mkdir -p "fakewebpack-unpacked/jupyter-js-widgets/css/" && m4 -DNODE_PATH=../..
-DCSS_INPUT=./widgets.css "fakewebpack-helpers/style-loader.js.m4" >
"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css?7dc3"
mkdir -p "fakewebpack-unpacked/widgetsnbextension/webpack/ ./" && m4
-DWEBPACK_PUBLIC_PATH= "fakewebpack-helpers/webpack-bootstrap.js.m4" >
"fakewebpack-unpacked/widgetsnbextension/webpack/bootstrap e65abc6196a7e23c9fcf"
mkdir -p "fakewebpack-unpacked/widgetsnbextension/css/" &&
NODE_PATH=../node_modules fakewebpack-helpers/css-loader-pack.py <
"fakewebpack-unpacked/widgetsnbextension/css/outputarea.css.real" >
"fakewebpack-unpacked/widgetsnbextension/css/outputarea.css"
mkdir -p "fakewebpack-unpacked/widgetsnbextension/css/" && m4
-DNODE_PATH=../node_modules -DCSS_INPUT=./outputarea.css
"fakewebpack-helpers/style-loader.js.m4" >
"fakewebpack-unpacked/widgetsnbextension/css/outputarea.css?73c5"
printf "module.exports = $(cat
"fakewebpack-unpacked/widgetsnbextension/package.json.real");" >
"fakewebpack-unpacked/widgetsnbextension/package.json"
mkdir -p fakewebpack
touch "fakewebpack/prep.stamp"
make[3]: Leaving directory '/<>/debian'
touch fakewebpack/widgetsnbextension-unpacked.stamp
rm -rf "fakewebpack/widgetsnbextension" && mkdir -p
"fakewebpack/widgetsnbextension" && ./fakewebpack-generate.py
fakewebpack-meta/widgetsnbextension.files
Bug#928097: chromium: crc32 build errors on arm64
package: src:chromium severity: serious version: 74.0.3729.108-1 The latest upload fails to build on arm64 due to errors in crc32 [0]. Best wishes, Mike [0]https://buildd.debian.org/status/fetch.php?pkg=chromium=arm64=74.0.3729.108-1=1556085401=0
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 927913 serious Bug #927913 [chromium] Second chromium kills the first one, and we see "Restore pages?" Bug #927997 [chromium] Opening a link from a mail client restarts chromium Bug #928089 [chromium] chromium: crash when opening a new instance Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 927913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927913 927997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927997 928089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920408: marked as done (gsearchtool: flawed msgstr in help/pt.po)
Your message dated Sat, 27 Apr 2019 22:04:19 + with message-id and subject line Bug#920408: fixed in mate-utils 1.20.2-3 has caused the Debian Bug report #920408, regarding gsearchtool: flawed msgstr in help/pt.po 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.) -- 920408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mate-utils Version: 1.20.2-2 Severity: important Dear Maintainer, mate-utils has a hard dependency on mate-utils-common (>= 1.20.2-2), but it has not been uploaded, breaking upgrades. The latest version of mate-utils-common is 1.20.2-1 as indicated below. I have checked in Incoming, and it is not there either. Please fix. Thanks, Lars -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-utils depends on: ii libatk1.0-0 2.30.0-2 ii libc6 2.28-5 ii libcairo-gobject2 1.16.0-2 ii libcairo2 1.16.0-2 ii libcanberra-gtk3-00.30-7 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-02.38.0+dfsg-7 ii libglib2.0-0 2.58.2-4 ii libgtk-3-03.24.3-1 ii libgtop-2.0-112.38.0-4 ii libice6 2:1.0.9-2 ii libmate-panel-applet-4-1 1.20.4-2 ii libmatedict6 1.20.2-2 ii libpango-1.0-01.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libsm62:1.2.2-1+b3 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii mate-desktop-common 1.20.4-2 ii mate-utils-common 1.20.2-1 ii zlib1g1:1.2.11.dfsg-1 mate-utils recommends no packages. mate-utils suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: mate-utils Source-Version: 1.20.2-3 We believe that the bug you reported is fixed in the latest version of mate-utils, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated mate-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Apr 2019 22:06:22 +0200 Source: mate-utils Architecture: source Version: 1.20.2-3 Distribution: unstable Urgency: medium Maintainer: Debian+Ubuntu MATE Packaging Team Changed-By: Mike Gabriel Closes: 920408 922734 Changes: mate-utils (1.20.2-3) unstable; urgency=medium . * debian/patches: + Add 1001_fix-gsearchtool-pt-help-translation.patch. Fix FTBFS caused by itstool. (Closes: #920408, #922734). Checksums-Sha1: f2e34e479f3587160ed327bffc73cd9020f87e39 2599 mate-utils_1.20.2-3.dsc 9b40a737eb1b3343023acc86b112f7b978cf2a99 9812 mate-utils_1.20.2-3.debian.tar.xz 9bce637bcc257fd158d051fb6241373f8f2f5851 16361 mate-utils_1.20.2-3_source.buildinfo Checksums-Sha256: 079e10207add9f162cae5647d6c91b47b9c1580e0a4fabcf404a89d48d562e90 2599 mate-utils_1.20.2-3.dsc 64a79afd4fd8613b0c621d46b6f45345138912fdba59610e51be27235d6cca3e 9812 mate-utils_1.20.2-3.debian.tar.xz 5b2b7059c688736ff88b690d48e1c1c01f5dd0b42a10cf5dce398cfc4487d079 16361 mate-utils_1.20.2-3_source.buildinfo Files: 9739f64df91ca5ca8d8ea8d2714c0e67 2599 x11 optional mate-utils_1.20.2-3.dsc 5e1f5d1066e013dcb5bf0287ec35ad7a 9812 x11 optional mate-utils_1.20.2-3.debian.tar.xz c96bf739ad28f8193c8ee6c221d37821 16361 x11 optional mate-utils_1.20.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlzEzXAVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxoo4QAJQWIv8UbqfFns4KlskjADFeQWnf ujXts+aUmud+wtaiC7HDrGRVl6j3BZLVSA2B2OVvla4F4NTYV25a2QnbbyPua53Y Xo8haHoFa3IF28kjPHyM5rYnrBeWXFS2Jt7Gj1/Bg3bEGxMrT0UHcoD4aNRUdBnA
Bug#927906: marked as done (CVE-2019-8354 CVE-2019-8355 CVE-2019-8356 CVE-2019-8357)
Your message dated Sat, 27 Apr 2019 22:04:51 + with message-id and subject line Bug#927906: fixed in sox 14.4.2+git20190427-1 has caused the Debian Bug report #927906, regarding CVE-2019-8354 CVE-2019-8355 CVE-2019-8356 CVE-2019-8357 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.) -- 927906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sox Severity: grave Tags: security Please see these links for descriptions and patches: https://security-tracker.debian.org/tracker/CVE-2019-8354 https://security-tracker.debian.org/tracker/CVE-2019-8355 https://security-tracker.debian.org/tracker/CVE-2019-8356 https://security-tracker.debian.org/tracker/CVE-2019-8357 Cheers, Moritz --- End Message --- --- Begin Message --- Source: sox Source-Version: 14.4.2+git20190427-1 We believe that the bug you reported is fixed in the latest version of sox, 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 927...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tiago Bortoletto Vaz (supplier of updated sox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Apr 2019 15:57:59 -0400 Source: sox Binary: libsox-dev libsox-fmt-all libsox-fmt-alsa libsox-fmt-alsa-dbgsym libsox-fmt-ao libsox-fmt-ao-dbgsym libsox-fmt-base libsox-fmt-base-dbgsym libsox-fmt-mp3 libsox-fmt-mp3-dbgsym libsox-fmt-oss libsox-fmt-oss-dbgsym libsox-fmt-pulse libsox-fmt-pulse-dbgsym libsox3 libsox3-dbgsym sox sox-dbgsym Architecture: source amd64 Version: 14.4.2+git20190427-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Tiago Bortoletto Vaz Description: libsox-dev - Development files for the SoX library libsox-fmt-all - All SoX format libraries libsox-fmt-alsa - SoX alsa format I/O library libsox-fmt-ao - SoX Libao format I/O library libsox-fmt-base - Minimal set of SoX format libraries libsox-fmt-mp3 - SoX MP2 and MP3 format library libsox-fmt-oss - SoX OSS format I/O library libsox-fmt-pulse - SoX PulseAudio format I/O library libsox3- SoX library of audio effects and processing sox- Swiss army knife of sound processing Closes: 927906 Changes: sox (14.4.2+git20190427-1) unstable; urgency=medium . * Add patches to fix CVE-2019-8354, CVE-2019-8355, CVE-2019-8356 and CVE-2019-8357. Thanks to Moritz Muehlenhoff. (Closes: #927906) Checksums-Sha1: 3cc439c792a6bf0ec10b0d4d120ab52fe6703144 2783 sox_14.4.2+git20190427-1.dsc dc9668256b9d81ef25d672f14f12ec026b0b4087 935449 sox_14.4.2+git20190427.orig.tar.bz2 1a9a7643deef699977b45e7f69ac0a175837e8f4 24020 sox_14.4.2+git20190427-1.debian.tar.xz 44e2c0e8ae3f725dbfd4162a24cc186722c1d9ce 365400 libsox-dev_14.4.2+git20190427-1_amd64.deb 81ddedd97f57244e6d6663b7a82b7edcc574bdde 45836 libsox-fmt-all_14.4.2+git20190427-1_amd64.deb d2a668c2fdd58f416097d9b8c2771e6b9534f45c 15712 libsox-fmt-alsa-dbgsym_14.4.2+git20190427-1_amd64.deb 57d9f787a0cb4df0c77a8edde7c06608ded46740 51236 libsox-fmt-alsa_14.4.2+git20190427-1_amd64.deb 76c79fa60640121ec3c849ccf2588c36b702178a 7688 libsox-fmt-ao-dbgsym_14.4.2+git20190427-1_amd64.deb e648728f789b2b2d4f494d25a5ee2dc37fdf32db 48148 libsox-fmt-ao_14.4.2+git20190427-1_amd64.deb 2403390e8714273738b87090606647ae65450660 169916 libsox-fmt-base-dbgsym_14.4.2+git20190427-1_amd64.deb d98a7f27aa5a15aa55edaedcece5cf26c337ee6b 72112 libsox-fmt-base_14.4.2+git20190427-1_amd64.deb 2ad6302491b6d55b37e77148af1407c98832433d 27008 libsox-fmt-mp3-dbgsym_14.4.2+git20190427-1_amd64.deb 495533cc893a1bb8c22808327bc74be487223707 56688 libsox-fmt-mp3_14.4.2+git20190427-1_amd64.deb 7ac585773bca8fa844b2d91b24f650341034c3a3 10368 libsox-fmt-oss-dbgsym_14.4.2+git20190427-1_amd64.deb 2d46f54263e720aad73261747ead49b70dc8cb8e 49712 libsox-fmt-oss_14.4.2+git20190427-1_amd64.deb e6156b9b3e752067af929e5d82276e2e4bd30d98 7852 libsox-fmt-pulse-dbgsym_14.4.2+git20190427-1_amd64.deb 300c3aed344c1d77e965a76390ec8ec30a1829f0 48024 libsox-fmt-pulse_14.4.2+git20190427-1_amd64.deb 7e9698e4635d2e1b71174ab3846edc84acf2933e 587956
Bug#927862: youtube-dl: please update to 2019.04.24
Control: block -1 by 928092 Control: user debian-rele...@lists.debian.org Control: usertags 928092 + bsp-2019-04-ca-toronto Control: usertags -1 + bsp-2019-04-ca-toronto On 2019-04-27 20:50:11, Salvatore Bonaccorso wrote: > Control: tags -1 + patch > > Hi > > I have pushed a change cherry-picking the upstream change to adress > this issue in > https://salsa.debian.org/debian/youtube-dl/commit/ab926e5dbeca04924d1628992210084e67368d25 > . > > Rogério, fine with doing an NMU or do you want to go ahead with a > maintainer upload? I think the additional commit done in the packaging > repo should be as well fine as it is documentation update on how to > import new versions. I have pushed the above commit in a separate branch called "buster" in the repository so that we can get approval from the RT without the superfluous docs changes. I have opened an unblock request for this in #928092 and will upload the fix as it stands in salsa once it's approved. The debdiff lives in that unblock request as well. I leave the broader question of what to do with youtube-dl in stretch, jessie and, in general, in the long term as an exercise to the reader. :) A. -- May your trails be crooked, winding, lonesome, dangerous, leading to the most amazing view. May your mountains rise into and above the clouds. - Edward Abbey
Processed (with 3 errors): Re: Bug#927862: youtube-dl: please update to 2019.04.24
Processing control commands: > block -1 by 928092 Bug #927862 [youtube-dl] youtube-dl: needs upstream version update to continue working Bug #928001 [youtube-dl] youtube-dl: Fails to download videos from youtube 927862 was not blocked by any bugs. 927862 was not blocking any bugs. Added blocking bug(s) of 927862: 928092 928001 was not blocked by any bugs. 928001 was not blocking any bugs. Added blocking bug(s) of 928001: 928092 > user debian-rele...@lists.debian.org Unknown command or malformed arguments to command. > usertags 928092 + bsp-2019-04-ca-toronto Unknown command or malformed arguments to command. > usertags -1 + bsp-2019-04-ca-toronto Unknown command or malformed arguments to command. -- 927862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927862 928001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923438:
I'm also hitting this issue on Debian Buster/Testing, after installing the Tinc package from experimental. I'd like to use Tinc 1.1, but had to downgrade to the Tinc 1.0 package in Buster for it to work properly.
Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)
On Saturday, April 27 2019, Ximin Luo wrote: > Sergio Durigan Junior: >> Control: block -1 by 928090 >> On Saturday, April 27 2019, Ximin Luo wrote: >> >>> Awesome, thanks! I was just getting around to this today. Do you want to do >>> the NMU or shall I upload -4 as the "official maintainer"? >> >> Heya, thanks for the quick reply :-). >> >> I was actually going to write saying that I'm part of the Debian Python >> group, so I can just make a team upload. But I've created the unblock >> bug with release.debian.org (#928090), so let's just wait on their >> reply. Meanwhile, I'll push the changes to the git repo. >> > > We have to do an upload *as well as* unblock request, and we don't > need to wait for the release team to do that. So we should do it ASAP > when we're confident the bug is actually fixed, to avoid latency due > to the asynchronity between teams here. Ah, fair enough, thanks for clarifying. > (The point of the unblock is to unblock *the package already in unstable* to > be able to migrate to testing.) > > As a team member you are free to take the -4 version, just put "Team upload" > instead of "Non-maintainer upload" at the top line of your changelog, or use > "dch --team" instead of "dch --nmu". Yep, this is what I already did. > OK, I think I'll let you take care of the whole process :) Let me know if you > need anything else. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)
Sergio Durigan Junior: > Control: block -1 by 928090 > On Saturday, April 27 2019, Ximin Luo wrote: > >> Awesome, thanks! I was just getting around to this today. Do you want to do >> the NMU or shall I upload -4 as the "official maintainer"? > > Heya, thanks for the quick reply :-). > > I was actually going to write saying that I'm part of the Debian Python > group, so I can just make a team upload. But I've created the unblock > bug with release.debian.org (#928090), so let's just wait on their > reply. Meanwhile, I'll push the changes to the git repo. > We have to do an upload *as well as* unblock request, and we don't need to wait for the release team to do that. So we should do it ASAP when we're confident the bug is actually fixed, to avoid latency due to the asynchronity between teams here. (The point of the unblock is to unblock *the package already in unstable* to be able to migrate to testing.) As a team member you are free to take the -4 version, just put "Team upload" instead of "Non-maintainer upload" at the top line of your changelog, or use "dch --team" instead of "dch --nmu". OK, I think I'll let you take care of the whole process :) Let me know if you need anything else. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#926802: Bug #926802 in ipywidgets marked as pending
Control: tag -1 pending Hello, Bug #926802 in ipywidgets 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/ipywidgets/commit/5652fd28b0ab3526d959a18081b8100871ef594c Use 'Object.prototype' instead of 'path.scope.getBindings' when calling 'hasOwnProperty'. Closes: #926802 (this message was generated automatically) -- Greetings https://bugs.debian.org/926802
Processed: Re: Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)
Processing control commands: > block -1 by 928090 Bug #926802 [src:ipywidgets] ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function) 926802 was not blocked by any bugs. 926802 was not blocking any bugs. Added blocking bug(s) of 926802: 928090 -- 926802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #926802 in ipywidgets marked as pending
Processing control commands: > tag -1 pending Bug #926802 [src:ipywidgets] ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function) Added tag(s) pending. -- 926802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)
Control: block -1 by 928090 On Saturday, April 27 2019, Ximin Luo wrote: > Awesome, thanks! I was just getting around to this today. Do you want to do > the NMU or shall I upload -4 as the "official maintainer"? Heya, thanks for the quick reply :-). I was actually going to write saying that I'm part of the Debian Python group, so I can just make a team upload. But I've created the unblock bug with release.debian.org (#928090), so let's just wait on their reply. Meanwhile, I'll push the changes to the git repo. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)
Awesome, thanks! I was just getting around to this today. Do you want to do the NMU or shall I upload -4 as the "official maintainer"? X Sergio Durigan Junior: > tags 926802 + patch > usertags 926802 + bsp-2019-04-ca-toronto > thanks > > On Wednesday, April 10 2019, Santiago Vila wrote: > >> Dear maintainer: >> >> I tried to build this package in buster but it failed: > [...] > > Heya from the Toronto BSP! > > So, I've given it a try and managed to... hm... fix the issue. My > JavaScript knowledge is rudimentary at best, but with the diff below > makes the build complete without any apparent side effects (i.e., the > testsuite still pass). > > Kudos to Samuel Vale for helping verifying the code and making sure it > looks OK. > > I'll open an unblock request soon. > > Thanks, > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#913978: Maybe at least document those keystrokes?
found 913978 1:3.30.3-1 tags 913978 +confirmed thanks -- >From what I could understand, it is unlikely this will be fixed before Buster release. So how should we proceed about his bug? Even if a backport can possibly be provided later, would it be possible to just document the keystrokes "workaround" mentioned by Jeremy Bicha in the package shipped with Buster? It might be a big difference for users in need of this accessibility feature. Thanks, Tassia.
Processed: Maybe at least document those keystrokes?
Processing commands for cont...@bugs.debian.org: > found 913978 1:3.30.3-1 Bug #913978 [gnome-control-center] is not accessible with Orca screenreader Marked as found in versions gnome-control-center/1:3.30.3-1. > tags 913978 +confirmed Bug #913978 [gnome-control-center] is not accessible with Orca screenreader Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 913978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 927913 928089 Bug #927913 [chromium] Second chromium kills the first one, and we see "Restore pages?" Bug #927997 [chromium] Opening a link from a mail client restarts chromium Bug #928089 [chromium] chromium: crash when opening a new instance Severity set to 'important' from 'grave' Added tag(s) confirmed. Bug #927997 [chromium] Opening a link from a mail client restarts chromium Merged 927913 927997 928089 > thanks Stopping processing here. Please contact me if you need assistance. -- 927913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927913 927997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927997 928089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928089: chromium: crash when opening a new instance
Package: chromium Version: 74.0.3729.108-1 Severity: grave Justification: renders average web browser use impossible Hello, On a recent upgrade to Chromium 74.0.3729.108-1, any attempts to open a new instance of the browser (via the app launcher or by clicking an external link) hang for several seconds before crashing the previous Chromium instance and opening a new window. This causes work to be potentially lost. Downgrading to version 73.0.3683.75-1 in testing makes the problem go away. I can reproduce this with two systems, one running the NVIDIA binary driver (version 418.56-2 in unstable) and another running an Intel iGPU. Based on the command line output I've seen, I think the graphics setup might be related? On my NVIDIA system, running chromium from the terminal gives this: $ chromium [17554:17554:0427/125307.938566:ERROR:vaapi_wrapper.cc(335)] vaInitialize failed: unknown libva error Then I tried to install vdpau-va-driver and got this instead: james@intrepid:~$ chromium [13422:13422:0427/124503.122545:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122582:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 0 and entrypoint 1 [13422:13422:0427/124503.122591:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122596:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 1 and entrypoint 1 [13422:13422:0427/124503.122601:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122606:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 2 and entrypoint 1 [13422:13422:0427/124503.122612:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122616:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 3 and entrypoint 1 [13422:13422:0427/124503.122621:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122626:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 5 and entrypoint 1 [13422:13422:0427/124503.122632:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122636:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 6 and entrypoint 1 [13422:13422:0427/124503.122640:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122643:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 7 and entrypoint 1 [13422:13422:0427/124503.122647:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122650:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 8 and entrypoint 1 [13422:13422:0427/124503.122654:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122658:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 9 and entrypoint 1 [13422:13422:0427/124503.122662:ERROR:vaapi_wrapper.cc(684)] vaQuerySurfaceAttributes failed VA error: invalid parameter [13422:13422:0427/124503.122666:ERROR:vaapi_wrapper.cc(574)] GetMaxResolution failed for va_profile 10 and entrypoint 1 [13375:13375:0427/124511.868642:ERROR:http_bridge.cc(127)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived() [13375:13403:0427/124511.949307:ERROR:browser_process_sub_thread.cc(217)] Waited 13 ms for network service On my Intel system I see the following: $ chromium (chromium:17594): Gtk-WARNING **: 13:04:19.122: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version (chromium:17594): Gtk-WARNING **: 13:04:19.122: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version (chromium:17594): Gtk-WARNING **: 13:04:19.122: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version [17638:17638:0427/130419.283245:ERROR:sandbox_linux.cc(368)] InitializeSandbox() called with multiple threads in process gpu-process. [17638:17638:0427/130439.725484:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command Best, James signature.asc Description: OpenPGP digital signature
Processed: reassing back to mate-utils
Processing commands for cont...@bugs.debian.org: > reassign #920408 src:mate-utils Bug #920408 [itstool] its-tools: crashes when freeing xmlDocs Bug reassigned from package 'itstool' to 'src:mate-utils'. No longer marked as found in versions itstool/2.0.4-1. Ignoring request to alter fixed versions of bug #920408 to the same values previously set > retitle #920408 gsearchtool: flawed msgstr in help/pt.po Bug #920408 [src:mate-utils] its-tools: crashes when freeing xmlDocs Changed Bug title to 'gsearchtool: flawed msgstr in help/pt.po' from 'its-tools: crashes when freeing xmlDocs'. > kthxbye Stopping processing here. Please contact me if you need assistance. -- 920408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913978: (no subject)
user debian-rele...@lists.debian.org usertags 913978 + bsp-2019-04-ca-toronto thank you
Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)
tags 926802 + patch
usertags 926802 + bsp-2019-04-ca-toronto
thanks
On Wednesday, April 10 2019, Santiago Vila wrote:
> Dear maintainer:
>
> I tried to build this package in buster but it failed:
[...]
Heya from the Toronto BSP!
So, I've given it a try and managed to... hm... fix the issue. My
JavaScript knowledge is rudimentary at best, but with the diff below
makes the build complete without any apparent side effects (i.e., the
testsuite still pass).
Kudos to Samuel Vale for helping verifying the code and making sure it
looks OK.
I'll open an unblock request soon.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
diff --git a/debian/changelog b/debian/changelog
index e19e631..166519b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ipywidgets (6.0.0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use 'Object.prototype' instead of 'path.scope.getBindings' when
+calling 'hasOwnProperty'. (Closes: #926802)
+
+ -- Sergio Durigan Junior Sat, 27 Apr 2019 14:47:09
-0400
+
ipywidgets (6.0.0-3) unstable; urgency=medium
[ Ondřej Nový ]
diff --git a/debian/fakewebpack-postprocess.js
b/debian/fakewebpack-postprocess.js
index e7f7dbc..8126eef 100755
--- a/debian/fakewebpack-postprocess.js
+++ b/debian/fakewebpack-postprocess.js
@@ -127,7 +127,7 @@ var transform = function transform(ast, fn, moduleList) {
&& injectGlobalsReplace.hasOwnProperty(path.node.name)
&& (parent.type !== 'MemberExpression' || parent.object ===
path.node)
&& (parent.type !== 'Property' || parent.value === path.node)) {
-if (!path.scope.getBindings().hasOwnProperty(path.node.name)) {
+if
(!Object.prototype.hasOwnProperty.call(path.scope.getBindings(),
path.node.name)) {
injectGlobals.push(path.node.name);
}
}
signature.asc
Description: PGP signature
Processed: Re: Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)
Processing commands for cont...@bugs.debian.org: > tags 926802 + patch Bug #926802 [src:ipywidgets] ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function) Added tag(s) patch. > usertags 926802 + bsp-2019-04-ca-toronto User is sergi...@debian.org There were no usertags set. Usertags are now: bsp-2019-04-ca-toronto. > thanks Stopping processing here. Please contact me if you need assistance. -- 926802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928084: marked as done ([src:wine-development] wineserver doens't work when /run/user/pid is not available)
Your message dated Sat, 27 Apr 2019 19:33:46 +
with message-id
and subject line Bug#928084: fixed in wine 4.0-2
has caused the Debian Bug report #928084,
regarding [src:wine-development] wineserver doens't work when /run/user/pid is
not available
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.)
--
928084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wine-development
Version: 4.2-2
wineserver fails to setup it's directory when /run/user/${pid} is not
available due to buggy patch.
please fix debian/patches/fixes/temporary-directory.patch:
line 65:
-+tmp_dir = xmalloc( sizeof(tmp_env) );
++tmp_dir = xmalloc( strlen(tmp_env) + 1 );
line 110:
-+n = fputs( root + sizeof(tmp_dir) + 1, stream );
++n = fputs( root + strlen(tmp_dir) + 1, stream );
bug is caused by copy-paste mistake, because tmp_env and tmp_dir are
type of "char *", not "char []", therefore sizeof() isn't equal to
strlen() + 1.
--
SY,
Konstantin Demin
--- End Message ---
--- Begin Message ---
Source: wine
Source-Version: 4.0-2
We believe that the bug you reported is fixed in the latest version of
wine, 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 928...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jens Reyer (supplier of updated wine 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: Sat, 27 Apr 2019 20:20:01 +0200
Source: wine
Architecture: source
Version: 4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party
Changed-By: Jens Reyer
Closes: 928013 928084
Changes:
wine (4.0-2) unstable; urgency=medium
.
* Point to branch buster in the Vcs fields.
* Support building with unicode-data 12.
Build against new unicode-data supporting the new Japanese era
"令和 (Reiwa)" (closes: #928013).
* Fix incorrect uses of sizeof in temporary-directory.patch (closes:
#928084).
Thanks to Konstantin Demin.
Checksums-Sha1:
b4319008357bfba8e091157475246eb735cad45b 3880 wine_4.0-2.dsc
8444a4509823de0def5363ade0061b617d269eca 192944 wine_4.0-2.debian.tar.xz
610793dc21c1f41d6af89b2f42e5c119ebd15c67 18875 wine_4.0-2_all.buildinfo
Checksums-Sha256:
55bd6c5c923cfa53968894dc39ab97f27f5a5e7f7691c2057407b06e619b51af 3880
wine_4.0-2.dsc
cfc864c750a13a13dc67c02e082b3d233f822a9a100fd60253c7d71af32d4539 192944
wine_4.0-2.debian.tar.xz
d5731c53a29e88c06e639f2ed15f9d8a4e70effdd8ff64c85bfdd798861c12a9 18875
wine_4.0-2_all.buildinfo
Files:
a70dd160d3c0e68f8c277d47eb059b04 3880 otherosfs optional wine_4.0-2.dsc
099a03c29cdf9ab7ba65e4faaef51145 192944 otherosfs optional
wine_4.0-2.debian.tar.xz
942a59dbaf20b3476aa02c0e1d77995d 18875 otherosfs optional
wine_4.0-2_all.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEo+4EaAPA6D5jhqo9YIQSAytXMHYFAlzEp5sACgkQYIQSAytX
MHbaeg//VYZpnya/Y1DBoteOviFIEg7/z4/vXJNYs5rL4f9ZDmaITHUvdZxtR8iZ
r19sru+TFKVIRWB3aKQ3Ps9dGGnpCMmz92rVpem2HpxGjxSeEi59LXkfIRUwaf0J
h60V8V1U3t6UxX1/OlOfFnjOFWz0apjM0zorL9pi2eOxBbrUAsE8ZVt2wM2AAJGW
snkPenMNmZpc0vAxAklTM/1+wOv3fzJax++sUxpENTuZfXzAEJH84F6vE4c/w4k2
FDajEjjl3CbbLRtkLsHr5BmGdMFfATS6UntOu1xZfrOKS8v/2xWljaMQI788BRsF
txYgSqMsbHxgOPPZZdKojrEalW3UigY92yoDRWlP3qxOz2mik8BrkzRPHyYuc3fX
ygRDmt/kWAaimTX2TKGXaBvIIxK/gvb0Ji0ONjhehMm+kYYC/fWSYna24mvIu0s1
ZTILu/eLYVRBJ8UeB5Akr+CCdqYRNdYUyXg6N50CXgtzo7eS7P2PWnrJ7fUhKDfM
HfnGk4lhvpFTkiYVw2YuA+U3ndaaGTSDL+Es/fMHNZxwzKt6T0fBYt8g+BO5Fv0e
K0rhJJad5N5N3MoKZvTA+cHjy4QsSEGoO1ObR4hpnL9k/mRVLMLyqYyo4BKsXRoI
9s56MU7Q0b4hSsKvCgudFpaMkHjGdxVYAJVEnnqPNqKzTAap+nI=
=sUgx
-END PGP SIGNATURE End Message ---
Processed: unmerge #920408
Processing commands for cont...@bugs.debian.org: > unmerge #920408 Bug #920408 [itstool] its-tools: crashes when freeing xmlDocs Bug #919058 [itstool] its-tools: crashes when freeing xmlDocs Disconnected #920408 from all other report(s). > kthxbye Stopping processing here. Please contact me if you need assistance. -- 919058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919058 920408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 4 errors): clone #919058
Processing commands for cont...@bugs.debian.org:
> clone #919058 -1
Bug #919058 [itstool] its-tools: crashes when freeing xmlDocs
Bug #920408 [itstool] its-tools: crashes when freeing xmlDocs
Failed to clone 919058: Bug is marked as being merged with others. Use an
existing clone.
> reassign -1 src:mate-utils
Failed to clear fixed versions and reopen on -1: The 'bug' parameter ("-1") to
Debbugs::Control::set_package did not pass regex check
.
> retitle -1 gsearchtool: flawed msgstr in help/pt.po
Failed to set the title of -1: The 'bug' parameter ("-1") to
Debbugs::Control::set_title did not pass regex check
.
> severity -1 grave
Failed to set severity of Bug -1 to grave: The 'bug' parameter ("-1") to
Debbugs::Control::set_severity did not pass regex check
.
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
--
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#927862: youtube-dl: please update to 2019.04.24
Processing control commands: > tags -1 + patch Bug #927862 [youtube-dl] youtube-dl: needs upstream version update to continue working Bug #928001 [youtube-dl] youtube-dl: Fails to download videos from youtube Added tag(s) patch. Added tag(s) patch. -- 927862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927862 928001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927862: youtube-dl: please update to 2019.04.24
Control: tags -1 + patch Hi I have pushed a change cherry-picking the upstream change to adress this issue in https://salsa.debian.org/debian/youtube-dl/commit/ab926e5dbeca04924d1628992210084e67368d25 . Rogério, fine with doing an NMU or do you want to go ahead with a maintainer upload? I think the additional commit done in the packaging repo should be as well fine as it is documentation update on how to import new versions. Regards, Salvatore
Bug#927057: marked as done (1Gb of logs is too much)
Your message dated Sat, 27 Apr 2019 18:18:51 + with message-id and subject line Bug#927057: fixed in matrix-synapse 0.99.2-4 has caused the Debian Bug report #927057, regarding 1Gb of logs is too much 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.) -- 927057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: matrix-synapse Version: 0.99.2-3 Severity: serious Justification: Policy 10.8 Dear Maintainer, https://www.debian.org/doc/debian-policy/ch-files.html Log files must be rotated occasionally so that they don’t grow indefinitely. The best way to do this is to install a log rotation configuration file in the directory /etc/logrotate.d, normally named /etc/logrotate.d/package, and use the facilities provided by logrotate. % l /var/log/matrix-synapse total 322M -rw-r- 1 matrix-synapse nogroup 22M 2019-04-14 15:10 homeserver.log -rw-r- 1 matrix-synapse nogroup 100M 2019-04-14 11:43 homeserver.log.1 -rw-r- 1 matrix-synapse nogroup 100M 2019-04-13 18:41 homeserver.log.2 -rw-r- 1 matrix-synapse nogroup 100M 2019-04-13 14:53 homeserver.log.3 % l /etc/logrotate.d/matrix-synapse ls: cannot access '/etc/logrotate.d/matrix-synapse': No such file or directory -- sergio. --- End Message --- --- Begin Message --- Source: matrix-synapse Source-Version: 0.99.2-4 We believe that the bug you reported is fixed in the latest version of matrix-synapse, 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 927...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated matrix-synapse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Apr 2019 20:03:23 +0200 Source: matrix-synapse Architecture: source Version: 0.99.2-4 Distribution: unstable Urgency: medium Maintainer: Matrix Packaging Team Changed-By: Andrej Shadura Closes: 927057 Changes: matrix-synapse (0.99.2-4) unstable; urgency=medium . [ Antoine Beaupré ] * Fix log rotation to be less verbose (Closes: #927057). Checksums-Sha1: e017ba16257553286797adc5d7d007e7459cae2d 2521 matrix-synapse_0.99.2-4.dsc fa57dfa9c8f5359e083f5c8de756231815307b32 89576 matrix-synapse_0.99.2-4.debian.tar.xz Checksums-Sha256: b4749a6da7371f80fbbd50f44a27632a07f11b641354ac0c45ffa15485ec6dde 2521 matrix-synapse_0.99.2-4.dsc 732f4d813323c701e4ee0f5b6336e3d338d81c2e43f05d509d44a13f7c514a34 89576 matrix-synapse_0.99.2-4.debian.tar.xz Files: 9886ef9f72c4c9d872f7e0efc3a8f474 2521 net optional matrix-synapse_0.99.2-4.dsc 78a735ea90ca4f132dd894fa65625a26 89576 net optional matrix-synapse_0.99.2-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlzEmb4ACgkQXkCM2RzY OdKwrgf8Cz82D0P6e7U4L5bMjb2u8Nylt8DAuLrnoIeqNxeHH7Px0/yEucMsMKE2 a9Ry7POXRTTaPPzOhFKGi9qsjhqNaIHT9dbSMpGVdgbRf7pSnv81l6gIKzG/ovVg 3nU7grKRAHemvRuJrLF1ZwDaLV3VYKxWtuat31OrnMF+2/6l8TYNuwCkQQei7CAK hOsqjoF+5UvuroQ5g3ucqTZJfTOcemZHNsMOwl6jPp11zyuw4wKnx0Cofe41t8mM BQpF/i7QyJu33vpDGMQ13Q6aY5Kh1IqDp99maI4yNbNj8dNe6sxtQ/LSyQIsjNBu rW22nazZmL217CbR0D8cbpZenDc97g== =LxKZ -END PGP SIGNATURE End Message ---
Processed: Re: Processed: Clone 927139: [src:wine-development] wineserver doens't work when /run/user/pid is not available
Processing commands for cont...@bugs.debian.org:
> reopen 928084
Bug #928084 {Done: Michael Gilbert } [wine]
[src:wine-development] wineserver doens't work when /run/user/pid is not
available
Bug reopened
Ignoring request to alter fixed versions of bug #928084 to the same values
previously set
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
928084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 927862 in 2017.05.18.1-1
Processing commands for cont...@bugs.debian.org: > found 927862 2017.05.18.1-1 Bug #927862 [youtube-dl] youtube-dl: needs upstream version update to continue working Bug #928001 [youtube-dl] youtube-dl: Fails to download videos from youtube Marked as found in versions youtube-dl/2017.05.18.1-1. Marked as found in versions youtube-dl/2017.05.18.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 927862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927862 928001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Clone 927139: [src:wine-development] wineserver doens't work when /run/user/pid is not available
Processing commands for cont...@bugs.debian.org:
> # 927139: [src:wine-development] wineserver doens't work when
> # /run/user/pid is not available is also in src:wine
> clone 927139 -1
Bug #927139 {Done: Michael Gilbert }
[src:wine-development] [src:wine-development] wineserver doens't work when
/run/user/pid is not available
Bug 927139 cloned as bug 928084
> reassign -1 wine 4.0-1
Bug #928084 {Done: Michael Gilbert }
[src:wine-development] [src:wine-development] wineserver doens't work when
/run/user/pid is not available
Bug reassigned from package 'src:wine-development' to 'wine'.
No longer marked as found in versions wine-development/4.2-2.
No longer marked as fixed in versions wine-development/4.2-3.
Bug #928084 {Done: Michael Gilbert } [wine]
[src:wine-development] wineserver doens't work when /run/user/pid is not
available
Marked as found in versions wine/4.0-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
927139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927139
928084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#927057: Fwd:
I have originally sent this, but due to broken HTML markup (thanks, gmail!) it didn’t get processed or posted to the bug report. I still do not consider this a very serious issue, but since fixes have appeared, I will upload them. Thanks. -- Forwarded message - From: Andrej Shadura Date: Tue, 23 Apr 2019 at 06:52 Subject: To: severity 927057 important thanks I don't think this deserves serious. It's up to the admin to configure the logging. The defaults could be better, sure. -- Cheers, Andrej -- Cheers, Andrej
Bug#918826: marked as done (python-pyknon: FTBFS with Sphinx 1.8: No module named pngmath)
Your message dated Sat, 27 Apr 2019 17:33:46 + with message-id and subject line Bug#918826: fixed in python-pyknon 1.0-2 has caused the Debian Bug report #918826, regarding python-pyknon: FTBFS with Sphinx 1.8: No module named pngmath 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.) -- 918826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pyknon Version: 1.0-1 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.8 Dear Maintainer, python-pyknon fails to build with Sphinx 1.8, currently available in experimental: cd docs && make html make[2]: Entering directory '/<>/docs' sphinx-build -b html -d _build/doctrees . _build/html Running Sphinx v1.8.3 Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath) make[2]: *** [Makefile:39: html] Error 2 The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1] in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which also has SVG support in addition to PNG. To me it looks like this extension is unused anyway: there are no “.. math::” directives or “:math:” roles, and the binary package does not have any generated PNG images. So this extension can be simply removed from extensions in conf.py. [1]: https://github.com/sphinx-doc/sphinx/pull/4702 [2]: https://www.sphinx-doc.org/en/1.8/usage/extensions/math.html -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: python-pyknon Source-Version: 1.0-2 We believe that the bug you reported is fixed in the latest version of python-pyknon, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tiago Bortoletto Vaz (supplier of updated python-pyknon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Apr 2019 11:36:55 -0400 Source: python-pyknon Binary: python-pyknon Architecture: source amd64 Version: 1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Tiago Bortoletto Vaz Description: python-pyknon - Simple Python music library Closes: 918826 Changes: python-pyknon (1.0-2) unstable; urgency=medium . * Minor updates in control file. * Remove deprecated pngmath dependency for Sphinx docs building. Thanks to Dmitry Shachnev. (Closes: #918826) Checksums-Sha1: 1b61290196182d2dce2274e3dc8cce6be007f713 2006 python-pyknon_1.0-2.dsc ca7384823cc6bb6bcd19a82f4f4352199ec580f1 2728 python-pyknon_1.0-2.debian.tar.xz e4f3352fbf479af7c837472693e99a97f5f74047 7194 python-pyknon_1.0-2_amd64.buildinfo 101bac120a826d04e1ca14ecd0d341fb77a1f46e 129548 python-pyknon_1.0-2_amd64.deb Checksums-Sha256: 6309671925a7a98131d4d37670a31269b3989dbe76543c589f0c377ad7519e8b 2006 python-pyknon_1.0-2.dsc 475d6d58602e4c2b6a466e00ac2e624d317547a8cf4dfd78a805cd44fe995745 2728 python-pyknon_1.0-2.debian.tar.xz 265f27961b1518c9f8e544d68758c57557948b92eaa4bc2d2b43f94b9b6e9f42 7194 python-pyknon_1.0-2_amd64.buildinfo c572a27aeb20e56312af0c76af66aa837e353deb21b7672c7b044884f576fac4 129548 python-pyknon_1.0-2_amd64.deb Files: 2779b693ef460d71709f5f85923962da 2006 python optional python-pyknon_1.0-2.dsc 3077969f620d1e00d951a7c97531f90e 2728 python optional python-pyknon_1.0-2.debian.tar.xz 5ac2227871d2a6dc79de713e968eebe7 7194 python optional python-pyknon_1.0-2_amd64.buildinfo a8582332f29c42d8354c3bd14e78011c 129548 python optional python-pyknon_1.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYsAXsSqWkZu7etRd2EdHrOS2gT0FAlzEg58ACgkQ2EdHrOS2 gT0RKw/6A2HG6+YbUffD3vNm8HHhgOIlZDa8oLNKuFjHUY8FX3HiWNAXfbtJG8Bi nqg9mEZwmaryZWo88dpnai4AwKEpxKjyvdsaYddyQQi2eCHKJgmIL1Um7DCtxxxp WvYZVc3OhqAJWJZM+FwsX7fL76x/ES6Hda+4Fw/CiXcDG0J6sM/KkauTMoPbeB1Z LqxriMsmvuwGwVvdoZHnPzmHz7xpZ9zja7XGPzt9v/CkcQ8FxClYD2tvoP1pp4QA MCp/PYXqWCWIqA1pup+BVQcn86dSf5pEOELif92zyxMfjAzjP/99Q6G9sBz7cDoz qzSIs8qpSXBpC/qF5dyRWCzfy5UuowZLljzGtOj/OFE74+/R26cXEr8ZqwfUqShT
Bug#928077: marked as done (mariadb-server-10.3: fails to start. init files don't create directory /run/mysqld)
Your message dated Sat, 27 Apr 2019 18:32:03 +0100
with message-id <1556386323.2690.37.ca...@adam-barratt.org.uk>
and subject line Bug#928077: mariadb-server-10.3: fails to start. init files
don't create directory /run/mysqld
has caused the Debian Bug report #928077,
regarding mariadb-server-10.3: fails to start. init files don't create
directory /run/mysqld
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.)
--
928077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server-10.3
Version: 1:10.3.14-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
in the latest update the pid and socket files have been moved from
/var/run/mysqld to /run/mysqld.
The directory /run/mysqld must be created in the init files:
/etc/init.d/mysql
/var/lib/systemd/system/mariadb*
Those file still create the directory /var/run/mysqld
I have also changed some configuration file to honor the new location of
the pid and socket files:
/etc/mysql/mariadb.conf.d/50-client.cnf
/etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf
/etc/mysql/debian.cnf
Regards,
Michael Farmbauer
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.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 mariadb-server-10.3 depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.71
ii galera-3 25.3.25-2
ii gawk 1:4.2.1+dfsg-1
ii iproute2 4.20.0-2
ii libc6 2.28-8
ii libdbi-perl 1.642-1+b1
ii libgnutls30 3.6.6-2
ii libpam0g 1.3.1-5
ii libstdc++68.3.0-6
ii lsb-base 10.2019031300
ii lsof 4.91+dfsg-1
ii mariadb-client-10.3 1:10.3.14-1
ii mariadb-common1:10.3.14-1
ii mariadb-server-core-10.3 1:10.3.14-1
ii passwd1:4.5-1.1
ii perl 5.28.1-6
ii psmisc23.2-1
ii rsync 3.1.3-6
ii socat 1.7.3.2-2
ii zlib1g1:1.2.11.dfsg-1
Versions of packages mariadb-server-10.3 recommends:
ii libhtml-template-perl 2.97-1
Versions of packages mariadb-server-10.3 suggests:
ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1
ii mailutils [mailx] 1:3.5-3
pn mariadb-test
ii netcat-openbsd 1.195-2
pn tinyca
-- Configuration Files:
/etc/init.d/mysql changed:
set -e
set -u
${DEBIAN_SCRIPT_DEBUG:+ set -v -x}
test -x /usr/sbin/mysqld || exit 0
. /lib/lsb/init-functions
SELF=$(cd $(dirname $0); pwd -P)/$(basename $0)
MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"
ERR_LOGGER="logger -p daemon.err -t /etc/init.d/mysql -i"
if [ -f /etc/default/mysql ]; then
. /etc/default/mysql
fi
if [ -f /etc/default/mariadb ]; then
. /etc/default/mariadb
fi
cd /
umask 077
export HOME=/etc/mysql/
mysqld_get_param() {
/usr/sbin/mysqld --print-defaults \
| tr " " "\n" \
| grep -- "--$1" \
| tail -n 1 \
| cut -d= -f2
}
sanity_checks() {
# check for config file
if [ ! -r /etc/mysql/my.cnf ]; then
log_warning_msg "$0: WARNING: /etc/mysql/my.cnf cannot be read. See
README.Debian.gz"
echo"WARNING: /etc/mysql/my.cnf cannot be read. See
README.Debian.gz" | $ERR_LOGGER
fi
# check for diskspace shortage
datadir=`mysqld_get_param datadir`
if LC_ALL=C BLOCKSIZE= df --portability $datadir/. | tail -n 1 | awk '{ exit
($4>4096) }'; then
log_failure_msg "$0: ERROR: The partition with $datadir is too full!"
echo"ERROR: The partition with $datadir is too full!" |
$ERR_LOGGER
exit 1
fi
}
mysqld_status () {
ping_output=`$MYADMIN ping 2>&1`; ping_alive=$(( ! $? ))
ps_alive=0
pidfile=`mysqld_get_param pid-file`
if [ -f "$pidfile" ] && ps `cat $pidfile` >/dev/null 2>&1; then ps_alive=1; fi
if [ "$1" = "check_alive" -a $ping_alive = 1 ] ||
[ "$1" = "check_dead" -a $ping_alive = 0 -a $ps_alive = 0 ]; then
return 0 # EXIT_SUCCESS
else
if [ "$2" = "warn" ]; then
echo -e "$ps_alive processes alive and '$MYADMIN ping' resulted
in\n$ping_output\n" | $ERR_LOGGER -p daemon.debug
fi
return 1 # EXIT_FAILURE
fi
}
case "${1:-''}" in
Bug#918826: (no subject)
control: user debian-rele...@lists.debian.org control: usertags -1 + bsp-2019-04-ca-toronto control: thanks -- tiago
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
On Sat, Apr 27, 2019 at 09:35:51AM -0700, Sean Whitton wrote: > Hello, > > On Sat 27 Apr 2019 at 11:14AM -04, Antoine Beaupré wrote: > > > ... and it looks like it's a bug / limitation in ghc itself... > > Right, it has been reassigned to ghc. > > > From the Toronto BSP's point of view, this is looking more and more like > > a "well, this means we won't support that hardware for git-annex" kind > > of bug. The "too buggy for shipping in a stable release" kind of bug. > This would mean reassigning it to git-annex, wouldn't it? No, there is nothing specific to git-annex here. It means that likely all Haskell packages are currently miscompiled and won't work on the armel baseline. git-annex is just the most popular of these, so several people running unstable/testing on the armel baseline quickly noticed. The vast majority of users would only run into these miscompilations if it doesn't get fixed before buster is released. > Sean Whitton 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
Processed: control command
Processing commands for cont...@bugs.debian.org: > tags 927471 +moreinfo Bug #927471 [src:curl] curl: Regression that fails to exhaust socket data Added tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 927471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
On 2019-04-27 09:35:51, Sean Whitton wrote: > Hello, > > On Sat 27 Apr 2019 at 11:14AM -04, Antoine Beaupré wrote: > >> ... and it looks like it's a bug / limitation in ghc itself... > > Right, it has been reassigned to ghc. > >> From the Toronto BSP's point of view, this is looking more and more like >> a "well, this means we won't support that hardware for git-annex" kind >> of bug. > > This would mean reassigning it to git-annex, wouldn't it? Possibly yes, but Adrian was on to something with that patch: https://sources.debian.org/src/ghc/8.4.4+dfsg1-2/debian/patches/llvm-arm-unknown-linux-gnueabi.patch/ I'm still trying to figure out what that means. A. -- Men often become what they believe themselves to be. If I believe I cannot do something, it makes me incapable of doing it. But when I believe I can, then I acquire the ability to do it even if I didn't have it in the beginning. - Mahatma Gandhi
Processed: block 927057 with 928081
Processing commands for cont...@bugs.debian.org: > block 927057 with 928081 Bug #927057 [matrix-synapse] 1Gb of logs is too much 927057 was not blocked by any bugs. 927057 was not blocking any bugs. Added blocking bug(s) of 927057: 928081 > thanks Stopping processing here. Please contact me if you need assistance. -- 927057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
Hello, On Sat 27 Apr 2019 at 11:14AM -04, Antoine Beaupré wrote: > ... and it looks like it's a bug / limitation in ghc itself... Right, it has been reassigned to ghc. > From the Toronto BSP's point of view, this is looking more and more like > a "well, this means we won't support that hardware for git-annex" kind > of bug. This would mean reassigning it to git-annex, wouldn't it? -- Sean Whitton signature.asc Description: PGP signature
Bug#927057: 1Gb of logs is too much
Control: blocks -1 by 928081 On 2019-04-27 12:09:19, Antoine Beaupré wrote: > On 2019-04-24 16:23:15, Willem Mulder wrote: >> On Wed, 24 Apr 2019 01:03:35 + Linda Lapinlampi >> wrote: >>> I also agree the logs should be compressed on daily rotation, but it >>> remains unclear to me how one would change this in Synapse without big >>> hacky behaviors. Preferably I'd use logrotate(8) if at all possible. >>> >>> This might be helpful: >>> https://docs.python.org/3/library/logging.handlers.html >>> >>> So maybe change logging.handlers.RotatingFileHandler in debian/log.yaml >>> to WatchFileHandler (use with logrotate(8)) if I've understood >>> correctly. TimedRotatingFileHandler is an alternative to let Python >> manage log >>> rotation by itself, but no logs will be compressed then. >> >> On my personal setup, I have the following changes to log.yaml: > > [...] > > I believe the attached debdiff fixes this problem. I have filed unblock request # for this and submitted this as a MR here as well: https://salsa.debian.org/matrix-team/matrix-synapse/merge_requests/1 I have proposed the update to the release team as well, in the bug that I marked as blocking to this bug. A. -- The ultimate test of your knowledge is your capacity to convey it to another. - Richard Feynman
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
On Sat, Apr 27, 2019 at 12:12:10PM -0400, Antoine Beaupré wrote: > On 2019-04-27 18:30:32, Adrian Bunk wrote: > > On Sat, Apr 27, 2019 at 11:14:33AM -0400, Antoine Beaupré wrote: > >> user debian-rele...@lists.debian.org > >> usertags 915333 + bsp-2019-04-ca-toronto > >> thank you > >> > >> On 2019-04-09 08:46:10, Adrian Bunk wrote: > >> > On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote: > >> >> Hey, > >> >> > >> >> On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote: > >> >> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote: > >> >> > > Hello Everyone, > >> >> > > I own a qnap ts-119pII with a similar cpu. > >> >> > > > >> >> > > See attached file with several debugging attempts. > >> >> > >> >> I took some time and wanted to reproduce and test this issue. > >> >>... > >> > > >> > What are you planning to do after reproducing it? > >> > > >> > Bernhard did debug it back in January, > >> > and I described what line the problem is. > >> > >> ... and it looks like it's a bug / limitation in ghc itself... > >> > >> Has anyone considered forwarding this upstream or looked at whether it's > >> been reported? > > > > Why should a bug in a Debian patch be reported upstream? > > Because I wasn't aware it was a Debian patch? :) I guess not then. > > >> Is this a regression? > >>... > > > > Yes. > > Well crap. > > You mentioned some "line" where the bug was earlier, but i couldn't find > a clear indication of where the bug was in the source... is there > actually a patch for this? See comment #37. 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#927471: More info on curl regression.
control: tags -1 +more-info Hi Guillem, I'm working on this bug as a part of Toronto BSP. https://wiki.debian.org/BSP/2019/04/ca/Toronto Can you give more details on how to reproduce the bug. For example to which tracker rtorrent is connecting. Does this happen with every torrent connection or just some? Is it possible to reproduce the bug by running curl command on the url? Alex.
Processed (with 1 error): More info on curl regression.
Processing control commands: > tags -1 +more-info Unknown tag/s: more-info. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore. Bug #927471 [src:curl] curl: Regression that fails to exhaust socket data Requested to add no tags; doing nothing. -- 927471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
On 2019-04-27 18:30:32, Adrian Bunk wrote: > On Sat, Apr 27, 2019 at 11:14:33AM -0400, Antoine Beaupré wrote: >> user debian-rele...@lists.debian.org >> usertags 915333 + bsp-2019-04-ca-toronto >> thank you >> >> On 2019-04-09 08:46:10, Adrian Bunk wrote: >> > On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote: >> >> Hey, >> >> >> >> On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote: >> >> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote: >> >> > > Hello Everyone, >> >> > > I own a qnap ts-119pII with a similar cpu. >> >> > > >> >> > > See attached file with several debugging attempts. >> >> >> >> I took some time and wanted to reproduce and test this issue. >> >>... >> > >> > What are you planning to do after reproducing it? >> > >> > Bernhard did debug it back in January, >> > and I described what line the problem is. >> >> ... and it looks like it's a bug / limitation in ghc itself... >> >> Has anyone considered forwarding this upstream or looked at whether it's >> been reported? > > Why should a bug in a Debian patch be reported upstream? Because I wasn't aware it was a Debian patch? :) I guess not then. >> Is this a regression? >>... > > Yes. Well crap. You mentioned some "line" where the bug was earlier, but i couldn't find a clear indication of where the bug was in the source... is there actually a patch for this? a. -- Sous un gouvernement qui emprisonne injustement, la place de l’homme juste est aussi en prison. - La désobéissance civile, Henry David Thoreau
Bug#927057: 1Gb of logs is too much
On 2019-04-24 16:23:15, Willem Mulder wrote:
> On Wed, 24 Apr 2019 01:03:35 + Linda Lapinlampi
> wrote:
>> I also agree the logs should be compressed on daily rotation, but it
>> remains unclear to me how one would change this in Synapse without big
>> hacky behaviors. Preferably I'd use logrotate(8) if at all possible.
>>
>> This might be helpful:
>> https://docs.python.org/3/library/logging.handlers.html
>>
>> So maybe change logging.handlers.RotatingFileHandler in debian/log.yaml
>> to WatchFileHandler (use with logrotate(8)) if I've understood
>> correctly. TimedRotatingFileHandler is an alternative to let Python
> manage log
>> rotation by itself, but no logs will be compressed then.
>
> On my personal setup, I have the following changes to log.yaml:
[...]
I believe the attached debdiff fixes this problem.
A.
--
Nothing in life is to be feared, it is only to be understood.
Now is the time to understand more, so that we may fear less.
- Marie Curie
diff -Nru matrix-synapse-0.99.2/debian/changelog matrix-synapse-0.99.2/debian/changelog
--- matrix-synapse-0.99.2/debian/changelog 2019-03-24 09:02:48.0 -0400
+++ matrix-synapse-0.99.2/debian/changelog 2019-04-27 11:48:31.0 -0400
@@ -1,3 +1,10 @@
+matrix-synapse (0.99.2-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * fix log rotation to be less verbose (Closes: #927057)
+
+ -- Antoine Beaupré Sat, 27 Apr 2019 11:48:31 -0400
+
matrix-synapse (0.99.2-3) unstable; urgency=medium
* Make the code querying the location of the key file actually work.
diff -Nru matrix-synapse-0.99.2/debian/log.yaml matrix-synapse-0.99.2/debian/log.yaml
--- matrix-synapse-0.99.2/debian/log.yaml 2019-03-24 09:02:48.0 -0400
+++ matrix-synapse-0.99.2/debian/log.yaml 2019-04-27 11:48:31.0 -0400
@@ -14,12 +14,12 @@
handlers:
file:
-class: logging.handlers.RotatingFileHandler
+class: logging.handlers.WatchedFileHandler
formatter: precise
filename: /var/log/matrix-synapse/homeserver.log
-maxBytes: 104857600
-backupCount: 10
filters: [context]
+level: DEBUG
+encoding: utf8
console:
class: logging.StreamHandler
formatter: precise
@@ -31,12 +31,18 @@
SYSLOG_IDENTIFIER: synapse
loggers:
+twisted:
+level: WARN
+
synapse:
-level: INFO
+level: WARN
synapse.storage.SQL:
level: INFO
+synapse.http.matrixfederationclient:
+level: ERROR
+
root:
level: INFO
handlers: [file, journal]
diff -Nru matrix-synapse-0.99.2/debian/matrix-synapse.logrotate matrix-synapse-0.99.2/debian/matrix-synapse.logrotate
--- matrix-synapse-0.99.2/debian/matrix-synapse.logrotate 1969-12-31 19:00:00.0 -0500
+++ matrix-synapse-0.99.2/debian/matrix-synapse.logrotate 2019-04-27 11:48:31.0 -0400
@@ -0,0 +1,8 @@
+/var/log/matrix-synapse/homeserver.log {
+rotate 7
+daily
+missingok
+notifempty
+delaycompress
+compress
+}
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
On Sat, Apr 27, 2019 at 11:14:33AM -0400, Antoine Beaupré wrote: > user debian-rele...@lists.debian.org > usertags 915333 + bsp-2019-04-ca-toronto > thank you > > On 2019-04-09 08:46:10, Adrian Bunk wrote: > > On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote: > >> Hey, > >> > >> On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote: > >> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote: > >> > > Hello Everyone, > >> > > I own a qnap ts-119pII with a similar cpu. > >> > > > >> > > See attached file with several debugging attempts. > >> > >> I took some time and wanted to reproduce and test this issue. > >>... > > > > What are you planning to do after reproducing it? > > > > Bernhard did debug it back in January, > > and I described what line the problem is. > > ... and it looks like it's a bug / limitation in ghc itself... > > Has anyone considered forwarding this upstream or looked at whether it's > been reported? Why should a bug in a Debian patch be reported upstream? > Is this a regression? >... Yes. 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#928077: mariadb-server-10.3: fails to start. init files don't create directory /run/mysqld
Package: mariadb-server-10.3
Version: 1:10.3.14-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
in the latest update the pid and socket files have been moved from
/var/run/mysqld to /run/mysqld.
The directory /run/mysqld must be created in the init files:
/etc/init.d/mysql
/var/lib/systemd/system/mariadb*
Those file still create the directory /var/run/mysqld
I have also changed some configuration file to honor the new location of
the pid and socket files:
/etc/mysql/mariadb.conf.d/50-client.cnf
/etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf
/etc/mysql/debian.cnf
Regards,
Michael Farmbauer
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.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 mariadb-server-10.3 depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.71
ii galera-3 25.3.25-2
ii gawk 1:4.2.1+dfsg-1
ii iproute2 4.20.0-2
ii libc6 2.28-8
ii libdbi-perl 1.642-1+b1
ii libgnutls30 3.6.6-2
ii libpam0g 1.3.1-5
ii libstdc++68.3.0-6
ii lsb-base 10.2019031300
ii lsof 4.91+dfsg-1
ii mariadb-client-10.3 1:10.3.14-1
ii mariadb-common1:10.3.14-1
ii mariadb-server-core-10.3 1:10.3.14-1
ii passwd1:4.5-1.1
ii perl 5.28.1-6
ii psmisc23.2-1
ii rsync 3.1.3-6
ii socat 1.7.3.2-2
ii zlib1g1:1.2.11.dfsg-1
Versions of packages mariadb-server-10.3 recommends:
ii libhtml-template-perl 2.97-1
Versions of packages mariadb-server-10.3 suggests:
ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1
ii mailutils [mailx] 1:3.5-3
pn mariadb-test
ii netcat-openbsd 1.195-2
pn tinyca
-- Configuration Files:
/etc/init.d/mysql changed:
set -e
set -u
${DEBIAN_SCRIPT_DEBUG:+ set -v -x}
test -x /usr/sbin/mysqld || exit 0
. /lib/lsb/init-functions
SELF=$(cd $(dirname $0); pwd -P)/$(basename $0)
MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"
ERR_LOGGER="logger -p daemon.err -t /etc/init.d/mysql -i"
if [ -f /etc/default/mysql ]; then
. /etc/default/mysql
fi
if [ -f /etc/default/mariadb ]; then
. /etc/default/mariadb
fi
cd /
umask 077
export HOME=/etc/mysql/
mysqld_get_param() {
/usr/sbin/mysqld --print-defaults \
| tr " " "\n" \
| grep -- "--$1" \
| tail -n 1 \
| cut -d= -f2
}
sanity_checks() {
# check for config file
if [ ! -r /etc/mysql/my.cnf ]; then
log_warning_msg "$0: WARNING: /etc/mysql/my.cnf cannot be read. See
README.Debian.gz"
echo"WARNING: /etc/mysql/my.cnf cannot be read. See
README.Debian.gz" | $ERR_LOGGER
fi
# check for diskspace shortage
datadir=`mysqld_get_param datadir`
if LC_ALL=C BLOCKSIZE= df --portability $datadir/. | tail -n 1 | awk '{ exit
($4>4096) }'; then
log_failure_msg "$0: ERROR: The partition with $datadir is too full!"
echo"ERROR: The partition with $datadir is too full!" |
$ERR_LOGGER
exit 1
fi
}
mysqld_status () {
ping_output=`$MYADMIN ping 2>&1`; ping_alive=$(( ! $? ))
ps_alive=0
pidfile=`mysqld_get_param pid-file`
if [ -f "$pidfile" ] && ps `cat $pidfile` >/dev/null 2>&1; then ps_alive=1; fi
if [ "$1" = "check_alive" -a $ping_alive = 1 ] ||
[ "$1" = "check_dead" -a $ping_alive = 0 -a $ps_alive = 0 ]; then
return 0 # EXIT_SUCCESS
else
if [ "$2" = "warn" ]; then
echo -e "$ps_alive processes alive and '$MYADMIN ping' resulted
in\n$ping_output\n" | $ERR_LOGGER -p daemon.debug
fi
return 1 # EXIT_FAILURE
fi
}
case "${1:-''}" in
'start')
sanity_checks;
# Start daemon
log_daemon_msg "Starting MariaDB database server" "mysqld"
if mysqld_status check_alive nowarn; then
log_progress_msg "already running"
log_end_msg 0
else
# Could be removed during boot
test -e /run/mysqld || install -m 755 -o mysql -g root -d /run/mysqld
# Start MariaDB!
/usr/bin/mysqld_safe "${@:2}" 2>&1 >/dev/null | $ERR_LOGGER &
for i in $(seq 1 "${MYSQLD_STARTUP_TIMEOUT:-30}"); do
sleep 1
if mysqld_status check_alive nowarn ; then break; fi
log_progress_msg "."
done
if mysqld_status check_alive warn; then
log_end_msg 0
# Now start mysqlcheck or whatever the admin wants.
output=$(/etc/mysql/debian-start)
if [ -n "$output" ]; then
log_action_msg "$output"
fi
else
log_end_msg 1
log_failure_msg "Please take a look at the syslog"
fi
fi
;;
'stop')
# * As a passwordless mysqladmin
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
user debian-rele...@lists.debian.org usertags 915333 + bsp-2019-04-ca-toronto thank you On 2019-04-09 08:46:10, Adrian Bunk wrote: > On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote: >> Hey, >> >> On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote: >> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote: >> > > Hello Everyone, >> > > I own a qnap ts-119pII with a similar cpu. >> > > >> > > See attached file with several debugging attempts. >> >> I took some time and wanted to reproduce and test this issue. >>... > > What are you planning to do after reproducing it? > > Bernhard did debug it back in January, > and I described what line the problem is. ... and it looks like it's a bug / limitation in ghc itself... Has anyone considered forwarding this upstream or looked at whether it's been reported? Is this a regression? >From the Toronto BSP's point of view, this is looking more and more like a "well, this means we won't support that hardware for git-annex" kind of bug. A. -- Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway. - Andrew S. Tanenbaum, "Computer Networks"
Bug#928056: dhcpcd5: Open security issues in dhcpcd5 prior to 7.2.1 affecting all versions found in Debian
On 2019-04-27.03:46, Timo Sigurdsson wrote: > * auth: Use consttime_memequal to avoid latency attack consttime_memequal > is supplied if libc does not support it > dhcpcd >=6.2 <7.2.1 are vulnerable > > * DHCP: Fix a potential 1 byte read overflow with DHO_OPTSOVERLOADED > dhcpcd >=4 <7.2.1 are vulnerable > > * DHCPv6: Fix a potential buffer overflow reading NA/TA addresses > dhcpcd >=7 <7.2.1 are vulnerable Hi Timo, Thanks for the heads up, I agree with the severity. I'll put together some uploads to fix this in the next few days. -- Regards, Scott Leggett. signature.asc Description: PGP signature
Bug#927229: marked as done (libexadrums requires libatomic on some archiectures)
Your message dated Sat, 27 Apr 2019 12:06:11 + with message-id and subject line Bug#927229: fixed in libexadrums 0.3.0-2 has caused the Debian Bug report #927229, regarding libexadrums requires libatomic on some archiectures 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.) -- 927229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: exadrums Version: 0.3.0-1 Severity: serious Justification: failure to build from scratch on release architecture Hello. The package source fails to build from scratch on armel mips mipsel (as well as other non released architectures) https://buildd.debian.org/status/package.php?p=exadrums=experimental with the following message /usr/bin/ld: /usr/lib/gcc/.../libexadrums.so: undefined reference to `__atomic_store_8' /usr/bin/ld: /usr/lib/gcc/.../libexadrums.so: undefined reference to `__atomic_load_8' /usr/bin/ld: /usr/lib/gcc/.../libexadrums.so: undefined reference to `__atomic_exchange_8' The solution is most probably to add -pthread to both CXXFLAGS and LDFLAGS. In LDFLAGS, it should come after --as-needed so the dependency is only effective on architectures actually using these 3 symbols. --- End Message --- --- Begin Message --- Source: libexadrums Source-Version: 0.3.0-2 We believe that the bug you reported is fixed in the latest version of libexadrums, 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 927...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Oden (supplier of updated libexadrums package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Apr 2019 11:46:50 +0200 Source: libexadrums Architecture: source Version: 0.3.0-2 Distribution: experimental Urgency: medium Maintainer: Jeremy Oden Changed-By: Jeremy Oden Closes: 927229 Changes: libexadrums (0.3.0-2) experimental; urgency=medium . * Add -pthread -latomic --no-undefined build flags. Closes: #927229. . [ Nicolas Boulenguez ] * Move --as-needed before libraries it is supposed to act on. Checksums-Sha1: 1c4b57b9ebe1ed8b00f3608a3c531de406e9ea67 2034 libexadrums_0.3.0-2.dsc b4abef87c155b186ea90947317f275271d5e67cc 3912 libexadrums_0.3.0-2.debian.tar.xz Checksums-Sha256: 5beaa2ec8ec00b63b13a96a9937a15f8bc4dea10214872fe1d3755eff9f36690 2034 libexadrums_0.3.0-2.dsc c8361770eef828b27f94acecc55a433fb8ca81c4ecc7310554897b9e79bbe277 3912 libexadrums_0.3.0-2.debian.tar.xz Files: 18324fd3272c76c5be7ae00f4da42b0b 2034 libdevel optional libexadrums_0.3.0-2.dsc ef35ef829405b78e31796a9c41185bbb 3912 libdevel optional libexadrums_0.3.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAlzEMlkTHG5pY29sYXNA ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jRdhEACwGidOvkwUvDlwuFz9mq2PYfNYWjL8 4Md2uxzdhVxTHw9aTPxFSfVEZODybgtiY2n+fscS5qTLnulw9kL7SxitoifYUrP7 DJZUY6EY7s01/dSCnMgVsazWPQigKtjt/b9PowbZOiWtRW2QfSf4pcevm8gUkP1X FEdOh4l2+AHc9d7suNvmkopEX8qXssykDQnnnr8iAEfHBFHoUbMD0PGpaRAii3hb iTZlz48FuvsVOPVggDSDoeMeHz1SoxRLba337bg+ii/krLElAEa/Ig1tPXIZtGMQ bUpP04wiXpzIAe9a6ss2/xCvTsSKJ8ht7wigKmIdzk8RVclKwsaR0Z2GGVluIDRn W9Gv7tkeZsseJVQphUqBc7z7XlBgr+FHG/k+fZsdW+c2BHwqEQlirE3013ThFRpE ZLjqZrTeQVhkJZ6wsoRfqOHFH7gTrl1hWW0Z94zijOC0n1TRVuEO6O6xTHB/0CHu 5uBB1HgtcdrVK9x/o5Fh9iDEb/MG/bZfM76EhPoyI9YfmdKYieBcerIPm6kLTtrp ck2TixmwrMvAtJ6p5flHLMczn1vHkafJEFkqpttg6tZy7Vh5co7xfyhVFBPpjW2e wlUU6RUdYzwEntT2MWCkLhWAHjqCwwmBThe2KAWgdaR27XM9N9qBPa4IIT9a0bnN i34gclaKVezpKQ== =Qh/d -END PGP SIGNATURE End Message ---
Bug#927991: (no subject)
FYI, this flag is used to request build arguments for linking against the embedded MySQL server library. That library was removed in MySQL 8.0: https://mysqlserverteam.com/mysql-8-0-retiring-support-for-libmysqld/ MariaDB still supports it, and there's a separate package called libmariadbd containing it. However, mariadb_config doesn't support getting the corresponding build flags. If Amarok can work without the embedded MySQL server, I think a quick fix would be to remove the check for libmysqldbd/libmariadbd. Otherwise, the cmake find script needs to be patched.
Bug#927941: marked as done (utf8proc: FTBFS with unicode-data >= 12.0.0)
Your message dated Sat, 27 Apr 2019 09:50:01 + with message-id and subject line Bug#927941: fixed in utf8proc 2.3.0-1 has caused the Debian Bug report #927941, regarding utf8proc: FTBFS with unicode-data >= 12.0.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.) -- 927941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: utf8proc Version: 2.2.0-1 Severity: serious Justification: Policy 4.2 unicode-data 12.0.0 is now in unstable/testing (Buster). utf8proc 2.2.0-1 FTBFS with this; it needs updating to 2.3.0. It is expected that unicoode-data will be updated to 12.1.* (probably 12.1.0~pre1-1) for Buster to include 'Reiwa' for Japanese era handling. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: utf8proc Source-Version: 2.3.0-1 We believe that the bug you reported is fixed in the latest version of utf8proc, 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 927...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated utf8proc 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: Sat, 27 Apr 2019 08:12:00 + Source: utf8proc Architecture: source Version: 2.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Julia Team Changed-By: Mo Zhou Closes: 927260 927941 Changes: utf8proc (2.3.0-1) unstable; urgency=medium . * New upstream version 2.3.0 (Closes: #927941) * Bump unicode-data requirement to (>= 12.1) && (<< 12.2). * Refresh use-unicode-data.patch; Remove pass-hardening-flags.patch (merged). * Patch: update utf8proc_data.c against unicode-data 12.1.0~pre1. * Patch: update unicode-data version strings to 12.1.0 * Patch: upstream didn't bump minor version in build system and header. * Install the newly-added pkgconfig file. (Closes: #927260) * Add a new symbol. Checksums-Sha1: 7e8bc50c8591d4bbb259fe574e1bddf56af4f2b7 2097 utf8proc_2.3.0-1.dsc f13f0ea64b2ea955865d2c248f231806950b477d 154282 utf8proc_2.3.0.orig.tar.gz b0c46c27e2314cf5e5e8ab5a32d2ebcd714c0c6d 49176 utf8proc_2.3.0-1.debian.tar.xz 63b8c851cd44532cae0aeb29400fe542006a34b6 5624 utf8proc_2.3.0-1_source.buildinfo Checksums-Sha256: 046ea990ad7ebbe39c5a1db14a360cde520ac289a7e50cc33907c0607b9ed5c0 2097 utf8proc_2.3.0-1.dsc c0265a49b59bab95481cab1ae958ba034dedc47ad58676a61f5de1fa9347930e 154282 utf8proc_2.3.0.orig.tar.gz 0b1689423d166cb671812e990bc30682c18e0cea8b97e1d71fb7f8136d81d317 49176 utf8proc_2.3.0-1.debian.tar.xz e394338fd08cdce04bcf59f2e16f35ef2a8681b0b7093d68f3b210f66fb5deba 5624 utf8proc_2.3.0-1_source.buildinfo Files: 93a0e1749c51a528a7ba276927944f81 2097 libs optional utf8proc_2.3.0-1.dsc 0e5c6e33fce3b2df5b553b9ccd407a77 154282 libs optional utf8proc_2.3.0.orig.tar.gz 4cc2d91c5314d55a4489a49f72431657 49176 libs optional utf8proc_2.3.0-1.debian.tar.xz 6fc611e1d514e94345ba037153d03652 5624 libs optional utf8proc_2.3.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAlzEDxEACgkQYmRes19o aopwuA/9G51vD9/8/mfm2IdZQCxhCYTpFDU17ZKoQG/g1GxAaWV7env/uP/GCOOD HxCe3m34rCQLXVuHz3U0pqikud6AxYVC+bJzof/QA2ZIznWj1CKHFkgOmi9wQMdG gFq1/vSsR/LvGpb/03cK6BAqKyj+pfFm6CbrXV3C6ay+mQMd5TJ6BDTR2+g5oamZ JxyuwZB7MY5PaTwMT1SNQhgwDUm94EXIRSshyJfHt3zqIm5aR7nWGelIV56zgt5b SDADuwV6piKeWP/+LLt1zPo0OBflLmAMyiTDwEB6VpZWz9klFkrSw3gHQ415vixJ /KIGGsxnVLmrcrUmcGYX+GTmZWbil17DjgRzUzZyisfMTpbi+GfYtCJ2ogqTX9F9 GgFsHiGbalwgIDH6WfqKeqkQSUWRW7FEhaAzACZXRsa6xiTVoUjIt2HqsFHQ/Ud9 dl4LW4KPBmCe1ybvzqqrPJOkT0ry9G/iBRm3aNNEmNbOMogMM7OtikPasenAG61x QfzLNuBs7hFtQDsm+YXjoZxTsj8TAhkaWFWIXFX3N8AeT5PRSHymZtG5huuZJsUS
Bug#927314: Reported upstream
Thanks for your report. Forwarded to upstream: https://github.com/tomprogrammer/rust-ascii/issues/61
Bug#927862: youtube-dl: please update to 2019.04.24
On Sat, Apr 27, 2019 at 08:45:11AM +0200, Andreas Beckmann wrote: > > # justification: this indeed breaks download of youtube videos > Does this affect stretch (2017.05.18.1-1), too? yes -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Processed: found 928056 in 7.1.0-1
Processing commands for cont...@bugs.debian.org: > found 928056 7.1.0-1 Bug #928056 [dhcpcd5] dhcpcd5: Open security issues in dhcpcd5 prior to 7.2.1 affecting all versions found in Debian Marked as found in versions dhcpcd5/7.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 928056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926218: range-v3: FTBFS with gcc 8.3
Alexis Murzeau, thank you very much for the investigation. Then we can ignore that warning in a good conscience. To avoid "unrecognized command line option" errors, I've rewritten the ranges_append_flag macro used by CMake.
Processed: tagging 928056, found 928056 in 5.2.7-3, notfound 928056 in any
Processing commands for cont...@bugs.debian.org: > tags 928056 + security Bug #928056 [dhcpcd5] dhcpcd5: Open security issues in dhcpcd5 prior to 7.2.1 affecting all versions found in Debian Added tag(s) security. > found 928056 5.2.7-3 Bug #928056 [dhcpcd5] dhcpcd5: Open security issues in dhcpcd5 prior to 7.2.1 affecting all versions found in Debian Marked as found in versions dhcpcd5/5.2.7-3. > notfound 928056 any Bug #928056 [dhcpcd5] dhcpcd5: Open security issues in dhcpcd5 prior to 7.2.1 affecting all versions found in Debian There is no source info for the package 'dhcpcd5' at version 'any' with architecture '' Unable to make a source version for version 'any' No longer marked as found in versions any. > thanks Stopping processing here. Please contact me if you need assistance. -- 928056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #926218 in range-v3 marked as pending
Processing control commands: > tag -1 pending Bug #926218 [src:range-v3] range-v3: FTBFS with gcc 8.3 Added tag(s) pending. -- 926218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926218: Bug #926218 in range-v3 marked as pending
Control: tag -1 pending Hello, Bug #926218 in range-v3 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/debian/range-v3/commit/7c52e44a671922f23f960e5c6e0d79be893f771a Ignore false positive -Werror=maybe-uninitialized Closes: #926218 (this message was generated automatically) -- Greetings https://bugs.debian.org/926218
Bug#927862: youtube-dl: please update to 2019.04.24
On Thu, 25 Apr 2019 19:09:47 + Holger Levsen wrote: > control: severity -1 serious > # justification: this indeed breaks download of youtube videos Does this affect stretch (2017.05.18.1-1), too? Andreas
Processed: found 856939 in 0.78.1-2, tagging 927765, found 927809 in 2.79.b+dfsg0-6, fixed 925317 in 4.8.1-2 ...
Processing commands for cont...@bugs.debian.org:
> found 856939 0.78.1-2
Bug #856939 [buildd] buildd: broken symlinks: /usr/share/man/man?/buildd-*.?.gz
-> /sbuild-*.?.gz
Marked as found in versions sbuild/0.78.1-2.
> tags 927765 + sid buster
Bug #927765 {Done: Niels Thykier } [debian-archive-keyring]
debian-archive-keyring: Team maintainer but no human uploaders (policy 3.3)
Added tag(s) sid and buster.
> found 927809 2.79.b+dfsg0-6
Bug #927809 {Done: m...@debian.org (Matteo F. Vescovi)} [blender] blender:
Blender deletes PSD files upon viewing
Marked as found in versions blender/2.79.b+dfsg0-6.
> fixed 925317 4.8.1-2
Bug #925317 {Done: Thomas Goirand }
[python3-barbicanclient] python3-barbicanclient: fails to install:
update-alternatives: error: alternative path /usr/bin/python3-barbican doesn't
exist
Marked as fixed in versions python-barbicanclient/4.8.1-2.
> fixed 925318 5.15.2-2
Bug #925318 {Done: Thomas Goirand } [python3-oslo.rootwrap]
python3-oslo.rootwrap: fails to install: update-alternatives: error:
alternative path /usr/bin/python3-oslo-rootwrap doesn't exist
Marked as fixed in versions python-oslo.rootwrap/5.15.2-2.
> reassign 927688 src:graphicsmagick 1.4~hg15968-1
Bug #927688 {Done: Laszlo Boszormenyi (GCS) } [src:mpfit,
src:graphicsmagick] graphicsmagick breaks mpfit autopkgtest: LockSemaphoreInfo:
Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed
Bug reassigned from package 'src:mpfit, src:graphicsmagick' to
'src:graphicsmagick'.
No longer marked as found in versions mpfit/1.85+2017.01.03-3 and
graphicsmagick/1.4~hg15968-1.
No longer marked as fixed in versions graphicsmagick/1.4~hg15976-1.
Bug #927688 {Done: Laszlo Boszormenyi (GCS) }
[src:graphicsmagick] graphicsmagick breaks mpfit autopkgtest:
LockSemaphoreInfo: Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed
Marked as found in versions graphicsmagick/1.4~hg15968-1.
> affects 927688 src:mpfit
Bug #927688 {Done: Laszlo Boszormenyi (GCS) }
[src:graphicsmagick] graphicsmagick breaks mpfit autopkgtest:
LockSemaphoreInfo: Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed
Added indication that 927688 affects src:mpfit
> fixed 927688 1.4~hg15976-1
Bug #927688 {Done: Laszlo Boszormenyi (GCS) }
[src:graphicsmagick] graphicsmagick breaks mpfit autopkgtest:
LockSemaphoreInfo: Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed
Marked as fixed in versions graphicsmagick/1.4~hg15976-1.
> tags 928040 + sid buster
Bug #928040 [lprng] lprng: fails to install
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
856939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856939
925317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925317
925318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925318
927688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927688
927765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927765
927809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927809
928040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#926218: its gcc, not ranges. dropping -Werror makes the build pass
Hi, this seems to be caused by /usr/bin/c++ accepting flags during cmake configuration, but not later during compilation. ranges uses the check_cxx_compiler_flag in order to set a lot of flags, including the ones mentioned by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926218#5 Using the c++98-compat as an example: cmake executes /usr/bin/c++ -Wno-c++98-compat /range-v3/build/CMakeFiles/CMakeTmp/src.cxx -o to see if no-c++98-compat is supported. But c++ accepts even nonexistant warnings: touch empty.cpp /usr/bin/c++ -Wno-iamsurethisonedoesnotexist -c empty.cpp -o /dev/null works fine, even if the following gives (as expected) an error: /usr/bin/c++ -Wiamsurethisonedoesnotexist -c empty.cpp -o /dev/null c++: error: unrecognized command line option ‘-Wiamsurethisonedoesnotexist’ so I would say this it not ranges that is broken, it's gcc. I would say that the proper action (for the ranges package) is to drop the Werror from line 34 in cmake/ranges_flags.cmake makes the build pass. Paul -- Paul Dreik Web: https://www.pauldreik.se/ Phone: +46 (0)73 99 26 333 Alt. voice channels: Signal, Whatsapp signature.asc Description: OpenPGP digital signature
