Processed: tagging 921365
Processing commands for cont...@bugs.debian.org: > tags 921365 + buster sid Bug #921365 [node-async-stacktrace] Not suitable for buster, package probably unmaintained Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 921365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921360
Processing commands for cont...@bugs.debian.org: > tags 921360 + buster sid Bug #921360 [node-base64id] No suitable for buster, package probably unmaintained Bug #921368 [node-base64id] Not suitable for buster, package probably unmaintained Ignoring request to alter tags of bug #921360 to the same tags previously set Ignoring request to alter tags of bug #921368 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 921360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921360 921368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921363
Processing commands for cont...@bugs.debian.org: > tags 921363 + buster sid Bug #921363 [src:ejs.js] Not suitable for buster, package unmaintained Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921362
Processing commands for cont...@bugs.debian.org: > tags 921362 + buster sid Bug #921362 [src:bignumber.js] Not suitable for buster, package unmaintained Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 921362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921367
Processing commands for cont...@bugs.debian.org: > tags 921367 + buster sid Bug #921367 [src:unorm.js] Not suitable for buster, package probably unmaintained Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921358
Processing commands for cont...@bugs.debian.org: > tags 921358 + buster sid Bug #921358 [node-yajsml] Not suitable for buster, package probably unmaintained Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921359
Processing commands for cont...@bugs.debian.org: > tags 921359 + buster sid Bug #921359 [node-security] Not suitable for buster, package probably unmaintained Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921366
Processing commands for cont...@bugs.debian.org: > tags 921366 + buster sid Bug #921366 [src:zeparser.js] Not suitable for buster, package probably unmaintained Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921364
Processing commands for cont...@bugs.debian.org: > tags 921364 + buster sid Bug #921364 [node-active-x-obfuscator] Not suitable for buster, package unmaintained Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 921364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921356
Processing commands for cont...@bugs.debian.org:
> tags 921356 + buster sid
Bug #921356 {Done: Xavier Guimard } [node-tinycolor] Not
suitable for buster, package probably unmaintained
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 921369
Processing commands for cont...@bugs.debian.org: > tags 921369 + buster sid Bug #921369 [node-xmlhttprequest] Not suitable for buster, package probably unmaintained Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921370
Processing commands for cont...@bugs.debian.org: > tags 921370 + buster sid Bug #921370 [src:yamm3] Not suitable for buster, package probably unmaintained Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 921371
Processing commands for cont...@bugs.debian.org: > tags 921371 + buster sid Bug #921371 [node-log4js] Not suitable for buster, package probably unmaintained Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 921371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#915657 closed by Helge Kreutzmann (Bug#915657: fixed in google-android-installers 1472023576+nmu2)
Processing control commands:
> reopen -1
Bug #915657 {Done: Helge Kreutzmann }
[src:google-android-installers] google-android-installers NMU binaries cannot
be installed due to unchanged version of the binary packages
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions google-android-installers/1472023576+nmu2.
--
915657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915657: closed by Helge Kreutzmann (Bug#915657: fixed in google-android-installers 1472023576+nmu2)
Control: reopen -1 On Mon, Feb 04, 2019 at 12:36:08PM +, Debian Bug Tracking System wrote: >... > google-android-installers (1472023576+nmu2) unstable; urgency=medium > . >* Non-maintainer upload >* Explicitly increment version numbers. Closes: #915657. >... Your upload included the binary package google-android-build-tools-19-installer, version 19.0.3, for amd64, however stable already has version 19.0.3. 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#921369: Bug #921369 in node-xmlhttprequest marked as pending
Control: tag -1 pending Hello, Bug #921369 in node-xmlhttprequest 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/js-team/node-xmlhttprequest/commit/131f5e85c489ca845f3e7cd5cae4be7e0d54cd28 Replace Mike Gabriel by me in uploaders. Thanks for your work! Closes: #921369 (this message was generated automatically) -- Greetings https://bugs.debian.org/921369
Bug#921376: frr: missing Breaks+Replaces
Hi Andreas,
I've added Conflicts: lines, as that seemed to be the most conservative
option to me. ("Replaces: quagga" is a 'layer 9' discussion that I
think it's a bit early to have at this point.)
If you have any comments/opinions/input, I'd appreciate that.
Diff is at:
https://github.com/FRRouting/frr/commit/7ad413ce0ff5295fbbab840be533b3eb112c0dc8
Cheers,
-David
Bug#921369: Bug #921369 in node-xmlhttprequest marked as pending
Hi Xavier, On Monday, 4 February 2019, Xavier Guimard wrote: > Control: tag -1 pending > > Hello, > > Bug #921369 in node-xmlhttprequest 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/js-team/node-xmlhttprequest/commit/131f5e85c489ca845f3e7cd5cae4be7e0d54cd28 > > > Replace Mike Gabriel by me in uploaders. Thanks for your work! > > Closes: #921369 > > > (this message was generated automatically) > -- > Greetings > > https://bugs.debian.org/921369 > Thanks for adopting this ( and other ) js pkgs from me. Mike -- Sent from my Sailfish device
Processed: reassign 909165 to linkchecker, forcibly merging 901780 909165, fixed 901780 in 9.4.0-2
Processing commands for cont...@bugs.debian.org: > reassign 909165 linkchecker Bug #909165 [linkchecker-gui] linkchecker-gui: linkcheker-gui does not start Bug reassigned from package 'linkchecker-gui' to 'linkchecker'. No longer marked as found in versions linkchecker/9.3-4. Ignoring request to alter fixed versions of bug #909165 to the same values previously set > forcemerge 901780 909165 Bug #901780 [linkchecker] linkchecker: Should depend on python-xdg Bug #909165 [linkchecker] linkchecker-gui: linkcheker-gui does not start Marked as found in versions linkchecker/9.4.0-1. Merged 901780 909165 > fixed 901780 9.4.0-2 Bug #901780 [linkchecker] linkchecker: Should depend on python-xdg Bug #909165 [linkchecker] linkchecker-gui: linkcheker-gui does not start Marked as fixed in versions linkchecker/9.4.0-2. Marked as fixed in versions linkchecker/9.4.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 901780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901780 909165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921376: frr: missing Breaks+Replaces
Hi David,
On 2019-02-04 22:01, David Lamparter wrote:
> I've added Conflicts: lines, as that seemed to be the most conservative
> option to me. ("Replaces: quagga" is a 'layer 9' discussion that I
> think it's a bit early to have at this point.)
>
> If you have any comments/opinions/input, I'd appreciate that.
Looks good to me. You can reconsider the Breaks+Replaces once you
implement whatever conclusion such a 'layer 9' discussion has reached.
I'll come back to you in case you missed to Conflicts: some package :-)
Andreas
Bug#921356: marked as done (Not suitable for buster, package probably unmaintained)
Your message dated Mon, 04 Feb 2019 19:36:46 + with message-id and subject line Bug#921356: fixed in node-tinycolor 0.0.1-1 has caused the Debian Bug report #921356, regarding Not suitable for buster, package probably unmaintained 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.) -- 921356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-tinycolor Version: 0.0.1~git20130725-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-tinycolor depends on: ii nodejs 4.8.2~dfsg-1 node-tinycolor recommends no packages. node-tinycolor suggests no packages. --- End Message --- --- Begin Message --- Source: node-tinycolor Source-Version: 0.0.1-1 We believe that the bug you reported is fixed in the latest version of node-tinycolor, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-tinycolor 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: Mon, 04 Feb 2019 20:18:56 +0100 Source: node-tinycolor Binary: node-tinycolor Architecture: source Version: 0.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 921356 Description: node-tinycolor - No-fuzz, barebone, zero muppetry color module for Node.js Changes: node-tinycolor (0.0.1-1) unstable; urgency=medium . * Add minimal test based on pkg-js-tools * Bump debhelper compatibility version to 11 * Declare compliance with policy 4.3.0 * Change section to javascript * Change prioroty to optional * Update VCS fields to salsa * Add upstream/metadata * Add Berne Convention comment in debian/copyright * Replace Mike Gabriel by me in uploaders. Thanks for your work! (Closes: #921356) * Fix install * Add minimal autopkgtest file * Hide false positive lintian error Checksums-Sha1: 1b74caca8ce8e09492ba6334d50ed26db9020c31 2032 node-tinycolor_0.0.1-1.dsc 320b5a52d83abb5978d81a3e887d4aefb15a6164 1006 node-tinycolor_0.0.1.orig.tar.gz 7d638061d87b9f3244d01d45ca6bb95ca33648e4 2696 node-tinycolor_0.0.1-1.debian.tar.xz Checksums-Sha256: b1199df75390adf3dd26726a6997565608c7f5c9dc96d0f842f0343a97a7864d 2032 node-tinycolor_0.0.1-1.dsc f5aaf5df002750c4af19181988c8789c9e230445747e511dde7c660424f286a0 1006 node-tinycolor_0.0.1.orig.tar.gz 8120571977e84c5655df84fb6199ad8a42968d25439fb131446f779efd324b63 2696 node-tinycolor_0.0.1-1.debian.tar.xz Files: 9629e52bd82b8c6b85c8c9a666e32bc8 2032 javascript optional node-tinycolor_0.0.1-1.dsc 795da891c356e097957f541ad6755eb4 1006 javascript optional node-tinycolor_0.0.1.orig.tar.gz d809521f64b52350703e8949eb8e641a 2696 javascript optional node-tinycolor_0.0.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxYkL4ACgkQ9tdMp8mZ 7ukBeA/9GSBXu/Vkm478ID10d6CFeQTyiSpFbqyhj1nPtFSBi2SwacEjImrgPJs4 3bNIr28hdMXfacNZb60GWexJE8ZypGhn0DX7Zr0asjSrpVutVSONkGxbHML/EbrW HwhCtNXgHu5DJtjiyANJrYvJ5UPAG84RmTez938mf5rrtwhIudrUZSEgVMrE5oS2 xB/9UAe0HCvS5UV69HYaLmzUc2rUafi9d+5MAw/zBG0+z818/XhlrRWC79g15gJX 2On62YwJ88W3r7eRr5dWRhJp7yOH2hlWA959O6og+4/EB7aIZuRjqbiOz0jvy+cd z9+mKN1RIA4+WgCYHqB2p27fmrqTi7/IexmahXNWLoE+aI2eeWMtvupfd/OPiXnh dEQ1UIiNxmFs96+wWZZacXyfDL7M2jFLqueG9MfFylkeBi0mLob6ZVCt6TnkeEQH
Processed (with 1 error): Re: Bug#909165: linkchecker-gui: linkcheker-gui does not start
Processing control commands: > merge 909165 901780 Bug #909165 [linkchecker-gui] linkchecker-gui: linkcheker-gui does not start Unable to merge bugs because: done of #901780 is 'Antoine Beaupré ' not '' package of #901780 is 'linkchecker' not 'linkchecker-gui' Failed to merge 909165: Did not alter merged bugs. -- 901780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901780 909165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915023: marked as done (openstack-dashboard: fails to install in buster along python3-senlin-dashboard)
Your message dated Mon, 04 Feb 2019 19:49:40 + with message-id and subject line Bug#915023: fixed in horizon 3:14.0.2-1 has caused the Debian Bug report #915023, regarding openstack-dashboard: fails to install in buster along python3-senlin-dashboard 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.) -- 915023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openstack-dashboard Version: 3:14.0.0-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + python3-senlin-dashboard Control: found -1 python3-senlin-dashboard/0.9.0-2 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): [...] Copying '/usr/lib/python3/dist-packages/horizon/static/auth/login/login.controller.spec.js' Copying '/usr/lib/python3/dist-packages/horizon/static/auth/login/login.controller.js' Copying '/usr/lib/python3/dist-packages/horizon/static/auth/login/login-finder.directive.js' 2674 static files copied to '/usr/share/openstack-dashboard/static'. INFO:keyring.backend:Loading KWallet INFO:keyring.backend:Loading SecretService INFO:keyring.backend:Loading Windows INFO:keyring.backend:Loading chainer INFO:keyring.backend:Loading macOS Found 'compress' tags in: /usr/share/openstack-dashboard/openstack_dashboard/templates/horizon/_scripts.html /usr/share/openstack-dashboard/openstack_dashboard/templates/serial_console.html /usr/share/openstack-dashboard/openstack_dashboard/templates/horizon/_conf.html /usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html [ESC][31;1mCommandError: An error occurred during rendering /usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html: Couldn't find anything to import: /app/core/cluster.scss Extensions: , , Search path: on line 1 of 'string:299652627aecc518:\n// My Themes\n@import "/themes/default/variables";\n\n// Horizon\n@import "/dashboard/scss/horizon.' [ESC][0mCompressing... dpkg: error processing package openstack-dashboard (--configure): installed openstack-dashboard package post-installation script subprocess returned error exit status 1 Setting up python3-senlinclient (1.8.0-2) ... dpkg: dependency problems prevent configuration of python3-senlin-dashboard: python3-senlin-dashboard depends on openstack-dashboard (>= 3:14.0.0~rc1); however: Package openstack-dashboard is not configured yet. dpkg: error processing package python3-senlin-dashboard (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.27-8) ... Processing triggers for ca-certificates (20170717) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: openstack-dashboard python3-senlin-dashboard cheers, Andreas python3-senlin-dashboard_0.9.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: horizon Source-Version: 3:14.0.2-1 We believe that the bug you reported is fixed in the latest version of horizon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michal Arbet (supplier of updated horizon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 19:50:30 +0100 Source: horizon Binary: horizon-doc openstack-dashboard openstack-dashboard-apache python3-django-horizon Architecture: source all Version: 3:14.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Michal Arbet Description: horizon-doc - web application to control an OpenStack cloud - doc openstack-dashboard - web application to control an OpenStack cloud openstack-dashboard-apache - web application to control an
Bug#909165: linkchecker-gui: linkcheker-gui does not start
Control: merge 909165 901780 This is a duplicate of #901780 which was reported in june 2018 and fixed, although no fix has been done in stretch yet. A. On Wed, Sep 19, 2018 at 09:40:28AM +0200, jEsuSdA wrote: > Package: linkchecker-gui > Version: 9.3-4 > Severity: important > > Dear Maintainer, > > Linkcheker-gui does not start. > > Here is the ouput: > > linkchecker-gui > Traceback (most recent call last): > File "/usr/bin/linkchecker-gui", line 78, in > main() > File "/usr/bin/linkchecker-gui", line 68, in main > window = LinkCheckerMain(**mainkwargs) > File "/usr/lib/python2.7/dist-packages/linkcheck/gui/__init__.py", line 121, > in __init__ > self.init_menu() > File "/usr/lib/python2.7/dist-packages/linkcheck/gui/__init__.py", line 142, > in init_menu > self.urlinput.addMenuEntries(self.menuEdit) > File "/usr/lib/python2.7/dist-packages/linkcheck/gui/lineedit.py", line 179, > in addMenuEntries > if find_chrome(): > File "/usr/lib/python2.7/dist-packages/linkcheck/gui/lineedit.py", line 207, > in find_chrome > from ..bookmarks.chrome import find_bookmark_file > File "/usr/lib/python2.7/dist-packages/linkcheck/bookmarks/chrome.py", line > 20, in > from xdg import xdg_config_home > ImportError: cannot import name xdg_config_home > > > Maybe any missing dependency? > Thanks! > > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), > LANGUAGE=es_ES.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages linkchecker-gui depends on: > ii libqt4-sql-sqlite 4:4.8.7+dfsg-17 > ii linkchecker9.4.0-2 > ii python 2.7.15-3 > ii python-qt4 4.12.1+dfsg-2+b1 > ii python-qt4-sql 4.12.1+dfsg-2+b1 > > Versions of packages linkchecker-gui recommends: > ii python-qscintilla2 2.10.4+dfsg-1+b1 > > linkchecker-gui suggests no packages. > > -- no debconf information -- signature.asc Description: PGP signature
Processed (with 1 error): Re: Bug#909165: linkchecker-gui: linkcheker-gui does not start
Processing control commands: > merge 909165 901780 Bug #909165 [linkchecker-gui] linkchecker-gui: linkcheker-gui does not start Unable to merge bugs because: done of #901780 is 'Antoine Beaupré ' not '' package of #901780 is 'linkchecker' not 'linkchecker-gui' Failed to merge 909165: Did not alter merged bugs. -- 901780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901780 909165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libgd2: diff for NMU version 2.2.5-5.1
Processing control commands: > tags 920645 + pending Bug #920645 [src:libgd2] libgd2: CVE-2019-6977 Added tag(s) pending. > tags 920728 + patch Bug #920728 [src:libgd2] libgd2: CVE-2019-6978 Added tag(s) patch. > tags 920728 + pending Bug #920728 [src:libgd2] libgd2: CVE-2019-6978 Added tag(s) pending. -- 920645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920645 920728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920645: libgd2: diff for NMU version 2.2.5-5.1
Control: tags 920645 + pending
Control: tags 920728 + patch
Control: tags 920728 + pending
Dear maintainer,
I've prepared an NMU for libgd2 (versioned as 2.2.5-5.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru libgd2-2.2.5/debian/changelog libgd2-2.2.5/debian/changelog
--- libgd2-2.2.5/debian/changelog 2018-10-28 23:20:23.0 +0100
+++ libgd2-2.2.5/debian/changelog 2019-02-02 10:55:00.0 +0100
@@ -1,3 +1,12 @@
+libgd2 (2.2.5-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Heap-based buffer overflow in gdImageColorMatch (CVE-2019-6977)
+(Closes: #920645)
+ * Potential double-free in gdImage*Ptr() (CVE-2019-6978) (Closes: #920728)
+
+ -- Salvatore Bonaccorso Sat, 02 Feb 2019 10:55:00 +0100
+
libgd2 (2.2.5-5) unstable; urgency=medium
* Update Vcs-* links to salsa.d.o
diff -Nru libgd2-2.2.5/debian/patches/CVE-2019-6977.patch libgd2-2.2.5/debian/patches/CVE-2019-6977.patch
--- libgd2-2.2.5/debian/patches/CVE-2019-6977.patch 1970-01-01 01:00:00.0 +0100
+++ libgd2-2.2.5/debian/patches/CVE-2019-6977.patch 2019-02-02 10:55:00.0 +0100
@@ -0,0 +1,28 @@
+Description: Heap-based buffer overflow in gdImageColorMatch
+Origin: other, https://gist.github.com/cmb69/1f36d285eb297ed326f5c821d7aafced
+Bug-PHP: https://bugs.php.net/bug.php?id=77270
+Bug-Debian: https://bugs.debian.org/920645
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-6977
+Forwarded: no
+Author: "Christoph M. Becker"
+Last-Update: 2019-02-01
+
+At least some of the image reading functions may return images which
+use color indexes greater than or equal to im->colorsTotal. We cater
+to this by always using a buffer size which is sufficient for
+`gdMaxColors` in `gdImageColorMatch()`.
+---
+
+--- a/src/gd_color_match.c
b/src/gd_color_match.c
+@@ -31,8 +31,8 @@ BGD_DECLARE(int) gdImageColorMatch (gdIm
+ return -4; /* At least 1 color must be allocated */
+ }
+
+- buf = (unsigned long *)gdMalloc(sizeof(unsigned long) * 5 * im2->colorsTotal);
+- memset (buf, 0, sizeof(unsigned long) * 5 * im2->colorsTotal );
++ buf = (unsigned long *)gdMalloc(sizeof(unsigned long) * 5 * gdMaxColors);
++ memset (buf, 0, sizeof(unsigned long) * 5 * gdMaxColors );
+
+ for (x=0; x < im1->sx; x++) {
+ for( y=0; ysy; y++ ) {
diff -Nru libgd2-2.2.5/debian/patches/Fix-492-Potential-double-free-in-gdImage-Ptr.patch libgd2-2.2.5/debian/patches/Fix-492-Potential-double-free-in-gdImage-Ptr.patch
--- libgd2-2.2.5/debian/patches/Fix-492-Potential-double-free-in-gdImage-Ptr.patch 1970-01-01 01:00:00.0 +0100
+++ libgd2-2.2.5/debian/patches/Fix-492-Potential-double-free-in-gdImage-Ptr.patch 2019-02-02 10:55:00.0 +0100
@@ -0,0 +1,259 @@
+From: "Christoph M. Becker"
+Date: Thu, 17 Jan 2019 11:54:55 +0100
+Subject: Fix #492: Potential double-free in gdImage*Ptr()
+Origin: https://github.com/libgd/libgd/commit/553702980ae89c83f2d6e254d62cf82e204956d0
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-6978
+Bug-Debian: https://bugs.debian.org/920728
+Bug: https://github.com/libgd/libgd/issues/492
+
+Whenever `gdImage*Ptr()` calls `gdImage*Ctx()` and the latter fails, we
+must not call `gdDPExtractData()`; otherwise a double-free would
+happen. Since `gdImage*Ctx()` are void functions, and we can't change
+that for BC reasons, we're introducing static helpers which are used
+internally.
+
+We're adding a regression test for `gdImageJpegPtr()`, but not for
+`gdImageGifPtr()` and `gdImageWbmpPtr()` since we don't know how to
+trigger failure of the respective `gdImage*Ctx()` calls.
+
+This potential security issue has been reported by Solmaz Salimi (aka.
+Rooney).
+---
+
+--- a/src/gd_gif_out.c
b/src/gd_gif_out.c
+@@ -99,6 +99,7 @@ static void char_init(GifCtx *ctx);
+ static void char_out(int c, GifCtx *ctx);
+ static void flush_char(GifCtx *ctx);
+
++static int _gdImageGifCtx(gdImagePtr im, gdIOCtxPtr out);
+
+
+
+@@ -131,8 +132,11 @@ BGD_DECLARE(void *) gdImageGifPtr(gdImag
+ void *rv;
+ gdIOCtx *out = gdNewDynamicCtx(2048, NULL);
+ if (out == NULL) return NULL;
+- gdImageGifCtx(im, out);
+- rv = gdDPExtractData(out, size);
++ if (!_gdImageGifCtx(im, out)) {
++ rv = gdDPExtractData(out, size);
++ } else {
++ rv = NULL;
++ }
+ out->gd_free(out);
+ return rv;
+ }
+@@ -221,6 +225,12 @@ BGD_DECLARE(void) gdImageGif(gdImagePtr
+ */
+ BGD_DECLARE(void) gdImageGifCtx(gdImagePtr im, gdIOCtxPtr out)
+ {
++ _gdImageGifCtx(im, out);
++}
++
++/* returns 0 on success, 1 on failure */
++static int _gdImageGifCtx(gdImagePtr im, gdIOCtxPtr out)
++{
+ gdImagePtr pim = 0, tim = im;
+ int interlace, BitsPerPixel;
+ interlace = im->interlace;
+@@ -231,7 +241,7 @@ BGD_DECLARE(void) gdImageGifCtx(gdImageP
+ based temporary image. */
+ pim = gdImageCreatePaletteFromTrueColor(im, 1, 256);
+ if(!pim) {
+- return;
++ return 1;
+ }
+ tim = pim;
+ }
+@@ -247,6 +257,8 @@
Processed: libgd2: diff for NMU version 2.2.5-5.1
Processing control commands: > tags 920645 + pending Bug #920645 [src:libgd2] libgd2: CVE-2019-6977 Ignoring request to alter tags of bug #920645 to the same tags previously set > tags 920728 + patch Bug #920728 [src:libgd2] libgd2: CVE-2019-6978 Ignoring request to alter tags of bug #920728 to the same tags previously set > tags 920728 + pending Bug #920728 [src:libgd2] libgd2: CVE-2019-6978 Ignoring request to alter tags of bug #920728 to the same tags previously set -- 920645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920645 920728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): unarchiving 901780, reopening 901780, forcibly merging 901780 909165
Processing commands for cont...@bugs.debian.org:
> unarchive 901780
Bug #901780 {Done: Antoine Beaupré } [linkchecker]
linkchecker: Should depend on python-xdg
Unarchived Bug 901780
> reopen 901780
Bug #901780 {Done: Antoine Beaupré } [linkchecker]
linkchecker: Should depend on python-xdg
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linkchecker/9.4.0-2.
> forcemerge 901780 909165
Bug #901780 [linkchecker] linkchecker: Should depend on python-xdg
Unable to merge bugs because:
package of #909165 is 'linkchecker-gui' not 'linkchecker'
Failed to forcibly merge 901780: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
901780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901780
909165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#897945: [Openjdk] Bug#920037: Bug#897945: #897945 still present/breaks with Java 8
On Mon, Feb 04, 2019 at 03:04:41PM +0100, Markus Koschany wrote: > I would add a NEWS file to OpenJDK 8 and explain the situation and in > addition create a wrapper around the OpenJDK 8 java command that prints > out a message and quits. javac shall continue to work because it is > needed to build some packages. The debconf approach could also work but > it is a bit more work to implement. Then we also announce it via release > news. Just some thoughts. What is the specific use case for this, is there some package which needs 8 and can't be fixed in time for 11? If we do keep openjdk-8 after all, could we simply omit the jre binary packages when building for distrel=buster? That should ensure that noone uses an unsupported Java (along with a NEWS file maybe) to run Java applications. Cheers, Moritz
Bug#918807: taurus: diff for NMU version 4.0.3+dfsg-1.1
On Mon, Feb 04, 2019 at 05:49:24PM +, PICCA Frederic-Emmanuel wrote: > The upstream, Just packages the latest taurus. > > So I think that you can defer your upload now. Thanks, I've cancelled my NMU. > thanks a lot for your help. > > Frederic 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#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
Hi Andreas, So I improved the upstream libmurmurhash, adapted the package and filed an ITP (#921353). I even managed to locally build mash against the new package. So hereby I kindly ask you to fix the last lintian issue about NMU which I don't fully understand and then maybe sponsor an upload. Best Fabian
Bug#921355: libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c
Source: libpng1.6 Version: 1.6.36-3 Severity: grave Tags: security upstream Forwarded: https://github.com/glennrp/libpng/issues/275 Control: found -1 1.6.28-1 Control: found -1 1.6.36-2 Hi, The following vulnerability was published for libpng1.6. CVE-2019-7317[0]: | png_image_free in png.c in libpng 1.6.36 has a use-after-free because | png_image_free_function is called under png_safe_execute. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-7317 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7317 [1] https://github.com/glennrp/libpng/issues/275 Regards, Salvatore
Processed: libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c
Processing control commands: > found -1 1.6.28-1 Bug #921355 [src:libpng1.6] libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c Marked as found in versions libpng1.6/1.6.28-1. > found -1 1.6.36-2 Bug #921355 [src:libpng1.6] libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c Marked as found in versions libpng1.6/1.6.36-2. -- 921355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921367: Not suitable for buster, package probably unmaintained
Source: unorm.js Version: 1.0.5-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921370: Not suitable for buster, package probably unmaintained
Source: yamm3 Version: 1.1.0+dfsg1-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921371: Not suitable for buster, package probably unmaintained
Package: node-log4js Version: 0.6.18-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-log4js depends on: ii node-async 0.8.0-1 ii nodejs 4.8.2~dfsg-1 node-log4js recommends no packages. node-log4js suggests no packages. -- no debconf information
Bug#921365: Not suitable for buster, package probably unmaintained
Package: node-async-stacktrace Version: 0.0.2-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-async-stacktrace depends on: ii nodejs 4.8.2~dfsg-1 node-async-stacktrace recommends no packages. node-async-stacktrace suggests no packages. -- no debconf information
Bug#921369: Not suitable for buster, package probably unmaintained
Package: node-xmlhttprequest Version: 1.6.0-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-xmlhttprequest depends on: ii nodejs 4.8.2~dfsg-1 node-xmlhttprequest recommends no packages. node-xmlhttprequest suggests no packages. -- no debconf information
Bug#921369: [Pkg-javascript-devel] Bug#921369: Not suitable for buster, package probably unmaintained
This is used in: flashproxy (popcon 25), node-d3-request (popcon 2), node-xmlhttprequest-ssl (popcon 14) Paolo Il 04/02/19 17:35, Mike Gabriel ha scritto: > Package: node-xmlhttprequest > Version: 1.6.0-1 > Severity: serious > > Dear all, > > In 2016/12 I removed my name from this package's Uploaders: field. It > hasn't been touch sinced then and seems unmaintained. > > Due to this, the package might not be suitable for the Debian buster > release. This needs to be checked by someone with more involvement in > Javascript packaging than me. Thanks! > > light+love, > Mike > > > -- System Information: > Debian Release: 9.7 > APT prefers stable > APT policy: (990, 'stable'), (500, 'stable-updates') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages node-xmlhttprequest depends on: > ii nodejs 4.8.2~dfsg-1 > > node-xmlhttprequest recommends no packages. > > node-xmlhttprequest suggests no packages. > > -- no debconf information >
Bug#921356: [Pkg-javascript-devel] Bug#921356: Not suitable for buster, package probably unmaintained
This is used in node-ws (popcon 92) Paolo
Bug#920337: Bug #920337 in python-igraph marked as pending
Control: tag -1 pending Hello, Bug #920337 in python-igraph 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/python-igraph/commit/4e6b96a3240a303c34cc07f1dc311937e2fcc963 Temporary workaround for invalid install layout * Patch by Nicolas Boulenguez, thanks! * Temporary workaround to avoid shipping headers in /usr/include/python3.7 (instead of /usr/include/python3.7m). This is likely to be a python3-stdlib-extensions bug so we should consider removing this as soon as the bug as been addressed (Closes: #920337). * Migrate to compat = 12: * debian/control: - update debhelper dependency and migrate to debhelper-compat. - Rules-Requires-Root: no. * Remove now useless debian/compat file. * Bump debian/watch version to 4. (this message was generated automatically) -- Greetings https://bugs.debian.org/920337
Processed: Bug #920337 in python-igraph marked as pending
Processing control commands: > tag -1 pending Bug #920337 [python3-igraph] python3-igraph: ships header in /usr/include/python3.7/ Added tag(s) pending. -- 920337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 921227 is forwarded to https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218
Processing commands for cont...@bugs.debian.org: > forwarded 921227 https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218 Bug #921227 [dnssec-trigger] dnssec-trigger: crashes (SIGSEGV) Set Bug forwarded-to-address to 'https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218'. > thanks Stopping processing here. Please contact me if you need assistance. -- 921227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921359: Not suitable for buster, package probably unmaintained
Package: node-security Version: 1.0.0~git20130515-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-security depends on: ii nodejs 4.8.2~dfsg-1 node-security recommends no packages. node-security suggests no packages.
Bug#921362: Not suitable for buster, package unmaintained
Source: bignumber.js Version: 1.3.0+dfsg-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921358: Not suitable for buster, package probably unmaintained
Package: node-yajsml Version: 1.1.5-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-yajsml depends on: ii nodejs 4.8.2~dfsg-1 node-yajsml recommends no packages. Versions of packages node-yajsml suggests: ii libjs-jquery 3.1.1-2 ii libjs-underscore 1.8.3~dfsg-1 -- no debconf information
Bug#921361: Not suitable for buster, package probably unmaintained
Source: node-clean-css Version: 1.0.12-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921360: No suitable for buster, package probably unmaintained
Package: node-base64id Version: 0.1.0-3 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-base64id depends on: ii nodejs 4.8.2~dfsg-1 node-base64id recommends no packages. node-base64id suggests no packages. -- no debconf information
Bug#921357: Not suitable for buster, package probably unmaintained
Package: node-dequeue Version: 1.0.5-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-dequeue depends on: ii nodejs 4.8.2~dfsg-1 node-dequeue recommends no packages. node-dequeue suggests no packages. -- no debconf information
Bug#921363: Not suitable for buster, package unmaintained
Source: ejs.js Version: 1.0.0+dfsg1-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921368: Not suitable for buster, package probably unmaintained
Package: node-base64id Version: 0.1.0-3 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-base64id depends on: ii nodejs 4.8.2~dfsg-1 node-base64id recommends no packages. node-base64id suggests no packages. -- no debconf information
Bug#921364: Not suitable for buster, package unmaintained
Package: node-active-x-obfuscator Version: 0.0.2-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-active-x-obfuscator depends on: pn node-zeparser ii nodejs 4.8.2~dfsg-1 node-active-x-obfuscator recommends no packages. node-active-x-obfuscator suggests no packages.
Bug#921366: Not suitable for buster, package probably unmaintained
Source: zeparser.js Version: 0.0.7+dfsg-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921356: Not suitable for buster, package probably unmaintained
Package: node-tinycolor Version: 0.0.1~git20130725-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-tinycolor depends on: ii nodejs 4.8.2~dfsg-1 node-tinycolor recommends no packages. node-tinycolor suggests no packages.
Processed: [bts-link] source package src:matplotlib2
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:matplotlib2 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #918896 (http://bugs.debian.org/918896) > # Bug title: matplotlib2: FTBFS with Sphinx 1.8: directive u'math' is already > registered, it will be overridden > # * https://github.com/matplotlib/matplotlib/issues/13258 > # * remote status changed: closed -> open > # * reopen upstream > tags 918896 - fixed-upstream Bug #918896 [src:matplotlib2] matplotlib2: FTBFS with Sphinx 1.8: directive u'math' is already registered, it will be overridden Removed tag(s) fixed-upstream. > usertags 918896 - status-closed Usertags were: status-closed. Usertags are now: . > usertags 918896 + status-open There were no usertags set. Usertags are now: status-open. > thanks Stopping processing here. Please contact me if you need assistance. -- 918896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 909165 in 9.3-4
Processing commands for cont...@bugs.debian.org: > found 909165 9.3-4 Bug #909165 [linkchecker] linkchecker-gui: linkcheker-gui does not start Bug #901780 [linkchecker] linkchecker: Should depend on python-xdg Marked as found in versions linkchecker/9.3-4. Marked as found in versions linkchecker/9.3-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 901780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901780 909165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
Hi Fabian, On Mon, Feb 04, 2019 at 05:26:08PM +0100, Fabian Klötzl wrote: > So I improved the upstream libmurmurhash, adapted the package and filed an > ITP (#921353). I even managed to locally build mash against the new package. Thanks a lot - that's really cool. > So hereby I kindly ask you to fix the last lintian issue about NMU which I > don't fully understand and then maybe sponsor an upload. Please have a look at https://salsa.debian.org/med-team/libmurmurhash/commit/dddc2707ffea44a40c2e39b3b23f7576fe0ebda3 I took the freedom to realise my suggestion to use automake. The advantage is that you get multiarch for free and the build system is somehow "convenient" in terms of not needing any override. I admit I'm not fully happy with my work since I'm also not an automake adept and thus the manpage is not part of the Makefile.am installation and the check is also not as elegant as I would prefer it to be. However, there is also pkg-config which might be convenient in some situations. Would you mind integrating my patch upstream before I upload? Feel free to enhance it - I'm not really proud about that code ... Kind regards and thanks again for your work on this Andreas. -- http://fam-tille.de
Bug#921369: marked as done (Not suitable for buster, package probably unmaintained)
Your message dated Mon, 04 Feb 2019 21:38:22 + with message-id and subject line Bug#921369: fixed in node-xmlhttprequest 1.8.0-1 has caused the Debian Bug report #921369, regarding Not suitable for buster, package probably unmaintained 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.) -- 921369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-xmlhttprequest Version: 1.6.0-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-xmlhttprequest depends on: ii nodejs 4.8.2~dfsg-1 node-xmlhttprequest recommends no packages. node-xmlhttprequest suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: node-xmlhttprequest Source-Version: 1.8.0-1 We believe that the bug you reported is fixed in the latest version of node-xmlhttprequest, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-xmlhttprequest 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: Mon, 04 Feb 2019 21:55:52 +0100 Source: node-xmlhttprequest Binary: node-xmlhttprequest Architecture: source Version: 1.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 921369 Description: node-xmlhttprequest - XMLHttpRequest for Node Changes: node-xmlhttprequest (1.8.0-1) unstable; urgency=medium . * New upstream version 1.8.0 * Replace Mike Gabriel by me in uploaders. Thanks for your work! (Closes: #921369) * Bump debhelper compatibility version to 11 * Declare compliance with policy 4.3.0 * Change section to javascript * Change priority to optional * Update VCS fields to salsa * Update debian/copyright * Add upstream/metadata * Fix install * Patch source to avoid deprecation warning * Update homepage * Add tests based on pkg-js-tools * Add Multi-Arch: foreign Checksums-Sha1: a16b200536d8d8fecbcdeeebe489b314b671cc13 2135 node-xmlhttprequest_1.8.0-1.dsc f899300122dcf501ed7135a75cb262fbab6668d4 10153 node-xmlhttprequest_1.8.0.orig.tar.gz 2c4aa0c9293876ce9e28b6480f9057068aca4320 3508 node-xmlhttprequest_1.8.0-1.debian.tar.xz Checksums-Sha256: 63fb260b51b7977e77b7fb77965f535412a036de69c1d74be00c3d3ca5d89510 2135 node-xmlhttprequest_1.8.0-1.dsc 5c11240947f73cfd5f2053630b7ea7ad9df79b53a1e02657801c7226041a3e9c 10153 node-xmlhttprequest_1.8.0.orig.tar.gz adc499bc6f3bf14447a0ef3ca1f45042e1b25a6c2b3c7a484ff9863167b41d3c 3508 node-xmlhttprequest_1.8.0-1.debian.tar.xz Files: 5976159efadbe7d4c71cab00937923a8 2135 javascript optional node-xmlhttprequest_1.8.0-1.dsc 3dc1d4f65e10823631046ae51391b1ea 10153 javascript optional node-xmlhttprequest_1.8.0.orig.tar.gz 258ab347ea287899c6d343848b8e9f5e 3508 javascript optional node-xmlhttprequest_1.8.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxYp8EACgkQ9tdMp8mZ 7un71g/+O+NrKMPfMU3e7PPkUkAAxNcme3Ct0twhhEzpWkbI2EAeLQwIR8tu91hF Nw0pOQfUPPt5MfZwH1tvACDAffuQYPwh9sZacIcng3uB8RKcxsVwkUMQ3TAwM7E1 X8iaJXh4HeC8O3dohXfs74l5Or2VsaJbiCqziAWqVwnHH6Jl8744gId1VYjq8aXx EZ+oXyDNubLew8oajMxx4PPQt9YSn8k0WcDUqY+Np3HoNtDFbuN1VYGxcIccQ4+8 Qz8FsqHDDd95sUKzUUYmXRqJUdy7Vgt/yc1VpRk65kddr0u/oCDQsRXHGwgI0Q7w
Bug#916034: marked as done (sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64)
Your message dated Mon, 04 Feb 2019 21:47:13 + with message-id and subject line Bug#916034: fixed in sl-modem 2.9.11~20110321-12+deb9u1 has caused the Debian Bug report #916034, regarding sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sl-modem-dkms Version: 2.9.11~20110321-13 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 2.9.11~20110321-12 Hi, sl-modem-dkms fails to build a module for 4.18.0-3-amd64 and 4.9.0-8-amd64 Selecting previously unselected package sl-modem-dkms. (Reading database ... 33401 files and directories currently installed.) Preparing to unpack .../sl-modem-dkms_2.9.11~20110321-13_amd64.deb ... Unpacking sl-modem-dkms (2.9.11~20110321-13) ... Setting up sl-modem-dkms (2.9.11~20110321-13) ... Loading new sl-modem-2.9.11~20110321 DKMS files... grep: /lib/modules/4.9.0-6-amd64/build/.config: No such file or directory It is likely that 4.9.0-6-amd64 belongs to a chroot's host Building for 4.18.0-3-amd64 Building initial module for 4.18.0-3-amd64 Error! Build of slusb.ko failed for: 4.18.0-3-amd64 (x86_64) Consult the make.log in the build directory /var/lib/dkms/sl-modem/2.9.11~20110321/build/ for more information. dpkg: error processing package sl-modem-dkms (--configure): installed sl-modem-dkms package post-installation script subprocess returned error exit status 7 Errors were encountered while processing: sl-modem-dkms # cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.18.0-3-amd64 (x86_64) Sun Dec 9 13:53:21 UTC 2018 make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers' doing %.o: %.c cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB `test -f /lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h && echo -DMODVERSIONS --include /lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h -I/lib/modules/4.18.0-3-amd64/build/include` -I. -I./../modem -o old_st7554.o -c old_st7554.c old_st7554.c:49:10: fatal error: linux/init.h: No such file or directory #include ^~ compilation terminated. make: *** [Makefile:129: old_st7554.o] Error 1 make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers' make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem' make modules -C /lib/modules/4.18.0-3-amd64/build SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem make[1]: Entering directory '/usr/src/linux-headers-4.18.0-3-amd64' CC [M] /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o Building modules, stage 2. MODPOST 1 modules CC /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.mod.o LD [M] /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko make[1]: Leaving directory '/usr/src/linux-headers-4.18.0-3-amd64' make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem' # cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.9.0-8-amd64 (x86_64) Sun Dec 9 14:02:25 UTC 2018 make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers' doing %.o: %.c cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB `test -f /lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h && echo -DMODVERSIONS --include /lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h -I/lib/modules/4.9.0-8-amd64/build/include` -I. -I./../modem -o old_st7554.o -c old_st7554.c old_st7554.c:48:26: fatal error: linux/module.h: No such file or directory #include ^ compilation terminated. Makefile:128: recipe for target 'old_st7554.o' failed make: *** [old_st7554.o] Error 1 make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers' make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem' make modules -C /lib/modules/4.9.0-8-amd64/build SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem make[1]: Entering directory '/usr/src/linux-headers-4.9.0-8-amd64' CC [M] /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o Building modules, stage 2. MODPOST 1 modules CC
Bug#773720: marked as done (sox: CVE-2014-8145)
Your message dated Mon, 04 Feb 2019 21:47:14 + with message-id and subject line Bug#773720: fixed in sox 14.4.1-5+deb9u1 has caused the Debian Bug report #773720, regarding sox: CVE-2014-8145 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.) -- 773720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sox Version: 14.3.1-1 Severity: grave Tags: security upstream Hi, the following vulnerability was published for sox. CVE-2014-8145[0]: two heap-based buffer overflows If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-8145 [1] http://www.ocert.org/advisories/ocert-2014-010.html Patches are not yet attached/referenced in the advisory, but should be referenced in upstream git repository soon. Regards, Salvatore --- End Message --- --- Begin Message --- Source: sox Source-Version: 14.4.1-5+deb9u1 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 773...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (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: SHA512 Format: 1.8 Date: Fri, 01 Feb 2019 16:18:21 +0100 Source: sox Binary: sox libsox2 libsox-fmt-base libsox-fmt-alsa libsox-fmt-ao libsox-fmt-mp3 libsox-fmt-oss libsox-fmt-pulse libsox-fmt-all libsox-dev Architecture: source Version: 14.4.1-5+deb9u1 Distribution: stretch Urgency: medium Maintainer: Pascal Giard Changed-By: Salvatore Bonaccorso Closes: 773720 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 libsox2- SoX library of audio effects and processing sox- Swiss army knife of sound processing Changes: sox (14.4.1-5+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * Add patches for CVE-2014-8145 to series file and really apply fixes. Thanks to Mike Salvatore for spotting the issue. (Closes: #773720) Checksums-Sha1: dfe40844d1bdae2311ce0fcc47ad464733c5993b 2818 sox_14.4.1-5+deb9u1.dsc 451ae46dd8c14e5399338469b52fca16737fbd14 13520 sox_14.4.1-5+deb9u1.debian.tar.xz Checksums-Sha256: 4b1ef19966c78a030e3f7101398d3af0d3af92153845d6182fd754feb62fc9a3 2818 sox_14.4.1-5+deb9u1.dsc e485136bc8f34ea2b08f359856e20b4a2f902643cc20f79a4217feed08dd4476 13520 sox_14.4.1-5+deb9u1.debian.tar.xz Files: 3e0dd0b71ce9c5956a6bcaeb14f10c7b 2818 sound optional sox_14.4.1-5+deb9u1.dsc b5e66f8f193eb54eddd284f2f2363998 13520 sound optional sox_14.4.1-5+deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxUbYpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EcY8P/2mB9Ue4nYPXv/+Zt0L9LVKxbsB3w8EI hFXQnClmsLl112LzzRAH5y8AqspcKu6Os0SUAEX2xRhtC89feInoh3O2IHm1p3JD hHG+GLlFMuMolvaPpk/2dqTyVStHE1ujf/grOCkIbqALbmTj1wRk49iFWuqSMR64 2e3onm15rlAkosd65ZKGLURsdSoW4YbwjSXgtHhxYpuXlDA/LmJMl5uVn//r4aHc 1C+hoov97ufOCyEMaMWk0TDoB5phbWio1/S/r73dQ2/OjFxAf16W4o2tDHP/lWRU FYDlcn/e2isDKuSw7LPtCfFg06pCgHsnsNgGVk2hH3vsNKyPzWJXnZcTabt2PFKw 02C7cf5XFhLPkCNlU39gSnZbbATBhlume9+DwS+K7ymOUTprVGPeei4tVpSE3DcU hjt0kTsiXK7B4gNq1vUc1zARc/yciNhG/TOgJ3K5XC4cLmi0e0OHyzOn34oaGXMV Isjj5PklmjEJDkewh9bTkbV8DCVY5EFi7TNfQ+4+t/tfN3ZidVIqadBdRxGG/paU 8pd2LHnYi4T+CLDl9y/qHOIV7W/xTyU1Ctm9WcmIcDXiaH3wXgMXLyXCY2GbDjKc pvp2I6ZJd8GG2s9YfWmSHTgTQN5GyQsQFuFip+Ao4YkpL4Xn6+/Mbgl6qIV0142A Q/xBrR9xFxBd =B3uc -END PGP SIGNATURE End Message ---
Bug#774527: marked as done (arc: CVE-2015-9275: directory traversal)
Your message dated Mon, 04 Feb 2019 21:47:08 + with message-id and subject line Bug#774527: fixed in arc 5.21q-4+deb9u1 has caused the Debian Bug report #774527, regarding arc: CVE-2015-9275: directory traversal 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.) -- 774527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arc Version: 5.21q-1 Tags: security arc is susceptible to directory traversal: $ pwd /home/jwilk $ arc x traversal.arc Extracting file: /tmp/moo $ ls -l /tmp/moo -rw-r--r-- 1 jwilk users 4 Jan 4 2015 /tmp/moo The script I used to create the test case is available at: https://bitbucket.org/jwilk/path-traversal-samples -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages arc depends on: ii libc6 2.19-13 -- Jakub Wilk traversal.arc Description: Binary data --- End Message --- --- Begin Message --- Source: arc Source-Version: 5.21q-4+deb9u1 We believe that the bug you reported is fixed in the latest version of arc, 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 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated arc 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: Sun, 03 Feb 2019 22:39:01 +0100 Source: arc Binary: arc Architecture: source Version: 5.21q-4+deb9u1 Distribution: stretch Urgency: medium Maintainer: Adilson dos Reis Changed-By: Salvatore Bonaccorso Closes: 774527 Description: arc- Archive utility based on the MSDOS ARC program Changes: arc (5.21q-4+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * Fix version 1 arc header reading * Fix arcdie crash when called with more then 1 variable argument * Fix directory traversal bugs (CVE-2015-9275) Thanks to Hans de Goede (Closes: #774527) Checksums-Sha1: 2bcd5a31aabf2ebaf80abc64dc8dd7c6fad511b7 1850 arc_5.21q-4+deb9u1.dsc ff84976741f5dcc490f72f95f0d97596d6c8b9f0 6052 arc_5.21q-4+deb9u1.debian.tar.xz Checksums-Sha256: 0b8f102f4c82b9b272f35dfaf4c4f97ceb40998d600908a429ea0a6aac195d60 1850 arc_5.21q-4+deb9u1.dsc bfe0912036fed5a035e508a05d8fe5037c80a9058deea89ae9a4e9132b15d797 6052 arc_5.21q-4+deb9u1.debian.tar.xz Files: 79898e9146c4c05f01eb32062df1682c 1850 utils optional arc_5.21q-4+deb9u1.dsc 79b8d97df74b7e5a79f77ec089c0a51d 6052 utils optional arc_5.21q-4+deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxXYF5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89ErigP+gJOD6jLZ5BujbhDpuvcFusFW6U0adM7 QYAEvjKittY5wkTnvT+4t99r0jbG0cQOdBRIJdcORdD5pronLITlh9QN5mGGSe87 UiQBwwaOyRIpfP3NupjNe/hsrP+E+EVaixj/0lKC98vaPLN5WxQQjH4v0fczrCtV V5NNHQQvGyfoeINNgN+u+DtgzP03ZNcbaU+KXgeC4XuMKt/CxL24RZiSuLdbWJxs P/lmAsKjJflSA58AQNnVPE0xbsGJkAYfc2tTZif1zIBayBLbxFyKhSZNFv6jUQ3h 0ylPdILUQqasPq/+01lOd1l6JIgsF3qkmy1Yh/PlRhNxi4x14pEqNMjGha4mPPQB lHBPiAMHob2Nni9NVmZdi0+M54/tsEvXmU8kyZKlFf94Cx45rv+DZ0G7UyXpe0a/ jZzBZVR2fyAIjzsdkhY8BeGazni0Zit+bG81aiQ/RyjYesS5x9SHiEDCMx80K4wZ zcp6t1MaXgBaAQORTu87N2vOzowA16bTphrfy2g8ZZ1N+N+KtKyBykiehBnyYwN0 fghFxX/1AYKwZeR87dv5GGTcjDd9FhbKFAzuqB9dfJJu3yb9cewY5Ypvtr/rCOQF JQ8EnvOWI7bGSnFbSCHfH8YBfMfNyGxxQKPo8ZAN4y6GHo4qY3/qbGREHT7ssF6a jQGmdcy0bALG =gJNt -END PGP SIGNATURE End Message ---
Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init
Hi Felipe, Felipe Sateler wrote: > > > Upstream asks if cgroup is in v2-mode in the affected systems. > With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cgroup > or cgroup2 filesystems. root@lorenz:~# findmnt -R /sys/fs/cgroup TARGET SOURCE FSTYPE OPTIONS /sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,mode=755 ├─/sys/fs/cgroup/unified cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate └─/sys/fs/cgroup/elogind cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind/elogind-cgroups-agent,name=elogind Il giorno lun 4 feb 2019 alle ore 16:11 Gedalya ha scritto: > > > This currently looks like this now (after I have uninstalled > > cgroupfs-mount): > > > > → findmnt -R /sys/fs/cgroup > > TARGET SOURCE FSTYPE OPTIONS > > /sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,mode=755 > > ├─/sys/fs/cgroup/unified cgroup2 cgroup2 > rw,nosuid,nodev,noexec,relatime,nsdelegate > > └─/sys/fs/cgroup/elogind cgroup cgroup > rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind > > > > But I have to assume that these mount points where at least present > > before I uninstalled cgroupfs-mount, too. > > > > Regards, Axel > > I can say I've always had this issue with only cgroup2 mounted and no > cgroup (what you might call "v1") > > >
Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)
On Mon, Feb 04, 2019 at 04:36:22PM +0100, Andreas Tille wrote: > Hi Adrian, > > On Mon, Feb 04, 2019 at 01:06:35PM +0200, Adrian Bunk wrote: > > >Bug#916576: pbdagcon: FTBFS pbdata/Types.h: No such file or directory > > > > > > I need to make some noise in the team since I'm definitely overworked > > > with these pb* packages. It might be that we will loose these for > > > Buster. :-( > > > > the patches for pbbam and pbdagcon should sort out most of the issues. > > I've now uploaded the old upstream version of pbdagcon. Unfortunately > I can not see that pbbam has fixed the build issues[1] - thus I think > #909071 needs to be re-opened. >... pbbam does now build on arm64/mips64el/ppc64el, this is what #909071 fixed. pbbam fails its tests on 32bit (#829741) and big endian, these are expected failures that won't block migration. But the pbdagcon build failure points at a bug in pbbam: libpbbam0.19.0 is not ABI compatible with the stretch libpbbam, so mustn't provide it. The following changes should fix the latter problem: - remove the Provides: libpbbam from libpbbam0.19.0 - remove manual dependencies on libpbbam from the following source packages (correct dependencies on libpbbam0.19.0 are now generated): - blasr - pbdagcon - pbseqlib - unanimity > Kind regards > > Andreas. > > > [1] https://buildd.debian.org/status/package.php?p=pbbam 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#921176: redis-server service is failing to start in buster lxc container
On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb wrote: >Hi, > >> redis-server service is failing to start in buster lxc container > >Any update on this? :) I'm traveling. hopefully tonight or tomorrow night I can try. Adding Raju, and Abhijith, who may be able to try this before. > >Regards, -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#919189: Fwd: probabel FTBFS on arm64, likely due to Eigen 3 NEON code
Dear all, As one of the developers of ProbABEL I can confirm this is a rounding error. We have had similar problems in the past. The test run by make is simply diff-ing the output of a test run with a 'known good' file. Back when ProbABEL was still actively developed, I tried my best to maintain accuracy across the platforms I knew were being actively used by our users. ARM and PPC where never among those, neither did I have access to machines with that architecture. All in all I think either of Andreas' proposed solutions is fine. Best regards, Lennart. On 02-02-19 12:19, Andreas Tille wrote: > On Sat, Feb 02, 2019 at 11:56:50AM +0100, Thierry fa...@linux.ibm.com wrote: >> Hi, >> >> Thanks for pointing out that my analysis wasn't good - the arm patch >> doesn't change anything for ppc64el (which make sense whatsoever) - the >> problem on ppc64el is similar to the one on arm except the test value >> are opposite ! ( which was confusing). >> So what do we need to do ? expect that someone with a better expertise >> help going though it ? ( can you confirm we stay with that bug for both >> arch or do we need to open one for ppc64el ?) > > As long as we are sure that its just a rounding error I think an apropriate > solution would be to ignore the error for ppc64el (either exclude the test > or run > > dh_auto_test || true > > to be able to inspect the log. > > Do you think that's in your interest? > > Kind regards > > Andreas. > -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* L.C. Karssen 's-Hertogenbosch The Netherlands lenn...@karssen.org http://blog.karssen.org GPG key ID: A88F554A -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- signature.asc Description: OpenPGP digital signature
Bug#921316: marked as done (python3-sqt: Depends: python3 (< 3.6) but 3.7.2-1 is to be installed)
Your message dated Mon, 04 Feb 2019 08:45:01 + with message-id and subject line Bug#921316: fixed in python-sqt 0.8.0-3 has caused the Debian Bug report #921316, regarding python3-sqt: Depends: python3 (< 3.6) but 3.7.2-1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-sqt Version: 0.8.0-2 Severity: serious The following packages have unmet dependencies: python3-sqt : Depends: python3 (< 3.6) but 3.7.2-1 is to be installed Was this binary built in an old/outdated chroot with Python 3.6 as default? --- End Message --- --- Begin Message --- Source: python-sqt Source-Version: 0.8.0-3 We believe that the bug you reported is fixed in the latest version of python-sqt, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-sqt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 09:14:28 +0100 Source: python-sqt Binary: python3-sqt Architecture: source Version: 0.8.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: python3-sqt - SeQuencing Tools for biological DNA/RNA high-throughput data Closes: 921316 Changes: python-sqt (0.8.0-3) unstable; urgency=medium . * Team upload. * Rebuild Closes: #921316 Checksums-Sha1: 2f0ba898482da437210f481f80b323550468e1f6 2136 python-sqt_0.8.0-3.dsc d933efea03a4bbdce2aa7dee1fe794bb32919909 4828 python-sqt_0.8.0-3.debian.tar.xz Checksums-Sha256: b709d5d9969246b6518351b142a39d87a79eefadbd554caaadae8c6587177ef8 2136 python-sqt_0.8.0-3.dsc 8b0b49efc4d139f9c9fb6270e78058892bb5c6504679d9e608e84092ffd8948e 4828 python-sqt_0.8.0-3.debian.tar.xz Files: 16a70a7ab570f9b4585756f6ea8a4be5 2136 science optional python-sqt_0.8.0-3.dsc 991501ebdbcd8365618c1714017bcf3d 4828 science optional python-sqt_0.8.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxX9gYRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGvqw/+PG1RMSWLqPcA6Q6h155Jw22qzma21U4e L9y8p+LV1b7q57lSTMUkjkK5v7xa0VI3PFcldE6BlMZ1nkkf2AJCN0RLBBSGEBP4 +4G9bkqC9ZvtMJVM/QmUhemXGOvVMQaQeSitqauYK8f3uTmB8Bwre2ND21fsctiG 4u4GpO/w1Z89w6gp5CAfo6rsseix7s7cf1bLkI30Gj/aN1itKLNC7rnbQZme/HjT Pgr5UVSDsHb7zojVScclrqdrks0xRvZ70DFeU7yGBATPA5Htj6aJTecGo0GDwT+/ Dg05ApSpFP9tE3sGP8CS+h6YYOI8hJiBTs4IvrHc3EbLtog7lIm3/rvx3V+bD2V9 0Ja7kqYMuAxl96AFhWiTLj3TPPLQfHkPWjdN98P46rb7YdbyvYV6AoKrMJsKkjp6 lPXT250vBCA7sT2/9sueU66+ZBfhEe0ptSZf1n1BNHLFbCd+maI0gVkun+iwj+6F aw79qy38N20Brw3/i39esTqH0LgqDrWov9SeOSi7NSYppJfKfWycfLAaczZCSxbr YdbyCKj8hRquB6ia4YzH2zgXfqZERN4ykcT5LqIpdxz9Ydr1nXSM6YBRiIBb0SiW sdfaHUehWeopi5kGWDedJQzPWmiMHFfUw8Bj7DyTwn5yj+PX32crDwZZDduzQvxR BRsUbZ5abYA= =05yJ -END PGP SIGNATURE End Message ---
Bug#915266: marked as done (python-wither FTBFS with Pyrhon 3.7)
Your message dated Mon, 04 Feb 2019 08:45:07 +
with message-id
and subject line Bug#915266: fixed in python-wither 1.1-2
has caused the Debian Bug report #915266,
regarding python-wither FTBFS with Pyrhon 3.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
915266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wither
Version: 1.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-wither.html
...
cd . && python3 setup.py build
--build-base="/build/1st/python-wither-1.1/./build"
Warning: 'classifiers' should be a list, got type 'NoneType'
Traceback (most recent call last):
File "setup.py", line 75, in
cmdclass = {'test': PyTest},
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 140, in
setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.7/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 370, in
__init__
k: v for k, v in attrs.items()
File "/usr/lib/python3.7/distutils/dist.py", line 267, in __init__
getattr(self.metadata, "set_" + key)(val)
File "/usr/lib/python3.7/distutils/dist.py", line 1215, in set_classifiers
self.classifiers = _ensure_list(value, 'classifiers')
File "/usr/lib/python3.7/distutils/dist.py", line 40, in _ensure_list
value = list(value)
TypeError: 'NoneType' object is not iterable
make: *** [/usr/share/cdbs/1/class/python-distutils.mk:78:
debian/python-module-stampdir/python3-wither] Error 1
--- End Message ---
--- Begin Message ---
Source: python-wither
Source-Version: 1.1-2
We believe that the bug you reported is fixed in the latest version of
python-wither, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated python-wither package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 04 Feb 2019 09:13:09 +0100
Source: python-wither
Binary: python3-wither
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Mike Gabriel
Description:
python3-wither - XML/HTML Generation DSL (Python 3)
Closes: 915266
Changes:
python-wither (1.1-2) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
* d/watch: Use https protocol
* d/control: Remove ancient X-Python3-Version field
.
[ Mike Gabriel ]
* debian/patches:
+ Add 1001_fix-ftbfs-py3-7.patch. Fix FTBFS against recent distutils in
Python 3.7. (Closes: #915266).
* debian/control:
+ Bump Standards-Version: to 4.3.0. No changes needed.
Checksums-Sha1:
a25d61dd97d64d56655869aa586ac64e89d93a17 2079 python-wither_1.1-2.dsc
5ca03aada01719e411b9b172b62bb555c7c2c7c0 2840 python-wither_1.1-2.debian.tar.xz
f8d47419dcc0232a4b17a8b5c806104ff78f80d8 6773
python-wither_1.1-2_source.buildinfo
Checksums-Sha256:
8314b8d5f4ee3d51e8327e78deb080c9eab5f753703b0ad1c75e12707dd870ce 2079
python-wither_1.1-2.dsc
c6159e170b3cefc92a6e3f2f1e044a2d9c364510991e579af830aa9ba622a34b 2840
python-wither_1.1-2.debian.tar.xz
2318e2227f10844b8b0a8329c73cce8c1dd800187120698a4a541caaeeaeac00 6773
python-wither_1.1-2_source.buildinfo
Files:
efb355361d5825bc6b6563ff66a63d33 2079 python optional python-wither_1.1-2.dsc
564d92766b1892140facee29ee96f63e 2840 python optional
python-wither_1.1-2.debian.tar.xz
aafba4882307f40d5dcbe96b50a2d42f 6773 python optional
python-wither_1.1-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlxX9I8VHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxSD4P/jTnAaYXeZloxBc7t/fYkXC1x/Hp
Fk/yBw2ZwP0igwBmKVC6t+O81qKCmAUI0khp0sHnz9qwBc/HmHPmttihSQjc9T8d
qLITU/I58P0DXWHvP97SGNVze9N7jrgmrOJAibDKmFRNTd8UnQ18ffvEKKZ8EdUb
IEuJMD1IEVDU/nJS139skSG9TjWAh2Pc2drrMiFph5aoTyDTuS0ZJuyqfGM7nRpn
Bug#918623: dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT
Hi Florian, > It's probably a bit late in the release cycle to "just find out" by > uploading a -2 with that modified patch. ... but its even worse to do nothing since this is an RC bug and this package as well as its rdepends would be excluded from next release if the bug is not fixed. Kind regards Andreas. -- http://fam-tille.de
Bug#921271: marked as done (buildbot: CVE-2019-7313: CRLF injection in Buildbot login and logout redirect code)
Your message dated Mon, 04 Feb 2019 09:34:23 + with message-id and subject line Bug#921271: fixed in buildbot 2.0.0-1 has caused the Debian Bug report #921271, regarding buildbot: CVE-2019-7313: CRLF injection in Buildbot login and logout redirect code 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.) -- 921271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: buildbot Version: 1.8.0-1 Severity: grave Tags: security upstream Hi, The following vulnerability was published for buildbot. CVE-2019-7313[0]: | www/resource.py in Buildbot before 1.8.1 allows CRLF injection in the | Location header of /auth/login and /auth/logout via the redirect | parameter. This affects other web sites in the same domain. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-7313 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7313 [1] https://github.com/buildbot/buildbot/wiki/CRLF-injection-in-Buildbot-login-and-logout-redirect-code Regards, Salvatore --- End Message --- --- Begin Message --- Source: buildbot Source-Version: 2.0.0-1 We believe that the bug you reported is fixed in the latest version of buildbot, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robin Jarry (supplier of updated buildbot 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: Mon, 04 Feb 2019 10:06:17 +0100 Source: buildbot Architecture: source Version: 2.0.0-1 Distribution: unstable Urgency: high Maintainer: Python Applications Packaging Team Changed-By: Robin Jarry Closes: 920542 920710 920979 921089 921155 921271 Changes: buildbot (2.0.0-1) unstable; urgency=high . [ Robin Jarry ] * Set buildbot-doc as Multi-Arch: foreign * New upstream version 2.0.0 * [CVE-2019-7313] Fix CRLF injection bug (Closes: #921271) * d/patches: remove 0005-tests-use-explicit-python-executable-path . [ Adriano Rafael Gomes ] * Add debconf translations: Brazilian Portuguese (Closes: #920542) . [ Jean-Pierre Giraud ] * Add debconf translations: French (Closes: #920710) . [ Yangfl ] * Add debconf translations: Chinese (Closes: #920979) . [ Frans Spiesschaert ] * Add debconf translations: Dutch (Closes: #921089) . [ victory ] * Add debconf translations: Japanese (Closes: #921155) Checksums-Sha1: 98fc2eb6a716d89f858b54c3427b1f86877e1a15 3180 buildbot_2.0.0-1.dsc b02205197a239a232060bd84163e370047845d7e 3941061 buildbot_2.0.0.orig.tar.gz 71f7b8d29cf0c8ae00b714e94b45f2f4fd1804be 537 buildbot_2.0.0.orig.tar.gz.asc fca8fc65b45fb75ccedc311df1374b1a55dd6fae 25652 buildbot_2.0.0-1.debian.tar.xz 411d8814e0451f76c434a6259227876f1c4e0597 10290 buildbot_2.0.0-1_amd64.buildinfo Checksums-Sha256: 0afff54741fd4a996c7ee727ab54dc9165efb780ca2a0c00169fccb63cd61dd4 3180 buildbot_2.0.0-1.dsc 51b3e839bf31edada6764d015c1172acef40c10687b350b0dc4338e909e0c586 3941061 buildbot_2.0.0.orig.tar.gz 5a0cb5266e47bdece8106f74c8c8218650682284a180a63e01ba615f38717851 537 buildbot_2.0.0.orig.tar.gz.asc 1b3c02283df6852ae5796918581ce871c48b16424c612f0f42a2598978737aa6 25652 buildbot_2.0.0-1.debian.tar.xz b240e511ea5444a5b7273ff5c4a4f850019bc2caad868c7aea2d9ec93185d827 10290 buildbot_2.0.0-1_amd64.buildinfo Files: bd7f930f2c086dcc794ec38f13272a2f 3180 devel optional buildbot_2.0.0-1.dsc 080faea77fb0427494ef638237025b50 3941061 devel optional buildbot_2.0.0.orig.tar.gz 5d4019019229fbc3789c04e6844a1061 537 devel optional buildbot_2.0.0.orig.tar.gz.asc 8be0875351ffb77f77c5c5d6691ae4a0 25652 devel optional buildbot_2.0.0-1.debian.tar.xz deadd749fe9dc090ab773fb7723ad629 10290 devel optional buildbot_2.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlxYAw0ACgkQCBa54Yx2 K608xg//R/eTIrIVL5NlcwPkmimtIR6AZ9yMZt10EL9HbIOjFlM+YS2gYBQo6Y6k
Bug#921320: ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster
Source: ruby-rspec-rails Version: 3.8.1-2 Severity: serious Tags: ftbfs Control: block -1 by 900156 ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster due to #900156.
Bug#921315: samtools: baseline violation on i386
On Mon, 04 Feb 2019 08:43:08 +0200 Adrian Bunk wrote: > Source: samtools > Version: 1.9-2 > Severity: serious > Tags: patch > > SSE is not part of the i386 baseline, fix: > > --- debian/rules.old 2019-02-03 20:43:51.747130097 + > +++ debian/rules 2019-02-03 20:44:04.383129977 + > @@ -5,7 +5,7 @@ > > export DEB_BUILD_MAINT_OPTIONS=hardening=+all > ifneq (,$(filter $(DEB_HOST_ARCH),i386 kfreebsd-i386 hurd-i386)) > - export DEB_CFLAGS_MAINT_APPEND=-msse -mfpmath=sse > + export DEB_CFLAGS_MAINT_APPEND=-ffloat-store Very cool, I did not know about this option; thank you! > endif > > %: > >
Bug#921316: python3-sqt: Depends: python3 (< 3.6) but 3.7.2-1 is to be installed
Hi Adrian, On Mon, Feb 04, 2019 at 09:01:55AM +0200, Adrian Bunk wrote: > The following packages have unmet dependencies: > python3-sqt : Depends: python3 (< 3.6) but 3.7.2-1 is to be installed > > Was this binary built in an old/outdated chroot with Python 3.6 > as default? I'm always using up to date chroot. The only reason might be that I accidentally have build for stretch backport? Just re-uploading. Thanks a lot for your extremely valuable QA work Andreas. -- http://fam-tille.de
Processed: ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster
Processing control commands: > block -1 by 900156 Bug #921320 [src:ruby-rspec-rails] ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster 921320 was not blocked by any bugs. 921320 was not blocking any bugs. Added blocking bug(s) of 921320: 900156 and 907022 -- 921320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921324: astropy-healpix FTBFS on i386: test filure
Source: astropy-healpix
Version: 0.4-4
Severity: serious
Tags: ftbfs patch
https://buildd.debian.org/status/fetch.php?pkg=astropy-healpix=i386=0.4-4=1548693347=0
...
=== FAILURES ===
___ test_boundaries
@given(nside_pow=integers(0, 29), step=integers(1, 10), nest=booleans(),
> frac=floats(0, 1, allow_nan=False,
> allow_infinity=False).filter(lambda x: x < 1))
astropy_healpix/tests/test_healpy.py:185:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/hypothesis/core.py:519: in execute
result = self.test_runner(data, run)
/usr/lib/python3/dist-packages/hypothesis/executors.py:58: in
default_new_style_executor
return function(data)
/usr/lib/python3/dist-packages/hypothesis/core.py:517: in run
return test(*args, **kwargs)
astropy_healpix/tests/test_healpy.py:185: in test_boundaries
frac=floats(0, 1, allow_nan=False, allow_infinity=False).filter(lambda x: x
< 1))
/usr/lib/python3/dist-packages/hypothesis/core.py:464: in test
result = self.test(*args, **kwargs)
astropy_healpix/tests/test_healpy.py:190: in test_boundaries
b1 = hp_compat.boundaries(nside, pix, step=step, nest=nest)
astropy_healpix/healpy.py:152: in boundaries
lon, lat = boundaries_lonlat(pix, step, nside, order='nested' if nest else
'ring')
astropy_healpix/core.py:673: in boundaries_lonlat
lon, lat = healpix_to_lonlat(healpix_index.ravel(), nside, dx.ravel(),
dy.ravel(), order=order)
astropy_healpix/core.py:393: in healpix_to_lonlat
lat = Latitude(lat, unit=u.rad, copy=False)
/usr/lib/python3/dist-packages/astropy/coordinates/angles.py:514: in __new__
self._validate_angles()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
angles =
def _validate_angles(self, angles=None):
"""Check that angles are between -90 and 90 degrees.
If not given, the check is done on the object itself"""
# Convert the lower and upper bounds to the "native" unit of
# this angle. This limits multiplication to two values,
# rather than the N values in `self.value`. Also, the
# comparison is performed on raw arrays, rather than Quantity
# objects, for speed.
if angles is None:
angles = self
lower = u.degree.to(angles.unit, -90.0)
upper = u.degree.to(angles.unit, 90.0)
if np.any(angles.value < lower) or np.any(angles.value > upper):
raise ValueError('Latitude angle(s) must be within -90 deg <= angle
<= 90 deg, '
>'got {0}'.format(angles.to(u.degree)))
E ValueError: Latitude angle(s) must be within -90 deg <= angle <= 90
deg, got [ 0.-41.8103149 -90.-41.8103149] deg
/usr/lib/python3/dist-packages/astropy/coordinates/angles.py:531: ValueError
-- Hypothesis --
Falsifying example: test_boundaries(nside_pow=0, frac=0.,
step=1, nest=False)
1 failed, 124 passed in 24.30 seconds =
/usr/lib/python3/dist-packages/astropy/config/configuration.py:536:
ConfigurationMissingWarning: Configuration defaults will be used due to
FileNotFoundError:2 on None
warn(ConfigurationMissingWarning(msg))
make[1]: *** [debian/rules:17: test-python3.7] Error 1
Fix:
--- debian/rules.old2019-02-04 09:12:02.674701984 +
+++ debian/rules2019-02-04 09:13:52.286700939 +
@@ -9,6 +9,10 @@
# Astropy-affiliated packages do.
export PYBUILD_AFTER_INSTALL := find {destdir} -name '*.c' -delete
+ifeq ($(DEB_HOST_ARCH),i386)
+ export DEB_CFLAGS_MAINT_APPEND=-ffloat-store
+endif
+
%:
dh $@ --with python3 --buildsystem=pybuild
Processed: RFS: doxygen/1.8.15-1 [ITA]
Processing control commands: > severity 921295 important Bug #921295 [src:wcslib] wcslib: FTBFS with upcoming doxygen 1.8.15 Severity set to 'important' from 'serious' > severity -1 normal Bug #919413 [sponsorship-requests] RFS: doxygen/1.8.15-1 [ITA] Severity set to 'normal' from 'important' -- 919413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919413 921295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921185: marked as done (picard-tools should become Architecture: amd64)
Your message dated Mon, 04 Feb 2019 09:20:37 + with message-id and subject line Bug#921185: fixed in picard-tools 2.18.25+dfsg-2 has caused the Debian Bug report #921185, regarding picard-tools should become Architecture: amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: picard-tools Version: 2.18.25+dfsg-1 Severity: serious The dependency libgkl-java is amd64-only, and the easiest way to fix testing migration as well as being generally correct (what's the point of binary-all when it is only installable on 1 architecture?) is Architecture: all -> amd64 for all packages. --- End Message --- --- Begin Message --- Source: picard-tools Source-Version: 2.18.25+dfsg-2 We believe that the bug you reported is fixed in the latest version of picard-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated picard-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Feb 2019 08:53:09 +0100 Source: picard-tools Binary: picard-tools libpicard-java libpicard-java-doc Architecture: source Version: 2.18.25+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libpicard-java - Java library to manipulate SAM and BAM files libpicard-java-doc - Documentation for the java picard library picard-tools - Command line tools to manipulate SAM and BAM files Closes: 921185 Changes: picard-tools (2.18.25+dfsg-2) unstable; urgency=medium . * Architecture amd64 (for libpicard-java and picard-tools) Closes: #921185 * Remove trailing whitespace in debian/changelog Checksums-Sha1: e0d87e4ffe0219d2e604c05287d79f75f6f79b4f 2683 picard-tools_2.18.25+dfsg-2.dsc cd5ea0798af010b10eb4554ecb8aea2d38d9b4f6 16836 picard-tools_2.18.25+dfsg-2.debian.tar.xz 30f64bae65f61b4f94b2cf07cd312fc11c737949 21707 picard-tools_2.18.25+dfsg-2_source.buildinfo Checksums-Sha256: 2bfc5cc0be341179e210df23b8533a9be31e3cb378c5f34924d61a7f4ac2e353 2683 picard-tools_2.18.25+dfsg-2.dsc d58ec215994012cf765d26a4278fa475ab563f40ae46e05c3633db46f6f9e479 16836 picard-tools_2.18.25+dfsg-2.debian.tar.xz 183e052b91a13201cd483443f2e1d94d578a00f5d6667961ffbfed4a0ae5cbac 21707 picard-tools_2.18.25+dfsg-2_source.buildinfo Files: 626563e068dab1b2433975ac382b6900 2683 science optional picard-tools_2.18.25+dfsg-2.dsc 1e1029fc6189984cd60a2c1963dbea9b 16836 science optional picard-tools_2.18.25+dfsg-2.debian.tar.xz 564e48e41bddf601afb4aa3556edc8ac 21707 science optional picard-tools_2.18.25+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxYABoOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtHvHw/+LcvEeWgJUXRVUE7brSMck6oJWmRY9r+RfPDM LJi3GXaLibKMQuaC+ZVhVdvj+ov0xp5l+ox+8R7Nh6RV6vA1p4kiIATiI96lLGto 572cLUqZQO9aFY3X+/4WM9dETVfePOu+fWj1N31CkeKJeSNZ1XWgsBM3QDfISWVa yEuneKqWr97306nnzxkTGcgXVm8vKvAamGRiHolH2V6tSoHPk8atB9zPWmK4w3NG 192xDHXWKBxCuCVJ5vgutCadjmA6fgZ3yWqzQXZDhZcCqXtcCmEJCFa5eLuHDO95 HKR6DFwHiYOM4aUg/DO1e/aGRE7+vmMKus+xtIzcsDoA5nVvE2i0WbAS++CHlWPq usx7nf9rNeZXIzzRj/EYOTxbBLH0JVp9lw94G+/WQi8h4KXpFmCbMxfK4bYxYMF5 J4jds+yGA+KBDbEItSG342L0wbZnq63CAmzJ/6HG4mKrAAM4DiFxsQDP/Ms24NCT u4uDBT/mrqr1Ro0af4fFIFpReCvaiqUsD8v3bxIhtwrSKbEu7a4EJ3JdD8tVKPTB DI17yvn9NKA2YYvHit3xFzjutlUCl1Q70usaw3Zl2WohwoCgX/dE19YYVpX3BfAe dlRGTrbgCN4D2KZVTAXK1ZXRPO6uTWpA4CiBwAP8A8WKjGfts7ZM8EPqbhaVl66F A6WW96Y= =Wt1C -END PGP SIGNATURE End Message ---
Bug#921296: ccfits: FTBFS with upcoming doxygen 1.8.15
On 2019-02-04 01:04, Paolo Greppi wrote: > Source: ccfits > Severity: serious > > Dear Maintainer, > > I tested your package against a draft package for doxygen 1.8.15: > https://bugs.debian.org/919413 > > and it FTBFS with this error: > make[2]: *** [Makefile:8: refman.pdf] Error 1 > That actually looks like a bug in doxygen. CCfits depends on doxygen-latex, which according to its description should provide everything needed: | Package: doxygen-latex | ... | Description-en: Documentation system for C, C++, Java, Python and other languages | Doxygen is a documentation system for C, C++, Java, Objective-C, Python, IDL | and to some extent PHP, C#, and D. It can generate an on-line class browser | (in HTML) and/or an off-line reference manual (in LaTeX) from a set of | documented source files. | . | This dependency package adds dependencies for all LaTeX packages required | to build documents using the default stylesheet. ccfits doesn't do anything fancy, it just generates the latex file using doxygen and then run pdflatex on it. If a dependency is missing for that, it should be added to doxygen-latex. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
