Processed: Re: [Pkg-electronics-devel] Bug#930890: ghdl: Debian ghdl.wrapper prevents build when GHDL is not already installed.
Processing control commands: > severity -1 wishlist Bug #930890 [src:ghdl] ghdl: Debian ghdl.wrapper prevents build when GHDL is not already installed. Severity set to 'wishlist' from 'serious' > retitle -1 Update GHDL packaging for newer releases Bug #930890 [src:ghdl] ghdl: Debian ghdl.wrapper prevents build when GHDL is not already installed. Changed Bug title to 'Update GHDL packaging for newer releases' from 'ghdl: Debian ghdl.wrapper prevents build when GHDL is not already installed.'. -- 930890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930890: [Pkg-electronics-devel] Bug#930890: ghdl: Debian ghdl.wrapper prevents build when GHDL is not already installed.
Control: severity -1 wishlist Control: retitle -1 Update GHDL packaging for newer releases On Sun, Jun 23, 2019 at 11:57:33PM +0200, Pavel Pisa wrote: > On Sunday 23 of June 2019 10:52:47 Jonathan McDowell wrote: > > On Sat, Jun 22, 2019 at 12:26:36AM +0200, Pavel Pisa wrote: > > > Source: ghdl > > > Version: 0.36+20190617 > > > > This is not a version of GHDL from Debian. testing/unstable both have > > 0.35+git20181129+dfsg-3. I don't think this is a valid bug against the > > Debian package - it seems that you've obtained an updated package from > > somewhere else, or have manually updated to a newer release? > > I have used original Debian package as "debian" directory > source to port newer GHDL version for Debian Buster. > > I am not sure if the problem applies to old version, > but solution should work for all versions. I have built older > version but on the system where GHDL has already been installed. > So I expect that the problem may be there as well. You have raised a release critical bug stating the package currently in Debian fails to build from source. I think what you wanted to raise was a wishlist bug requesting the packaging be updated to support newer versions of GHDL. Retitling and updating the severity to indicate this fact. This can be looked at once we have Buster released. (I've confirmed that I can still build 0.35+git20181129+dfsg-3 in a clean sbuild environment, so the FTBFS does not apply to the Debian package and thus there's no need to fix it to ensure it's ok for Buster.) J. -- /-\ | Evil is as evil does, but evil |@/ Debian GNU/Linux Developer | doesn't wear shoes. \- |
Bug#864320: [RFC] Changing the default cursor on the Linux console?
In Bash it is possible to set a feature that runs when a command runs called precmd to an ANSI sequence that sets a non-blinking block cursor. This make Bash usable. However, that fails if there is no Bash or you not have your .bashrc. There are shell-like entitities that are needed to fix booting. Also, Emacs still blinks! It seems to be either the Linux console or the Emacs C code. Elisp lets you control blinking if you are running Emacs in an terminal under X or as GUI uner X, but not if you are running Emacs in the Linux console. So if you need Emacs to fix a booting problem, you can't use it if you have problems with blinking. Finally, an off-topic comment that white and blue are too bright at night for me, and that the debconf blue and grey have the same problem (the red is OK). Not all can physically adjust their monitors. What would be good is the ability to adjust the console text color to amber, and debconf to a contrasty amber theme, and brightness.
Bug#928963: [pkg-gnupg-maint] Bug#928963: fixed in gnupg2 2.2.13-2
Hi Paul-- On Sat 2019-06-22 20:51:00 +0200, Paul Gevers wrote: > On Tue, 14 May 2019 06:18:31 + Daniel Kahn Gillmor > wrote: >> gnupg2 (2.2.13-2) unstable; urgency=medium >> . >>* Correct gpg-wks-server manpage (Closes: #927431) Thanks, ju xor! >>* Fix handling private keys with comments (Closes: #928963, #928964) >>* clean up logcheck rules for gpg-agent (Closes: #918466) >>* Update gpg-wks-client.1 (Closes: #918586) >>* cherry-pick more patches from upstream STABLE-BRANCH-2-2 > > Is there any reason that we shouldn't want to unblock this for buster > (i.e. is there any reason why you didn't file an unblock bug request)? Filing an unblock for gnupg2 version 2.2.13-2 for buster is on my stack of things to do, but i'm quite far behind on other work. I do think it would be useful to have, and i welcome any help in filing such an unblock request. This change includes several upstream cleanup changes beyond the 2.2.12-1 that is in buster right now, in particular (from upstream's NEWS): * gpg: Implement key lookup via keygrip (using the & prefix). * gpg: Allow generating Ed25519 key from existing key. * gpg: Emit an ERROR status line if no key was found with -k. * gpg: Stop early when trying to create a primary Elgamal key. [#4329] * gpgsm: Print the card's key algorithms along with their keygrips in interactive key generation. * agent: Clear bogus pinentry cache in the error case. [#4348] * scd: Support "acknowledge button" feature. * scd: Fix for USB INTERRUPT transfer. [#4308] * wks: Do no use compression for the the encrypted challenge and response. Since the gnupg2 source produces a udeb for gpgv, there are likely to be additional hurdles to clearing the queue. :/ --dkg signature.asc Description: PGP signature
Bug#929850: marked as done (buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster)
Your message dated Mon, 24 Jun 2019 23:48:42 + with message-id and subject line Bug#929850: fixed in dhelp 0.6.26 has caused the Debian Bug report #929850, regarding buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster 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.) -- 929850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: buildd.debian.org Severity: normal Dear Maintainer, KDE packages install their documentation files in /usr/share/doc/HTML on buster (in debian 8 this was: /usr/share/doc/kde/HTML). The "dhelp" package erases this folder when it rebuilds its index. The KHelpcenter documentation gets erased this way. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8), LANGUAGE=en_US.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: dhelp Source-Version: 0.6.26 We believe that the bug you reported is fixed in the latest version of dhelp, 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 929...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas Guriev (supplier of updated dhelp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Jun 2019 22:40:44 +0300 Source: dhelp Architecture: source Version: 0.6.26 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Nicholas Guriev Closes: 929850 Changes: dhelp (0.6.26) unstable; urgency=medium . * QA upload. * Do not remove entire /usr/share/doc/HTML directory while reindexing or deinstalling (closes: #929850). * Add the sensible-utils package as runtime dependency. * Use Git repository at the salsa.debian.org site. Checksums-Sha1: a6a2ff7c1dce60e0bda68a48b239d87115f4a244 1288 dhelp_0.6.26.dsc 36db2bf579d50086e5084a34623d44fb1516db6a 73360 dhelp_0.6.26.tar.xz Checksums-Sha256: 0fe202e17a5177c14ee84ffebfabf720d731dcdb855c656eddc590beaee2262c 1288 dhelp_0.6.26.dsc 18eb6046c72309c176d2f8585501af7a02fcd8a11c884f70feac75247bd949a8 73360 dhelp_0.6.26.tar.xz Files: cd77e9b329812e4feb4eb29ed211c489 1288 doc optional dhelp_0.6.26.dsc 44b1f970c67719bb1858c3f8d8b60ca9 73360 doc optional dhelp_0.6.26.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl0RW5kACgkQXkCM2RzY OdLAKQf+K5/55ZXprb2xRzLeQMeLK4eAkcywTy6KKsuX5NmwcLT3dQ8HEhtQHHZG K/a/lglp39jI1EA+Q9hhHTipUrIxcIGV1XiZitRQJHZO8F/t0J5fARrNGHmArV0Z 1FOkMjeuC0KyDVckFgMQSrE3VQCK9gsy1kF6+d9mKm+EBaibOUnmhXA3n14NanQx cB2cSUBW68MgjgYwaqjG2i/2ruwUI5FTwOu8LQ9ksm1VeoZZzULYaOOPdNLf8yRf OICVaLaPHUS4fcyg6gMq8MZdKPGSgOVDEvjMcIKlH6u7NekBQ1Ou2ZYq6aINdKcA UjQL0NlGQaVoJSN1AO8eSzFFOcIzFA== =D2cR -END PGP SIGNATURE End Message ---
Bug#931038: missing Recommends: for shim-signed
On Tue, Jun 25, 2019 at 12:17:20AM +0100, Steve McIntyre wrote: >Source: grub2 >Version: 2.02+dfsg1-19 >Severity: serious >Tags: patch > >The grub-efi-amd64-signed package recommends shim-signed, but the >equivalent grub-efi-ia32-signed and grub-efi-arm64-signed packages are >missing the same Recommends: > >Simple tweak needed to the signing-template, MR ready as soon as I get >a bug# from the BTS for this. https://salsa.debian.org/grub-team/grub/merge_requests/11 Happy to merge and upload myself if that's easier. Arg, only just spotted this in testing for the Buster d-i RC2 build. -- Steve McIntyre, Cambridge, UK.st...@einval.com There's no sensation to compare with this Suspended animation, A state of bliss
Bug#931021: marked as done (musescore: phones home, including to Google Analytics, on first start)
Your message dated Mon, 24 Jun 2019 23:21:01 + with message-id and subject line Bug#931021: fixed in musescore 2.3.2+dfsg2-7 has caused the Debian Bug report #931021, regarding musescore: phones home, including to Google Analytics, on first start 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.) -- 931021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: musescore Version: 2.3.2+dfsg2-6 Severity: serious Tags: security Justification: phones home Bugreport for myself and for release tracking. Dear release team, please indicate whether this is buster release-critical, I will try to fix it later tonight. On first startup, MuseScore connects to: connect2.musescore.com CNAME cds.z5r7u8v4.hwcdn.net cds.z5r7u8v4.hwcdn.net A 205.185.216.10 cds.z5r7u8v4.hwcdn.net A 205.185.216.42 (Highwinds Network Operations Center) The currently shipped HTML content makes it also connect to: www.google-analytics.comCNAME www-google-analytics.l.google.com www-google-analytics.l.google.com A 172.217.16.174 www-google-analytics.l.google.com 2A00:1450:4001:81B:0:0:0:200E Also: mc.yandex.ruA 93.158.134.119 mc.yandex.ruA 77.88.21.119 mc.yandex.ruA 87.250.250.119 mc.yandex.ruA 87.250.251.119 mc.yandex.ru2A02:6B8:0:0:0:0:1:119 And: stats.g.doubleclick.net CNAME stats.l.doubleclick.net stats.l.doubleclick.net A 74.125.133.155 stats.l.doubleclick.net A 74.125.133.156 stats.l.doubleclick.net A 74.125.133.157 stats.l.doubleclick.net A 74.125.133.154 stats.l.doubleclick.net 2A00:1450:400C:C0B:0:0:0:9D I’ll simply remove the offending “web start centre” functionality, given that MuseScore 3.x will not ship it either anyway (for tech reasons). -- System Information: Debian Release: 10.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages musescore depends on: ii desktop-file-utils 0.23-4 ii libasound2 1.1.8-1+x32.1 ii libc62.28-10 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.3.0-7 ii libportaudio219.6.0-1 ii libportmidi0 1:217-6 ii libpulse012.2-4 ii libqt5core5a 5.11.3+dfsg1-2 ii libqt5gui5 5.11.3+dfsg1-2 ii libqt5help5 5.11.3-4 ii libqt5network5 5.11.3+dfsg1-2 ii libqt5printsupport5 5.11.3+dfsg1-2 ii libqt5qml5 5.11.3-4 ii libqt5quick5 5.11.3-4 ii libqt5sql5-sqlite5.11.3+dfsg1-2 ii libqt5svg5 5.11.3-2 ii libqt5webkit55.212.0~alpha2-21 ii libqt5widgets5 5.11.3+dfsg1-2 ii libqt5xml5 5.11.3+dfsg1-2 ii libqt5xmlpatterns5 5.11.3-2 ii libsndfile1 1.0.28-6 ii libstdc++6 8.3.0-7 ii libvorbisfile3 1.3.6-2 ii musescore-common 2.3.2+dfsg3-2 ii qml-module-qtquick-controls 5.11.3-2 ii qml-module-qtquick-dialogs 5.11.3-2 ii qml-module-qtquick-layouts 5.11.3-4 ii qml-module-qtquick2 5.11.3-4 ii shared-mime-info 1.10-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages musescore recommends: ii libmp3lame0 3.100-2+b1 pn pulseaudio-utils musescore suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: musescore Source-Version: 2.3.2+dfsg2-7 We believe that the bug you reported is fixed in the latest version of musescore, 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 931...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated musescore package)
Bug#931038: missing Recommends: for shim-signed
Source: grub2 Version: 2.02+dfsg1-19 Severity: serious Tags: patch The grub-efi-amd64-signed package recommends shim-signed, but the equivalent grub-efi-ia32-signed and grub-efi-arm64-signed packages are missing the same Recommends: Simple tweak needed to the signing-template, MR ready as soon as I get a bug# from the BTS for this. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#929850: marked as pending in dhelp
Control: tag -1 pending Hello, Bug #929850 in dhelp 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/mymedia-guest/dhelp/commit/c2075fff759a2650b9272e5e37cec0daa514987c Do not remove entire /usr/share/doc/HTML Closes: #929850 (this message was generated automatically) -- Greetings https://bugs.debian.org/929850
Processed: Bug#929850 marked as pending in dhelp
Processing control commands: > tag -1 pending Bug #929850 [dhelp] buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster Added tag(s) pending. -- 929850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 929850 by 931036 Bug #929850 [dhelp] buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster 929850 was not blocked by any bugs. 929850 was not blocking any bugs. Added blocking bug(s) of 929850: 931036 > End of message, stopping processing here. Please contact me if you need assistance. -- 929850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914639: marked as done (gpsshogi FTBFS with boost 1.67)
Your message dated Mon, 24 Jun 2019 22:03:57 + with message-id and subject line Bug#928997: Removed package(s) from unstable has caused the Debian Bug report #914639, regarding gpsshogi FTBFS with boost 1.67 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.) -- 914639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpsshogi Version: 0.7.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=gpsshogi=sid ... /usr/bin/ld: gpsusi.o: in function `makePlayer(osl::Player, osl::SimpleState const&, std::ostream&)': ./bin/gpsusi.cc:1412: undefined reference to `osl::search::UsiMonitor::setUdpLogging(std::__cxx11::basic_string, std::allocator >&, boost::asio::basic_datagram_socket*, boost::asio::ip::basic_endpoint*)' collect2: error: ld returned 1 exit status make[1]: *** [: gpsusi] Error 1 --- End Message --- --- Begin Message --- Version: 0.7.0-2+rm Dear submitter, as the package gpsshogi has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/928997 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#926313: marked as done (leptonica-progs: trying to overwrite '/usr/bin/imagetops', which is also in package netpbm)
Your message dated Mon, 24 Jun 2019 21:36:09 + with message-id and subject line Bug#926313: fixed in leptonlib 1.78.0-2 has caused the Debian Bug report #926313, regarding leptonica-progs: trying to overwrite '/usr/bin/imagetops', which is also in package netpbm 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.) -- 926313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: leptonica-progs Version: 1.78.0-1 Severity: serious leptonica-progs fails to upgrade here: Unpacking leptonica-progs (1.78.0-1) over (1.76.0-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-HhGtJC/7-leptonica-progs_1.78.0-1_i386.deb (--unpack): trying to overwrite '/usr/bin/imagetops', which is also in package netpbm 2:10.0-15.3+b2 Errors were encountered while processing: /tmp/apt-dpkg-install-HhGtJC/7-leptonica-progs_1.78.0-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- Jakub Wilk --- End Message --- --- Begin Message --- Source: leptonlib Source-Version: 1.78.0-2 We believe that the bug you reported is fixed in the latest version of leptonlib, 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. Jeff Breidenbach (supplier of updated leptonlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Jun 2019 13:22:19 -0700 Source: leptonlib Binary: leptonica-progs leptonica-progs-dbgsym liblept5 liblept5-dbgsym libleptonica-dev Architecture: source amd64 Version: 1.78.0-2 Distribution: unstable Urgency: medium Maintainer: Jeff Breidenbach Changed-By: Jeff Breidenbach Description: leptonica-progs - sample programs for Leptonica image processing library liblept5 - image processing library libleptonica-dev - image processing library Closes: 926313 Changes: leptonlib (1.78.0-2) unstable; urgency=medium . * Remove imagetops binary (closes: #926313) Checksums-Sha1: 3f93ac93d03043ff05494e55da1bfc039426fd0b 1991 leptonlib_1.78.0-2.dsc faf0d6de24226e506d03e8cc599c6b874edfe3ed 5928 leptonlib_1.78.0-2.debian.tar.xz c7da928c00f8360efab5e9c1bd368ab77cd2d97f 35192 leptonica-progs-dbgsym_1.78.0-2_amd64.deb 33a6640648dd7a972d5351dcdac0a1ff0b29d41f 17224 leptonica-progs_1.78.0-2_amd64.deb 68b71121982338456f69c2a713af28ff121f96b2 7964 leptonlib_1.78.0-2_amd64.buildinfo 6643ed60d1b9c137c22edfe6d3ca968f0f45c066 2768100 liblept5-dbgsym_1.78.0-2_amd64.deb a892821540d725ec1417650e25e89d33931f72b0 997400 liblept5_1.78.0-2_amd64.deb b39fea424c9190f732754756d1b1921449e666a7 1383760 libleptonica-dev_1.78.0-2_amd64.deb Checksums-Sha256: d2cddeec0c29c521b4663f73f985c9ec29208c6a33528aa04568bf8b23663df1 1991 leptonlib_1.78.0-2.dsc 641fcc47dc7639ec35e729e2d78b78279641dc90b3be0b1403ce3246406924d5 5928 leptonlib_1.78.0-2.debian.tar.xz 69994933aa915bbb344acde8992480ea4968a76afc6a75ea391204662b5c7b1f 35192 leptonica-progs-dbgsym_1.78.0-2_amd64.deb 1765f5e1f85d81b2fab0490e0ca0c8216259abe9adef22fb4dea70f81b9be482 17224 leptonica-progs_1.78.0-2_amd64.deb 0b9330bc5e03e2d53e22891f04a44ab71a3cdb9d37626e8109b124331fa08fd7 7964 leptonlib_1.78.0-2_amd64.buildinfo 612974ca5ae4907859e0cad291610fb61ef32041d57ac51cc569c04c38256e81 2768100 liblept5-dbgsym_1.78.0-2_amd64.deb 4f00d1662dba861590fc46403ef0c2d458d53b1de7a496160e463e0142350cfc 997400 liblept5_1.78.0-2_amd64.deb d181293b459d76b2196055e6825f8afa72dd04f96a22d5c877ee6c50a9d33640 1383760 libleptonica-dev_1.78.0-2_amd64.deb Files: 637c9f8d51004b5651447a2af0b22fa3 1991 graphics optional leptonlib_1.78.0-2.dsc 8989a7dc2d23bf24493732c19bd2e766 5928 graphics optional leptonlib_1.78.0-2.debian.tar.xz 0aeb52c3d8271f209c241e84f65fa8eb 35192 debug optional leptonica-progs-dbgsym_1.78.0-2_amd64.deb d2c1c4f071597ceed405898127930b62 17224 graphics optional leptonica-progs_1.78.0-2_amd64.deb 50d3e3e89606c63cba0a557fba1a1b99 7964 graphics optional leptonlib_1.78.0-2_amd64.buildinfo c9b28938c16ce8393b2812edde6db9d2 2768100 debug optional liblept5-dbgsym_1.78.0-2_amd64.deb dae97e4852c63b1fd3fcdc3a8f0f32ed
Bug#930858: gif2png: "not expected to be able to deal with arbitrarily broken input"
On Mon, Jun 24, 2019 at 01:05:13PM +0200, Erik Schanze wrote: > Hi all, > > > this is OK for me, Because Upstream (ESR) changed programming language to > "GO" recently (3.0.0) and this is not my cup of tea. > > I decided to orphan it, but popcorn count is low, so it should be removed. Can you please file a removal bug against ftp.debian.org, then? Cheers, Moritz
Bug#927226: libpaper1: Fresh RC1 install doesn't configure /etc/papersize
Hello Thorsten, thank you very much for your testing. Indeed the bug required more fixing than what I did. I did follow your steps for reproducing it, and now I have a new package that fix it. If you want to try it, please fetch it here: https://eppesuigoccas.homedns.org/~giuseppe/debian/libpaper1_1.1.27_amd64.deb https://eppesuigoccas.homedns.org/~giuseppe/debian/libpaper-utils_1.1.27_amd64.deb or dget https://eppesuigoccas.homedns.org/~giuseppe/debian/libpaper_1.1.27.dsc Bye, Giuseppe
Bug#930935: marked as done (webkit2gtk: Baseline violation on i386)
Your message dated Mon, 24 Jun 2019 19:49:33 + with message-id and subject line Bug#930935: fixed in webkit2gtk 2.24.2-2 has caused the Debian Bug report #930935, regarding webkit2gtk: Baseline violation on i386 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.) -- 930935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: webkit2gtk Version: 2.24.1-2 Severity: serious Tags: patch webkit2gtk violates the baseline on i386 by using SSE. While keeping floating point values consistent between 32bit and 64bit is nice in general, it is bad if this makes the code crash on large parts of the supported i386 hardware - most hardware with SSE2 runs the amd64 port, and at least one non-SSE i386 CPU is still in production for embedded systems (AMD Geode). Fix is attached. diff -Nru webkit2gtk-2.24.2/debian/NEWS webkit2gtk-2.24.2/debian/NEWS --- webkit2gtk-2.24.2/debian/NEWS 2019-05-17 17:40:52.0 +0300 +++ webkit2gtk-2.24.2/debian/NEWS 2019-05-17 17:40:52.0 +0300 @@ -1,12 +1,3 @@ -webkit2gtk (2.24.1-2) unstable; urgency=high - - Since version 2.24.0, i386 builds of WebKitGTK require an SSE2-capable - CPU. This instruction set was first introduced with the Pentium 4 in - year 2000. Support for older processors was dropped in WebKitGTK - upstream and is unfortunately not expected to come back. - - -- Alberto Garcia Fri, 10 May 2019 15:40:28 +0300 - webkit2gtk (2.20.0-2) unstable; urgency=medium webkit2gtk 2.20.0 contains a security feature named Gigacage that diff -Nru webkit2gtk-2.24.2/debian/patches/i386-no-sse.patch webkit2gtk-2.24.2/debian/patches/i386-no-sse.patch --- webkit2gtk-2.24.2/debian/patches/i386-no-sse.patch 1970-01-01 02:00:00.0 +0200 +++ webkit2gtk-2.24.2/debian/patches/i386-no-sse.patch 2019-05-17 17:40:52.0 +0300 @@ -0,0 +1,21 @@ +Description: SSE is a baseline violation on i386 +Author: Adrian Bunk + +--- webkit2gtk-2.24.2.orig/Source/cmake/WebKitCompilerFlags.cmake webkit2gtk-2.24.2/Source/cmake/WebKitCompilerFlags.cmake +@@ -144,15 +144,6 @@ if (COMPILER_IS_GCC_OR_CLANG) + if (CMAKE_COMPILER_IS_GNUCXX) + WEBKIT_PREPEND_GLOBAL_COMPILER_FLAGS(-Wno-expansion-to-defined) + endif () +- +-# Force SSE2 fp on x86 builds. +-if (WTF_CPU_X86 AND NOT CMAKE_CROSSCOMPILING) +-WEBKIT_PREPEND_GLOBAL_COMPILER_FLAGS(-msse2 -mfpmath=sse) +-include(DetectSSE2) +-if (NOT SSE2_SUPPORT_FOUND) +-message(FATAL_ERROR "SSE2 support is required to compile WebKit") +-endif () +-endif () + endif () + + if (COMPILER_IS_GCC_OR_CLANG AND NOT MSVC) diff -Nru webkit2gtk-2.24.2/debian/patches/series webkit2gtk-2.24.2/debian/patches/series --- webkit2gtk-2.24.2/debian/patches/series 2019-05-17 17:40:52.0 +0300 +++ webkit2gtk-2.24.2/debian/patches/series 2019-05-17 17:40:52.0 +0300 @@ -7,3 +7,4 @@ detect-woff.patch user-agent-branding.patch prefer-pthread.patch +i386-no-sse.patch diff -Nru webkit2gtk-2.24.2/debian/rules webkit2gtk-2.24.2/debian/rules --- webkit2gtk-2.24.2/debian/rules 2019-05-17 17:40:52.0 +0300 +++ webkit2gtk-2.24.2/debian/rules 2019-05-17 17:40:52.0 +0300 @@ -23,11 +23,6 @@ CFLAGS := $(CFLAGS:-g=-g1) endif -# The 32-bit x86 build requires SSE2 -ifneq (,$(filter $(DEB_HOST_ARCH),i386)) - CFLAGS += -msse2 -mfpmath=sse -endif - # See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81426 ifneq (,$(filter $(DEB_HOST_ARCH),armhf sh3 sh4 powerpc)) CFLAGS := $(CFLAGS:-O2=-O1) --- End Message --- --- Begin Message --- Source: webkit2gtk Source-Version: 2.24.2-2 We believe that the bug you reported is fixed in the latest version of webkit2gtk, 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 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Garcia (supplier of updated webkit2gtk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Jun 2019 16:34:09 +0300 Source: webkit2gtk Binary: libjavascriptcoregtk-4.0-18
Bug#912076: marked as done (kodiplatform FTBFS with debhelper 11.4)
Your message dated Mon, 24 Jun 2019 19:18:36 + with message-id and subject line Bug#912076: fixed in kodiplatform 17.1.0-1.1 has caused the Debian Bug report #912076, regarding kodiplatform FTBFS with debhelper 11.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 912076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kodiplatform Version: 17.1.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kodiplatform.html ... dh_auto_install cd obj-x86_64-linux-gnu && make -j1 install DESTDIR=/build/1st/kodiplatform-17.1.0/debian/tmp AM_UPDATE_INFO_DIR=no make[1]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' /usr/bin/cmake -H/build/1st/kodiplatform-17.1.0 -B/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make -f CMakeFiles/kodiplatform.dir/build.make CMakeFiles/kodiplatform.dir/depend make[3]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' cd /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/1st/kodiplatform-17.1.0 /build/1st/kodiplatform-17.1.0 /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/kodiplatform.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make -f CMakeFiles/kodiplatform.dir/build.make CMakeFiles/kodiplatform.dir/build make[3]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make[3]: Nothing to be done for 'CMakeFiles/kodiplatform.dir/build'. make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' [100%] Built target kodiplatform make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_start /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles 0 make -f CMakeFiles/Makefile2 preinstall make[2]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make[2]: Nothing to be done for 'preinstall'. make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "None" -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16.0.0 -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16 -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/usr/include/kodi/util/XMLUtils.h -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/pkgconfig/kodiplatform.pc -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/kodiplatform/kodiplatform-config.cmake make[1]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' dh_install dh_install: Cannot find (any matches for) "usr/lib/*/*.so" (tried in ., debian/tmp) dh_install: libkodiplatform-dev missing files: usr/lib/*/*.so dh_install: Cannot find (any matches for) "usr/lib/*/pkgconfig/*.pc" (tried in ., debian/tmp) dh_install: libkodiplatform-dev missing files: usr/lib/*/pkgconfig/*.pc dh_install: Cannot find (any matches for) "usr/lib/*/kodiplatform/*" (tried in ., debian/tmp) dh_install: libkodiplatform-dev missing files: usr/lib/*/kodiplatform/* dh_install: Cannot find (any matches for) "usr/lib/*/*.so.*" (tried in ., debian/tmp) dh_install: libkodiplatform16 missing files: usr/lib/*/*.so.* dh_install: missing files, aborting make: *** [debian/rules:16: binary] Error 25 --- End Message --- --- Begin Message --- Source: kodiplatform Source-Version: 17.1.0-1.1 We believe that the bug you reported is fixed in the latest
Bug#927226: libpaper1: Fresh RC1 install doesn't configure /etc/papersize
On Mon, 24 Jun 2019 09:34:17 +0200 Giuseppe Sacco wrote: > Hello Thorsten, Voip, and Jacob, > I think the problem has been solved in version 1.1.27, currently in > unstable. I would really appreciate if you could test it, as well as I > did. > > If this package passes your tests, I will ask for an unblock that will > let the package migrate to testing/buster in a few days. > > Bye, > Giuseppe Hello Giuseppe, I tried version 1.2.27 today but I'm afraid the problem still remains. What I did in a fresh, German localized, text-only install of RC1 (AMD64) with "sid" updates installed: Downloaded both 1.2.24+nmu5 (stretch) and 1.2.27 (sid) versions of libpaper1 and libpaper-utils. Purged the installed packages: dpkg --force-all --purge libpaper1 libpaper-utils Checked /var/cache/debconf/config.dat for remaining configuration of libpaper and deleted it if any. (This happens after a manual override of /etc/papersize with dpkg-reconfigure libpaper1) Installed either version a) 24 or b) 27: dpkg --install ./libpaper1_XXX_amd64.deb ./libpaper-utils_XXX_amd64.deb In case a) I got a4 and in case b) letter in both /etc/papersize and /var/cache/debconf/config.dat. I hope this will help you to finally nail down this nasty bug... Bye, Thorsten
Bug#931002: Updating crates for Debian stable release
I am on vacation for the next two weeks, please can someone else deal with the
following:
Due to Firefox we updated/unblocked rustc 1.34.2 for Debian Testing (and the
next Debian Stable) release.
This causes two FTBFS bugs for crates which no longer build on rustc 1.34.2:
- #931002 coresimd https://crates.io/crates/coresimd
- #931003 simd https://crates.io/crates/simd
In fact these crates are deprecated and should be RMd. We also need to:
- update encoding-rs so it doesn't depend on simd
- update packed-simd so it doesn't depend on coresimd
- package NEW core-arch package which is a new dependency of the updated
packed-simd
and unblock these.
Otherwise {encoding-rs, packed-simd} and its reverse dependencies (including
ripgrep) will have to be dropped from the next Debian Stable release.
X
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
Bug#930563: (no subject)
severity 930563 important thanks Downgrading severity since this issue is not "rendering it completely unusable to everyone."
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 930563 important Bug #930563 [freecad] Can not start freecad Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 930563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#931021: musescore: phones home, including to Google Analytics, on first start
Processing commands for cont...@bugs.debian.org: > notfound 931021 musescore-snapshot/3.1+dfsg1-1 Bug #931021 [musescore] musescore: phones home, including to Google Analytics, on first start Ignoring request to alter found versions of bug #931021 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 931021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#931021: musescore: phones home, including to Google Analytics, on first start
notfound 931021 musescore-snapshot/3.1+dfsg1-1 thanks > Bugreport for myself and for release tracking. MuseScore 3, which is currently sitting in experimental, intending to hit sid after the release, is NOT affected; disabling the web centre thingy seems to suffice. bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die!
Bug#931021: musescore: phones home, including to Google Analytics, on first start
Package: musescore Version: 2.3.2+dfsg2-6 Severity: serious Tags: security Justification: phones home Bugreport for myself and for release tracking. Dear release team, please indicate whether this is buster release-critical, I will try to fix it later tonight. On first startup, MuseScore connects to: connect2.musescore.com CNAME cds.z5r7u8v4.hwcdn.net cds.z5r7u8v4.hwcdn.net A 205.185.216.10 cds.z5r7u8v4.hwcdn.net A 205.185.216.42 (Highwinds Network Operations Center) The currently shipped HTML content makes it also connect to: www.google-analytics.comCNAME www-google-analytics.l.google.com www-google-analytics.l.google.com A 172.217.16.174 www-google-analytics.l.google.com 2A00:1450:4001:81B:0:0:0:200E Also: mc.yandex.ruA 93.158.134.119 mc.yandex.ruA 77.88.21.119 mc.yandex.ruA 87.250.250.119 mc.yandex.ruA 87.250.251.119 mc.yandex.ru2A02:6B8:0:0:0:0:1:119 And: stats.g.doubleclick.net CNAME stats.l.doubleclick.net stats.l.doubleclick.net A 74.125.133.155 stats.l.doubleclick.net A 74.125.133.156 stats.l.doubleclick.net A 74.125.133.157 stats.l.doubleclick.net A 74.125.133.154 stats.l.doubleclick.net 2A00:1450:400C:C0B:0:0:0:9D I’ll simply remove the offending “web start centre” functionality, given that MuseScore 3.x will not ship it either anyway (for tech reasons). -- System Information: Debian Release: 10.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages musescore depends on: ii desktop-file-utils 0.23-4 ii libasound2 1.1.8-1+x32.1 ii libc62.28-10 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.3.0-7 ii libportaudio219.6.0-1 ii libportmidi0 1:217-6 ii libpulse012.2-4 ii libqt5core5a 5.11.3+dfsg1-2 ii libqt5gui5 5.11.3+dfsg1-2 ii libqt5help5 5.11.3-4 ii libqt5network5 5.11.3+dfsg1-2 ii libqt5printsupport5 5.11.3+dfsg1-2 ii libqt5qml5 5.11.3-4 ii libqt5quick5 5.11.3-4 ii libqt5sql5-sqlite5.11.3+dfsg1-2 ii libqt5svg5 5.11.3-2 ii libqt5webkit55.212.0~alpha2-21 ii libqt5widgets5 5.11.3+dfsg1-2 ii libqt5xml5 5.11.3+dfsg1-2 ii libqt5xmlpatterns5 5.11.3-2 ii libsndfile1 1.0.28-6 ii libstdc++6 8.3.0-7 ii libvorbisfile3 1.3.6-2 ii musescore-common 2.3.2+dfsg3-2 ii qml-module-qtquick-controls 5.11.3-2 ii qml-module-qtquick-dialogs 5.11.3-2 ii qml-module-qtquick-layouts 5.11.3-4 ii qml-module-qtquick2 5.11.3-4 ii shared-mime-info 1.10-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages musescore recommends: ii libmp3lame0 3.100-2+b1 pn pulseaudio-utils musescore suggests no packages. -- no debconf information
Bug#930796: spindown_time and force_spindown_time are broken in hdparm 9.58+ds-1
On 6/20/19 8:42 PM, Sébastien Béhuret wrote: > Package: hdparm > Version: 9.58+ds-1 > Severity: serious > > Dear Maintainers, > > In this version of hdparm, a new option 'force_spindown_time' was > introduced to set the spindown time for disks that don't support APM. > This option is supposed to translate to hdparm -S, similarly to the > original option 'spindown_time'. > > hdparm package comes with 3 main scripts: > > 1) /usr/lib/pm-utils/power.d/95hdparm-apm > This script will translate 'force_spindown_time' to hdparm -S and apply > the option even if APM was not detected. > This is the desired behavior. > > 2) /etc/apm/event.d/20hdparm > This script will ignore /etc/hdparm.conf and apply hard-coded defaults > instead. > This behavior is unexpected. > Expected/Desired behavior: Read /etc/hdparm.conf and apply relevant options. > > 3) /lib/hdparm/hdparm-functions (sourced from /lib/udev/hdparm, which is > invoked by udev rule /lib/udev/rules.d/85-hdparm.rules) > - 'force_spindown_time' is buggy because it is not converted back to -S, > which leads to a syntax error during hdparm execution (e.g. hdparm > force_spindown_time$VALUE instead of hdparm -S$VALUE). > - Both options 'spindown_time' and 'force_spindown_time' are processed > even if APM is not supported. From the comments in the configuration > file (/etc/hdparm.conf), it is understood that 'spindown_time' will be > applied for APM disks only and 'force_spindown_time' for all disks (or > possibly for non-APM disks only). > - The scripts will also apply hard-coded defaults for -S and -B if APM > was detected. The hard-coded defaults differ from those used in > /etc/apm/event.d/20hdparm, leading to inconsistent behavior. > > 4) Additional issues with non-APM disks: > - Manually invoking hdparm -S$VALUE /dev/sdx is simply ignored even > though hdparm executes successfully. The disks do not spin down after > the time delay when there was no access. > - Manually invoking hdparm -y /dev/sdx will spin down the disks > immediately. The disks will not wake up unless they are accessed, which > is the expected behavior. > > These were all working fine in hdparm 9.51+ds-1+deb9u1, which is the > current version in stretch. > > In short, it is currently impossible to obtain a consistent and working > configuration for non-APM disks. > > Many thanks and regards, > Sebastien Behuret Hi Sebastien, 2. As APM is almost dead and most likely there are no laptops using APM and buster. I'll drop /etc/apm/event.d/20hdparm in the next release. 3. This is a real issue. In /lib/hdparm/hdparm-functions I've left the "force_spindown_time$VALUE" option intentionally, it need to be translated to "-S" later in scripts using hdparm-functions like it is done in 95hdparm-apm /lib/udev/hdparm is called by udev and need to be fixed. /usr/lib/pm-utils/power.d/95hdparm-apm called by pm-utils events and takes care only about spin_down and apm options for the disks which support apm. To obtain a consistent behavior /lib/udev/hdparm can call /usr/lib/pm-utils/power.d/95hdparm-apm for spindown and apm options and hdparm directly for all other options. 4. I failed to reproduce that. I couldn't put to standby a non-apm disk on a stretch system with hdparm -S (hdparm 9.51) Could you please try to build hdparm 9.51 or just get a binary package and run it to see if 9.51 works for your disks compared to 9.58? Thank you for the detailed report. Alex
Processed: Re: Bug#930935: webkit2gtk: Baseline violation on i386
Processing control commands: > tags -1 patch pending Bug #930935 [libjavascriptcoregtk-4.0-18] webkit2gtk: Baseline violation on i386 Added tag(s) patch and pending. -- 930935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930935: webkit2gtk: Baseline violation on i386
Control: tags -1 patch pending On Mon, Jun 24, 2019 at 10:29:56AM +0200, Alberto Garcia wrote: > 2) Build with SSE2 completely disabled (using WTF_CPU_UNKNOWN, or >somethig else, I'm still discussing this with the team). Ok, this patch disables SSE2 and forces Webkit to use CLoop, the C-based JavaScript interpreter (instead of using JIT or the asm-based intepreter). That's the one used when the CPU is unknown or not supported. If no one has anything to say I'll upload it today. This should work on all i386 CPUs, and we can later discuss if it's worth thinking of a solution for SSE2-capable machines. Berto diff --git a/debian/NEWS b/debian/NEWS index 8b5be11c238..72ce8c9fdd9 100644 --- a/debian/NEWS +++ b/debian/NEWS @@ -1,12 +1,3 @@ -webkit2gtk (2.24.1-2) unstable; urgency=high - - Since version 2.24.0, i386 builds of WebKitGTK require an SSE2-capable - CPU. This instruction set was first introduced with the Pentium 4 in - year 2000. Support for older processors was dropped in WebKitGTK - upstream and is unfortunately not expected to come back. - - -- Alberto Garcia Fri, 10 May 2019 15:40:28 +0300 - webkit2gtk (2.20.0-2) unstable; urgency=medium webkit2gtk 2.20.0 contains a security feature named Gigacage that diff --git a/debian/changelog b/debian/changelog index e5224cae539..6ddef67d1b8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,26 @@ +webkit2gtk (2.24.2-2) unstable; urgency=high + + * The WebKitGTK security advisory WSA-2019-0003 lists the following +security fixes in the latest versions of WebKitGTK+: ++ CVE-2019-8571, CVE-2019-8583, CVE-2019-8586, CVE-2019-8594, + CVE-2019-8609, CVE-2019-8611, CVE-2019-8622 and CVE-2019-8623 + (fixed in 2.24.0). ++ CVE-2019-6237, CVE-2019-8584, CVE-2019-8587, CVE-2019-8596, + CVE-2019-8597, CVE-2019-8601, CVE-2019-8608, CVE-2019-8610 and + CVE-2019-8619 (fixed in 2.24.1). ++ CVE-2019-8595, CVE-2019-8607 and CVE-2019-8615 (fixed in 2.24.2). + * Use the CLoop Javascript interpreter in i386 and stop telling gcc to +use SSE2 instructions (Closes: #930935). ++ debian/rules: + - Build with -DENABLE_JIT=OFF -DENABLE_C_LOOP=ON and stop using +-msse2 -mfpmath=sse. ++ debian/patches/dont-detect-sse2.patch: + - Don't check for SSE2 support. ++ debian/NEWS: + - Remove item about the requirement to have an SSE2-capable CPU. + + -- Alberto Garcia Mon, 24 Jun 2019 16:34:09 +0300 + webkit2gtk (2.24.2-1) unstable; urgency=medium * New upstream release. diff --git a/debian/patches/dont-detect-sse2.patch b/debian/patches/dont-detect-sse2.patch new file mode 100644 index 000..59b3650f6b6 --- /dev/null +++ b/debian/patches/dont-detect-sse2.patch @@ -0,0 +1,24 @@ +From: Alberto Garcia +Subject: Don't check for SSE2 support on i386 +Bug-Debian: https://bugs.debian.org/930935 +Forwarded: no +Index: webkitgtk/Source/cmake/WebKitCompilerFlags.cmake +=== +--- webkitgtk.orig/Source/cmake/WebKitCompilerFlags.cmake webkitgtk/Source/cmake/WebKitCompilerFlags.cmake +@@ -144,15 +144,6 @@ if (COMPILER_IS_GCC_OR_CLANG) + if (CMAKE_COMPILER_IS_GNUCXX) + WEBKIT_PREPEND_GLOBAL_COMPILER_FLAGS(-Wno-expansion-to-defined) + endif () +- +-# Force SSE2 fp on x86 builds. +-if (WTF_CPU_X86 AND NOT CMAKE_CROSSCOMPILING) +-WEBKIT_PREPEND_GLOBAL_COMPILER_FLAGS(-msse2 -mfpmath=sse) +-include(DetectSSE2) +-if (NOT SSE2_SUPPORT_FOUND) +-message(FATAL_ERROR "SSE2 support is required to compile WebKit") +-endif () +-endif () + endif () + + if (COMPILER_IS_GCC_OR_CLANG AND NOT MSVC) diff --git a/debian/patches/series b/debian/patches/series index 1bcc251ee09..12740b1f4e3 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -7,3 +7,4 @@ detect-gstreamer-gl.patch detect-woff.patch user-agent-branding.patch prefer-pthread.patch +dont-detect-sse2.patch diff --git a/debian/rules b/debian/rules index b1e8caeb46f..ae93d5e38f8 100755 --- a/debian/rules +++ b/debian/rules @@ -23,9 +23,10 @@ ifeq (,$(filter $(DEB_HOST_ARCH),amd64 ppc64 ppc64el)) CFLAGS := $(CFLAGS:-g=-g1) endif -# The 32-bit x86 build requires SSE2 +# Use the CLoop Javascript interpreter and disable the JIT. This is +# slow but it is the most compatible solution for old (non-SSE2) CPUs. ifneq (,$(filter $(DEB_HOST_ARCH),i386)) - CFLAGS += -msse2 -mfpmath=sse + EXTRA_CMAKE_ARGUMENTS += -DENABLE_JIT=OFF -DENABLE_C_LOOP=ON endif # See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81426
Processed: Re: [Pkg-xmpp-devel] Bug#930991: gajim in Debian Stable does not start anymore
Processing commands for cont...@bugs.debian.org: > tags 930991 + stretch Bug #930991 [gajim] gajim in Debian Stable does not start anymore Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 930991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908678: Update on the security-tracker git discussion
Hi, On Sun, Jun 09, 2019 at 01:48:58PM +0200, Salvatore Bonaccorso wrote: > On Sat, Jun 08, 2019 at 06:29:24PM +0200, Salvatore Bonaccorso wrote: > > Notes on possible CVE/list splits > > - > [...] > > After a face-to-face conversation with Daniel, Daniel suggested to > create a priority list out of that, we will followup with that to that > (ideally as gitlab task-list) here with a link once we have made our > minds on it. The plan was initially to do that in that week. Due to some other issues (Debian related, and other) this was not possible. The plan still holds to prioritize these tasks so that people wanting to help contribute have something to tackle. Regards, Salvatore
Bug#931003: rust-simd: FTBFS (unrecognized platform-specific intrinsic function: `x86_mm_movemask_ps`unrecognized platform-specific intrinsic function: `x86_mm_movemask_ps`)
Package: src:rust-simd
Version: 0.2.4-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --buildsystem cargo
dh_update_autotools_config -a -O--buildsystem=cargo
dh_autoreconf -a -O--buildsystem=cargo
dh_auto_configure -a -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<>/debian/cargo_registry/
dh_auto_build -a -O--buildsystem=cargo
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
export RUSTC_BOOTSTRAP=1; \
case x86_64-unknown-linux-gnu in \
aarch64-*|x86-*|x86_64-*) \
dh_auto_test;; \
*) \
dh_auto_test || true;; \
esac
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j2',
'--target', 'x86_64-unknown-linux-gnu'],) {}
Compiling simd v0.2.4 (/<>)
Running `rustc --crate-name build_script_build build.rs --color never
--crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=2a26cedc068f1b94 -C extra-filename=-2a26cedc068f1b94 --out-dir
/<>/target/debug/build/simd-2a26cedc068f1b94 -C
incremental=/<>/target/debug/incremental -L
dependency=/<>/target/debug/deps`
Running
`/<>/target/debug/build/simd-2a26cedc068f1b94/build-script-build`
[simd 0.2.4] cargo:rustc-env=RUSTC_BOOTSTRAP=1
Running `rustc --crate-name simd src/lib.rs --color never --crate-type lib
--emit=dep-info,link -C debuginfo=2 -C metadata=d42c16898eaf30fc -C
extra-filename=-d42c16898eaf30fc --out-dir
/<>/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -C
incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
-L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn
-C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix
/<>=/usr/share/cargo/registry/simd-0.2.4`
warning: unnecessary parentheses around function argument
--> src/common.rs:181:39
|
181 |$name($( ($first as $repr_elem) ),*,
| ^^ help:
remove these parentheses
...
280 | / bool_impls! {
281 | | bool32ix4: bool32i, i32x4, i32, 4, bool32ix4_all, bool32ix4_any,
x0, x1 | x2, x3
282 | | [/// Convert `self` to a boolean vector for interacting with
floating point vectors.
283 | | to_f -> bool32fx4];
... |
290 | | bool8ix16: bool8i, i8x16, i8, 16, bool8ix16_all, bool8ix16_any, x0,
x1, x2, x3, x4, x5, x6, x7 | x8, x9, x10, x11, x12, x13, x14, x15 [];
291 | | }
| |_- in this macro invocation
|
= note: #[warn(unused_parens)] on by default
warning: unnecessary parentheses around function argument
--> src/common.rs:181:39
|
181 |$name($( ($first as $repr_elem) ),*,
| ^^ help:
remove these parentheses
...
280 | / bool_impls! {
281 | | bool32ix4: bool32i, i32x4, i32, 4, bool32ix4_all, bool32ix4_any,
x0, x1 | x2, x3
282 | | [/// Convert `self` to a boolean vector for interacting with
floating point vectors.
283 | | to_f -> bool32fx4];
... |
290 | | bool8ix16: bool8i, i8x16, i8, 16, bool8ix16_all, bool8ix16_any, x0,
x1, x2, x3, x4, x5, x6, x7 | x8, x9, x10, x11, x12, x13, x14, x15 [];
291 | | }
| |_- in this macro invocation
warning: unnecessary parentheses around function argument
--> src/common.rs:182:39
|
182 | $( ($last as $repr_elem) ),*))
| ^ help:
remove these parentheses
...
280 | / bool_impls! {
281 | | bool32ix4: bool32i, i32x4, i32, 4, bool32ix4_all, bool32ix4_any,
x0, x1 | x2, x3
282 | | [/// Convert `self` to a boolean vector for interacting with
floating point vectors.
283 | | to_f -> bool32fx4];
... |
290 | | bool8ix16: bool8i, i8x16, i8, 16, bool8ix16_all, bool8ix16_any, x0,
x1, x2, x3, x4, x5, x6, x7 | x8, x9, x10, x11, x12, x13, x14, x15 [];
291 | | }
| |_- in this macro invocation
warning: unnecessary parentheses around function argument
--> src/common.rs:181:39
|
181 |$name($( ($first as $repr_elem) ),*,
| ^^ help:
remove these parentheses
|
::: src/sixty_four.rs:79:1
|
79 | / bool_impls! {
80 | |
Bug#931000: libompl-dev: missing dependency on libode-dev
Package: libompl-dev Version: 1.4.2+ds1-3 Severity: serious Justification: Policy 3.5 Hi Leo, the current version in unstable adds libode.so to the ompl.pc. This results in an error if libode-dev is not installed (it is only suggested): http://ompl.kavrakilab.org/RigidBodyPlanningWithIntegrationAndControls_8cpp_source.html $ g++ $(pkg-config --cflags --libs ompl) -o RigidBodyPlanningWithIntegrationAndControls RigidBodyPlanningWithIntegrationAndControls.cpp g++: error: /usr/lib/x86_64-linux-gnu/libode.so: No such file or directory Installing libode-dev fixes this. Filling this as a bug as I'm not sure if this intended and you expressed you are not happy with the current version in https://lists.debian.org/debian-release/2019/06/msg00526.html Cheers Jochen -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-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) LSM: AppArmor: enabled Versions of packages libompl-dev depends on: ii libboost-dev 1.67.0.1 ii libeigen3-dev 3.3.7-1 ii libompl15 1.4.2+ds1-3 libompl-dev recommends no packages. Versions of packages libompl-dev suggests: ii libode-dev 2:0.16-3 ii pkg-config 0.29-6 -- no debconf information
Bug#931002: rust-coresimd: FTBFS (unrecognized platform-specific intrinsic function: `x86_rdrand16_step`unrecognized platform-specific intrinsic function: `x86_rdrand16_step`)
Package: src:rust-coresimd
Version: 0.1.2-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --buildsystem cargo
dh_update_autotools_config -a -O--buildsystem=cargo
dh_autoreconf -a -O--buildsystem=cargo
dh_auto_configure -a -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<>/debian/cargo_registry/
dh_auto_build -a -O--buildsystem=cargo
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
export RUSTC_BOOTSTRAP=1; \
dh_auto_test
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j2',
'--target', 'x86_64-unknown-linux-gnu'],) {}
Compiling coresimd v0.1.2 (/<>)
Running `rustc --crate-name build_script_build build.rs --color never
--crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=4c9f73b74e941fa4 -C extra-filename=-4c9f73b74e941fa4 --out-dir
/<>/target/debug/build/coresimd-4c9f73b74e941fa4 -C
incremental=/<>/target/debug/incremental -L
dependency=/<>/target/debug/deps`
Running
`/<>/target/debug/build/coresimd-4c9f73b74e941fa4/build-script-build`
[coresimd 0.1.2] cargo:rustc-env=TARGET=x86_64-unknown-linux-gnu
Running `rustc --crate-name coresimd src/lib.rs --color never --crate-type
lib --emit=dep-info,link -C debuginfo=2 -C metadata=709a32ec1dae0a97 -C
extra-filename=-709a32ec1dae0a97 --out-dir
/<>/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -C
incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
-L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn
-C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix
/<>=/usr/share/cargo/registry/coresimd-0.1.2`
error: unrecognized platform-specific intrinsic function: `x86_rdrand16_step`
--> src/coresimd/x86/rdrand.rs:6:5
|
6 | fn x86_rdrand16_step() -> (u16, i32);
| ^
error: unrecognized platform-specific intrinsic function: `x86_rdrand32_step`
--> src/coresimd/x86/rdrand.rs:7:5
|
7 | fn x86_rdrand32_step() -> (u32, i32);
| ^
error: unrecognized platform-specific intrinsic function: `x86_rdseed16_step`
--> src/coresimd/x86/rdrand.rs:8:5
|
8 | fn x86_rdseed16_step() -> (u16, i32);
| ^
error: unrecognized platform-specific intrinsic function: `x86_rdseed32_step`
--> src/coresimd/x86/rdrand.rs:9:5
|
9 | fn x86_rdseed32_step() -> (u32, i32);
| ^
error: unrecognized platform-specific intrinsic function: `x86_rdrand64_step`
--> src/coresimd/x86_64/rdrand.rs:6:5
|
6 | fn x86_rdrand64_step() -> (u64, i32);
| ^
error: unrecognized platform-specific intrinsic function: `x86_rdseed64_step`
--> src/coresimd/x86_64/rdrand.rs:7:5
|
7 | fn x86_rdseed64_step() -> (u64, i32);
| ^
error: aborting due to 6 previous errors
error: Could not compile `coresimd`.
Caused by:
process didn't exit successfully: `rustc --crate-name coresimd src/lib.rs
--color never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
metadata=709a32ec1dae0a97 -C extra-filename=-709a32ec1dae0a97 --out-dir
/<>/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -C
incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
-L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn
-C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix
/<>=/usr/share/cargo/registry/coresimd-0.1.2` (exit code: 1)
dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101
make[1]: *** [debian/rules:8: override_dh_auto_test] Error 101
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-coresimd.html
where you can get a full build log if you need it.
If this is really a bug in one of the
Bug#930858: Aw: Bug#930858: gif2png: "not expected to be able to deal with arbitrarily broken input"
Hi all, this is OK for me, Because Upstream (ESR) changed programming language to "GO" recently (3.0.0) and this is not my cup of tea. I decided to orphan it, but popcorn count is low, so it should be removed. Thanks for your attention, Erik Schanze Von: "Ivo De Decker" > Hi, > > On Fri, Jun 21, 2019 at 05:16:49PM +0200, Moritz Mühlenhoff wrote: > > On Fri, Jun 21, 2019 at 02:58:00PM +0100, Colin Watson wrote: > > > At the very least, the limitation that this program cannot safely be > > > used with untrusted input needs to be prominently documented (I'd > > > suggest the package description and the manual page). web2png would be > > > harder to replace this way, but at least people wanting to make > > > straightforward use of gif2png should perhaps be advised to use some > > > other image processing system instead whose maintainers have a more > > > reasonable approach to reports of undefined behaviour in their programs. > > > > Thanks for reporting this! > > > > Let's just remove the package, we have properly maintained (and heavily > > fuzzed) alternatives like imagemagick/graphicsmagick's convert and web2png > > seems to be entirely a fringe use case. > > I added a removal hint, so it should be gone soon. > > Ivo >
Bug#930996: cloudkitty: FTBFS in buster (Can't resolve label reference for ORDER BY / GROUP BY)
Package: src:cloudkitty Version: 8.0.0-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions py3versions: no X-Python3-Version in control file, using supported versions dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc,systemd dh_update_autotools_config -i -O--buildsystem=python_distutils dh_autoreconf -i -O--buildsystem=python_distutils dh_auto_configure -i -O--buildsystem=python_distutils dh_auto_configure: Please use the third-party "pybuild" build system instead of python-distutils dh_auto_configure: This feature will be removed in compat 12. debian/rules override_dh_auto_build make[1]: Entering directory '/<>' pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions [... snipped ...] INFO [alembic.runtime.migration] Running upgrade 464e951dc3b8 -> 2ac2217dcbd9, Added support for meta collector INFO [alembic.runtime.migration] Running upgrade 2ac2217dcbd9 -> 385e33fef139, Added priority to modules_state. cloudkitty.tests.transformers.test_gnocchi.GnocchiTransformerTest.test_strip_gnocchi_volume(sqlite) cloudkitty.tests.transformers.test_gnocchi.GnocchiTransformerTest.test_strip_gnocchi_volume(sqlite) ... ok == FAIL: cloudkitty.tests.storage.v1.test_storage.StorageTotalTest.test_get_total_groupby_tenant_and_restype(sqlite,sqlalchemy,sqlalchemy) cloudkitty.tests.storage.v1.test_storage.StorageTotalTest.test_get_total_groupby_tenant_and_restype(sqlite,sqlalchemy,sqlalchemy) -- _StringException: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 758, in visit_textual_label_reference col = with_cols[element.element] KeyError: 'res_type,tenant_id' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/cloudkitty/tests/storage/v1/test_storage.py", line 249, in test_get_total_groupby_tenant_and_restype groupby=['project_id', 'type']) File "/<>/cloudkitty/storage/__init__.py", line 122, in total groupby=storage_gby) File "/<>/cloudkitty/storage/v1/sqlalchemy/__init__.py", line 134, in get_total results = q.all() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2925, in all return list(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3081, in __iter__ return self._execute_and_instances(context) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3106, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 980, in execute return meth(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 273, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1090, in _execute_clauseelement else None, File "", line 1, in File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 448, in compile return self._compiler(dialect, bind=bind, **kw) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 454, in _compiler return dialect.statement_compiler(dialect, self, **kw) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 553, in __init__ Compiled.__init__(self, dialect, statement, **kwargs) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 310, in __init__ self.string = self.process(self.statement, **compile_kwargs) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 341, in process return obj._compiler_dispatch(self, **kwargs) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/visitors.py", line 90, in _compiler_dispatch return meth(self, **kw) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 2068, in visit_select text, select, inner_columns, froms, byfrom, kwargs File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 2172, in _compose_select_body text += self.group_by_clause(select, **kwargs) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 2230, in group_by_clause group_by = select._group_by_clause._compiler_dispatch(self, **kw) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/visitors.py", line 90, in
Bug#930858: gif2png: "not expected to be able to deal with arbitrarily broken input"
Hi, On Fri, Jun 21, 2019 at 05:16:49PM +0200, Moritz Mühlenhoff wrote: > On Fri, Jun 21, 2019 at 02:58:00PM +0100, Colin Watson wrote: > > At the very least, the limitation that this program cannot safely be > > used with untrusted input needs to be prominently documented (I'd > > suggest the package description and the manual page). web2png would be > > harder to replace this way, but at least people wanting to make > > straightforward use of gif2png should perhaps be advised to use some > > other image processing system instead whose maintainers have a more > > reasonable approach to reports of undefined behaviour in their programs. > > Thanks for reporting this! > > Let's just remove the package, we have properly maintained (and heavily > fuzzed) alternatives like imagemagick/graphicsmagick's convert and web2png > seems to be entirely a fringe use case. I added a removal hint, so it should be gone soon. Ivo
Bug#930991: gajim in Debian Stable does not start anymore
On 24.06.19 11:22, W. Martin Borgert wrote: > Anyway, I suggest strongly to give Gajim >= 1 a try! Gajim > improved massively between 0.16 and 1. I'll go with that. Thanks for the hint! Yours David -- David Rabel Linux Consultant & Trainer Tel.: +49-1511-5908566 Mail: ra...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 signature.asc Description: OpenPGP digital signature
Bug#905022: Bug#908589: gcc-8 documentation packages
Hello Matthias and Dmitry, Sorry for being MIA. As I'm currently busy with my life and work, I want to give up all my packages for adoption. (I forgot about the proper procedure here, so please kindly take over as you wish.) Please let me know if a GPG-signed copy of this email is needed. Thank you! Yixuan On Mon, Jun 24, 2019 at 5:51 PM Matthias Klose wrote: > On 22.06.19 01:01, Dmitry Eremin-Solenikov wrote: > > Hello, > > > > вт, 21 мая 2019 г. в 16:58, Dmitry Eremin-Solenikov < > dbarysh...@gmail.com>: > >> > >> Hello, > >> > >> I've updated gcc-doc/gcc-doc-defaults packages to support new gcc-8 > >> documentation generation. NMU Packages are uploaded to > >> mentors.debian.net > >> for review, git trees are put on salsa.debian.org/gcc-doc (-defaults). > > > > It's been nearly a month without any response. Is it an expected thing > before > > buster release? Or should I contact debian-mentors looking for sponsors > > for these packages? > > I'm trying to stay away uploading the gcc*-doc packages. Yes, maybe > contacting > debian-mentors is the right thing to do, if Guo is MIA. >
Bug#930991: gajim in Debian Stable does not start anymore
On 2019-06-24 09:47, David Rabel wrote: > Package: gajim > Version: 0.16.6-1.1 Dear David, I'll try to analyse this problem, but don't hold your breath, because I'm a little bit busy. Anyway, I suggest strongly to give Gajim >= 1 a try! Gajim improved massively between 0.16 and 1. Installation should be more or less: $ echo deb https://deb.debian.org/debian stretch-backports main \ | sudo tee /etc/apt/sources.list.d/stretch-backports.list $ sudo apt update $ sudo apt install -t stretch-backports gajim Of course, there might be good reasons to stay with the older version and the problem still needs to be fixed. Cheers
Processed: Re: Bug#930932: zenity: Zenity crashes out on Athlon XP CPU.
Processing control commands: > reassign -1 libjavascriptcoregtk-4.0-18 2.24.2-1 Bug #930935 [src:webkit2gtk] webkit2gtk: Baseline violation on i386 Bug reassigned from package 'src:webkit2gtk' to 'libjavascriptcoregtk-4.0-18'. No longer marked as found in versions webkit2gtk/2.24.1-2. Ignoring request to alter fixed versions of bug #930935 to the same values previously set Bug #930935 [libjavascriptcoregtk-4.0-18] webkit2gtk: Baseline violation on i386 Marked as found in versions webkit2gtk/2.24.2-1. > forcemerge 930935 -1 Bug #930935 [libjavascriptcoregtk-4.0-18] webkit2gtk: Baseline violation on i386 Merged 930935 > affects 930935 zenity Bug #930935 [libjavascriptcoregtk-4.0-18] webkit2gtk: Baseline violation on i386 Added indication that 930935 affects zenity -- 930935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): Re: Bug#930932: zenity: Zenity crashes out on Athlon XP CPU.
Processing control commands: > reassign -1 libjavascriptcoregtk-4.0-18 2.24.2-1 Bug #930932 [zenity] zenity: Zenity crashes out on Athlon XP CPU. Bug reassigned from package 'zenity' to 'libjavascriptcoregtk-4.0-18'. No longer marked as found in versions zenity/3.22.0-1. Ignoring request to alter fixed versions of bug #930932 to the same values previously set Bug #930932 [libjavascriptcoregtk-4.0-18] zenity: Zenity crashes out on Athlon XP CPU. Marked as found in versions webkit2gtk/2.24.2-1. > forcemerge 930935 -1 Bug #930935 [src:webkit2gtk] webkit2gtk: Baseline violation on i386 Unable to merge bugs because: package of #930932 is 'libjavascriptcoregtk-4.0-18' not 'src:webkit2gtk' Failed to forcibly merge 930935: Did not alter merged bugs. > affects 930935 zenity Failed to mark 930935 as affecting package(s): failed to get lock on /org/bugs.debian.org/spool/lock/930935 -- Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/930935 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. -- 930932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930932 930935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930935: Bug#930932: zenity: Zenity crashes out on Athlon XP CPU.
Control: reassign -1 libjavascriptcoregtk-4.0-18 2.24.2-1 Control: forcemerge 930935 -1 Control: affects 930935 zenity On Mon, 24 Jun 2019 at 18:12:50 +1000, Iris (Delta) wrote: > Jun 24 18:09:05 Iris kernel: traps: zenity[17538] trap invalid opcode > ip:b2cb9d97 sp:bffe9550 error:0 > Jun 24 18:09:05 Iris kernel: in > libjavascriptcoregtk-4.0.so.18.13.5[b2493000+b1c000] This appears to be the same thing as #930935. zenity uses webkit2gtk (for the --html option) and that library requires SSE2. > model name : AMD Athlon(tm) XP 3200+ To give an idea of the scope of this issue, Wikipedia says this is a 15 year old CPU with a 75+ watt TDP. You might find that replacing this computer with a semi-recent laptop (for example a second-hand 64-bit laptop from the last 5 years) would not only increase performance, but also reduce electricity consumption enough to be cheaper overall. smcv
Bug#930935: webkit2gtk: Baseline violation on i386
On Mon, Jun 24, 2019 at 10:29:56AM +0200, Alberto Garcia wrote: > On Mon, Jun 24, 2019 at 12:34:26AM +0300, Adrian Bunk wrote: > > > > Building with SSE2 is not a decision made by the Debian > > > maintainers. Upstream WebKit dropped support for non-SSE2 > > > processors and the code assumes that SSE2 is always available: > > > > > >https://bugs.webkit.org/show_bug.cgi?id=194853 > > > > "as part of Igalia's work on 32bit support" > > "there were no negative comments" > > > > Someone should have told upstream at Igalia that non-SSE is > > supported by the Debian i386 port. > > This was actually discussed, IIRC the concusion was that this was > a reasonable choice because (a) SSE2 is almost 20 years old, Hardware without SSE2 was still pretty common 15 years ago (e.g. Athlon XP), and surprisingly many people still have such ancient hardware running somewhere. The non-SSE AMD Geode was quite popular in embedded devices, and is still in production. There were also many people unhappy when stretch dropped i586 support, since this dropped support for hardware they were still using. > (b) supporting non-SSE2 CPUs was increasing the maintaince burden for > upstream, and (c) other browsers had already followed the same path > for a few yeas. > > > > And so did Firefox: > > > > > >https://support.mozilla.org/en-US/kb/your-hardware-no-longer-supported > > > > The Debian maintainers have patched both Rust and Firefox to make > > them work on non-SSE i386 despite upstream no longer supporting it. > > > > There were plenty of bug reports when an SSE-using Firefox recently > > slipped through - and in general based on the numbers of bugs > > submitted non-SSE i386 has more users than half our release > > architectures combined. > > Ok, that's interesting information. > > Let's try to move forward then. I see three possibilities: > > 1) Detect SSE2 at runtime. This doesn't seem to be possible at this >point, or at least not trivially so. Although we still have the >JavaScriptCoreUseJIT variable, it's unclear whether this would be >enough. I need to test it. > > 2) Build with SSE2 completely disabled (using WTF_CPU_UNKNOWN, or >somethig else, I'm still discussing this with the team). This would >probably solve the problem but would make all i386 builds much >slower (in already slow machines) so I suppose many users would >also complain. Users on such hardware are usually aware that their hardware is slow. The slowest i386 hardware is the one without SSE, and people are running Firefox on such hardware and submit bugs when this breaks. > 3) Make two builds for i386: one with SSE2 and one without, and have >two separate packages. Maybe it's too late for this? I'm adding debian-release to Cc for that. >In any case >I think this would only affect the libjavascriptcore package, the >libwebkit2gtk build should be valid for all CPUs. So we'd have >libjavascriptcoregtk-4.0-18 and libjavascriptcoregtk-4.0-18-sse2 or >something like that. The old hardware capabilities (see ld.so(8)) could be used for providing these in one package, with runtime detection done by the dynamic linker for optimized libraries placed in /usr/lib/sse2/. > Berto 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#928631: Question
Just got a msg from Michael send to me personally, I assume by accident. Summary of the affected systems: AMD Ryzen 1700X + VEGA64 + Sid AMD Ryzen 2700X + VEGA64 + Sid AMD Ryzen 2700X + VEGA56 + Sid It's up to the maintainers, but as I said, I would be fine if severity of the bug is lowered or some other method is used so that firmware-nonfree version 20190502-1 can transition to testing and be included in Buster. signature.asc Description: This is a digitally signed message part.
Bug#905022: gcc-8 documentation packages
On 22.06.19 01:01, Dmitry Eremin-Solenikov wrote: > Hello, > > вт, 21 мая 2019 г. в 16:58, Dmitry Eremin-Solenikov : >> >> Hello, >> >> I've updated gcc-doc/gcc-doc-defaults packages to support new gcc-8 >> documentation generation. NMU Packages are uploaded to >> mentors.debian.net >> for review, git trees are put on salsa.debian.org/gcc-doc (-defaults). > > It's been nearly a month without any response. Is it an expected thing before > buster release? Or should I contact debian-mentors looking for sponsors > for these packages? I'm trying to stay away uploading the gcc*-doc packages. Yes, maybe contacting debian-mentors is the right thing to do, if Guo is MIA.
Bug#930935: webkit2gtk: Baseline violation on i386
On Mon, Jun 24, 2019 at 12:34:26AM +0300, Adrian Bunk wrote: > > Building with SSE2 is not a decision made by the Debian > > maintainers. Upstream WebKit dropped support for non-SSE2 > > processors and the code assumes that SSE2 is always available: > > > >https://bugs.webkit.org/show_bug.cgi?id=194853 > > "as part of Igalia's work on 32bit support" > "there were no negative comments" > > Someone should have told upstream at Igalia that non-SSE is > supported by the Debian i386 port. This was actually discussed, IIRC the concusion was that this was a reasonable choice because (a) SSE2 is almost 20 years old, (b) supporting non-SSE2 CPUs was increasing the maintaince burden for upstream, and (c) other browsers had already followed the same path for a few yeas. > > And so did Firefox: > > > >https://support.mozilla.org/en-US/kb/your-hardware-no-longer-supported > > The Debian maintainers have patched both Rust and Firefox to make > them work on non-SSE i386 despite upstream no longer supporting it. > > There were plenty of bug reports when an SSE-using Firefox recently > slipped through - and in general based on the numbers of bugs > submitted non-SSE i386 has more users than half our release > architectures combined. Ok, that's interesting information. Let's try to move forward then. I see three possibilities: 1) Detect SSE2 at runtime. This doesn't seem to be possible at this point, or at least not trivially so. Although we still have the JavaScriptCoreUseJIT variable, it's unclear whether this would be enough. I need to test it. 2) Build with SSE2 completely disabled (using WTF_CPU_UNKNOWN, or somethig else, I'm still discussing this with the team). This would probably solve the problem but would make all i386 builds much slower (in already slow machines) so I suppose many users would also complain. 3) Make two builds for i386: one with SSE2 and one without, and have two separate packages. Maybe it's too late for this? In any case I think this would only affect the libjavascriptcore package, the libwebkit2gtk build should be valid for all CPUs. So we'd have libjavascriptcoregtk-4.0-18 and libjavascriptcoregtk-4.0-18-sse2 or something like that. Berto
Bug#927226: libpaper1: Fresh RC1 install doesn't configure /etc/papersize
Hello Thorsten, Voip, and Jacob, I think the problem has been solved in version 1.1.27, currently in unstable. I would really appreciate if you could test it, as well as I did. If this package passes your tests, I will ask for an unblock that will let the package migrate to testing/buster in a few days. Bye, Giuseppe Il giorno mar, 16/04/2019 alle 16.35 +0200, Thorsten Ehlers ha scritto: > Package: libpaper1 > Version: 1.1.26 > Severity: normal > Tags: d-i > > Dear Maintainer, > >* What led up to the situation? > > I did a fresh installation with RC1 Debian installer > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I chose German/Germany locale in the install process but got a > "letter" instead > of "a4" default in /etc/papersize > >* What was the outcome of this action? > > bad formatted prints > > I had to start "dpkg-reconfigure libpaper1" manually and choose A4 > here, this > should be part of the installation process. In fact it was in earlier > alpha > versions of the installer.
Bug#930991: gajim in Debian Stable does not start anymore
Package: gajim Version: 0.16.6-1.1 Severity: grave Justification: renders package unusable Dear Maintainer, last week I noticed, that gajim does not start anymore in Debian Stable. Trying to start it from the commandline: $ gajim Traceback (most recent call last): File "gajim.py", line 327, in OpenSSL.rand.load_file(str(RNG_SEED)) File "/usr/lib/python2.7/dist-packages/OpenSSL/rand.py", line 178, in load_file return _lib.RAND_load_file(filename, maxbytes) AttributeError: 'module' object has no attribute 'RAND_load_file' Regards David -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-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 gajim depends on: ii dnsutils1:9.10.3.dfsg.P4-12.3+deb9u5 ii python 2.7.13-2 ii python-gtk2 2.24.0-5.1 ii python-nbxmpp 0.5.4-1 ii python-openssl 16.2.0-1 ii python-pyasn1 0.1.9-2 Versions of packages gajim recommends: ii alsa-utils 1.1.3-1 ii ca-certificates 20161130+nmu1 ii cinnamon [notification-daemon] 3.2.7-4 ii dbus1.10.28-0+deb9u1 ii pulseaudio-utils10.0-1 ii python-crypto 2.6.1-7 ii python-dbus 1.2.4-1+b1 Versions of packages gajim suggests: ii aspell-de [aspell-dictionary] 20161207-1 ii aspell-de-1901 [aspell-dictionary] 1:2-31 ii aspell-en [aspell-dictionary] 2016.11.20-0-0.1 ii avahi-daemon0.6.32-2 pn dvipng ii gnome-keyring 3.20.0-3 pn gstreamer0.10-plugins-ugly pn kwalletcli ii libgtkspell02.0.16-1.1 ii libxss1 1:1.2.2-1 pn nautilus-sendto ii network-manager 1.6.2-3 pn python-avahi ii python-gconf2.28.1+dfsg-1.2 ii python-gnome2 2.28.1+dfsg-1.2 pn python-gnomekeyring pn python-gupnp-igd ii python-kerberos 1.1.5-2+b2 ii python-pycurl 7.43.0-2 ii texlive-latex-base 2016.20170123-5 -- no debconf information
