Processed: Re: Bug#924374: busybox ip --oneline displays nothing
Processing control commands: > tag 924374 pending Bug #924374 [busybox] busybox ip -oneline link show displays nothing Added tag(s) pending. -- 924374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924374: busybox ip --oneline displays nothing
Control: tag 924374 pending Dominik George wrote... > busybox upstream found out that their ip address show command, with the > oneline option, includes link layer addresses, which iproute2 normally > doesn't. They patched that, without realising their ip link show code > ultimately calls their ip address show code. > > Attached debdiff reverts this change. This makes the ip address show > behaviour "wrong" again, but including too much in a machine-readable > output seems less broken than this regression. Thanks for this finding. While I not haven't decided yet how to deal with this in the long run, I've applied the patch for buster since fixing that regression for buster is certainly the priority here. Christoph
Processed: reassign 925165 to wnpp, found 859840 in 6.0.10-4, unarchiving 916566
Processing commands for cont...@bugs.debian.org:
> reassign 925165 wnpp
Bug #925165 [libansilove] RFP: libansilove -- Library for converting ANSI,
ASCII, and other formats to PNG
Warning: Unknown package 'libansilove'
Bug reassigned from package 'libansilove' to 'wnpp'.
Ignoring request to alter found versions of bug #925165 to the same values
previously set
Ignoring request to alter fixed versions of bug #925165 to the same values
previously set
> found 859840 6.0.10-4
Bug #859840 [zorp] zorp: Please migrate to openssl1.1 in Buster
Marked as found in versions zorp/6.0.10-4.
> unarchive 916566
Bug #916566 {Done: Debian FTP Masters }
[dansguardian] dansguardian: logrotate exits with error after package removal
Unarchived Bug 916566
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
859840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859840
916566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916566
925165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and
Hi, I've created a patch for squid-deb-proxy-client bug as below. But I'm not sure it's okay to override conffile under /etc with symlink. Any comments? If not, I'll upload it. On Sat, 16 Mar 2019 15:58:30 +0900 Hideki Yamane wrote: > How about moving 30autoproxy to /usr/share and create symlink under > /etc/apt/apt.conf.d to it? Here's a patch, works well after package > removal and piuparts clean one. > diff -Nru squid-deb-proxy-0.8.14+nmu1/Makefile > squid-deb-proxy-0.8.14+nmu2/Makefile > --- squid-deb-proxy-0.8.14+nmu1/Makefile 2018-08-16 03:25:06.0 > +0900 > +++ squid-deb-proxy-0.8.14+nmu2/Makefile 2019-03-16 15:30:32.0 > +0900 > @@ -19,4 +19,4 @@ > install -m 644 mirror-dstdomain.acl $(DESTDIR)/etc/squid-deb-proxy/ > # client > install -m 755 apt-avahi-discover > $(DESTDIR)/usr/share/squid-deb-proxy-client/ > - install -m 644 30autoproxy $(DESTDIR)/etc/apt/apt.conf.d > + install -m 644 30autoproxy $(DESTDIR)/usr/share/squid-deb-proxy-client/ > diff -Nru squid-deb-proxy-0.8.14+nmu1/debian/changelog > squid-deb-proxy-0.8.14+nmu2/debian/changelog > --- squid-deb-proxy-0.8.14+nmu1/debian/changelog 2018-08-16 > 03:25:06.0 +0900 > +++ squid-deb-proxy-0.8.14+nmu2/debian/changelog 2019-03-16 > 15:30:32.0 +0900 > @@ -1,3 +1,12 @@ > +squid-deb-proxy (0.8.14+nmu2) unstable; urgency=medium > + > + * Non-maintainer upload. > + * move /etc/apt/conf.d/30autoproxy to under > /usr/share/squid-deb-proxy-client > +and make symlink to it, to avoid package fetch failure after removed its > +package (Closes: #867682) -- Hideki Yamane
Processed: Re: openstack-dashboard: needs Breaks: python-app-catalog-ui, python-designate-dashboard, python-murano-dashboard, python-zaqar-ui
Processing control commands: > tag -1 patch Bug #925226 [openstack-dashboard] openstack-dashboard: needs Breaks: python-app-catalog-ui, python-designate-dashboard, python-murano-dashboard, python-zaqar-ui Added tag(s) patch. > affects -1 + python-app-catalog-ui python-designate-dashboard > python-ironic-ui python-murano-dashboard python-zaqar-ui Bug #925226 [openstack-dashboard] openstack-dashboard: needs Breaks: python-app-catalog-ui, python-designate-dashboard, python-murano-dashboard, python-zaqar-ui Added indication that 925226 affects python-app-catalog-ui, python-designate-dashboard, python-ironic-ui, python-murano-dashboard, and python-zaqar-ui -- 925226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925226: openstack-dashboard: needs Breaks: python-app-catalog-ui, python-designate-dashboard, python-murano-dashboard, python-zaqar-ui
Followup-For: Bug #925226 Control: tag -1 patch Control: affects -1 + python-app-catalog-ui python-designate-dashboard python-ironic-ui python-murano-dashboard python-zaqar-ui Hi, attached you can find a patch adding Breaks against 5 obsolete packages from stretch. (python-ironic-ui had a slightly different error and wasn't in my list when I filed this bug because it looked like a more serious problem that could not be fixed by a simple Breaks.) I've tested in piuparts that this solves these 5 problematic upgrade cases. Andreas >From eacf3b982053c3f00bbf26bda25ae81fbc01dc6e Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Fri, 22 Mar 2019 02:15:40 +0100 Subject: [PATCH] add breaks against some obsolete packages from stretch --- debian/changelog | 9 + debian/control | 5 + 2 files changed, 14 insertions(+) diff --git a/debian/changelog b/debian/changelog index 2750843ca..369f15bad 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +horizon (3:14.0.2-3) UNRELEASED; urgency=medium + + * openstack-dashboard: Add Breaks against obsolete packages from stretch: +python-app-catalog-ui, python-designate-dashboard, python-ironic-ui, +python-murano-dashboard, python-zaqar-ui for cleaner upgrades. +(Closes: #925226) + + -- Andreas Beckmann Fri, 22 Mar 2019 00:09:53 +0100 + horizon (3:14.0.2-2) unstable; urgency=medium [ Michal Arbet ] diff --git a/debian/control b/debian/control index 3c0ec291e..dd5e3d654 100644 --- a/debian/control +++ b/debian/control @@ -135,6 +135,11 @@ Breaks: python3-zaqar-ui (<< 5.0.0-2~), python3-manila-ui (<< 2.16.0-2~), python3-ironic-ui (<< 3.3.0-4~), + python-app-catalog-ui, + python-designate-dashboard, + python-ironic-ui, + python-murano-dashboard, + python-zaqar-ui, Description: web application to control an OpenStack cloud The OpenStack Dashboard is a web application to control an OpenStack cloud. It connects to OpenStack services such as Nova, Swift, or Keystone -- 2.11.0
Bug#925255: marked as done (ntfs-3g: CVE-2019-9755: heap buffer overflow)
Your message dated Fri, 22 Mar 2019 00:36:49 + with message-id and subject line Bug#925255: fixed in ntfs-3g 1:2017.3.23AR.3-3 has caused the Debian Bug report #925255, regarding ntfs-3g: CVE-2019-9755: heap buffer overflow to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 925255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ntfs-3g Version: 1:2017.3.23AR.3-2 Severity: grave Tags: security upstream fixed-upstream Control: found -1 1:2016.2.22AR.1+dfsg-1 Control: fixed -1 1:2016.2.22AR.1+dfsg-1+deb9u1 Control: fixed -1 1:2017.3.23AR.4-1 Hi, The following vulnerability was published for ntfs-3g, still filling a bug for tracking. CVE-2019-9755[0]: heap buffer overflow 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-9755 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9755 [1] https://sourceforge.net/p/ntfs-3g/ntfs-3g/ci/85c1634a26faa572d3c558d4cf8aaaca5202d4e9/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: ntfs-3g Source-Version: 1:2017.3.23AR.3-3 We believe that the bug you reported is fixed in the latest version of ntfs-3g, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated ntfs-3g package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 21 Mar 2019 23:52:51 + Source: ntfs-3g Architecture: source Version: 1:2017.3.23AR.3-3 Distribution: unstable Urgency: high Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 925255 Changes: ntfs-3g (1:2017.3.23AR.3-3) unstable; urgency=high . [ Salvatore Bonaccorso ] * Fix heap-based buffer overflow (CVE-2019-9755) (closes: #925255). Checksums-Sha1: 1af5228c5b3888a83b3fcdf95727922f1023d3dd 2176 ntfs-3g_2017.3.23AR.3-3.dsc 79893964d4b1c952cbc83aaad63f1043889211e7 23024 ntfs-3g_2017.3.23AR.3-3.debian.tar.xz ce6139d2c2c1d2e1e71e0f65f1692769efba72c5 9048 ntfs-3g_2017.3.23AR.3-3_amd64.buildinfo Checksums-Sha256: aa77d40ad25d04c2ec569ab16dbaa8e116dd3b16cd6377c5897e8c8cbe0415ad 2176 ntfs-3g_2017.3.23AR.3-3.dsc 029fb1f91bd69c9e7ca125ddca2524e0288724db022dc2bfd9c7c6cb6f648629 23024 ntfs-3g_2017.3.23AR.3-3.debian.tar.xz bf9ba2263583fffb08038655978acd32f2724c65aece98761dfac9cc7f67c243 9048 ntfs-3g_2017.3.23AR.3-3_amd64.buildinfo Files: 9544f562f7a61c347cd456a86ceea06a 2176 otherosfs optional ntfs-3g_2017.3.23AR.3-3.dsc 3f7c4578f6e7e85b45706c74a9eb21d7 23024 otherosfs optional ntfs-3g_2017.3.23AR.3-3.debian.tar.xz 0bcbab542a07710591c2ff009d582061 9048 otherosfs optional ntfs-3g_2017.3.23AR.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlyUKOUACgkQ3OMQ54ZM yL/a3A//UjP42v/IwgRbwhTpXbYNeR8QP/icS3ZFah2i416EqLdYY7XSMqjZY/MH vc3ISSTpySoS0Z42qvbpM/hpUjKPPT9Tfz/u87FZffftf+QigehgAlHTMZEYRqBi kVpV1DQAqKVzjazSMidQq24c77g5PiBcr19wsC57thoOV+IYavAIat/yhU2wdTQO 3YZ9dkZdvOtV8v1wygItkX0MzO5KJHKyiI6Ti32XIzZm+rgC3BvrdgJpDVQEa2lo ktXoRfJ/ZvqarXBP7BxBlVvBV47n5m6Hfd5ARXNISd2WJhVT4qyMDerV7uWI6BeH CCT9Rl9dtcgPQ34nZD0kIQrN020AXU8ALOoKko9hF84cgzjJMcIySSWaI3io3Rtx 4ShUVZrbKZ0QsgnIsBX0SJ9zMjepb6lai5kQHoynZq/79YHC6jx12ODd6E0GEPEP CXxPRMA6ZONk1eyEr8YRUYsE6tYBnnkHIE6XcAbM/THKRiWE29D/z+6SZ42R60/N Lsnw70YWIzztdmHbwlvxvaRh1rGJ27EnTvyN0Gbo0sKiCgIZRJe37PE6YgnO0jzu 2bS15ajSysH/bJNqZqyxHeuO09Oy8KlYc8B8ckmyaOYrlJjmCpVO6q9bs7GNd5TW X6j5YrQc6iq7B3r+1TAFOkz3TjHQtpesqWsc74Bm2Va35QsupEc= =8tmI -END PGP SIGNATURE End Message ---
Bug#924856: wxpython4.0: FTBFS: sip: /<>/wxpython4.0-4.0.4+dfsg/src/wacky_ints.sip:20: Invalid type for %MappedType
On Sun, 17 Mar 2019, Lucas Nussbaum wrote: During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. I'm working on this, but it's taking a bit of time. The FTBFS started due to the sip4 update to 4.19.14. Unfortunately, there were quite a few changes from 4.19.13 to 4.19.14, despite the innocuous sounding point release. Seems a bit late in the development cycle for such a change. :(
Bug#925269: redmine-plugin-recaptcha: breaks configuration of redmine
Package: redmine-plugin-recaptcha Version: 0.1.0+git20121018-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up redmine (4.0.1-1) ... dbconfig-common: writing config to /etc/dbconfig-common/redmine/instances/default.conf Creating config file /etc/dbconfig-common/redmine/instances/default.conf with new version Creating config file /etc/redmine/default/database.yml with new version creating database redmine_default: success. verifying database redmine_default exists: success. [ESC][33m`/var/www` is not a directory. Bundler will use `/tmp/bundler-20190316-93214-1wljkzi' as your home directory temporarily. [ESC][0mrake aborted! NoMethodError: undefined method `alias_method_chain' for Recaptcha::ClientHelper:Module Did you mean? alias_method /usr/share/redmine/plugins/redmine_recaptcha/lib/client_helper_patch.rb:5:in `block in included' /usr/share/redmine/plugins/redmine_recaptcha/lib/client_helper_patch.rb:4:in `class_eval' /usr/share/redmine/plugins/redmine_recaptcha/lib/client_helper_patch.rb:4:in `included' /usr/share/redmine/plugins/redmine_recaptcha/init.rb:11:in `include' /usr/share/redmine/plugins/redmine_recaptcha/init.rb:11:in `block in ' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:426:in `instance_exec' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:426:in `block in make_lambda' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:606:in `block (2 levels) in default_terminator' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:605:in `catch' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:605:in `block in default_terminator' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:199:in `block in halting' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:513:in `block in invoke_before' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:513:in `each' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:513:in `invoke_before' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:131:in `run_callbacks' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/reloader.rb:89:in `prepare!' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application/finisher.rb:63:in `block in ' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:32:in `instance_exec' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:32:in `run' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:61:in `block in run_initializers' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:60:in `run_initializers' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:361:in `initialize!' /usr/share/redmine/config/environment.rb:14:in `' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:337:in `require' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:337:in `require_environment!' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:520:in `block in run_tasks_blocks' Tasks: TOP => db:migrate => db:load_config => environment (See full trace by running task with --trace) dpkg: error processing package redmine (--configure): installed redmine package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of redmine-plugin-recaptcha: redmine-plugin-recaptcha depends on redmine (>= 2.0.0); however: Package redmine is not configured yet. cheers, Andreas redmine-plugin-recaptcha_0.1.0+git20121018-3.log.gz Description: application/gzip
Bug#925268: redmine-plugin-pretend: breaks configuration of redmine
Package: redmine-plugin-pretend Version: 0.0.2+git20130821-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up redmine (4.0.1-1) ... dbconfig-common: writing config to /etc/dbconfig-common/redmine/instances/default.conf Creating config file /etc/dbconfig-common/redmine/instances/default.conf with new version Creating config file /etc/redmine/default/database.yml with new version creating database redmine_default: success. verifying database redmine_default exists: success. [ESC][33m`/var/www` is not a directory. Bundler will use `/tmp/bundler-20190316-62490-12g8spg' as your home directory temporarily. [ESC][0mrake aborted! NoMethodError: undefined method `to_prepare' for ActionDispatch::Reloader:Class Did you mean? to_param /usr/share/redmine/plugins/redmine_pretend/init.rb:17:in `' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `require' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `block in require' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:257:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `require' /usr/share/redmine/lib/redmine/plugin.rb:173:in `block in load' /usr/share/redmine/lib/redmine/plugin.rb:164:in `each' /usr/share/redmine/lib/redmine/plugin.rb:164:in `load' /usr/share/redmine/config/initializers/30-redmine.rb:21:in `' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:285:in `load' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:285:in `block in load' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:257:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:285:in `load' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/engine.rb:657:in `block in load_config_initializer' /usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/notifications.rb:170:in `instrument' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/engine.rb:656:in `load_config_initializer' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/engine.rb:614:in `block (2 levels) in ' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/engine.rb:613:in `each' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/engine.rb:613:in `block in ' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:32:in `instance_exec' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:32:in `run' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:61:in `block in run_initializers' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:50:in `each' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:50:in `tsort_each_child' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:60:in `run_initializers' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:361:in `initialize!' /usr/share/redmine/config/environment.rb:14:in `' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:337:in `require' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:337:in `require_environment!' /usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:520:in `block in run_tasks_blocks' Tasks: TOP => db:migrate => db:load_config => environment (See full trace by running task with --trace) dpkg: error processing package redmine (--configure): installed redmine package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of redmine-plugin-pretend: redmine-plugin-pretend depends on redmine (>= 2.3.1~); however: Package redmine is not configured yet. cheers, Andreas redmine-plugin-pretend_0.0.2+git20130821-4.log.gz Description: application/gzip
Bug#920818: Should this package be removed?
On Tue, Jan 29, 2019 at 04:40:47PM +0100, Moritz Muehlenhoff wrote: > Source: mysql-connector-net > Severity: serious > > Last upload three years ago and removed from testing for a year. No objections in two months, filed a removal bug. Cheers, Moritz
Bug#925263: Do not release with Buster
Package: src:pjproject Version: 2.7.2~dfsg-4 Severity: serious Hi, as the sole Uploader of src:pjproject for the last two years I think we should not release Buster with src:pjproject. Reasons: - pjsip is a library where a lot of functionality and behaviour is selected at compile time using #define statements. Most of these define statements alter the ABI due to changing structs, which makes it ill-suited as a system wide library to be used by several programs. - Consequently, src:ring (now called jami) has always been built against an embedded copy and src:asterisk also switched to an embedded copy, both tailored to their needs. There are no other source packages depending on src:pjproject left - python-pjproject shipped by the same source package includes the old pjsua module that has been deprecated according to https://trac.pjsip.org/repos/wiki/Python_SIP_Tutorial . There is no rdep in the Debian archive. We don't package the newer pjsua2 module. - Due to the gone rdeps the version currently in the archive is not the latest upstream version. - Upstream sometimes mixes security fixes with large scale code refactoring/formatting, which makes security updates more painful than they need to be. We don't want to have this additional work for Buster when it's not necessary. Note that at least Asterisk upstream has published security advisories for issues in pjsip before and has patched them by adding the fix as patch to the Asterisk source, which makes it much easier to follow. I'm therefor filing this RC bug to start the autoremoval from Buster. I will revisit the packaging after the release of Buster and either drop the package or get it updated (and possibly backported to buster-backports). Bernhard
Bug#920817: Should this package be removed?
On Tue, Jan 29, 2019 at 04:38:23PM +0100, Moritz Muehlenhoff wrote: > Package: fsgateway > Severity: serious > > Should fsgateway be removed? Already missed stretch, seems dead upstream, > dropped from testing since two years and last upload was in 2015. No objections in two months, filed a removal bug. Cheers, Moritz
Bug#925259: Should this package be removed?
Source: jquery-jplayer Severity: serious Should jquery-jplayer be removed? It's the last package blocking the removal of swftools, it hasn't seen a maintainer upload since 2014 and is thus outdated compared to current upstream and there are no reverse dep in the archive (aside from some theme packages). Cheers, Moritz
Processed: found 925255 in 1:2016.2.22AR.1-3
Processing commands for cont...@bugs.debian.org: > found 925255 1:2016.2.22AR.1-3 Bug #925255 [src:ntfs-3g] ntfs-3g: CVE-2019-9755: heap buffer overflow Marked as found in versions ntfs-3g/1:2016.2.22AR.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 925255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 925256 is forwarded to https://bugs.ghostscript.com/show_bug.cgi?id=700585
Processing commands for cont...@bugs.debian.org: > forwarded 925256 https://bugs.ghostscript.com/show_bug.cgi?id=700585 Bug #925256 [src:ghostscript] ghostscript: CVE-2019-3835: superexec operator is available Set Bug forwarded-to-address to 'https://bugs.ghostscript.com/show_bug.cgi?id=700585'. > thanks Stopping processing here. Please contact me if you need assistance. -- 925256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925255: ntfs-3g: CVE-2019-9755: heap buffer overflow
Source: ntfs-3g Version: 1:2017.3.23AR.3-2 Severity: grave Tags: security upstream fixed-upstream Control: found -1 1:2016.2.22AR.1+dfsg-1 Control: fixed -1 1:2016.2.22AR.1+dfsg-1+deb9u1 Control: fixed -1 1:2017.3.23AR.4-1 Hi, The following vulnerability was published for ntfs-3g, still filling a bug for tracking. CVE-2019-9755[0]: heap buffer overflow 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-9755 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9755 [1] https://sourceforge.net/p/ntfs-3g/ntfs-3g/ci/85c1634a26faa572d3c558d4cf8aaaca5202d4e9/ Regards, Salvatore
Processed: ntfs-3g: CVE-2019-9755: heap buffer overflow
Processing control commands: > found -1 1:2016.2.22AR.1+dfsg-1 Bug #925255 [src:ntfs-3g] ntfs-3g: CVE-2019-9755: heap buffer overflow Marked as found in versions ntfs-3g/1:2016.2.22AR.1+dfsg-1. > fixed -1 1:2016.2.22AR.1+dfsg-1+deb9u1 Bug #925255 [src:ntfs-3g] ntfs-3g: CVE-2019-9755: heap buffer overflow Marked as fixed in versions ntfs-3g/1:2016.2.22AR.1+dfsg-1+deb9u1. > fixed -1 1:2017.3.23AR.4-1 Bug #925255 [src:ntfs-3g] ntfs-3g: CVE-2019-9755: heap buffer overflow Marked as fixed in versions ntfs-3g/1:2017.3.23AR.4-1. -- 925255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925256: ghostscript: CVE-2019-3835: superexec operator is available
Source: ghostscript Version: 9.26a~dfsg-2 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 9.26a~dfsg-0+deb9u1 Hi, The following vulnerability was published for ghostscript. CVE-2019-3835[0]: superexec operator is available 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-3835 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3835 Regards, Salvatore
Processed: ghostscript: CVE-2019-3838: forceput in DefineResource is still accessible
Processing control commands: > found -1 9.26a~dfsg-0+deb9u1 Bug #925257 [src:ghostscript] ghostscript: CVE-2019-3838: forceput in DefineResource is still accessible Marked as found in versions ghostscript/9.26a~dfsg-0+deb9u1. -- 925257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ghostscript: CVE-2019-3835: superexec operator is available
Processing control commands: > found -1 9.26a~dfsg-0+deb9u1 Bug #925256 [src:ghostscript] ghostscript: CVE-2019-3835: superexec operator is available Marked as found in versions ghostscript/9.26a~dfsg-0+deb9u1. -- 925256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925257: ghostscript: CVE-2019-3838: forceput in DefineResource is still accessible
Source: ghostscript Version: 9.26a~dfsg-2 Severity: grave Tags: security upstream Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=700576 Control: found -1 9.26a~dfsg-0+deb9u1 Hi, The following vulnerability was published for ghostscript. CVE-2019-3838[0]: forceput in DefineResource is still accessible 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-3838 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3838 Regards, Salvatore
Bug#924032: marked as done (mpqc3: FTBFS: Could NOT find MPI)
Your message dated Thu, 21 Mar 2019 21:41:22 +0100 with message-id and subject line Re: mpqc3: FTBFS: Could NOT find MPI has caused the Debian Bug report #924032, regarding mpqc3: FTBFS: Could NOT find MPI 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.) -- 924032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mpqc3 Version: 0.0~git20170114-4.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, mpqc3 FTBFS in sid and buster with [...] -- Detecting Fortran/C Interface -- Detecting Fortran/C Interface - Found GLOBAL and MODULE mangling -- Verifying Fortran/CXX Compiler Compatibility -- Verifying Fortran/CXX Compiler Compatibility - Success -- Found PAPI: /usr/lib/x86_64-linux-gnu/libpapi.a -- Found MPI_C: /usr/lib/x86_64-linux-gnu/libmpich.so (found version "3.1") -- Could NOT find MPI_CXX (missing: MPI_CXX_WORKS) -- Found MPI_Fortran: /usr/lib/x86_64-linux-gnu/libmpichfort.so (found version "3.1") -- Could NOT find MPI (missing: MPI_CXX_FOUND) (found version "3.1") CMake Error at external/MPI:36 (message): MPI not found Call Stack (most recent call first): external/External:8 (include) CMakeLists.txt:330 (include) -- Configuring incomplete, errors occurred! Andreas BTW, why does it link statically against papi? mpqc3.buster.build.gz Description: application/gzip --- End Message --- --- Begin Message --- On Mon, 18 Mar 2019 18:01:51 +0100 Andreas Tille wrote: > > But Alastair mentioned that MPICH was fixed, so yay. > > Please make sure you will care for the bug closing etc. I can confirm that it now builds again ... Andreas--- End Message ---
Bug#920992: marked as done (qt4-x11: FTBFS against libmariadb3 on amd64,i386,armhf)
Your message dated Thu, 21 Mar 2019 20:24:05 +0100 with message-id <5fa6513e-ed9e-7072-21c8-5be6b36ea...@debian.org> and subject line Re: qt4-x11: FTBFS against libmariadb3 on amd64,i386,armhf has caused the Debian Bug report #920992, regarding qt4-x11: FTBFS against libmariadb3 on amd64,i386,armhf 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.) -- 920992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt4-x11 Version: 4:4.8.7+dfsg-17 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, qt4-x11 did FTBFS against mariadb-10.3 on a few architectures: https://buildd.debian.org/status/package.php?p=qt4-x11&suite=unstable but given that you planned to remove Qt4, I didn't care about this package during my rebuild tests. Andreas --- End Message --- --- Begin Message --- On Thu, 31 Jan 2019 13:06:02 +0100 Andreas Beckmann wrote: > qt4-x11 did FTBFS against mariadb-10.3 on a few architectures: This was unrelated to mariadb-10.3, probably a compiler or toolchain issue. Finally built after a few givebacks and updates of other packages. Andreas--- End Message ---
Bug#925196: marked as done (gitlab: CVE-2019-9866: Project Runner Token Exposed Through Issues Quick Actions)
Your message dated Thu, 21 Mar 2019 19:20:15 + with message-id and subject line Bug#925196: fixed in gitlab 11.8.3-1 has caused the Debian Bug report #925196, regarding gitlab: CVE-2019-9866: Project Runner Token Exposed Through Issues Quick Actions 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.) -- 925196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gitlab Version: 11.8.2-3 Severity: grave Tags: security upstream Hi, The following vulnerability was published for gitlab. CVE-2019-9866[0]: Project Runner Token Exposed Through Issues Quick Actions 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-9866 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9866 [1] https://about.gitlab.com/2019/03/20/critical-security-release-gitlab-11-dot-8-dot-3-released/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: gitlab Source-Version: 11.8.3-1 We believe that the bug you reported is fixed in the latest version of gitlab, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sruthi Chandran (supplier of updated gitlab 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, 22 Mar 2019 00:19:33 +0530 Source: gitlab Binary: gitlab gitlab-common Architecture: source Version: 11.8.3-1 Distribution: unstable Urgency: high Maintainer: Debian Ruby Extras Maintainers Changed-By: Sruthi Chandran Description: gitlab - git powered software platform to collaborate on code (non-omnibus gitlab-common - git powered software platform to collaborate on code (common) Closes: 925196 Changes: gitlab (11.8.3-1) unstable; urgency=high . [ Pirate Praveen ] * Set minimum version of git to 2.18 . [ Sruthi Chandran ] * New upstream version 11.8.3 (Closes: #925196) (Fixes: CVE-2019-9866) Checksums-Sha1: 5da18b312fa9bba4d4df3a8c9ffac500ea903bbc 2268 gitlab_11.8.3-1.dsc 0dd018731b390f64dbb930ed0bd7b6e58e14b54f 47911944 gitlab_11.8.3.orig.tar.xz 8f269044faefe3d7f2f8c714f70e0f8d24556190 1252976 gitlab_11.8.3-1.debian.tar.xz f68629f6d2de8f5cbc0d4d1e39285339866b9291 11522 gitlab_11.8.3-1_source.buildinfo Checksums-Sha256: 58fd644d099a7bc37d4874e0cdcdc353a25d771f717146605a6e645d168763ed 2268 gitlab_11.8.3-1.dsc 235874cdb83d0818f0234cac9c649ea753ffb885d9786accd7960dc728563f10 47911944 gitlab_11.8.3.orig.tar.xz 4fe224c3cc03cb8ca68b413f9aa3cf7687b469ccd02c569a9c4db6230135ada2 1252976 gitlab_11.8.3-1.debian.tar.xz 1ac3f20dd0d4adbed024c0966353de8bde95c1facb76efb65ac9b5c6d90920cd 11522 gitlab_11.8.3-1_source.buildinfo Files: fede48f7de2a23377b969e86eefe9b1f 2268 net optional gitlab_11.8.3-1.dsc e1406ce444c3a92190ccf129d1941ea5 47911944 net optional gitlab_11.8.3.orig.tar.xz 04170ec0483c054656c6d143f2a32df9 1252976 net optional gitlab_11.8.3-1.debian.tar.xz 94727ef6ba5ea27103c0f2cacb98fe6c 11522 net optional gitlab_11.8.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsclPZxif+sAmSPvz1N6yL8C5bhUFAlyT3jcACgkQ1N6yL8C5 bhVvEhAAnfPNBdWJNHG49KuVOx9iX5fkt2TM9hCuk7HxKsXiIQs2s62Froku0xqf tsQ711N8VdbB59sTEId0JQH0qFmwbJtXlJbUqkHPAc3DCjYWgI+vBL2JSxFubQ5y SnOFp1chU+8TegIMt86XpFXgaL6ZIh5ZJXacV6Qknf19F2tdPpA2SGZC7q+6rZJy Nufcb3uEFU2GOSXRNmIYe3L3xRoDKRqvkrOneQGVG2AJKzxC18LRAJRCpM05pvZI y3etcwsJshlSFM5gkFB+Fl21g36XgDbnZSlgrBVEy0AIv1tjojL7zHAjDzUOP0KY Gk6F6uPDujPG2eGLlO6Yjt9j0jG56El8P4qQBbOAyRPNdzyNHHqv5e7viUfZjJRJ GVW/tdoL9Zns9K2vh9fR8Go4uBamGTFiPDcyw83AYjoPZGhpXPuuuEc3mxIefqgP iRUSHyJiOXvg/swr6MdGUMd7W912i7UT6uH1hxSx70T5ib8hUkBv8vAAQlMmSrHT aMs5aVZ1Oa5e8nql2gZvLwbPXomiMmZjrO/0sxSlDvUt1Q+f420D1thPXSIWFlfo jXd7E2ipRGSy4uK2ScETXyy+vSdGZoXMBMqVIgjCAj68fTxXe3WwgE9xj6Zu4lrY jfpiAPgc0/HE4daGxO95mRg0F4HPi+hB8kfqXorjBAFsmJrtojc= =GEoo -END PGP SIGNATURE End Message ---
Bug#924859: marked as done (libfurl-perl: FTBFS: tests failed)
Your message dated Thu, 21 Mar 2019 18:49:51 + with message-id and subject line Bug#924859: fixed in libfurl-perl 3.13-2 has caused the Debian Bug report #924859, regarding libfurl-perl: FTBFS: tests failed 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.) -- 924859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libfurl-perl Version: 3.13-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > test -x debian/rules > mkdir -p "." > cd . && perl -I. Build.PL --installdirs vendor --config ccflags="-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv > -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64" --config cxxflags="-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" --config cppflags="-Wdate-time -D_FORTIFY_SOURCE=2 > -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe > -I/usr/local/include" --config lddlflags="-Wl,-z,relro -shared > -L/usr/local/lib -fstack-protector-strong" --destdir > /<>/debian/libfurl-perl > Creating new 'Build' script for 'Furl' version '3.13' > cd . && ./Build build > cp lib/Furl/ZlibStream.pm blib/lib/Furl/ZlibStream.pm > cp lib/Furl/HTTP.pm blib/lib/Furl/HTTP.pm > cp lib/Furl/ConnectionCache.pm blib/lib/Furl/ConnectionCache.pm > cp lib/Furl/Headers.pm blib/lib/Furl/Headers.pm > cp lib/Furl/Request.pm blib/lib/Furl/Request.pm > cp lib/Furl/Response.pm blib/lib/Furl/Response.pm > cp lib/Furl.pm blib/lib/Furl.pm > touch debian/stamp-perl-build > cd . && ./Build test --verbose 1 > # Perl/v5.28.1 > # Furl/3.13 > # Net::IDN::Encode/2.5 > # IO::Socket::SSL/2.060 > # Compress::Raw::Zlib/2.076 > t/00_compile.t .. > 1..1 > ok 1 - use Furl; > ok > t/01_version.t .. > ok 1 > 1..1 > ok > t/100_low/01_simple.t ... > ok 1 > ok 2 > ok 3 - request()/1 > ok 4 > ok 5 - header > ok 6 > ok 7 > ok 8 > ok 9 - request()/2 > ok 10 > ok 11 - header > ok 12 > ok 13 > ok 14 > ok 15 - request()/3 > ok 16 > ok 17 - header > ok 18 > ok 19 > ok 20 - get()/1 > ok 21 > ok 22 - header > ok 23 > ok 24 > ok 25 - get()/2 > ok 26 > ok 27 - header > ok 28 > ok 29 > ok 30 - get()/3 > ok 31 > ok 32 - header > ok 33 > 1..33 > ok > t/100_low/03_redirect.t . > # Subtest: redirect > ok 1 > ok 2 > ok 3 > ok 4 > 1..4 > ok 1 - redirect > # Subtest: not enough redirect > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > 1..5 > ok 2 - not enough redirect > # Subtest: over max redirect > ok 1 - code ok > ok 2 - msg ok > ok 3 - content length ok > ok 4 - url ok > ok 5 - content ok > 1..5 > ok 3 - over max redirect > # Subtest: POST redirects > ok 1 - POST into 301 results in a POST > ok 2 - POST into 302 is implemented as 303 > ok 3 - POST into 303 results in a GET > ok 4 - POST into 307 results in a POST > 1..4 > ok 4 - POST redirects > 1..4 > ok > t/100_low/04_chunked.t .. > # -- TEST (packets: 1) > ok 1 - status > ok 2 - content > # -- TEST (packets: 3) > ok 3 - status > ok 4 - content > # -- TEST (packets: 1024) > ok 5 - status > ok 6 - content > # -- TEST (packets: 1) > ok 7 - status > ok 8 - content > # -- TEST (packets: 3) > ok 9 - status > ok 10 - content > # -- TEST (packets: 1024) > ok 11 - status > ok 12 - content > 1..12 > ok > t/100_low/05_slowloris.t > ok 1 > ok 2 - request()/1 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 - request()/2 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 - request()/3 > ok 13 > ok 14 > ok 15 > ok 16 - get()/1 > ok 17 > ok 18 > ok 19 > ok 20 - get()/2 > ok 21 > ok 22 > ok 23 > ok 24 - get()/3 > ok 25 > ok 26 > ok 27 > 1..27 > ok > t/100_low/06_errors.t ... > ok 1 - missuse > ok 2 - missuse > ok 3 - malformed URL: hogehoge > ok 4 - malformed URL: http://example.com:80foobar > ok 5 - malformed URL: http://example.com: > # Errorneous::Server listening > ok 6 > ok 7 - request()/1 > ok 8 > ok 9 > ok 10 - content: Unexpected EOF while reading response header at > t/100_low/06_errors.t line 66. > # > ok
Bug#924809: marked as done (node-timeago.js: FTBFS: webpack can't be used with uglifyjs)
Your message dated Thu, 21 Mar 2019 15:50:35 + with message-id and subject line Bug#924809: fixed in node-timeago.js 3.0.2+dfsg-2 has caused the Debian Bug report #924809, regarding node-timeago.js: FTBFS: webpack can't be used with uglifyjs 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.) -- 924809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-timeago.js Version: 3.0.2+dfsg-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11~), nodejs (>= 6), uglifyjs, webpack > Filtered Build-Depends: debhelper (>= 11~), nodejs (>= 6), uglifyjs, webpack > dpkg-deb: building package 'sbuild-build-depends-node-timeago.js-dummy' in > '/<>/resolver-WQ6dSh/apt_archive/sbuild-build-depends-node-timeago.js-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-node-timeago.js-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-WQ6dSh/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-WQ6dSh/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-WQ6dSh/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-WQ6dSh/apt_archive ./ Sources [520 B] > Get:5 copy:/<>/resolver-WQ6dSh/apt_archive ./ Packages [602 B] > Fetched 2085 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install node-timeago.js build dependencies (apt-based resolver) > --- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-node-timeago.js-dummy : Depends: webpack but it is not > going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/node-timeago.js_3.0.2+dfsg-1_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: node-timeago.js Source-Version: 3.0.2+dfsg-2 We believe that the bug you reported is fixed in the latest version of node-timeago.js, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-timeago.js 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: Thu, 21 Mar 2019 16:32:22 +0100 Source: node-timeago.js Architecture: source Version: 3.0.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Xavier Guimard Changed-By: Xavier Guimard Closes: 924809 Changes: node-timeago.js (3.0.2+dfsg-2) unstable; urgency=medium . * Team upload * Switch minimal test to autopkgtest * Add upstream/metadata * Pa
Bug#924807: marked as done (node-jschardet: FTBFS: webpack can't be used with uglifyjs)
Your message dated Thu, 21 Mar 2019 15:20:48 + with message-id and subject line Bug#924807: fixed in node-jschardet 1.6.0+dfsg-2 has caused the Debian Bug report #924807, regarding node-jschardet: FTBFS: webpack can't be used with uglifyjs 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.) -- 924807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-jschardet Version: 1.6.0+dfsg-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, > webpack > Filtered Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, > webpack > dpkg-deb: building package 'sbuild-build-depends-node-jschardet-dummy' in > '/<>/resolver-wJ4w5E/apt_archive/sbuild-build-depends-node-jschardet-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-node-jschardet-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-wJ4w5E/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-wJ4w5E/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-wJ4w5E/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-wJ4w5E/apt_archive ./ Sources [518 B] > Get:5 copy:/<>/resolver-wJ4w5E/apt_archive ./ Packages [600 B] > Fetched 2081 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install node-jschardet build dependencies (apt-based resolver) > -- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-node-jschardet-dummy : Depends: webpack but it is not > going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/node-jschardet_1.6.0+dfsg-1_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: node-jschardet Source-Version: 1.6.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of node-jschardet, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-jschardet 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: Thu, 21 Mar 2019 15:52:01 +0100 Source: node-jschardet Architecture: source Version: 1.6.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Xavier Guimard Changed-By: Xavier Guimard Closes: 924807 Changes: node-jschardet (1.6.0+dfsg-2) unstable; urgency=medium . * Team upload * Add debian/clean * Use node-uglify if uglifyjs isn't available (Cl
Bug#924807: Bug #924807 in node-jschardet marked as pending
Control: tag -1 pending Hello, Bug #924807 in node-jschardet 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-jschardet/commit/b884e5c5ca56e5de3c6ae5243b18b6b10c331048 Use node-uglify if uglifyjs isn't available Closes: #924807 (this message was generated automatically) -- Greetings https://bugs.debian.org/924807
Processed: Bug #924807 in node-jschardet marked as pending
Processing control commands: > tag -1 pending Bug #924807 [node-jschardet] node-jschardet: FTBFS: webpack can't be used with uglifyjs Added tag(s) pending. -- 924807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
Le 21/03/19 à 09:32, Florian Weimer a écrit : * Laurent Bigonville: Le 19/03/19 à 19:43, Florian Weimer a écrit : Can you compile the software using _DEFAULT_SOURCE (well, the default) or _GNU_SOURCE instead? Yes, the software can be compile when _XOPEN_SOURCE is not defined or when _GNU_SOURCE is defined instead Sorry, what I was trying to ask is whether this would be an acceptable change for you. Ah. For the specific case I ran across, yes. But I don't know if that change breaks other projects
Bug#925227: biabam: debian-rules-missing-required-target binary-arch
Source: biabam Version: 0.9.7-7 Severity: serious Tags: sid buster debian-rules-missing-required-target causes an ftp-master autoreject. Andreas
Bug#925226: openstack-dashboard: needs Breaks: python-app-catalog-ui, python-designate-dashboard, python-murano-dashboard, python-zaqar-ui
Package: openstack-dashboard Version: 3:14.0.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package removes files that were installed by another package. At least I assume that openstack-dashboard is the one responsible here. I don't have time right now to test whether this actually works, but given that these 4 packages no longer exist, it's probably safe anyway to add unversioned Breaks against them. These problems were observed during upgrades from stretch to sid, but probably the same may will happen on stretch->buster upgrades. >From the attached log (scroll to the bottom...): 4m7.3s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/app_catalog/__init__.py (from python-app-catalog-ui package) debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/app_catalog/enabled/_80_project_catalog_panel_group.py (from python-app-catalog-ui package) debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/app_catalog/enabled/_90_project_app_catalog_panel.py (from python-app-catalog-ui package) [...] 5m14.2s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/enabled/_1710_project_dns_panel_group.py (from python-designate-dashboard package) debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/enabled/_1721_dns_zones_panel.py (from python-designate-dashboard package) debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/enabled/_1722_dns_reversedns_panel.py (from python-designate-dashboard package) [...] 5m29.4s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/enabled/_50_murano.py (from python-murano-dashboard package) debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/static/muranodashboard/css/catalog.css (from python-murano-dashboard package) debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/static/muranodashboard/css/checkbox.css (from python-murano-dashboard package) [...] 4m9.9s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /usr/share/openstack-dashboard/openstack_dashboard/enabled/_1510_project_messaging_group.py (from python-zaqar-ui package) cheers, Andreas python-app-catalog-ui_None.log.gz Description: application/gzip
Bug#916145: closure-compiler: Not working with recent JS code
Hello, Is that bug still valid with current version 20130227+dfsg1-10 ? thanks On Mon, 10 Dec 2018 17:42:12 +0100 Roland Gruber wrote: > Package: closure-compiler > Version: 20130227+dfsg1-9 > Severity: important > > Dear Maintainer, > > the current version is so old that it got incompatible with recent JS code. > E.g. jQuery 3.3.1 cannot be minified as the tool reports parsing errors. > > Please either update the tool or remove it from the archive. This is now > 5 years in unmaintained state. > > > -- System Information: > Debian Release: 9.6 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages closure-compiler depends on: > ii default-jre-headless [java6-runtime-headless]2:1.8-58 > ii java-wrappers0.1.28 > ii libclosure-compiler-java 20130227+dfsg1-9 > ii openjdk-8-jre-headless [java6-runtime-headless] 8u181-b13-2~deb9u1 > ii oracle-java8-jdk [java6-runtime-headless]8u77 > > closure-compiler recommends no packages. > > closure-compiler suggests no packages. > > -- no debconf information > > -- Thierry Fauck @ fr.ibm.com
Bug#909750: applications tries to write to /usr/* directories via libfontconfig1
On Sun, 11 Nov 2018 12:04:06 +0100 Jakub Wilk wrote: > * Laurent Bigonville , 2018-11-11, 11:18: > >Do you have any .uuid files in these directories? > > IIRC, I didn't have any back then. > > >Can you try to run "fc-cache -s -f -v" (as root) and see if it helps. > > I think I upgraded some font package, which triggered fontconfig, which > ran the aforementioned command. Yes, it did help. > > >What file system do you use for /usr/share/fonts/? > > ext4 > > >The only occurrence I'm seeing on my system is: > > > >openat(AT_FDCWD, "/usr/lib/firefox/fonts/.uuid.TMP-EWjEq0", > >O_RDWR|O_CREAT|O_EXCL|O_CLOEXEC, 0600) = -1 EACCES (Permission denied) > > Now it's the only occurrence for me, too. > > -- > Jakub Wilk > Hello, With current packages I don't see any more issues of openat() EACESS(...) when tracing firefox-bin Can you confirm and state about that bug Thanks
Processed: reassign 924829 to texlive-latex-extra, forcibly merging 920459 924829, affects 920459
Processing commands for cont...@bugs.debian.org:
> reassign 924829 texlive-latex-extra
Bug #924829 [src:caffe] caffe: FTBFS: Fatal error occurred, no output PDF file
produced!
Bug reassigned from package 'src:caffe' to 'texlive-latex-extra'.
No longer marked as found in versions caffe/1.0.0+git20180821.99bd997-2.
Ignoring request to alter fixed versions of bug #924829 to the same values
previously set
> forcemerge 920459 924829
Bug #920459 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #920621 {Done: Norbert Preining }
[texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15
Bug #921272 {Done: Norbert Preining }
[texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is
used
Bug #921299 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921776 {Done: Norbert Preining }
[texlive-latex-extra] bliss: FTBFS (LaTeX error)
Bug #921779 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921783 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921789 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921802 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921838 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #924829 [texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output
PDF file produced!
Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'.
Marked Bug as done
Marked as fixed in versions texlive-extra/2018.20190227-1 and
texlive-extra/2018.20190131-2.
Marked as found in versions texlive-extra/2018.20190131-1 and
texlive-extra/2018.20190207-1.
Added tag(s) patch and ftbfs.
Bug #920621 {Done: Norbert Preining }
[texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15
Bug #921272 {Done: Norbert Preining }
[texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is
used
Bug #921299 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921776 {Done: Norbert Preining }
[texlive-latex-extra] bliss: FTBFS (LaTeX error)
Bug #921779 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921783 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921789 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921802 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921838 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Merged 920459 920621 921272 921299 921776 921779 921783 921789 921802 921838
924829
> affects 920459 src:caffe
Bug #920459 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #920621 {Done: Norbert Preining }
[texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15
Bug #921272 {Done: Norbert Preining }
[texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is
used
Bug #921299 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921776 {Done: Norbert Preining }
[texlive-latex-extra] bliss: FTBFS (LaTeX error)
Bug #921779 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921783 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921789 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921802 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #921838 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
Bug #924829 {Done: Norbert Preining }
[texlive-latex-extra] caffe: FTBFS: Fatal error occ
Bug#923759: One step ahead but compile errors (Was: netlib-java contains nealy empty jar)
Hi, On Tue, Mar 12, 2019 at 10:58:33AM +0100, Andreas Tille wrote: > I realised that > > /usr/share/java/netlib-java-0.9.3.jar > > is nearly empty, specifically > > /org/netlib/arpack > /org/netlib/blas > /org/netlib/lapack > > do not contain any classes. > ... > and the previous version on snapshots[1] contains a proper jar file with > all classes I suspect some issue with a change in the Java VM. > Unfortunately I have no idea how to fix this and hope Debian Java team > can help here. I went a bit further into the build system of netlib-java and found out that build.xml is lacking a compile target. I added this in my last commit[2] and need to admit that I have no idea why the package has ever build before. Unfortunately the build now leaves me with some errors: ... compile: [javac] Compiling 3 source files [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:48: error: package org.netlib.util does not exist [javac] import org.netlib.util.StringW; [javac] ^ [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:49: error: package org.netlib.util does not exist [javac] import org.netlib.util.booleanW; [javac] ^ [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:50: error: package org.netlib.util does not exist [javac] import org.netlib.util.doubleW; [javac] ^ [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:51: error: package org.netlib.util does not exist [javac] import org.netlib.util.floatW; [javac] ^ [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:52: error: package org.netlib.util does not exist [javac] import org.netlib.util.intW; [javac] ^ [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:104: error: cannot find symbol [javac] classDefs.put(intW.class, "intW"); [javac] ^ [javac] symbol: class intW [javac] location: class JavaGenerator [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:105: error: cannot find symbol [javac] classDefs.put(doubleW.class, "doubleW"); [javac] ^ [javac] symbol: class doubleW [javac] location: class JavaGenerator [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:106: error: cannot find symbol [javac] classDefs.put(booleanW.class, "booleanW"); [javac] ^ [javac] symbol: class booleanW [javac] location: class JavaGenerator [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:107: error: cannot find symbol [javac] classDefs.put(floatW.class, "floatW"); [javac] ^ [javac] symbol: class floatW [javac] location: class JavaGenerator [javac] /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:108: error: cannot find symbol [javac] classDefs.put(StringW.class, "StringW"); [javac] ^ [javac] symbol: class StringW [javac] location: class JavaGenerator [javac] 10 errors BUILD FAILED /build/netlib-java-0.9.3/build.xml:30: Compile failed; see the compiler error output for details. Total time: 1 second make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 Any hint how to get rid of these? Kind regards Andreas. > [1] > https://snapshot.debian.org/archive/debian/20160625T105051Z/pool/main/n/netlib-java/libnetlib-java_0.9.3-3_all.deb [2] https://salsa.debian.org/java-team/netlib-java/blob/master/debian/patches/add_compile_target.patch -- http://fam-tille.de
Bug#876905: qtwebkit should not be release with buster
On Tue, 26 Sep 2017 22:15:12 +0300 Adrian Bunk wrote: > Source: qtwebkit > Version: 2.3.4.dfsg-9.1 > Severity: serious > Tags: buster sid > > qtwebkit should not be release with buster > (RC bugs are already open against all r-deps). > > As version 2.3.4.dfsg-10 is part of buster what do we do with that bug ? thanks
Bug#912333: Is this fixed in version 8u212-b01-1~deb9u1?
Hi. Does version 8u212-b01-1~deb9u1 in security fixes this issue? (I believe it could). Thanks.
Bug#925212: marked as done (yubikey-manager: ykman doesn't properly handle static passwords on non-QWERTY keyboards)
Your message dated Thu, 21 Mar 2019 11:49:08 + with message-id and subject line Bug#925212: fixed in yubikey-manager 2.1.0-1 has caused the Debian Bug report #925212, regarding yubikey-manager: ykman doesn't properly handle static passwords on non-QWERTY keyboards 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.) -- 925212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yubikey-manager Version: 2.0.0-2 Severity: serious Tags: fixed-upstream upstream pending Justification: RoM, severe usability degradation for many users -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 See https://github.com/Yubico/yubikey-manager/pull/220 - -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yubikey-manager depends on: ii pcscd1.8.24-1 ii python3 3.7.2-1 ii python3-click7.0-1 ii python3-yubikey-manager 2.0.0-2 yubikey-manager recommends no packages. yubikey-manager suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlyTcjMRHG5pY29vQGRl Ymlhbi5vcmcACgkQ5vmO4pLV7MuPSQ//Tub1Si5y5+JWfnAMj5tUtC/W7AIXC/Z5 LDW0irOlnXpKiT2FQGv0/wV7KXU1wlAkLuA4YGpHP4SDvBnohB5+ix3oWPvHnkX8 fP75V+SWsLWLPGmCtcYbfTxETs9o2zDmv13GIJMBGP9DVU2ucO+98rGnpG3y2gRB DPOilDR648ZbPkWcYrsm72oQ0SeREXZ1O27EsnRCCM5pPjAOfihpUbyNSdRkLmru /RbHsHlC7ObkeCB2iOuMEuIAwHojERTML/fNB9B/tpTJwO+3RnkQ+/rkgvn9ceIb I93H4pA9lYhFDr8/ipBha8A1rGAx5p/2S5wkMwNhZs3oRAoU6PR4vH3TE8Yll26X UyA9iTaRshHp0LBlMmXxwerKNXBtE84ww+R0hue2mHUp3YMpcdWYpqjfKQvatuof 0Zrlfc7j2wjADoL82Hei9VeC8L0WJn+ddS7Y/XiRfsFv2fK7d9JyhufYmpf18d7p 8e/ASIJvdK1+RIf0XF+Qt6AfdisDGz1XwxuYR/sHGc1N1yAoqOedJNS7FdAq74Kl RQTEHWlzJvNZbo/S1AH0+uUYynBLZmkriBPoPpFaEl0oWNIr3GHXHIuZeLPewLxR 5QnLgFA7rflmw0tz/AG8McKZvRwKmnx7kruJ6pH22XSyW8B59zh+u+WsJHx6fQ+J WLKGOaSku5o= =iCFg -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: yubikey-manager Source-Version: 2.1.0-1 We believe that the bug you reported is fixed in the latest version of yubikey-manager, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Braud-Santoni (supplier of updated yubikey-manager 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: Thu, 21 Mar 2019 12:30:40 +0100 Source: yubikey-manager Architecture: source Version: 2.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Nicolas Braud-Santoni Closes: 925212 Changes: yubikey-manager (2.1.0-1) unstable; urgency=medium . * New upstream release (2019-03-11) + PIV: Verify that the PIN must be between 6 - 8 characters long + PIV: Malformed certificates are now handled better + OpenPGP: The openpgp touch command now shows current touch policies + Bugfix: Fix support for german (DE) keyboard layout for static passwords Closes: #925212 . * debian/control: Add Afif Elghraoui as uploader Checksums-Sha1: a9174191bf256f7fe4d15f302f16a3f38ddecee1 2299 yubikey-manager_2.1.0-1.dsc df61834dad62130e4b6cb74847b83a7ab4fe45d9 132797 yubikey-manager_2.1.0.orig.tar.gz fe2be15115a638104283aa0c369d0bf5c78c6fb7 65368 yubikey-manager_2.1.0-1.debian.tar.xz bcf2fc1876c7cc2cecca47cba31416810dc275da 6782 yubikey-manager_2.1.0-1_amd64.buildinfo Checksums-Sha256: dcb6bad49b284cf7c8d2e8cc9cccb42d32a70bebd0d66036d1c1bd06cc020032 2299 yubikey-manager_2.1.0-1.dsc d59d5cd9b5b040077ef7741250476d8583bf961519b6576af163022315ab
Processed: unblock: yubikey-manager/2.1.0-1
Processing control commands: > block 925212 by -1 Bug #925212 [yubikey-manager] yubikey-manager: ykman doesn't properly handle static passwords on non-QWERTY keyboards 925212 was not blocked by any bugs. 925212 was not blocking any bugs. Added blocking bug(s) of 925212: 925213 -- 925212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925212 925213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919735: ruby-premailer-rails: FTBFS (failing tests)
On Fri, 18 Jan 2019 23:41:55 + Santiago Vila wrote:
> Failures:
>
> 1) Premailer::Rails::Hook when message also contains a text part does not
> replace any message part
> Failure/Error:
>expect { run_hook(message) }.to_not \
> change { message.all_parts.map(&:content_type) }
>
>expected `message.all_parts.map(&:content_type)` not to have changed,
> but did change from ["multipart/alternative;
> boundary=\"--==_mimepart_5c425ea927787_76ba2ab410f145c014523\";
> charset=UTF-8", "text/html; charset=UTF-8", "text/plain; charset=UTF-8"] to
> ["multipart/alternative;
> boundary=\"--==_mimepart_5c425ea927787_76ba2ab410f145c014523\";
> charset=UTF-8", "text/plain; charset=UTF-8", "text/html; charset=UTF-8"]
> # ./spec/integration/hook_spec.rb:93:in `block (3 levels) in (required)>'
>
This will be fixed when ruby-premailer is updated to 1.11.1 but that
update causes some test failures of its own.
signature.asc
Description: OpenPGP digital signature
Bug#925212: yubikey-manager: ykman doesn't properly handle static passwords on non-QWERTY keyboards
Package: yubikey-manager Version: 2.0.0-2 Severity: serious Tags: fixed-upstream upstream pending Justification: RoM, severe usability degradation for many users -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 See https://github.com/Yubico/yubikey-manager/pull/220 - -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yubikey-manager depends on: ii pcscd1.8.24-1 ii python3 3.7.2-1 ii python3-click7.0-1 ii python3-yubikey-manager 2.0.0-2 yubikey-manager recommends no packages. yubikey-manager suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlyTcjMRHG5pY29vQGRl Ymlhbi5vcmcACgkQ5vmO4pLV7MuPSQ//Tub1Si5y5+JWfnAMj5tUtC/W7AIXC/Z5 LDW0irOlnXpKiT2FQGv0/wV7KXU1wlAkLuA4YGpHP4SDvBnohB5+ix3oWPvHnkX8 fP75V+SWsLWLPGmCtcYbfTxETs9o2zDmv13GIJMBGP9DVU2ucO+98rGnpG3y2gRB DPOilDR648ZbPkWcYrsm72oQ0SeREXZ1O27EsnRCCM5pPjAOfihpUbyNSdRkLmru /RbHsHlC7ObkeCB2iOuMEuIAwHojERTML/fNB9B/tpTJwO+3RnkQ+/rkgvn9ceIb I93H4pA9lYhFDr8/ipBha8A1rGAx5p/2S5wkMwNhZs3oRAoU6PR4vH3TE8Yll26X UyA9iTaRshHp0LBlMmXxwerKNXBtE84ww+R0hue2mHUp3YMpcdWYpqjfKQvatuof 0Zrlfc7j2wjADoL82Hei9VeC8L0WJn+ddS7Y/XiRfsFv2fK7d9JyhufYmpf18d7p 8e/ASIJvdK1+RIf0XF+Qt6AfdisDGz1XwxuYR/sHGc1N1yAoqOedJNS7FdAq74Kl RQTEHWlzJvNZbo/S1AH0+uUYynBLZmkriBPoPpFaEl0oWNIr3GHXHIuZeLPewLxR 5QnLgFA7rflmw0tz/AG8McKZvRwKmnx7kruJ6pH22XSyW8B59zh+u+WsJHx6fQ+J WLKGOaSku5o= =iCFg -END PGP SIGNATURE-
Processed: retitle 925211 to uglifyjs conflicts with webpack which can hinder JS maintainers work ...
Processing commands for cont...@bugs.debian.org: > retitle 925211 uglifyjs conflicts with webpack which can hinder JS > maintainers work Bug #925211 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Changed Bug title to 'uglifyjs conflicts with webpack which can hinder JS maintainers work' from 'node-jschardet: FTBFS: build-dependency not installable: webpack'. > severity 925211 important Bug #925211 [uglify-js] uglifyjs conflicts with webpack which can hinder JS maintainers work Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 925211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unmerging 924807, cloning 924807, reassign 924807 to node-jschardet ...
Processing commands for cont...@bugs.debian.org: > unmerge 924807 Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Disconnected #924807 from all other report(s). > clone 924807 -1 Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Bug 924807 cloned as bug 925211 > reassign 924807 node-jschardet Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Bug reassigned from package 'uglify-js' to 'node-jschardet'. Ignoring request to alter found versions of bug #924807 to the same values previously set Ignoring request to alter fixed versions of bug #924807 to the same values previously set > reassign 924809 node-timeago.js Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Bug reassigned from package 'uglify-js' to 'node-timeago.js'. Ignoring request to alter found versions of bug #924809 to the same values previously set Ignoring request to alter fixed versions of bug #924809 to the same values previously set > retitle 924807 node-jschardet: FTBFS: webpack can't be used with uglifyjs Bug #924807 [node-jschardet] node-jschardet: FTBFS: build-dependency not installable: webpack Changed Bug title to 'node-jschardet: FTBFS: webpack can't be used with uglifyjs' from 'node-jschardet: FTBFS: build-dependency not installable: webpack'. > retitle 924809 node-timeago.js: FTBFS: webpack can't be used with uglifyjs Bug #924809 [node-timeago.js] node-timeago.js: FTBFS: build-dependency not installable: webpack Changed Bug title to 'node-timeago.js: FTBFS: webpack can't be used with uglifyjs' from 'node-timeago.js: FTBFS: build-dependency not installable: webpack'. > thanks Stopping processing here. Please contact me if you need assistance. -- 924807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924807 924809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884128: libical: don't release with buster
Hello, As currently we have (for most of the platforms) $ apt-cache madison libical2 libical2 | 2.0.0-4+b2 | http://ftp.fr.debian.org/debian buster/main amd64 Packages libical |2.0.0-4 | http://ftp.fr.debian.org/debian buster/main Sources What do we do with that bug ? Thanks On Wed, 8 Aug 2018 10:39:14 +0200 Emilio Pozuelo Monfort wrote: > On 08/08/18 09:33, Niels Thykier wrote: > > Control: tags -1 moreinfo > > > > On Mon, 11 Dec 2017 19:43:59 +0100 Emilio Pozuelo Monfort > > wrote: > >> Source: libical > >> Version: 2.0.0-1 > >> Severity: serious > >> > >> Hi, > >> > >> We have src:libical3 now, so libical2 should be dropped before the > >> freeze. We shouldn't need to release buster with both libical 2 and 3. > >> Filing this bug so we don't forget about that. > >> > >> Emilio > >> > >> [...] > > Hi Emilio, > > > > We are getting "close" to the transition freeze. If it is still the > > plan to remove libical from Debian buster, please start filing bugs > > against the (remaining) reverse dependencies and have them fixed. > > That's basically kdepimlibs, as cyrus-imapd is not in testing and kmymoney is > already fixed in experimental and just needs an upload to sid. > > kdepimlibs may not be easy though as disabling libical will probably disable > some libs that may be used by rdeps. Someone needs to look at that. I have > just > opened a bug for it and made it block this one. > > Cheers, > Emilio > > -- Thierry Fauck @ fr.ibm.com
Bug#870267: #870267 : still relevant ?
Hi Adrian, do you still feel it makes sense to keep that bug open ? I personally don't, but you're the reporter, so I'd like to have your opinion. László, thanks for the details. Regards, F. On Wed, 20 Mar 2019 19:49:02 +0100, László Böszörményi (GCS) wrote: > Hi Frédéric, > > On Wed, Mar 20, 2019 at 4:03 PM Frédéric Bonnard wrote: > > is this bug still relevant ? > It was never a bug in GraphicsMagick, see the discussion starting > about it[1]. A buildd admin later confirmed it's (it was) a bug on > their side only with the ppc64el-unicamp-01 buildd and they could fix > it. > > > Furthermore, this bug is RC, so may we close it now ? > It's up to you, after Adrian was aggressive about it I let it go. It > has no effect on the package (no migration problem or autoremoval). > > Regards, > Laszlo/GCS > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870267#10 > pgpAussRzC50b.pgp Description: PGP signature
Processed: unreproducible
Processing commands for cont...@bugs.debian.org: > tag 924858 unreproducible Bug #924858 [src:doxygen] doxygen: FTBFS: make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1 Added tag(s) unreproducible. > End of message, stopping processing here. Please contact me if you need assistance. -- 924858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925136: help2man: FTBFS in unstable (dh_clean fails)
On Wed, Mar 20, 2019 at 10:21:39AM +0100, Gianfranco Costamagna wrote: >Looks like README needs a newer timestamp wrt help2man.PL file? [...] >dpkg-buildpackage: info: host architecture amd64 > fakeroot debian/rules clean >test README -nt help2man.PL # maintainer sanity check >make: *** [debian/rules:40: clean] Error 1 Well this is odd, it seems that there has been a change in dpkg-source which breaks this particular sanity check (intended to ensure that I've run the maint-prep step since updating the version in help2man.PL). I suspect that it is related to reproducible builds, since the timestamps that ended up in the tarball have been changed to the changlog timestamp (in fact there are no files in the tarball with later dates). ~/debian/help2man-1.47.9 $ ls -l README help2man.PL -rw-r--r-- 1 bodbod 540 2019-03-18 19:16 README -rwxr-xr-x 1 bodbod 23166 2019-03-18 19:13 help2man.PL ~/debian/help2man-1.47.9 $ tar tvJf ../help2man-1.47.9.tar.xz help2man-1.47.9/README help2man-1.47.9/help2man.PL -rw-r--r-- 0/0 540 2019-03-18 19:10 help2man-1.47.9/README -rwxr-xr-x 0/0 23166 2019-03-18 19:10 help2man-1.47.9/help2man.PL ~/debian/help2man-1.47.9 $ dpkg-parsechangelog -S Date Mon, 18 Mar 2019 19:10:35 +1100 I'll try to find a way to revise this check that will be more robust to this kind of timestamp modification. Somewhat annoyingly, the "test" builtin has -nt and -ot options, but no way to test that timestamps are newer or equal (or even just equal). --bod
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 922346 mesa/18.3.2-1 Bug #922346 [libgl1-mesa-dri] eog: Opened an image and my display server crashed Marked as found in versions mesa/18.3.2-1. > tag 922346 patch Bug #922346 [libgl1-mesa-dri] eog: Opened an image and my display server crashed Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 922346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925208: python-smoke-zephyr: FTBFS randomly (tests hang the autobuilder)
Package: src:python-smoke-zephyr Version: 1.4.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3 --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python setup.py build running build running build_py creating /<>/.pybuild/cpython2_2.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/requirements.py -> /<>/.pybuild/cpython2_2.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/__init__.py -> /<>/.pybuild/cpython2_2.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/utilities.py -> /<>/.pybuild/cpython2_2.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/argparse_types.py -> /<>/.pybuild/cpython2_2.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/job.py -> /<>/.pybuild/cpython2_2.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/configuration.py -> /<>/.pybuild/cpython2_2.7_smoke-zephyr/build/smoke_zephyr I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/requirements.py -> /<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/__init__.py -> /<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/utilities.py -> /<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/argparse_types.py -> /<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/job.py -> /<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr copying smoke_zephyr/configuration.py -> /<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7_smoke-zephyr/build; python2.7 -m unittest discover -v -s /<>/tests -p "[a-z]*.py" test_cache (utilities.UtilitiesCacheTests) ... ok test_cache_cache_clear (utilities.UtilitiesCacheTests) ... ok test_cache_flatten_args (utilities.UtilitiesCacheTests) ... ok test_attribute_dict (utilities.UtilitiesTests) ... ok test_escape_single_quote (utilities.UtilitiesTests) ... ok test_is_valid_email_address (utilities.UtilitiesTests) ... ok test_parse_case_camel_to_snake (utilities.UtilitiesTests) ... ok test_parse_case_snake_to_camel (utilities.UtilitiesTests) ... ok test_parse_server (utilities.UtilitiesTests) ... ok test_parse_timespan (utilities.UtilitiesTests) ... ok test_parse_to_slug (utilities.UtilitiesTests) ... ok test_selection_collision (utilities.UtilitiesTests) ... ok test_unescape_single_quote (utilities.UtilitiesTests) ... ok test_bin_b64_type (argparse_types.ArgparseTypeTests) ... ok test_bin_hex_type (argparse_types.ArgparseTypeTests) ... ok test_dir_type (argparse_types.ArgparseTypeTests) ... ok test_log_level_type (argparse_types.ArgparseTypeTests) ... ok test_port_type (argparse_types.ArgparseTypeTests) ... ok test_timespan_type (argparse_types.ArgparseTypeTests) ... ok test_job_add (job.JobManagerTests) ... ok test_job_delete (job.JobManagerTests) ... E: Build killed with signal TERM after 10 minutes of inactivity The failure happens randomly. Sometimes it fails, sometimes it does not, but in some of my autobuilders the failure rate is around 100%, which is why I'm filing this as serious. I've put a bunch of failed build logs here: https://people.debian.org/~sanvila/build-logs/python-smoke-zephyr/ I've tested the build on machines with 1 CPU and 2 CPUs. The issue happens in both, but it's particularly easy to reproduce on machines with 1 CPU. If you need a test machine to reproduce it, please contact me privately and I will gladly offer ssh access. Note: In cases like this one I would recommend forwarding the bug upstream and disabling the offending test in the meantime. However, please note that there are several of them. If I grep "\.\.\. $" on the build logs above and count how many occurrences there are, this is the result: 74 test_job_delete (job.JobManagerTests) ... 7 test_job_disable (job.JobManagerTests) ... 3 test_job_init (job.JobManagerTests) ... Thanks.
Bug#922346: eog: Opened an image and my display server crashed
Hello, I found a similar bug on Ubuntu's Launchpad: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1815236 The patch for that issue was added in Mesa 18.3.5 released on March 18, 2019. Michel Le Bihan
Bug#909417: marked as done (gtk-vnc: FTBFS randomly (vncconnectiontest fails with "assertion failed"))
Your message dated Thu, 21 Mar 2019 08:56:38 + with message-id and subject line Bug#909417: fixed in gtk-vnc 0.9.0-1.1 has caused the Debian Bug report #909417, regarding gtk-vnc: FTBFS randomly (vncconnectiontest fails with "assertion failed") 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.) -- 909417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gtk-vnc Version: 0.6.0-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --with autoreconf dh_update_autotools_config -a dh_autoreconf -a libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:14: installing 'build-aux/compile' configure.ac:11: installing 'build-aux/missing' [... snipped ...] # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: vncconnectiontest === /conn/validation/rre: OK /conn/validation/copyrect: OK /conn/validation/hextile: OK /conn/validation/unexpectedcmap: ** ERROR:../../../src/vncconnectiontest.c:62:test_send_u16: assertion failed: (g_output_stream_write_all(os, &v, 2, NULL, NULL, NULL)) FAIL vncconnectiontest (exit status: 134) Testsuite summary for gtk-vnc 0.9.0 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See src/test-suite.log Please report to https://gitlab.gnome.org/GNOME/gtk-vnc/issues make[6]: *** [Makefile:1697: test-suite.log] Error 1 make[6]: Leaving directory '/<>/build/gtk2/src' make[5]: *** [Makefile:1805: check-TESTS] Error 2 make[5]: Leaving directory '/<>/build/gtk2/src' make[4]: *** [Makefile:1878: check-am] Error 2 make[4]: Leaving directory '/<>/build/gtk2/src' make[3]: *** [Makefile:1880: check] Error 2 make[3]: Leaving directory '/<>/build/gtk2/src' make[2]: *** [Makefile:624: check-recursive] Error 1 make[2]: Leaving directory '/<>/build/gtk2' dh_auto_test: cd build/gtk2 && make -j1 check VERBOSE=1 returned exit code 2 make[1]: *** [debian/rules:33: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 I'm reporting this as serious because it happens on the buildds: https://buildd.debian.org/status/fetch.php?pkg=gtk-vnc&arch=amd64&ver=0.6.0-3&stamp=1486745781&raw=0 The above error was from stretch, but it's the same error I get on buster and sid, which means the bug has not been fixed yet. If you could not reproduce this on a single-CPU machine using sbuild (as I do), where this failure seems to be particularly easy to trigger, please say so and I will gladly offer ssh access to a machine where this happens (contact me privately for details). Thanks. --- End Message --- --- Begin Message --- Source: gtk-vnc Source-Version: 0.9.0-1.1 We believe that the bug you reported is fixed in the latest version of gtk-vnc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steinar H. Gunderson (supplier of updated gtk-vnc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 21 Mar 2019 09:24:41 +0100 Source: gtk-vnc Binary: gir1.2-gtk-vnc-2.0 gvncviewer gvncviewer-db
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
* Laurent Bigonville: > Le 19/03/19 à 19:43, Florian Weimer a écrit : >> * Laurent Bigonville: >> >>> Package: libc6-dev >>> Version: 2.28-8 >>> Severity: serious >>> >>> Hi, >>> >>> The crypt.3 manpage, state that _XOPEN_SOURCE should be define for >>> crypt() to be available. >>> >>> But it looks that it's currently the opposite, if _XOPEN_SOURCE is >>> defined, the function cannot be found. >> Can you compile the software using _DEFAULT_SOURCE (well, the default) >> or _GNU_SOURCE instead? > > Yes, the software can be compile when _XOPEN_SOURCE is not defined or > when _GNU_SOURCE is defined instead Sorry, what I was trying to ask is whether this would be an acceptable change for you.
Bug#924858: also can't reproduce
While working on #925068, I built the version of doxygen in buster multiple times, and was unable to reproduce any build failures. -- Kunal signature.asc Description: OpenPGP digital signature
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
Le 19/03/19 à 19:43, Florian Weimer a écrit : * Laurent Bigonville: Package: libc6-dev Version: 2.28-8 Severity: serious Hi, The crypt.3 manpage, state that _XOPEN_SOURCE should be define for crypt() to be available. But it looks that it's currently the opposite, if _XOPEN_SOURCE is defined, the function cannot be found. Can you compile the software using _DEFAULT_SOURCE (well, the default) or _GNU_SOURCE instead? Yes, the software can be compile when _XOPEN_SOURCE is not defined or when _GNU_SOURCE is defined instead We do not want to provide the CRYPT extension anymore because it implies not just support for the crypt function, but also for the DES encryption functions, which definitely do not want. In _XOPEN_SOURCE mode, it's either all of these functions or none of them (and we chose the latter because of DES), otherwise glibc wouldn't conform to the interface specification. We definitely should update the manual page, though.
Bug#909417: [Pkg-libvirt-maintainers] Bug#909417: gtk-vnc: FTBFS randomly (vncconnectiontest fails with "assertion failed")
Hi,
On Thu, Mar 21, 2019 at 12:33:58AM +0100, Steinar H. Gunderson wrote:
> On Sat, Mar 09, 2019 at 07:26:52PM +0100, Santiago Vila wrote:
> > Whoever wants to reproduce this (and possibly debug it), *please*
> > contact me privately and I will gladly provide ssh access to a machine
> > where it happens very often.
>
> I've looked briefly into this.
>
> First, to reproduce this reliably, simply restrict it to one core
> (taskset -c 0 /build/gtk3/src/vncconnectiontest). The reason will be fairly
> clear from the text below.
>
> As far as I can see, this test simulates a broken VNC server (to test the
> client's robustness). It says it's got a 100x100 true color display, but then
> goes on and starts sending a color map.
>
> As soon as the client receives the information about the color map,
> it realizes something is wrong, and a race starts. Now the client wants to
> close the connection at the same time as the fake server wants to keep
> sending the cmap data. If you've got two cores, the server just keeps on
> sending data happily; by the time it's noticed that the client is gone,
> the test has passed and all is fine. But if you've only got one, then the
> first byte of the cmap causes a context switch over to the client, which then
> gets ample time to read the data and close the socket before the server gets
> to send the next byte. The server thus gets EPIPE, and test_send_u16()
> breaks.
>
> I believe the right fix is to send every byte after the first “set color map”
> byte using a non-asserting send. When we've done something invalid, we'd
> better be ready for sending data to fail.
>
> Please try the attached diff; it fixes the problem for me. I can NMU if the
> maintainers want.
I wouldn't mind an NMU.
-- Guido
>
> /* Steinar */
> --
> Homepage: https://www.sesse.net/
> Index: gtk-vnc-0.9.0/src/vncconnectiontest.c
> ===
> --- gtk-vnc-0.9.0.orig/src/vncconnectiontest.c
> +++ gtk-vnc-0.9.0/src/vncconnectiontest.c
> @@ -56,12 +56,23 @@ static void test_send_u8(GOutputStream *
> g_assert(g_output_stream_write_all(os, &v, 1, NULL, NULL, NULL));
> }
>
> +static void send_u8(GOutputStream *os, guint8 v)
> +{
> +g_output_stream_write_all(os, &v, 1, NULL, NULL, NULL);
> +}
> +
> static void test_send_u16(GOutputStream *os, guint16 v)
> {
> v = GUINT16_TO_BE(v);
> g_assert(g_output_stream_write_all(os, &v, 2, NULL, NULL, NULL));
> }
>
> +static void send_u16(GOutputStream *os, guint16 v)
> +{
> +v = GUINT16_TO_BE(v);
> +g_output_stream_write_all(os, &v, 2, NULL, NULL, NULL);
> +}
> +
> static void test_send_u32(GOutputStream *os, guint32 v)
> {
> v = GUINT32_TO_BE(v);
> @@ -429,18 +440,18 @@ static void test_unexpected_cmap_server(
> test_recv_u16(is, 100);
> test_recv_u16(is, 100);
>
> -/* set color map */
> +/* set color map -- after this, the client may close the connection at
> any time */
> test_send_u8(os, 1);
> /* pad */
> -test_send_u8(os, 0);
> +send_u8(os, 0);
> /* first color, ncolors */
> -test_send_u16(os, 0);
> -test_send_u16(os, 1);
> +send_u16(os, 0);
> +send_u16(os, 1);
>
> /* r,g,b */
> -test_send_u16(os, 128);
> -test_send_u16(os, 128);
> -test_send_u16(os, 128);
> +send_u16(os, 128);
> +send_u16(os, 128);
> +send_u16(os, 128);
> }
>
>
> @@ -505,11 +516,13 @@ static void test_overflow_cmap_server(GI
> test_send_u16(os, 65535);
> test_send_u16(os, 2);
>
> +/* after this, the client may close the connection at any time */
> +
> /* r,g,b */
> for (int i = 0 ; i < 2; i++) {
> -test_send_u16(os, i);
> -test_send_u16(os, i);
> -test_send_u16(os, i);
> +send_u16(os, i);
> +send_u16(os, i);
> +send_u16(os, i);
> }
> }
>
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
Bug#925202: Keep calypso out of testing/buster
Package: calypso Version: 1.5-5 Severity: grave Calypso has not seen much attention recently so it's likely better to not ship it in a stable release. It wasn't in stretch either so this will not affect current users. Cheers, -- Guido -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calypso depends on: ii git 1:2.20.1-2 ii python 2.7.15-4 ii python-daemon2.2.3-1 ii python-lockfile 1:0.12.2-2 ii python-vobject 0.9.6.1-0.1 calypso recommends no packages. calypso suggests no packages.
