Processed: affects 843315

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 843315 + libtextutils-ocaml-dev
Bug #843315 [janest-core-kernel] FTBFS: libsexplib-camlp4-dev is no longer 
available
Added indication that 843315 affects libtextutils-ocaml-dev
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
843315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#859587: x2goserver-fmbindings: fails to install: x2goserver-fmbindings.postinst: update-mime-database: not found

[Andreas Beckmann]

Followup-For: Bug #859587
Control: found -1 4.0.1.20-4

There is still a call to update-mime-database left in the postrm:

  Purging configuration files for x2goserver-fmbindings (4.0.1.20-4) ...
  /var/lib/dpkg/info/x2goserver-fmbindings.postrm: 24: 
/var/lib/dpkg/info/x2goserver-fmbindings.postrm: update-desktop-database: not 
found
  dpkg: error processing package x2goserver-fmbindings (--purge):
   subprocess installed post-removal script returned error exit status 127
  Errors were encountered while processing:
   x2goserver-fmbindings


Andreas

Processed: Re: x2goserver-fmbindings: fails to install: x2goserver-fmbindings.postinst: update-mime-database: not found

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.0.1.20-4
Bug #859587 {Done: Mike Gabriel } [x2goserver-fmbindings] 
x2goserver-fmbindings: fails to install: x2goserver-fmbindings.postinst: 
update-mime-database: not found
Marked as found in versions x2goserver/4.0.1.20-4; no longer marked as fixed in 
versions x2goserver/4.0.1.20-4 and reopened.

-- 
859587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#857360: gitlab_8.13.11+dfsg-4 no longer available, unable to install

[Joel Maxuel]

Hello,

Running Debian Stretch (with the exception of about a dozen Jessie packages
held back) with Systemd.  Kernel 4.9.0-2-amd64.

I have read above, and tried versions
gitlab_8.13.11+dfsg-1-2, gitlab_8.13.11+dfsg-1-3 and gitlab_8.13.11+dfsg-8
with no success.  When originally installing gitlab_8.13.11+dfsg-1-2
automatically via aptitude, dkpg choked on the example file not being
there.  I made a dummy file with touch and re-ran, but I got a different
set of errors and continue to get them after installing different versions,
re-configuring, and even purging/re-installing.

I should add that I am currently using ports 80, 443 and 8080 for other
purposes, so my challenge may be gitlab cannot find a port to bind to.  But
from my perspective it does not even attempt as the available-sites file
does not exist in the apache config directory.

My Config:

user: gitlab
gitlab_url: "http://localhost:8088/;
self_signed_cert: false
repos_path: "/tank/gitlab/repositories"
auth_file: "/usr/share/gitlab/.ssh/authorized_keys"
redis:
  bin: /usr/bin/redis-cli
  host: 127.0.0.1
  port: 6379
  database: 0
  namespace: resque:gitlab
log_level: INFO
audit_usernames: false
git_annex_enabled: false

My Install Stream:

gitlab_user="gitlab"
Creating/updating gitlab user account...
Making gitlab owner of /var/lib/gitlab...
Creating runtime directories for gitlab...
Updating file permissions...
GITLAB_HOST="skynet.maxuel.tk"
Configuring nginx with HTTPS...
GITLAB_HTTPS="true"
Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf
Registering /etc/gitlab-shell/config.yml via ucf
Registering /etc/gitlab/gitlab.yml via ucf
Registering /etc/gitlab/gitlab-debian.conf via ucf
Create database if not present
Make gitlab user owner of gitlab_production database...
ALTER DATABASE
Grant all privileges to gitlab user...
GRANT
NOTICE:  extension "pg_trgm" already exists, skipping
CREATE EXTENSION
Verifying we have all required libraries...
Resolving dependencies...
Using rake 10.5.0
Using RedCloth 4.3.2
Using ace-rails-ap 4.1.1
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.9.0
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using nokogiri 1.6.8.1
Using rack 1.6.4
Using mime-types 2.6.1
Using arel 6.0.3
Using multi_json 1.11.2
Using thor 0.19.1
Using addressable 2.4.0
Using akismet 2.0.0
Using allocations 1.0.3
Using multipart-post 1.2.0
Using jwt 1.5.4
Using multi_xml 0.5.5
Using asciidoctor 1.5.4
Using encryptor 3.0.0
Using attr_required 1.0.0
Using execjs 2.6.0
Using ice_nine 0.11.2
Using systemu 2.6.5
Using babel-source 5.8.35
Using babosa 1.0.2
Using base32 0.3.2
Using bcrypt 3.1.11
Using sass 3.4.23
Using browser 2.2.0
Using bundler 1.13.6
Using charlock_holmes 0.7.3
Using chronic 0.10.2
Using numerizer 0.1.1
Using coffee-script-source 1.10.0
Using concurrent-ruby 1.0.0
Using connection_pool 2.2.0
Using safe_yaml 1.0.4
Using creole 0.5.0
Using orm_adapter 0.5.0
Using rotp 2.1.1
Using diff-lcs 1.2.5
Using diffy 3.0.6
Using email_reply_parser 0.5.8
Using equalizer 0.0.10
Using escape_utils 1.1.0
Using excon 0.54.0
Using expression_parser 0.9.1
Using ffi 1.9.10
Using formatador 0.2.1
Using ipaddress 0.8.3
Using rugged 0.24.0
Using get_process_mem 0.2.0
Using posix-spawn 0.3.11
Using gitlab-markup 1.5.1
Using rouge 2.0.2
Using stringex 2.6.1
Using request_store 1.3.0
Using hashie 3.4.4
Using mustermann19 0.4.3
Using temple 0.7.7
Using tilt 2.0.1
Using mimemagic 0.3.0
Using htmlentities 4.3.3
Using httpclient 2.7.1
Using jquery-atwho-rails 1.3.2
Using kgio 2.10.0
Using mail_room 0.8.1
Using method_source 0.8.2
Using mousetrap-rails 1.4.6
Using nested_form 0.3.2
Using net-ldap 0.12.1
Using net-ssh 3.2.0
Using oauth 0.4.7
Using oj 2.17.4
Using timfel-krb5-auth 0.8.3
Using pyu-ruby-sasl 0.0.3.3
Using rubyntlm 0.3.4
Using rubypants 0.6.0
Using pg 0.18.4
Using rack-cors 0.4.0
Using rainbow 2.1.0
Using raindrops 0.17.0
Using rdoc 4.2.1
Using redcarpet 3.3.4
Using redis 3.2.2
Using rinku 1.7.3
Using rqrcode 0.4.2
Using ruby-prof 0.16.2
Using rufus-scheduler 3.1.10
Using settingslogic 2.0.9
Using slack-notifier 1.2.1
Using state_machines 0.4.0
Using u2f 0.2.1
Using underscore-rails 1.8.2
Using unf_ext 0.0.7.2
Using version_sorter 2.1.0
Using vmstat 2.2.0
Using gemojione 3.1.0
Using influxdb 0.2.3
Using recaptcha 3.2.0
Using tzinfo 1.2.2
Using descendants_tracker 0.0.4
Using loofah 2.0.3
Using sanitize 2.1.0
Using ruby-saml 1.4.1
Using rack-test 0.6.3
Using warden 1.2.3
Using rack-accept 0.4.5
Using rack-attack 4.3.1
Using rack-protection 1.5.3
Using mail 2.6.4
Using fog-json 1.0.0
Using select2-rails 3.5.9.3
Using css_parser 1.3.6
Using faraday 0.9.2
Using httparty 0.13.7
Using attr_encrypted 3.0.1
Using autoprefixer-rails 6.6.1
Using uglifier 2.7.2
Using macaddr 1.7.1
Using babel-transpiler 0.7.0
Using chronic_duration 0.10.6
Using coffee-script 2.4.1
Using sprockets 3.7.0
Using crack 0.4.3
Using sys-filesystem 1.1.7
Using fog-core 1.42.0
Using gemnasium-gitlab-service 0.2.6
Using github-linguist 4.7.2
Using gollum-rugged_adapter 

Bug#833114: Preparing NMU.

[Étienne Millon]

Hi,

Thanks for the NMU, this is appreciated.
You can go ahead and upload it immediately if you wish to do so.

I think that your remark about the activity on this package was rude, and I
am surprised that it comes from a Debian Developer who should know better
that motivation and time come and go. The NMU process is here precisely for
that.

​Cheers

Processed: Preparing NMU.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #833114 [rss2email] "RuntimeError: OrderedDict mutated during iteration" on 
some feeds
Severity set to 'grave' from 'important'
> tag -1 pending
Bug #833114 [rss2email] "RuntimeError: OrderedDict mutated during iteration" on 
some feeds
Added tag(s) pending.

-- 
833114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#859563: marked as done (mrboom: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 22:03:49 +
with message-id 
and subject line Bug#859563: fixed in mrboom 3.1.127-1
has caused the Debian Bug report #859563,
regarding mrboom: Incomplete debian/copyright?
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.)


-- 
859563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mrboom
Version: 3.1-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Gürkan Myczko 

Hi,

I just ACCEPTed mrboom from NEW but noticed it was missing 
attribution in debian/copyright for at least the embedded
zlib library.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: mrboom
Source-Version: 3.1.127-1

We believe that the bug you reported is fixed in the latest version of
mrboom, 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 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated mrboom package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Apr 2017 13:14:46 +0200
Source: mrboom
Binary: mrboom
Architecture: source
Version: 3.1.127-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Gürkan Myczko 
Description:
 mrboom - 8 players Bomberman
Closes: 859563 859699
Changes:
 mrboom (3.1.127-1) unstable; urgency=medium
 .
   * New upstream release.
   * Apply patch to fix .desktop file. (Closes: #859699)
   * Update debian/copyright. (Closes: #859563)
   * Drop debian/mrboom.6.
Checksums-Sha1:
 25772cd32f9caf4144e90421aa5ee44c6f5209b3 1478 mrboom_3.1.127-1.dsc
 18827e0667cf0eeadf14ea7244cd2db4a7521d44 4749047 mrboom_3.1.127.orig.tar.gz
 65ac3e8719a016c1db1094c501bc300461d9bc4f 3660 mrboom_3.1.127-1.debian.tar.xz
 20c77a8e07d3e79483bdd7d85067d2a6ef0c828f 9833 mrboom_3.1.127-1_source.buildinfo
Checksums-Sha256:
 f6e67b72b1ae4d978c49a186ac0ed320fba20be1a92ba88d7500a140045ca25e 1478 
mrboom_3.1.127-1.dsc
 7e0ef7f3202f87699881cb076539c35c2e2901185d5e6dd33a1fadc2e303f4f2 4749047 
mrboom_3.1.127.orig.tar.gz
 fb77e028b65e9bd5668b98ffd064c091ab7f130e58589cf0c8af32daac4ee22c 3660 
mrboom_3.1.127-1.debian.tar.xz
 6aba772e5951454c6a5c5fc523ccca9c00bca6926d6fbac879d5ee5650f46a61 9833 
mrboom_3.1.127-1_source.buildinfo
Files:
 e444fc92f4ef5974b5ecbe3c3d55657a 1478 games optional mrboom_3.1.127-1.dsc
 43f27c44c1ffe844d7c75ede5fed1c2c 4749047 games optional 
mrboom_3.1.127.orig.tar.gz
 4c6e0dffe0087d809c374c215a7d2b68 3660 games optional 
mrboom_3.1.127-1.debian.tar.xz
 93ef2237d584a3984cbe48ce89845adb 9833 games optional 
mrboom_3.1.127-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlj6ezgACgkQLDtDb+rG
gQFc3gf+LCKyxfIWcXagocclZc42R5SLHKVW0W/KBgO1kCQUdZjjNGOwlQlf4vS6
vhS1eV68OhjQ31SU6nCmocdaUuDV4Poe7cZ1vn4iU0h1KmWrp49o6E7pVerB2TEA
jyyaM9pi8/yaReuYZBhllSlqsIDG+/gQ8AsLvzNR1Ss1eCL/qzZGCgL36AiELkrz
HzXSTlIz3Kl60ueDLAK8rOm3dzNYnJyVuYq7mPtCidJOXcukSi7lSIMUpbWpjtUq
p2Vg99j0kW3MGCUiMcbXLjOz/Ep5gj2AU+bY83ljlH3ilo0Qf0gpC7urv8AQdmNv
5bmg471cbQb6EbSLBoCGyHK7lPraWA==
=fnlF
-END PGP SIGNATURE End Message ---

Bug#860839: marked as done (vlc fails to start due to missing QT platform plugin xcb)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 22:03:56 +
with message-id 

Bug#857238: marked as done (/usr/bin/leo: throws HTTP 404 (needs update to new remote API))

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 19:48:51 +
with message-id 
and subject line Bug#857238: fixed in libwww-dict-leo-org-perl 2.00-1
has caused the Debian Bug report #857238,
regarding /usr/bin/leo: throws HTTP 404 (needs update to new remote API)
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.)


-- 
857238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwww-dict-leo-org-perl
Version: 1.45-1
Severity: grave
File: /usr/bin/leo
Tags: upstream
Justification: renders package unusable

(CC'ed the upstream maintainer because this is most probably an error in
the upstream part, and because the --help output says so :-))

Dear Maintainers,

I use /usr/bin/leo daily, but it stopped working today:

$ leo -d test 
%DEBUG: connecting to site:
%DEBUG: GET 
/dictQuery/m-vocab/ende/de.html?deStem=standard=relaxed=standard=0=ende=test
 HTTP/1.0
%DEBUG: connection: done
got HTTP error 404!
 at /usr/bin/leo line 248.

That URL does indeed throw a 404, even in the browser :-)

A quick look on the LEO homepage shows that both the desktop and the
mobile version request their results via XML [0].

[0]: 
http://dict.leo.org/dictQuery/m-vocab/ende/query.xml?lp=ende=de=test=both=basic=show=16=1=-1==2017-03-09T02:05:33.714Z

Cheers,
 - Roland

-- System Information:
Debian Release: 9.0
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing-debug'), (500, 
'testing'), (170, 'unstable'), (1, 'unstable-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwww-dict-leo-org-perl depends on:
ii  libhtml-tableparser-perl  0.40-1
ii  perl  5.24.1-1

libwww-dict-leo-org-perl recommends no packages.

libwww-dict-leo-org-perl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libwww-dict-leo-org-perl
Source-Version: 2.00-1

We believe that the bug you reported is fixed in the latest version of
libwww-dict-leo-org-perl, 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 857...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libwww-dict-leo-org-perl 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, 21 Apr 2017 21:29:42 +0200
Source: libwww-dict-leo-org-perl
Binary: libwww-dict-leo-org-perl
Architecture: source
Version: 2.00-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 857238
Description: 
 libwww-dict-leo-org-perl - interface module to dict.leo.org online dictionary
Changes:
 libwww-dict-leo-org-perl (2.00-1) unstable; urgency=medium
 .
   * Import upstream version 2.00.
 Closes: #857238
   * Update (build) dependencies.
   * Update years of upstream and packaging copyright.
   * Add debian/upstream/metadata with upstream Git repository.
   * Switch some URLs for dict.leo.org to HTTPS.
Checksums-Sha1: 
 e7cfd4234a2f3a605363716aa9ac6a0abd08f068 2316 
libwww-dict-leo-org-perl_2.00-1.dsc
 84c3b3b154c33db41e131d772b9160757bcd31c1 14169 
libwww-dict-leo-org-perl_2.00.orig.tar.gz
 fe88e27076d225ba055657f76cb1631b4c53f6bb 2352 
libwww-dict-leo-org-perl_2.00-1.debian.tar.xz
Checksums-Sha256: 
 e005af821a483a9934cdef83b82e7ecd2f070e735c431e15daa83571a4c036c7 2316 
libwww-dict-leo-org-perl_2.00-1.dsc
 36da8827396263791c097724c9545c39877a0b827d1fa7f61463ee54b3c20428 14169 
libwww-dict-leo-org-perl_2.00.orig.tar.gz
 17deb98df3ed166279b79e35281dabf8f096bc94825aad6ce2ae6b3f5abb4a6f 2352 
libwww-dict-leo-org-perl_2.00-1.debian.tar.xz
Files: 
 5f27b704cf087093f944a1e29f8ba69d 2316 perl optional 
libwww-dict-leo-org-perl_2.00-1.dsc
 ee66b335546b60c72d02df9f6d03eb3b 14169 perl 

Bug#857238: Bug#860914: RM: libwww-dict-leo-org-perl/1.39-1

[gregor herrmann]

On Fri, 21 Apr 2017 21:38:26 +0200, gregor herrmann wrote:

> - or to remove 1.39-1 from stable, which looks like the logical way
>   to go forward.

Plus providing a backport once stretch is release and 2.00-1 or later
migrated to buster.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: The Dubliners: Dirty old town


signature.asc
Description: Digital Signature

Processed: Reported to only be a problem with the R in sid (that won't migrate to stretch)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 860876 sid
Bug #860876 [r-cran-kernsmooth] reapr: FTBFS: Error in system call: R CMD BATCH 
00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout
Added tag(s) sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Add version and affects

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 860876 2.23-15-2
Bug #860876 [r-cran-kernsmooth] reapr: FTBFS: Error in system call: R CMD BATCH 
00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout
Marked as found in versions kernsmooth/2.23-15-2.
> affects 860876 src:reapr
Bug #860876 [r-cran-kernsmooth] reapr: FTBFS: Error in system call: R CMD BATCH 
00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout
Added indication that 860876 affects src:reapr
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860879: marked as done (munin-httpd needs libo-string-perl and libhttp-server-simple-cgi-prefork-perl)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 18:33:51 +
with message-id 
and subject line Bug#860879: fixed in munin 2.999.6-2
has caused the Debian Bug report #860879,
regarding munin-httpd needs libo-string-perl and 
libhttp-server-simple-cgi-prefork-perl
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.)


-- 
860879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: munin
Version: 2.999.6-1
Severity: normal

Munin from experimtal fails to start if
libhttp-server-simple-cgi-prefork-perl and libio-string-perl is not
installed.

These are the errors:
Apr 21 10:36:30 artipc10 munin-httpd[6502]: Can't locate
HTTP/Server/Simple/CGI/PreFork.pm in @INC (you may need to install the
HTTP::Server::Simple::CGI::PreFork module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at
/usr/bin/munin-httpd line 35.

Apr 21 11:13:46 artipc10 munin-httpd[1478]: Can't locate IO/String.pm in
@INC (you may need to install the IO::String module) (@INC contains:
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24
/usr/share/perl/5.24 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at
/usr/share/perl5/Munin/Master/Graph.pm line 663,  line 16.


-- Package-specific info:
===
 Munin support information
==

This is support information for Munin version 2.999.6


Munin Master


Configuration items from /etc/munin/munin.conf

Directories
---

dbdir  /var/lib/munin
logdir /var/log/munin
rundir /var/run/munin
tmpldir/etc/munin/templates

Processes
-

fork   1
max_cgi_graph_jobs (unset)
max_graph_jobs (unset)
max_processes  16

TLS
---

tlsdisabled
tls_ca_certificate /etc/munin/cacert.pem
tls_certificate/etc/munin/munin.pem
tls_match  (unset)
tls_private_key/etc/munin/munin.pem
tls_verify_certificate (unset)
tls_verify_depth   5

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (500, 'stable'), (450, 
'proposed-updates'), (160, 'experimental'), (150, 'oldstable'), (140, 
'oldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin depends on:
ii  adduser  3.115
ii  cron [cron-daemon]   3.0pl1-128+b1
ii  fonts-dejavu-core2.37-1
ii  init-system-helpers  1.47
ii  libdbd-sqlite3-perl  1.54-1
ii  libfile-copy-recursive-perl  0.38-1
ii  libhtml-template-perl2.95-2
ii  libhtml-template-pro-perl0.9510-1+b4
ii  libhttp-server-simple-perl   0.51-1
ii  libio-socket-inet6-perl  2.72-2
ii  liblist-moreutils-perl   0.416-1+b1
ii  libmunin-master-perl 2.999.6-1
ii  librrds-perl 1.6.0-1+b2
ii  liburi-perl  1.71-1
ii  libxml-dumper-perl   0.81-1.2
ii  lsb-base 9.20161125
ii  munin-common 2.999.6-1
pn  perl:any 
ii  rrdcached1.6.0-1+b2
ii  rrdtool  1.6.0-1+b2

Versions of packages munin recommends:
pn  munin-doc   
pn  munin-node  

Versions of packages munin suggests:
ii  elinks [www-browser]  0.12~pre6-12

Versions of packages munin-common depends on:
pn  perl:any  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: munin
Source-Version: 2.999.6-2

We believe that the bug you reported is fixed in the latest version of
munin, 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 860...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen 

Bug#860839: Uploading logs

[Lisandro Damián Nicanor Pérez Meyer]

On viernes, 21 de abril de 2017 15:25:02 -03 Lisandro Damián Nicanor Pérez 
Meyer wrote:
> On viernes, 21 de abril de 2017 13:22:41 -03 Harlan Lieberman-Berg wrote:
> [snip qmake info]
> 
> The qmake stuff was just right, but...
> 
> > [hlieberm@crete ~]$ QT_DEBUG_PLUGINS=1 vlc
> > VLC media player 2.2.5 Weatherwax (revision 2.2.5-0-g9275f0fefa)
> > [56310dca2148] core libvlc: Running vlc with the default interface.
> > Use
> > 'cvlc' to use vlc without interface. QFactoryLoader::QFactoryLoader()
> > checking directory path "/usr/bin/platforms"
> 
> ... this is weird, and normally means ther eis Qt stuff not coming from
> Debian packages.
> 
> Have you installed anything Qt-based not using Debian's packages?

To be more verbose, that should be:

/usr/lib/x86_64-linux-gnu/qt5/plugins and not /usr/bin/platforms


-- 
perezmeyer: Gus no tiene inet :-(
PabloOdorico: oh
perezmeyer: te mando una copia de lo que hagamos esta noche
PabloOdorico: de ultima mandame un loro del parque con una flash en la pata ;)

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#860839: Uploading logs

[Lisandro Damián Nicanor Pérez Meyer]

On viernes, 21 de abril de 2017 13:22:41 -03 Harlan Lieberman-Berg wrote:
[snip qmake info]

The qmake stuff was just right, but...

> [hlieberm@crete ~]$ QT_DEBUG_PLUGINS=1 vlc
> VLC media player 2.2.5 Weatherwax (revision 2.2.5-0-g9275f0fefa)
> [56310dca2148] core libvlc: Running vlc with the default interface. Use
> 'cvlc' to use vlc without interface. QFactoryLoader::QFactoryLoader()
> checking directory path "/usr/bin/platforms"

... this is weird, and normally means ther eis Qt stuff not coming from Debian 
packages.

Have you installed anything Qt-based not using Debian's packages?


-- 
porque no respeta el orden natural en el que se leen las cosas
>¿por qué top-posting es tan molesto?
>>top-posting
>>>¿cuál es la peor molestia en los emails de respuesta?

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#859926: speechd-up: fails to install

[Paul Gevers]

Hi

On 21-04-17 16:21, Cobra wrote:
> The man page states:
> "speech-dispatcher is usually started automatically by client libraries
> (i.e. autospawn), so you only need to run it manually if 
> testing/debugging, or when in other explicit need for a special setup."
> 
> So this behaviour doesn't seem broken to me, that's rather exactly as
> expected. Also, starting speechd-up with start-stop-daemon doesn't show
> any failures, despite missing special handling of speech-dispatcher.
> There is an open bug about autospawn with multiple users in #616313,
> but I don't see an immediate connection to our issues; we're always
> root and not touching speechd-up directly.

Hmm, should the speech-dispatcher package than rather NOT ship an init
file? Does it make sense in some setups? An when speech-dispatcher has
no init file, maybe than speechd-up shouldn't "Required-Start"
speech-dispatcher in its init file. Not that it matters, it still
doesn't work when I do that.

> I enabled this line in /etc/speech-dispatcher/speechd.conf:
> CustomLogFile "protocol" 
> "/var/log/speech-dispatcher/speech-dispatcher-protocol.log"
> 
> /var/log/speech-dispatcher/speech-dispatcher-protocol.log stays empty
> when using service (my VM is still using sysvinit-core now), but when I
> use the usual start-stop-daemon command, I get this log:

May it be that starting daemons via service may not have $HOME set? It
occurs to me that when I start speechd-up manually I see this with "ps
aux" (notice the socket location):
root 22182  0.0  0.0 174708  2224 ?Ssl  19:47   0:00
/usr/bin/speech-dispatcher --spawn --communication-method unix_socket
--socket-path /root/.cache/speech-dispatcher/speechd.sock

By the way, with "service" it seems that configuration of
speech-dispatcher is ignored. I find the logging in
/root/.cache/speech-dispatcher... where it now also records what goes
wrong..
[Fri Apr 21 20:04:39 2017 : 549750] speechd: Error [speechd.c:665]:No
speech output modules were loaded - aborting...

I'll try to figure out further.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#860876: [Debian-med-packaging] Bug#860876: reapr: FTBFS: Error in system call: R CMD BATCH 00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout

[Sascha Steinbiss]

reassign 860876 r-cran-kernsmooth
thanks


Hi Chris,

thanks for your bug report. I can reproduce the problem; it looks like an R 
component within REAPR’s build time tests has started to fail, causing the 
whole build to break.

[…]
>  [REAPR preprocess] Error in system call:
>  R CMD BATCH 00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout
>  debian/rules:33: recipe for target 'override_dh_auto_test' failed
>  make[1]: *** [override_dh_auto_test] Error 1
>  make[1]: Leaving directory '«BUILDDIR»'
>  debian/rules:4: recipe for target 'build' failed
>  make: *** [build] Error 2
>  dpkg-buildpackage: error: debian/rules build gave error exit status 2

I have traced the error down to the R script in question used by the tests 
(00.Sample/gc_vs_cov.R). Indeed there is an error running it, which is apparent 
when looking at 00.Sample/gc_vs_cov.Rout:

  […]
  > data=read.csv(file="00.Sample/gc_vs_cov.dat", colClasses=c("numeric", 
"integer"), header=F, sep="   ", comment.char="")
  > l=lowess(data)
  > data_out=unique(data.frame(l$x,l$y))
  > write(t(data_out), sep="", ncolumns=2, 
file="00.Sample/gc_vs_cov.lowess.dat.tmp")
  > pdf("00.Sample/gc_vs_cov.lowess.pdf")
  >   smoothScatter(data, xlab="GC", ylab="Coverage")
  Error in linbin2D(x, gpoints1, gpoints2) : object 'F_lbtwod' not found
  Calls: smoothScatter ->  ->  -> linbin2D
  Execution halted

It looks like r-cran-kernsmooth has trouble finding the Fortran components on 
newer R versions (I tested 3.4.0 from unstable). It works fine on R 3.3.3 (as 
it is in stretch). To reproduce without messing with REAPR, it should even be 
enough to try and run the tests/bkfe.R script included in the kernsmooth source:

  [vagrant@vagrant-debian:/vagrant/kernsmooth-2.23-15/tests] $ R CMD BATCH 
bkfe.R
  [vagrant@vagrant-debian:/vagrant/kernsmooth-2.23-15/tests] $ cat bkfe.Rout
  R version 3.4.0 (2017-04-21) -- "You Stupid Darkness"
  Copyright (C) 2017 The R Foundation for Statistical Computing
  Platform: x86_64-pc-linux-gnu (64-bit)

  R is free software and comes with ABSOLUTELY NO WARRANTY.
  You are welcome to redistribute it under certain conditions.
  Type 'license()' or 'licence()' for distribution details.

  R is a collaborative project with many contributors.
  Type 'contributors()' for more information and
  'citation()' on how to cite R or R packages in publications.

  Type 'demo()' for some demos, 'help()' for on-line help, or
  'help.start()' for an HTML browser interface to help.
  Type 'q()' to quit R.

  > ## failed in bkfe with exaxt powers of 2 prior to 2.23-5
  > library(KernSmooth)
  KernSmooth 2.23 loaded
  Copyright M. P. Wand 1997-2009
  > x <- 1:100
  > dpik(x, gridsize = 256)
  Error in linbin(x, gpoints, truncate) : object 'F_linbin' not found
  Calls: dpik -> linbin
  Execution halted

This also works with no problems when run using R 3.3.3. Unfortunately, I am 
not an R expert, so could someone with some more experience please have a look? 
Thanks!

Cheers
Sascha



signature.asc
Description: Message signed with OpenPGP

Processed: Re: [Debian-med-packaging] Bug#860876: reapr: FTBFS: Error in system call: R CMD BATCH 00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 860876 r-cran-kernsmooth
Bug #860876 [src:reapr] reapr: FTBFS: Error in system call: R CMD BATCH 
00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout
Bug reassigned from package 'src:reapr' to 'r-cran-kernsmooth'.
No longer marked as found in versions reapr/1.0.18+dfsg-3.
Ignoring request to alter fixed versions of bug #860876 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860852: marked as done (qtcharts-opensource-src binary-all FTBFS: error: cannot find -lQt5Charts)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 17:33:51 +
with message-id 
and subject line Bug#860852: fixed in qtcharts-opensource-src 5.7.1-3
has caused the Debian Bug report #860852,
regarding qtcharts-opensource-src binary-all FTBFS: error: cannot find 
-lQt5Charts
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.)


-- 
860852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtcharts-opensource-src
Version: 5.7.1-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=qtcharts-opensource-src=all=5.7.1-2=1492693412=0

...
g++ -Wl,-z,relro -Wl,--as-needed -Wl,-O1 -fuse-ld=gold -Wl,--enable-new-dtags 
-shared -o libqtchartsqml2.so .obj/chartsqml2_plugin.o .obj/declarativechart.o 
.obj/declarativexypoint.o .obj/declarativexyseries.o 
.obj/declarativelineseries.o .obj/declarativesplineseries.o 
.obj/declarativeareaseries.o .obj/declarativescatterseries.o 
.obj/declarativepieseries.o .obj/declarativebarseries.o 
.obj/declarativecategoryaxis.o .obj/declarativemargins.o .obj/declarativeaxes.o 
.obj/declarativepolarchart.o .obj/declarativeboxplotseries.o 
.obj/declarativechartnode.o .obj/declarativerendernode.o 
.obj/moc_declarativerendernode.o  -L/«PKGBUILDDIR»/lib -lQt5Charts -lQt5Quick 
-lQt5Widgets -lQt5Gui -lQt5Qml -lQt5Network -lQt5Core -lGL -lpthread  
/usr/bin/ld.gold: error: cannot find -lQt5Charts
collect2: error: ld returned 1 exit status
Makefile:134: recipe for target '../../qml/QtCharts/libqtchartsqml2.so' failed
make[2]: *** [../../qml/QtCharts/libqtchartsqml2.so] Error 1
--- End Message ---
--- Begin Message ---
Source: qtcharts-opensource-src
Source-Version: 5.7.1-3

We believe that the bug you reported is fixed in the latest version of
qtcharts-opensource-src, 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 860...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtcharts-opensource-src 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: Fri, 21 Apr 2017 14:12:12 -0300
Source: qtcharts-opensource-src
Binary: libqt5charts5 libqt5charts5-dev qml-module-qtcharts qtcharts5-examples 
qtcharts5-doc qtcharts5-doc-html
Architecture: source
Version: 5.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 libqt5charts5 - Qt charts shared library
 libqt5charts5-dev - Qt charts development files
 qml-module-qtcharts - Qt charts QML module
 qtcharts5-doc - Qt charts QCH documentation
 qtcharts5-doc-html - Qt charts HTML documentation
 qtcharts5-examples - Qt chart examples
Closes: 860852
Changes:
 qtcharts-opensource-src (5.7.1-3) unstable; urgency=medium
 .
   [ Dmitry Shachnev ]
   * Run the tests only during architecture-specific builds (Closes: #860852).
   * Make qtcharts5-examples depend on qml-module-qtcharts, as there are
 QML examples.
Checksums-Sha1:
 c7d0ca81dfd48d7658869430e4d3b30883d8ea8b 2805 
qtcharts-opensource-src_5.7.1-3.dsc
 607c55d48d2bb4c2d12f6870f1a938418c35e9ca 10432 
qtcharts-opensource-src_5.7.1-3.debian.tar.xz
 b9eb8b73e2e8eeb920731a0d239e309118677a26 6482 
qtcharts-opensource-src_5.7.1-3_source.buildinfo
Checksums-Sha256:
 cdf3708cb1d2d928647fabc49bfe569e93de3f6bf4b356669e9637aab10c45a7 2805 
qtcharts-opensource-src_5.7.1-3.dsc
 d86d1ba9d133cd64e5580517f43b32b529353aa89e7e181043b23e03e3582668 10432 
qtcharts-opensource-src_5.7.1-3.debian.tar.xz
 d3a931a9a1d2ccd952e302d67e0704d20b1f2094d7f5b05949b5e171bf9098a2 6482 
qtcharts-opensource-src_5.7.1-3_source.buildinfo
Files:
 dbfef5322189c72fa7670517b38c163c 2805 libs optional 
qtcharts-opensource-src_5.7.1-3.dsc
 1237f5c18ff6ac35276668251e41bf9b 10432 libs optional 
qtcharts-opensource-src_5.7.1-3.debian.tar.xz
 0567d5b4e206f1afae72840ba345f769 6482 libs optional 
qtcharts-opensource-src_5.7.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#860839: Uploading logs

[Harlan Lieberman-Berg]

tag 860839 -moreinfo
thanks

[hlieberm@crete ~]$ qmake -query   
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file 
or directory
[hlieberm@crete ~]$ qmake -qt5 -query
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake': No such file 
or directory
[hlieberm@crete ~]$ qmake -qt4 -query
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file 
or directory
[hlieberm@crete ~]$ 

After installing qt5-qmake: 

[hlieberm@crete ~]$ qmake -qt5 -query
QT_SYSROOT:
QT_INSTALL_PREFIX:/usr
QT_INSTALL_ARCHDATA:/usr/lib/x86_64-linux-gnu/qt5
QT_INSTALL_DATA:/usr/share/qt5
QT_INSTALL_DOCS:/usr/share/qt5/doc
QT_INSTALL_HEADERS:/usr/include/x86_64-linux-gnu/qt5
QT_INSTALL_LIBS:/usr/lib/x86_64-linux-gnu
QT_INSTALL_LIBEXECS:/usr/lib/x86_64-linux-gnu/qt5/libexec
QT_INSTALL_BINS:/usr/lib/x86_64-linux-gnu/qt5/bin
QT_INSTALL_TESTS:/usr/tests
QT_INSTALL_PLUGINS:/usr/lib/x86_64-linux-gnu/qt5/plugins
QT_INSTALL_IMPORTS:/usr/lib/x86_64-linux-gnu/qt5/imports
QT_INSTALL_QML:/usr/lib/x86_64-linux-gnu/qt5/qml
QT_INSTALL_TRANSLATIONS:/usr/share/qt5/translations
QT_INSTALL_CONFIGURATION:/etc/xdg
QT_INSTALL_EXAMPLES:/usr/lib/x86_64-linux-gnu/qt5/examples
QT_INSTALL_DEMOS:/usr/lib/x86_64-linux-gnu/qt5/examples
QT_HOST_PREFIX:/usr
QT_HOST_DATA:/usr/lib/x86_64-linux-gnu/qt5
QT_HOST_BINS:/usr/lib/x86_64-linux-gnu/qt5/bin
QT_HOST_LIBS:/usr/lib/x86_64-linux-gnu
QMAKE_SPEC:linux-g++-64
QMAKE_XSPEC:linux-g++-64
QMAKE_VERSION:3.0
QT_VERSION:5.7.1

VLC still errors:

[hlieberm@crete ~]$ QT_DEBUG_PLUGINS=1 vlc
VLC media player 2.2.5 Weatherwax (revision 2.2.5-0-g9275f0fefa)
[56310dca2148] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" 
...
This application failed to start because it could not find or load the Qt 
platform plugin "xcb"
in "".

Reinstalling the application may fix this problem.
zsh: abort  QT_DEBUG_PLUGINS=1 vlc

Processed: Uploading logs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 860839 -moreinfo
Bug #860839 [src:qtbase-opensource-src] vlc fails to start due to missing QT 
platform plugin xcb
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: unmerge

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unmerge 860839
Bug #860839 [src:qtbase-opensource-src] vlc fails to start due to missing QT 
platform plugin xcb
Bug #809176 [src:qtbase-opensource-src] Merge platforms plugins into libqt5gui5
Bug #809989 [src:qtbase-opensource-src] vlc crashes at startup because it could 
not find or load the Qt platform plugin "xcb"
Bug #810253 [src:qtbase-opensource-src] vlc requires libqt5xcbqpa5 but does not 
declare dependency on it
Bug #811036 [src:qtbase-opensource-src] wireshark-qt: aborts immediately
Disconnected #860839 from all other report(s).
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
809176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809176
809989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809989
810253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810253
811036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811036
860839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: Bug#860839: vlc fails to start due to missing QT platform plugin xcb

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unmerge 860839 809989
Unknown command or malformed arguments to command.
> tag 860839 unreproducible moreinfo
Bug #860839 [src:qtbase-opensource-src] vlc fails to start due to missing QT 
platform plugin xcb
Bug #809176 [src:qtbase-opensource-src] Merge platforms plugins into libqt5gui5
Bug #809989 [src:qtbase-opensource-src] vlc crashes at startup because it could 
not find or load the Qt platform plugin "xcb"
Bug #810253 [src:qtbase-opensource-src] vlc requires libqt5xcbqpa5 but does not 
declare dependency on it
Bug #811036 [src:qtbase-opensource-src] wireshark-qt: aborts immediately
Added tag(s) moreinfo and unreproducible.
Added tag(s) moreinfo and unreproducible.
Added tag(s) unreproducible and moreinfo.
Added tag(s) moreinfo and unreproducible.
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
809176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809176
809989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809989
810253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810253
811036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811036
860839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860839: vlc fails to start due to missing QT platform plugin xcb

[Lisandro Damián Nicanor Pérez Meyer]

unmerge 860839 809989
tag 860839 unreproducible moreinfo
thanks

On viernes, 21 de abril de 2017 13:51:23 -03 Lisandro Damián Nicanor Pérez 
Meyer wrote:
> On jueves, 20 de abril de 2017 22:18:42 -03 Sebastian Ramacher wrote:
> > Control: reassign -1 src:qtbase-opensource-src 5.5.1+dfsg-13
> > Control: forcemerge -1 809989
> > 
> > On 2017-04-20 15:56:39, Harlan Lieberman-Berg wrote:
> > > Package: src:vlc
> > > Version: 2.2.5-1
> > > Severity: grave
> > > Justification: renders package unusable
> > > 
> > > Hello maintainer,
> > > 
> > > For vlc installed on stretch freshly after a `apt install vlc`, it
> > > refuses
> > > to open while complaining about a failure to find the xcb Qt module.
> > 
> > That's #809989. Please check with the Qt maintainers if the issue still
> > persists.
> 
> That can't be. The XCB plugin is part of libqt5gui5 which is a direct
> dependency of VLC (or vlc-plugins-qt).
> 
> So if Harlan can reproduce it then there is something else going on.

And indeed it is. The last lines of the log says:

This application failed to start because it could not find or load the Qt 
platform plugin "xcb"
in "".

"" should not be empty.

Please send us the output of the following commands:

qmake -query
qmake -qt5 -query
qmake -qt4 -qury


-- 
Sobre Argentina: "sé que es uno de los países mas hospitalarios del mundo"
 Albert Einstein

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Processed: reopening 734101

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Upload closed wrong bug
> reopen 734101
Bug #734101 {Done: Raoul Snyman } [libjs-jquery-mobile] 
libjs-jquery-mobile: New Release
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openlp/2.4.4-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
734101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854804: marked as done (saned: CVE-2017-6318: SANE_NET_CONTROL_OPTION response packet may contain memory contents of the server)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 17:04:12 +
with message-id 
and subject line Bug#854804: fixed in sane-backends 1.0.25-4
has caused the Debian Bug report #854804,
regarding saned: CVE-2017-6318: SANE_NET_CONTROL_OPTION response packet may 
contain memory contents of the server
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.)


-- 
854804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sane-utils
Version: 1.0.25-3
Severity: grave
Tags: security upstream
Justification: user security hole

Dear Maintainer,

When saned received a SANE_NET_CONTROL_OPTION packet with value_type ==
SANE_TYPE_STRING and value_size larger than the actual length of the
requested string, the response packet from the server contains a string
object as long as value_size in the request. The bytes following the
actual string appears to contain memory contents from the server.

It may be possible to trigger this bug with other packet types, but I
have not verified this.

I have previously filed a bug in the SANE bug tracker on Alioth
(#315576), but I received no response.


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sane-utils depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.60
ii  init-system-helpers1.47
ii  libavahi-client3   0.6.32-2
ii  libavahi-common3   0.6.32-2
ii  libc6  2.24-9
ii  libieee1284-3  0.2.11-13
ii  libjpeg62-turbo1:1.5.1-2
ii  libpng16-161.6.28-1
ii  libsane1.0.25-3
ii  libsystemd0232-6
ii  libusb-1.0-0   2:1.0.21-1
ii  lsb-base   9.20161125
ii  update-inetd   4.44

sane-utils recommends no packages.

Versions of packages sane-utils suggests:
ii  avahi-daemon  0.6.32-2
pn  unpaper   

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: sane-backends
Source-Version: 1.0.25-4

We believe that the bug you reported is fixed in the latest version of
sane-backends, 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 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated 
sane-backends package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Apr 2017 12:07:38 +0200
Source: sane-backends
Binary: sane-utils libsane-common libsane libsane-dev libsane-dbg
Architecture: source all amd64
Version: 1.0.25-4
Distribution: sid
Urgency: medium
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Description:
 libsane- API library for scanners
 libsane-common - API library for scanners -- documentation and support files
 libsane-dbg - API development library for scanners [debug symbols]
 libsane-dev - API development library for scanners [development files]
 sane-utils - API library for scanners -- utilities
Closes: 854804
Changes:
 sane-backends (1.0.25-4) unstable; urgency=medium
 .
   * CVE-2017-6318:
 - New debian/patches/0500-CVE-2017-6318.patch
   + cherry-picked from upstream to fix memory corruption and
 information leakage (Closes: #854804).
Checksums-Sha1:
 87ec5495e8d612aad027ee494cbc4a0d6da7ced8 2483 sane-backends_1.0.25-4.dsc
 9e539a8d188b423385175fd6902a86acd17486d7 111916 
sane-backends_1.0.25-4.debian.tar.xz
 118a68870874230bd79c4744539cd869d50fc582 1012304 
libsane-common_1.0.25-4_all.deb
 4000b0ec59ca99b8f633d08f3dbed1b25cefbe1d 7044372 libsane-dbg_1.0.25-4_amd64.deb
 5ae402a98fbcb231234b5452deb8db334afe6c21 2268916 libsane-dev_1.0.25-4_amd64.deb
 d45c864e948133bbe23b09d7608e875404bdeda6 2112160 libsane_1.0.25-4_amd64.deb
 f82e31b8c287d24332f8effd022de07617ca8bc9 10456 

Bug#860839: vlc fails to start due to missing QT platform plugin xcb

[Lisandro Damián Nicanor Pérez Meyer]

On jueves, 20 de abril de 2017 22:18:42 -03 Sebastian Ramacher wrote:
> Control: reassign -1 src:qtbase-opensource-src 5.5.1+dfsg-13
> Control: forcemerge -1 809989
> 
> On 2017-04-20 15:56:39, Harlan Lieberman-Berg wrote:
> > Package: src:vlc
> > Version: 2.2.5-1
> > Severity: grave
> > Justification: renders package unusable
> > 
> > Hello maintainer,
> > 
> > For vlc installed on stretch freshly after a `apt install vlc`, it refuses
> > to open while complaining about a failure to find the xcb Qt module.
> 
> That's #809989. Please check with the Qt maintainers if the issue still
> persists.

That can't be. The XCB plugin is part of libqt5gui5 which is a direct 
dependency of VLC (or vlc-plugins-qt).

So if Harlan can reproduce it then there is something else going on.

-- 
Theory and practice sometimes clash. And when that happens, theory loses.
Every single time.
  Linus Benedict Torvalds.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#734101: marked as done (libjs-jquery-mobile: New Release)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 16:48:50 +
with message-id 
and subject line Bug#734101: fixed in openlp 2.4.4-2
has caused the Debian Bug report #734101,
regarding libjs-jquery-mobile: New Release
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.)


-- 
734101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-jquery-mobile
Version: 1.2.0+dfsg-2
Severity: wishlist

Dear Maintainer,

Please update to the new version 1.4.0


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.11-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: openlp
Source-Version: 2.4.4-2

We believe that the bug you reported is fixed in the latest version of
openlp, 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 734...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raoul Snyman  (supplier of updated openlp 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: Tue, 11 Apr 2017 14:40:24 -0700
Source: openlp
Binary: openlp
Architecture: source all
Version: 2.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Raoul Snyman 
Changed-By: Raoul Snyman 
Description:
 openlp - Church lyrics projection application
Closes: 734101 860061
Changes:
 openlp (2.4.4-2) unstable; urgency=medium
 .
   * Remove libjs-jquery-mobile, libjs-jquery and associated link, and
 rely on bundled versions. Closes: #734101
   * Add libqt5multimedia5-plugins. Closes: #860061
   * Make use of PYBUILD_* environment variables rather than overrides
   * Update copyright
Checksums-Sha1:
 b9a58d9f31ee6c72adcdf30c69e426aef57cdbd2 1885 openlp_2.4.4-2.dsc
 06bd46476a5a4cab1c92dbaff078e212626ef838 5804 openlp_2.4.4-2.debian.tar.xz
 db036ade8c09e976d82ba2f87ec7b51472036fe2 2823094 openlp_2.4.4-2_all.deb
 8db7fbd12ad6fc358d6bbdae5588950fc6144ab3 9305 openlp_2.4.4-2_amd64.buildinfo
Checksums-Sha256:
 b0d9444c320030cab28818011ec92926cb287a324d17443998e9bc2276e95660 1885 
openlp_2.4.4-2.dsc
 b32ab75d983c4ad0e4ea8404659ded6d1f2b13d134b7366f2ea7df5d18020e19 5804 
openlp_2.4.4-2.debian.tar.xz
 5b4f28bec112ad47bb2fbd872cdc4e2ab255c2a5b36abc038993e38af4256441 2823094 
openlp_2.4.4-2_all.deb
 1f825b77f475a74c2abc503851a738c43b9718881dcb0a56598294939578bb06 9305 
openlp_2.4.4-2_amd64.buildinfo
Files:
 65abfc7a6c7339f5e2b95eb4cf20163d 1885 x11 optional openlp_2.4.4-2.dsc
 f7fb57e53d21203a7dd3bdd9fc029a47 5804 x11 optional openlp_2.4.4-2.debian.tar.xz
 f0ffaa9d28c0983093f49b3c5f2d68e7 2823094 x11 optional openlp_2.4.4-2_all.deb
 24183f751918df1ca4fd37a42857e774 9305 x11 optional 
openlp_2.4.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuuWYkVJAu9p+/awO9VvO15YmrpwFAlj6MggSHHJhb3VsQHNu
eW1hbi5pbmZvAAoJEPVbzteWJq6cWDYP/0nouX5Z2STnip8TBzBRnjYXixmDme0G
g7WA9VpVrcBCHrDxBsM3IFu6YV3mTfQjTz8wUL3uFyjMQc7kVjJoeWg7sn4bTFbH
wmbBcVMOQ+CxrEDAxySc7ipKnXi/pSlKcj4GMN/OM+7NV9y1GE/5yTYLCBVGXhaq
0qV17KSjnXhkK/KFEXhtMh2j6PuDSYKd7RvPINYj+q1lLlxhSceo08BgK1x7JoUi
tP6ILhd9vBQoUd2iZs2fMDxr4kWldDYB03r9Uq4tcdcEUvYGPf9rljGta/3RFJ3h
kM+fgaA09SJzPy1b4moVWGV+JwdymvKYbSHJjHWA7UVc1uCTrjdvIP3DHJ2cIAee
gbh+1pX13kJRNO0pKzycuZHp0sIJaX+8PxYz+ftiQSyAtoQzMevLWCWOKxRrypGI
jgNHakj0l1E29Twa+gSypzEgPN1UZlFDixcpo0haw/bEHgrb3k4gBZ9ozVL2RRij
luPi3wQn8SB/1rKGyYz0idHD+iCusi/im+XXeFFLXab61oXnyhewqNm6cCNhBOcD
mUe32OH7FdH8FoJ0c5VXtFsGktS53j4NORsTOz2IDK5/fyQhy/RjCxjn5aEGaEx/
+GufE2LLXJj+5cZ1NFTzoRnK40tIzRjALToQ9b+nM7lbhnZI+RIOu1v4cOLCol+T
Pe9hOqmx62S1
=wM5K
-END PGP SIGNATURE End Message ---

Bug#860866: marked as done (activemq: CVE-2015-7559: DoS in client via shutdown command)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 15:48:52 +
with message-id 
and subject line Bug#860866: fixed in activemq 5.14.3-3
has caused the Debian Bug report #860866,
regarding activemq: CVE-2015-7559: DoS in client via shutdown command
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.)


-- 
860866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: activemq
Version: 5.6.0+dfsg1-4
Severity: important
Tags: upstream patch security
Forwarded: https://issues.apache.org/jira/browse/AMQ-6470

Hi,

the following vulnerability was published for activemq.

CVE-2015-7559[0]:
DoS in client via shutdown command

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-2015-7559
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7559
[1] https://issues.apache.org/jira/browse/AMQ-6470
[2] https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=b8fc78e

I'm not too familiar with activemq, but from code inspection only the
class (although on different path in the source) is present back as
well in the version in jessie.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: activemq
Source-Version: 5.14.3-3

We believe that the bug you reported is fixed in the latest version of
activemq, 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 860...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated activemq 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, 21 Apr 2017 16:24:41 +0200
Source: activemq
Binary: libactivemq-java libactivemq-java-doc activemq
Architecture: source
Version: 5.14.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 activemq   - Java message broker - server
 libactivemq-java - Java message broker core libraries
 libactivemq-java-doc - Java message broker core libraries - documentation
Closes: 860866
Changes:
 activemq (5.14.3-3) unstable; urgency=medium
 .
   * Team upload.
   * Fix CVE-2017-7559.
 DoS in client via shutdown command.
 Thanks to Salvatore Bonaccorso for the report. (Closes: #860866)
Checksums-Sha1:
 2d550284bf5ec01dc797ce479a7ea79370470667 3646 activemq_5.14.3-3.dsc
 9f819702a3bc4f8f808f9fbe633fd3657eb2af44 15736 activemq_5.14.3-3.debian.tar.xz
 bd9eb3629c8c60850e9d812058c4839dccb1f7c9 17006 
activemq_5.14.3-3_amd64.buildinfo
Checksums-Sha256:
 c1e6390c2a5d2ae0a4ac348e9677ec356628aed7dc44b8eaa199312e5b910c12 3646 
activemq_5.14.3-3.dsc
 631f44d78e70a0b5aabc5f38ae0c8cde785918f44e62b8d8810ebc0d2e1533fb 15736 
activemq_5.14.3-3.debian.tar.xz
 35aabe3d2af941fa321a6dfa272800d72c2285ead2aa764bc98fd8c074e7cbac 17006 
activemq_5.14.3-3_amd64.buildinfo
Files:
 95ff553fa1e6b9cd7e5ac6c726b3ef31 3646 java optional activemq_5.14.3-3.dsc
 748746967306850ed23ad76d9cde3f49 15736 java optional 
activemq_5.14.3-3.debian.tar.xz
 994ef2581dd6d81f721af648b9ede305 17006 java optional 
activemq_5.14.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlj6I6pfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hkk6YP/1byh/G+XWDvkncQmxcR5CWFwYYh5yH+UWap
WI8Lf9TrgSD3wHXql/nRkWwMcgHcfIrYHL+GW8633w+Pk+x1E0qaD3AncKluGRxe
W3wEVH7E5HcACIJ4V4SRMPtyAjHJwDkDLdR1lAR2RBYfq1CP9/kxcymrFVL8CUDa
p/oz3kOLx8BuKjbp6e8ZsX8WJttp1XHfu5z1tNIFmkiYP4jqM2ntAwrR+nBoTmqX
CH1XeqXLWvVISwKM2Z4rklh40EGbe/aX0qUeyWjm380nrgXHn7sQF4FLk6QuVIxG
+yHQKZ5X0LbzbagaoV6jzYkGuydUQ6Mk9VQgTZAOopDuP9ROUWL3N4u+cUKWVz8Y
aF6qE9GxKc/wOxHfYS5QxE1CGn6GLn2OteURuBxvVoUMbG22sgaqwaQ3h1sgjdLq
+Ll8UyJlsjEvPn0NqhK4xuSsC5vsquwpKlUF8uqRqP83aHdoa7VBW9zJo3A73qlk
FaAfVi3s8OviHdTS9cbNc2RehKh0cCl9rHZUdvtrm08n2RPw31etWEjXUBtu49EB

Bug#860866: Pending fixes for bugs in the activemq package

[pkg-java-maintainers]

tag 860866 + pending
thanks

Some bugs in the activemq package are closed in revision
f25d1922b1221f9ad8bf44825827cb12e4c19084 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/activemq.git/commit/?id=f25d192

Commit message:

Fix CVE-2017-7559

Closes: #860866
Thanks: Salvatore Bonaccorso for the report.

Processed: Pending fixes for bugs in the activemq package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 860866 + pending
Bug #860866 [src:activemq] activemq: CVE-2015-7559: DoS in client via shutdown 
command
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#795211: Yaboot in Jessie, following Jessie OS installation, fails to boot Mac OS X

[Flos Lonicerae]

Hi,

> This is a bug that appears to crop up in the beginning of the development 
> cycle for a version of (recent) Debians.
> I run an Apple PowerPC G5 Dual 2.0 with Apple-branded Nvidia GeForce 6800 
> Ultra 256 MB graphics.
> To be clear, this issue is with Jessie’s current yaboot 
> functionality/compatibility with Mac OS X.
> Upon finishing the installation, rebooting, and seeing the yaboot boot menu 
> (“l” for Linux, etc.) choosing “x”
> or “m” for booting my respective version of OS X (“m” was able to boot OS X 
> “Tiger” in Wheezy) flashes the screen
> once and does not boot any OS X at all. Only “l” to boot Debian is able to 
> work, and this necessitates alt-booting
> if I wish to boot into (an) OS X at all.

I tried installing the Debian 8.7 on my iBOOK G4, both MacOSX 10.5.8
and Debian worked well after the installation. I press "x" to boot up
the MacOSX 10.5.8 in the yaboot menu.

> I have issuing ybin -v within Debian once booted (right after installation) 
> to see if that corrects the problem
> (I am addressing my OS X installations on a separate drive, /dev/sdb, and 
> Debian is on /dev/sda with the yaboot
> HDD byte-codea). This did not make a difference.

Can you reproduce this issue by installing an Debian 8.7? If yes, we
can collect some data, for example: using dd to get some data from
partitions, on the newly installed Debian Linux.

Regards,
Flos

Bug#860893: marked as done (src:softcatala-spell should stop building myspell-ca)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 15:04:57 +
with message-id 
and subject line Bug#860893: fixed in softcatala-spell 0.20111230b-10
has caused the Debian Bug report #860893,
regarding src:softcatala-spell should stop building myspell-ca
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.)


-- 
860893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: softcatala-spell
Version: 0.20111230b-9
Severity: important

Holger Levsen noticed:
myspell-ca | 0.20111230b-9   | unstable| all
myspell-ca | 3.0.1+repack1-3 | testing | all
myspell-ca | 3.0.1+repack1-3 | unstable| all

myspell-ca is now a transitional package in src:hunspell-ca,
and should therefore no longer be built by src:softcatala-spell.
--- End Message ---
--- Begin Message ---
Source: softcatala-spell
Source-Version: 0.20111230b-10

We believe that the bug you reported is fixed in the latest version of
softcatala-spell, 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 860...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Agustin Martin Domingo  (supplier of updated 
softcatala-spell 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: Fri, 21 Apr 2017 16:00:31 +0200
Source: softcatala-spell
Binary: icatalan wcatalan aspell-ca
Architecture: source all
Version: 0.20111230b-10
Distribution: unstable
Urgency: medium
Maintainer: Jordi Mallach 
Changed-By: Agustin Martin Domingo 
Description:
 aspell-ca  - Catalan dictionary for aspell
 icatalan   - Catalan dictionary for ispell
 wcatalan   - Catalan dictionary words for /usr/share/dict
Closes: 860893
Changes:
 softcatala-spell (0.20111230b-10) unstable; urgency=medium
 .
   * Stop building myspell-ca, it is now a transitional package in
 src:hunspell-ca (Closes: #860893).
Checksums-Sha1:
 41227a827808c6b82943fee998e6695027bc8e51 2184 
softcatala-spell_0.20111230b-10.dsc
 b3de6c3ccae365c11d0af06683335e6316a6dd2b 10816 
softcatala-spell_0.20111230b-10.debian.tar.xz
 5b99e62ec1e8ff541a7a7e1a384293fcb6bf8d49 318772 
aspell-ca_0.20111230b-10_all.deb
 5b6a78390402088f3a728e0f44294cd2032cb59a 566230 icatalan_0.20111230b-10_all.deb
 b640fc30d85d8a8e0f1750582b9bee411cbbabe8 6321 
softcatala-spell_0.20111230b-10_amd64.buildinfo
 dbebbf37d518370c8ceedb401ed92b926c7bdc59 1024702 
wcatalan_0.20111230b-10_all.deb
Checksums-Sha256:
 6df6763f79e3444d37d2a5b327dafd1b2a48194f6249b0bfa920a7bf3442cabc 2184 
softcatala-spell_0.20111230b-10.dsc
 64a8fdcfdc002b914d3fb574ab234c3ead33af161ce34b51ab146554d9be8c79 10816 
softcatala-spell_0.20111230b-10.debian.tar.xz
 db7a714d392fa9f0e38d120ee6e5779ac1e63f66ed9890402b670177e020 318772 
aspell-ca_0.20111230b-10_all.deb
 fd90e64d81821f8331176f78a0aaead117f9ab1940bdf04822d92235e638e7b6 566230 
icatalan_0.20111230b-10_all.deb
 8c8f19eb2340c1ece95d4532b58d4f781f5c14d01a9d9da2dacd4070ad24caee 6321 
softcatala-spell_0.20111230b-10_amd64.buildinfo
 be1fafcdb9be67f64b546fb281795350ab8788b586404cbcf1c3e1939f90e2a8 1024702 
wcatalan_0.20111230b-10_all.deb
Files:
 90296fc371c0245dc6273d241400a708 2184 text optional 
softcatala-spell_0.20111230b-10.dsc
 425c75add38f8e6815900c59e99d54b9 10816 text optional 
softcatala-spell_0.20111230b-10.debian.tar.xz
 29c2147d6cf6ce28cbe55b8e2fdce947 318772 text optional 
aspell-ca_0.20111230b-10_all.deb
 517def60e1623d31542951ed2619da89 566230 text optional 
icatalan_0.20111230b-10_all.deb
 9e26765edac74f864aba82c3a68f01de 6321 text optional 
softcatala-spell_0.20111230b-10_amd64.buildinfo
 9b0f26210f7bff6476d3d8079aede221 1024702 text optional 
wcatalan_0.20111230b-10_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEEehey7p+gYd346SEFJrCLeiggvwFAlj6GGYACgkQFJrCLeig
gvzDgRAAhIacQIREE2TbP4vt+n2Mt4ibC53KF7tgKMWV1/9CMHu7s6QxbVLZf87j
XQyuUNDZmV4X+HI845+IhnQK1m2Z1YrymwS2q9g8AQBVaImu+Rku4MfUoqfTjLPf
cRVwKVYrEgueTNSOGvGQeGQ9CiTbxXjHhTGBfrhO3vv6FQG00R2pbI3gAviJDtAb
xc40ZMoS6OSkAS9zJYsQ42B+RWC+v1E8M1anlySa4tjSFK3LOWyIkAwVSwVABWX+

Processed: Re: activemq: CVE-2015-7559: DoS in client via shutdown command

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #860866 [src:activemq] activemq: CVE-2015-7559: DoS in client via shutdown 
command
Severity set to 'serious' from 'important'

-- 
860866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#860893: src:softcatala-spell should stop building myspell-ca

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #860893 [src:softcatala-spell] src:softcatala-spell should stop building 
myspell-ca
Added tag(s) pending.

-- 
860893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860893: src:softcatala-spell should stop building myspell-ca

[Agustin Martin]

Control: tag -1 + pending

On Fri, Apr 21, 2017 at 04:00:58PM +0300, Adrian Bunk wrote:
> Source: softcatala-spell
> Version: 0.20111230b-9
> Severity: important
> 
> Holger Levsen noticed:
> myspell-ca | 0.20111230b-9   | unstable| all
> myspell-ca | 3.0.1+repack1-3 | testing | all
> myspell-ca | 3.0.1+repack1-3 | unstable| all
> 
> myspell-ca is now a transitional package in src:hunspell-ca,
> and should therefore no longer be built by src:softcatala-spell.

Hi, Adrian

Thanks for reminding. Some time ago we were in contact with ooo-dictionaries
maintainer about this. Since this is indeed harmless, although undesirable,
we did not give it a high priority. And time passed ...

> After discussing with the release team increasing severity to serious, 
> since this would result in stable updates of src:softcatala-spell to
> be rejected.

I was about to ask why this harmless thing could be serious, but if the
release team considers that it could cause any kind of problem I am fine
with it.

Jordi, I have started to drop myspell-ca from softcatala-spell and I think
work is mostly done. If you don't object, I will care of this.

I would have also liked to update vcs url and Standards-Version, but
considering the freeze I will leave this for later.

Regards,

-- 
Agustin

Bug#860464: wdm: Missing handling of plymouth (#782456)

[Niels Thykier]

Axel Beckert:
> Control: tag -1 unreproducible moreinfo
> 
> Hi again,
> 
> [...]
> 
> So I wonder: Shall I upload the fix suggested by Niels anyways? (Not
> untested, but unverified.)
> 

Laurent, can you help here?

> Niels: I'd also include a fix for #860576 (wdm: Missing dependency on
> an X server) in which I ran into recently and was able to verify and
> debug it in this minimal VM setup I intended primarly for this bug
> report.
> 
>   Regards, Axel
> 

Ack, that is fine with me.

Thanks,
~Niels

Processed: This is actually RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #860893 [src:softcatala-spell] src:softcatala-spell should stop building 
myspell-ca
Severity set to 'serious' from 'important'

-- 
860893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#707903: RFS: drgeo/1.1.0-10.3 [NMU, RC]

[Patrick Hetu]

drgeo is not in jessie and won't be in stretch, so there is no need to
hurry with patching this upstream version from 2005.

https://git.gnome.org/browse/archive/drgeo/log/
This looks very dead.

#736535 mentions an active fork (that seems to be quite different).


Yes, it use the pharo framework (smalltalk) now but it's released as
a vm snapshot so harder to package...


What drgeo needs is an active maintainer who packages code that is
also maintained upstream.

Trying to revive 2005 code after it has already missed two Debian
releases doesn't make much sense.


Indeed, this package fill the gap while we are waiting for the newer 
version to be packaged.



do you really need to patch:
Makefile.in.in


I'm afraid so, otherwise intltoolize gives an error.


and add a new config.rpath file?


No indeed, I added gettext as a dependency and I'm copy the file before 
the build instead.



also, please drop the last part of the patch:
@@ -443,4 +443,4 @@

;(new-figure "Ma figure")
;(define a (Numeric "a" 'free 0 0 1))
-;(define p (Point "o" 'intersection a a))
\ Pas de fin de ligne à la fin du fichier
+;(define p (Point "o" 'intersection a a))


Done.

The new version is here:

 
https://mentors.debian.net/debian/pool/main/d/drgeo/drgeo_1.1.0-10.3.dsc


Patrick

Bug#860702: pcl: FTBFS on i386: segmentation fault

[Jochen Sprickerhof]

Hi,

* Lucas Nussbaum  [2017-04-21 11:27]:
> I did the archive rebuild that resulted in this bug on a machine with a
> jessie kernel. I did another rebuild on a machine with a stretch
> kernel, and this failure disappeared.

I found the same, segfault on barriere.d.o (Kernel 3.16.0-4-amd64),
working on my PC (Kernel 4.9.0-2-amd64). The other difference between
these two is that barriere has 8G of memory and mine has 32G. So it
could be that we simply run out of memory. This is why we compile with
doxygen on the buildd only on amd64 (it's only needed for arch all
packages). See #780582.

> My best guess is that this has something to do with a stack overflow,
> in a way similar to #750593 (see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593#157 and #797530
> (fixed in stretch, not jessie).

For reference, here is a backtrace from barriere:

$ gdb ~/doxygen-1.8.13/b/bin/doxygen core
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/jspricke/doxygen-1.8.13/b/bin/doxygen...done.
[New LWP 7513]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Core was generated by `/home/jspricke/doxygen-1.8.13/b/bin/doxygen 
/home/jspricke/pcl-1.8.0+dfsg1/buil'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xf6d5bfc6 in SearchIndex::write (this=0xf8e6a608, fileName=0xecf9b320 
"/home/jspricke/pcl-1.8.0+dfsg1/build/doc/doxygen/html/search/search.idx") at 
/home/jspricke/doxygen-1.8.13/src/searchindex.cpp:305
305   indexOffsets[i]=0;
(gdb) bt
#0  0xf6d5bfc6 in SearchIndex::write (this=0xf8e6a608, fileName=0xecf9b320 
"/home/jspricke/pcl-1.8.0+dfsg1/build/doc/doxygen/html/search/search.idx") at 
/home/jspricke/doxygen-1.8.13/src/searchindex.cpp:305
#1  0xf6bc8be4 in generateOutput () at 
/home/jspricke/doxygen-1.8.13/src/doxygen.cpp:11626
#2  0xf6b91419 in main (argc=2, argv=0xfff4d2f4) at 
/home/jspricke/doxygen-1.8.13/src/main.cpp:38
(gdb) p i
$1 = 10226
(gdb) p *indexOffsets@i
$2 = {0 , 262148, 0 , 262159, 0 , 262183, 0 , 262197, 262218, 0, 262270, 0 , 262279, 0 , 262288, 0, 0, 0, 262300, 0, 262309,
  262714, 262746, 263116, 263301, 263461, 263579, 263741, 264067, 0, 264283, 
264323, 264586, 265019, 265127, 265251, 0, 265534, 266011, 266382, 266419, 
266488, 266531, 266571, 266580, 266602, 0 , 266611, 0, 
266621,
  0 }

Cheers Jochen


signature.asc
Description: PGP signature

Bug#859926: speechd-up: fails to install

[Paul Gevers]

Hi Jean-Philippe,

On 19-04-17 22:28, MENGUAL Jean-Philippe wrote:
> 1st, I have always had the idea the the spd service had bugs and was not
> really usable: spent so resource, didn't run really, etc. Hence the fact
> it's always been in "no" in defaults/speech-dispatcher.

So, does that mean that speechd-up should also have such a mechanism
that defaults to no?

What I am now seeing is that speech-dispatcher doesn't stay running when
started with it's init script. If I start it with "sudo service
speech-dispatcher start" than it is in the "active (running)" state for
about 20 seconds and then goes to an "active (exited)" state. I expect
that speechd-up is failing to start because it actually checks if it can
USE speech-dispatcher.

Two things that I then noticed, the man page of speech-dispatcher
mentions that it needs to be started with the "-d" option to run as
daemon (which isn't present in its init file). With debugging
information added I then noticed the following in
/tmp/speechd-debug/speech-dispatcher.log:
[Fri Apr 21 14:10:00 2017 : 638612] speechd: Currently no clients
connected, enabling shutdown timer.
[Fri Apr 21 14:10:05 2017 : 713820] speechd: Terminating...

So it seems speech-dispatcher doesn't want to stay running as daemon. I
guess this is the real issue at stake. (Should we reassign?)

> 2nd, given this feedback, maybe we may try requesting to the initscript
> to wait for some seconds, with a kind of pause parameter? Would it fix
> the bug?

Just to be sure, you mean pausing in the speech-dispatcher init script,
right? Speechd-up already has that. Because of the above, this doesn't
help. I even tried it (actually before I found out the above) and it
didn't work.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#860879: [Packaging] Bug#860879: munin-httpd needs libo-string-perl and libhttp-server-simple-cgi-prefork-perl

[Steve Schnepp]

Hi all,

Thanks for the bug report & its handling.

Note that I do maintain a rough dependency manager directly in the munin
code in the form of a shell script : dev_scripts/deps [1]

It has 2 main issues :
* It isn't complete (as it didn't contain
libhttp-server-simple-cgi-prefork-perl) but I can maintain it more
accurately if needed
* It is aimed at build dependencies of the master, and it therefore wider
than the binary package

[1] https://github.com/munin-monitoring/munin/blob/master/dev_scripts/deps

Bug#860649: #860649: works well when built on other archs

[Adam Borowski]

Control: severity -1 normal
Control: block -1 by 831425

Hi!
(Delayed response because due to #397761 Uploaders don't get bug mails.)

arch:all packages being buildable on only some architectures isn't
considered a problem -- although no way to add metadata documenting this
state is an issue.

Your reasoning for filing testsuite failures with severity:serious is good:
unlike "fails due to uninstallable B-Deps" it usually points to the package
being actually broken on the arch in question.  This is not the case for
3270font, though -- the font works correctly when built on amd64/armhf/...
and copied to i386/hppa, and broken if built on i386/hppa and copied to a
modern architecture.  It's all fine if caught by the testsuite -- and unlike
almost any font package, 3270font has one.

Thus, I'm downgrading the severity.

The real bug is #831425 in fontforge, but not many care about developing on
i386/hppa, thus it's only severity:important.


Thanks for your QA efforts!
-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!

Processed: #860649: works well when built on other archs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #860649 [src:3270font] 3270font: FTBFS on i386: Test failures
Severity set to 'normal' from 'serious'
> block -1 by 831425
Bug #860649 [src:3270font] 3270font: FTBFS on i386: Test failures
860649 was not blocked by any bugs.
860649 was not blocking any bugs.
Added blocking bug(s) of 860649: 831425

-- 
860649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860879: [Packaging] Bug#860879: munin-httpd needs libo-string-perl and libhttp-server-simple-cgi-prefork-perl

[Holger Levsen]

control: tags + pending
# fixed in git, will either be uploaded as 2.999.6-2 or as 2.999.7-1


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#860879: [Packaging] Bug#860879: munin-httpd needs libo-string-perl and libhttp-server-simple-cgi-prefork-perl

[Frederik Himpe]

On Fri, 2017-04-21 at 11:05 +, Holger Levsen wrote:
> control: severity -1 serious
> 
> On Fri, Apr 21, 2017 at 11:19:28AM +0200, Frederik Himpe wrote:
> > Munin from experimtal fails to start if
> > libhttp-server-simple-cgi-prefork-perl and libio-string-perl is not
> > installed.
> 
The Munin cron job is also missing libparallel-forkmanager-perl as a
dependency:

Can't locate Parallel/ForkManager.pm in @INC (you may need to install the 
Parallel::ForkManager module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Munin/Master/Update.pm line 154.
BEGIN failed--compilation aborted at /usr/share/perl5/Munin/Master/Update.pm 
line 154.
Compilation failed in require at /usr/bin/munin-update line 12.
BEGIN failed--compilation aborted at /usr/bin/munin-update line 12.

After installing that package, the cron job still fails with a
compilation error, but I'll open a separate bug report for that if I
can find out what's wrong exactly.

-- 
Frederik Himpe 
Vrije Universiteit Brussel

Bug#860608: 132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/ne

[Holger Levsen]

On Fri, Apr 21, 2017 at 01:00:20PM +0200, Lucas Nussbaum wrote:
> FYI, that's the number of additional copies of source packages in
> stretch, per source package:
> 
> udd=> select source, count(*) from sources where release='stretch' and
> component='main' and extra_source_only group by source order by count
> desc;
[...]
> (132 rows)

that's quite astounding (to me) and IMHO also quite bad… can we do something
to fix this for Buster at least?

reply-to: set to debian-devel@…


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Processed: Re: [Packaging] Bug#860879: munin-httpd needs libo-string-perl and libhttp-server-simple-cgi-prefork-perl

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #860879 [munin] munin-httpd needs libo-string-perl and 
libhttp-server-simple-cgi-prefork-perl
Severity set to 'serious' from 'normal'

-- 
860879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Lucas Nussbaum]

On 21/04/17 at 08:28 +, Niels Thykier wrote:
> Michael Stapelberg:
> > On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier  wrote:
> > 
> >> [...]
> >>>
> >>
> >> They seem to be arch:all packages.  We cannot binNMU arch:all packages,
> >> only architecture dependent ones.  :-/
> >>
> > 
> > Okay. How do you suggest we rectify this issue instead, then?
> > 
> 
> A (possibly "no change") sourceful upload to force a rebuild of the
> arch:all package.

FYI, that's the number of additional copies of source packages in
stretch, per source package:

udd=> select source, count(*) from sources where release='stretch' and
component='main' and extra_source_only group by source order by count
desc;

source | count 
---+---
 golang|10
 dh-elpa   | 7
 gcc-6 | 5
 linux | 4
 golang-golang-x-net-dev   | 4
 golang-1.7| 4
 golang-logrus | 3
 cdebconf  | 3
 binutils  | 3
 golang-1.6| 3
 golang-golang-x-sys   | 2
 hw-detect | 2
 choose-mirror | 2
 fonts-freefont| 2
 golang-codegangsta-cli| 2
 ndisc6| 2
 preseed   | 2
 golang-goprotobuf | 2
 golang-github-spf13-jwalterweatherman | 2
 systemd   | 2
 glibc | 2
 main-menu | 2
 gdk-pixbuf| 2
 libdebian-installer   | 2
 openssh   | 2
 espeak-ng | 2
 sphinx| 2
 console-setup | 2
 glib2.0   | 2
 openssl1.0| 2
 libgcrypt20   | 2
 golang-github-boltdb-bolt | 2
 python-urllib3| 1
 golang-go.crypto  | 1
 pcre3 | 1
 libx11| 1
 lcdf-typetools| 1
 appdirs   | 1
 gtk+2.0   | 1
 golang-golang-x-oauth2| 1
 golang-github-jacobsa-oglematchers| 1
 golang-protobuf-extensions| 1
 python-packaging  | 1
 golang-bazil-fuse | 1
 libnl3| 1
 golang-github-hashicorp-raft  | 1
 expat | 1
 wpa   | 1
 zlib  | 1
 lowmem| 1
 libxi | 1
 golang-pault-go-debian| 1
 gnupg2| 1
 anna  | 1
 xorg-server   | 1
 brltty| 1
 asm   | 1
 screen| 1
 rootskel  | 1
 poppler-data  | 1
 unicode-data  | 1
 jquery-typeahead.js   | 1
 golang-google-api | 1
 nano  | 1
 alsa-lib  | 1
 jqueryui  | 1
 influxdb  | 1
 golang-github-shirou-gopsutil | 1
 dbus  | 1
 syslinux  | 1
 banshee   | 1
 gdb   | 1
 publicsuffix  | 1
 golang-gopkg-tomb.v2  | 1
 golang-go.net-dev | 1
 xserver-xorg-input-evdev  | 1
 seabios   | 1
 libpng1.6 | 1
 installation-locale   | 1
 node-moment   | 1
 util-linux| 1
 libevdev  | 1
 golang-github-spf13-cobra | 1
 doxygen   | 1
 netcfg| 1
 golang-check.v1   | 1
 debian-installer-utils| 1
 courier   | 1
 python-distro | 1
 

Bug#860608: [pkg-golang-devel] Bug#860608: Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Michael Hudson-Doyle]

Not a DD, sadly (yet!)

sent from my phone, please excuse brevity

On 21 Apr 2017 19:36, "Michael Stapelberg"  wrote:

>
>
> On Wed, Apr 19, 2017 at 12:05 PM, Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
>
>> On 19 April 2017 at 20:55, Lucas Nussbaum  wrote:
>>
>>> On 19/04/17 at 09:05 +0200, Michael Stapelberg wrote:
>>> > This is the third time an FTBFS report against this package (which was
>>> > removed from Debian) was submitted.
>>> >
>>> > The other two times were
>>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855926 and
>>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848806, both were
>>> closed
>>> > asking for an explanation as to why the issue was filed in the first
>>> place.
>>>
>>> ... And none sending the question to the bug submitter.
>>
>>
>> Defeated by the Debian BTS, I didn't realize that you had to email the
>> submitter separately when closing a bug...
>>
>>
>>>
>>> > lucas, is this a bug in your rebuild infrastructure, or did something
>>> go
>>> > wrong with the removal?
>>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839364 (same issue
>>> as the
>>> > one you’re reporting) was closed by ftpmaster due to package removal.
>>>
>>> In my local Sources file, I have:
>>
>>
>> [...]
>>
>>
>>> 'Extra-Source-Only' means that there are still binary packages in the
>>> archive
>>> that were built using that version of the golang package.
>>>
>>> In fact, for that version:
>>> $ grep -e Package -e Using 127.0.0.1\:_debian_dists_t
>>> esting_main_binary-amd64_Packages |grep -B1 'golang (= 2:1.6.1-2)'
>>> Package: golang-github-armon-go-metrics-dev
>>> Built-Using: golang (= 2:1.6.1-2), golang-github-datadog-datadog-go (=
>>> 0.0~git20150930.0.b050cd8-1), golang-github-prometheus-common (=
>>> 0+git20160321.4045694-1), golang-goprotobuf (= 0.0~git20160330-1),
>>> golang-procfs (= 0+git20150616.c91d8ee-1), golang-prometheus-client (=
>>> 0.7.0+ds-3), golang-protobuf-extensions (= 0+git20150513.fc2b8d3-4)
>>> --
>>> Package: golang-github-gosexy-gettext-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>> --
>>> Package: golang-github-hashicorp-go-msgpack-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>> --
>>> Package: golang-github-stretchr-objx-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>> --
>>> Package: golang-github-kr-pty-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>>
>>> This case could be ignored by the rebuild scripts, or binnmus could be
>>> trigerred to get rid of the other versions. I'm not sure it makes sense
>>> to ship
>>> that many copies of golang in stretch.
>>>
>>> I think I read something about an organized plan to get rid of such extra
>>> packages using binnmus, but maybe I was dreaming. Ccing debian-release@.
>>>
>>
>> I think I heard something about that. FWIW, though, these Built-Using
>> fields are bogus, golang -dev packages just ship source and so do not
>> actually contain anything built by the mentioned version of the compiler. I
>> think I've managed to hammer this into everyone's heads now but I guess
>> there are plenty of packages in the archive that haven't had an upload
>> since then (so I guess the binNMUs could just drop the field?).
>>
>
> Updating or dropping the field seems fine with me. Could you do these 4
> binNMUs so that we can close out this bug please? :)
>
> --
> Best regards,
> Michael
>
> ___
> pkg-golang-devel mailing list
> pkg-golang-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-golang-devel
>

Processed: downgrading severity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 860644 wishlist
Bug #860644 [src:python-pbcore] python-pbcore: FTBFS on i386: build-dependency 
not installable: python-pysam (>= 0.9.0)
Severity set to 'wishlist' from 'serious'
> severity 860615 wishlist
Bug #860615 [src:python-pbcommand] python-pbcommand: FTBFS on i386: 
build-dependency not installable: python-pbcore
Severity set to 'wishlist' from 'serious'
> severity 860669 wishlist
Bug #860669 [src:pbgenomicconsensus] pbgenomicconsensus: FTBFS on i386: 
build-dependency not installable: python-pbcore (>= 1.2.9)
Severity set to 'wishlist' from 'serious'
> severity 860676 wishlist
Bug #860676 [src:pbalign] pbalign: FTBFS on i386: build-dependency not 
installable: python-pbcore (>= 0.8.5)
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860615
860644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860644
860669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860669
860676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#859200: marked as done (gitlab: Upgrading postgres and gitlab together fails)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 09:49:39 +
with message-id 
and subject line Bug#859200: fixed in gitlab 8.13.11+dfsg1-2
has caused the Debian Bug report #859200,
regarding gitlab: Upgrading postgres and gitlab together fails
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.)


-- 
859200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.11+dfsg-8
Severity: grave
Justification: renders package unusable

Hi,

I ran an "apt upgrade" which wanted to install gitlab 8.13.11+dfsg-8 and
upgrade postgres. The upgrade of gitlab fails because postgres was not
running. So you probably have to pre-depend on postgres if you rely on
having postgres running while postinst is running.

Relevant apt output:

Preparing to unpack .../18-postgresql-contrib-9.6_9.6.2-2_amd64.deb ...
Unpacking postgresql-contrib-9.6 (9.6.2-2) over (9.6.2-1) ...
Preparing to unpack .../19-postgresql-9.6_9.6.2-2_amd64.deb ...
Unpacking postgresql-9.6 (9.6.2-2) over (9.6.2-1) ...
[...]
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
createdb: could not connect to database template1: could not connect to server: 
No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up postgresql-client-9.6 (9.6.2-2) ...
[...]
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.13.11+dfsg1-2

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 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (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: SHA256

Format: 1.8
Date: Fri, 21 Apr 2017 13:16:43 +0530
Source: gitlab
Binary: gitlab
Architecture: source
Version: 8.13.11+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
Closes: 859200
Changes:
 gitlab (8.13.11+dfsg1-2) unstable; urgency=medium
 .
   * Integrate dbconfig-common (Closes: #859200)
   * Don't set default gitlab user in postinst
   * Change template name from purge to purge_data
   * Switch to runuser from su (runuser correctly handles PAM sessions)
Checksums-Sha1:
 bfcea0ed1f47d402fa3df4bfbaad69fd3146eabf 2541 gitlab_8.13.11+dfsg1-2.dsc
 4a9ded70679751f418cec1ebcefccaba758c20b4 50828 
gitlab_8.13.11+dfsg1-2.debian.tar.xz
 4941eddd26993afefeb1f9189773303885cf63a6 8343 
gitlab_8.13.11+dfsg1-2_source.buildinfo
Checksums-Sha256:
 87ef15ab0f07bf96c7f1aab2f30453de2d9cb25394125f8c46bd408757008231 2541 
gitlab_8.13.11+dfsg1-2.dsc
 d5ab35b6b73a9c205dca8e4137f13231e964dcec7827c5b3830f334f8ed8e689 50828 
gitlab_8.13.11+dfsg1-2.debian.tar.xz
 0c480e7c6de314bbcb26807150888c7a0781c5fcbfc310f23e34fd183df3dc7e 8343 
gitlab_8.13.11+dfsg1-2_source.buildinfo
Files:
 946184597edc7ef06af5cb6f60f7f8b2 2541 ruby optional gitlab_8.13.11+dfsg1-2.dsc
 07d487258bd0c674c27c1539c6c70adc 50828 ruby optional 
gitlab_8.13.11+dfsg1-2.debian.tar.xz
 c7c6dcf9bcd32c4742b992eac884f381 8343 ruby optional 

Processed: Re: Bug#860672: mhap: FTBFS on i386: build-dependency not installable: libssw-java

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 860672 wishlist
Bug #860672 [src:mhap] mhap: FTBFS on i386: build-dependency not installable: 
libssw-java
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860672: mhap: FTBFS on i386: build-dependency not installable: libssw-java

[Lucas Nussbaum]

severity 860672 wishlist
thanks

Downgrading: libssw-java is only available on 64b archs.

Lucas

Bug#860639: circlator: FTBFS on i386: unsatisfiable build-dependencies: python3-pysam (>= 0.8.1), spades, bwa (>= 0.7.12)

[Lucas Nussbaum]

severity 860639 wishlist
thanks

Downgrading as spades is only available on 64b architectures

Processed: Re: Bug#860639: circlator: FTBFS on i386: unsatisfiable build-dependencies: python3-pysam (>= 0.8.1), spades, bwa (>= 0.7.12)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 860639 wishlist
Bug #860639 [src:circlator] circlator: FTBFS on i386: unsatisfiable 
build-dependencies: python3-pysam (>= 0.8.1), spades, bwa (>= 0.7.12)
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860634: marked as done (node-grunt-contrib-copy: FTBFS on i386: Test failures)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 09:33:57 +
with message-id 
and subject line Bug#860634: fixed in node-grunt-contrib-copy 1.0.0-2
has caused the Debian Bug report #860634,
regarding node-grunt-contrib-copy: FTBFS on i386: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
860634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-grunt-contrib-copy
Version: 1.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>   at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
>   at /usr/lib/nodejs/nodeunit/lib/core.js:236:16
>   at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9)
>   at /usr/lib/nodejs/nodeunit/lib/core.js:118:25
>   at /usr/lib/nodejs/nodeunit/deps/async.js:513:13
>   at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13)
>   at /usr/lib/nodejs/nodeunit/deps/async.js:134:25
>   at /usr/lib/nodejs/nodeunit/deps/async.js:515:17
>   at Immediate._onImmediate (/usr/lib/nodejs/nodeunit/lib/types.js:146:17)
>   at processImmediate [as _immediateCallback] (timers.js:396:17)
> 
> 
> ✔ copy - timestamp_changed
> 
> FAILURES: 2/17 assertions failed (201ms)
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/node-grunt-contrib-copy_1.0.0-1_testing-i386.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-grunt-contrib-copy
Source-Version: 1.0.0-2

We believe that the bug you reported is fixed in the latest version of
node-grunt-contrib-copy, 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 860...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paolo Greppi  (supplier of updated 
node-grunt-contrib-copy 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: Fri, 21 Apr 2017 09:20:25 +0200
Source: node-grunt-contrib-copy
Binary: node-grunt-contrib-copy
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paolo Greppi 
Description:
 node-grunt-contrib-copy - Copy files and folders
Closes: 860634
Changes:
 node-grunt-contrib-copy (1.0.0-2) unstable; urgency=medium
 .
   * add Testsuite: autopkgtest entry in source stanza
   * run built-time tests with run_tests script
   * run autopkgtests with run_tests script (Closes: #860634)
Checksums-Sha1:
 f49c71286ae91c4c651fec847dae584bc61f9145 2202 
node-grunt-contrib-copy_1.0.0-2.dsc
 8636eaef0561e5cd1586c24166f9ed8f57606fed 2580 
node-grunt-contrib-copy_1.0.0-2.debian.tar.xz
Checksums-Sha256:
 b05413cb59ee03e3309784480f8c7d49042a0b2db348ab6db213da89642dcf61 2202 
node-grunt-contrib-copy_1.0.0-2.dsc
 7cb18ced15d4414e662c34605f475f401bb79d4697076f2956f87988bfa09ab1 2580 
node-grunt-contrib-copy_1.0.0-2.debian.tar.xz
Files:
 29b0361eb490a09969157dc0e9d99bbf 2202 web optional 
node-grunt-contrib-copy_1.0.0-2.dsc
 71b0487cff44e267a5c326eba0c8ea04 2580 web optional 
node-grunt-contrib-copy_1.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY+cq3AAoJEM4fnGdFEsIqK7cQAIDsGdan9SR/XJSXxp7KwHKC
4q9Sqh5HsjxPKJIP+thEoK5gNOPDP1cMRs/FN+5bsp5iJWnPAILo2AysBC9kPdXb
HWAuMFFIwuCx7+62LS2/jek97iuXu8q1ktqyJXhurVEK9kOTnGe+qca4zrF1LamH
AsWpl7O2jSNIrjMpBC8F9u9eM+E6aetayTLKljZg9x7jsWZ2xlNj7VCAnqkeN6wX

Bug#860673: marked as done (python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:23:05 +0200
with message-id <20170421092305.ch6jecmtxdxlx...@xanadu.blop.info>
and subject line Re: Bug#860673: [Python-modules-team] Bug#860673: 
python-django: FTBFS on i386: E: Build killed with signal TERM after 150 
minutes of inactivity
has caused the Debian Bug report #860673,
regarding python-django: FTBFS on i386: E: Build killed with signal TERM after 
150 minutes of inactivity
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
860673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.10.7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> Ensure is_null is handled correctly. ... ok
> test_limited_filter (admin_views.tests.AdminViewBasicTest)
> Ensure admin changelist filters do not contain objects excluded via 
> limit_choices_to. ... ok
> test_logout_and_password_change_URLs (admin_views.tests.AdminViewBasicTest) 
> ... ok
> test_multiple_sort_same_field (admin_views.tests.AdminViewBasicTest) ... ok
> test_named_group_field_choices_change_list 
> (admin_views.tests.AdminViewBasicTest) ... ok
> test_named_group_field_choices_filter (admin_views.tests.AdminViewBasicTest) 
> ... ok
> test_popup_add_POST (admin_views.tests.AdminViewBasicTest) ... ok
> test_popup_dismiss_related (admin_views.tests.AdminViewBasicTest) ... ok
> test_relation_spanning_filters (admin_views.tests.AdminViewBasicTest) ... ok
> test_resolve_admin_views (admin_views.tests.AdminViewBasicTest) ... ok
> test_sort_indicators_admin_order (admin_views.tests.AdminViewBasicTest) ... ok
> test_trailing_slash_required (admin_views.tests.AdminViewBasicTest) ... ok
> test_output_normal (test_runner.test_debug_sql.TestDebugSQL) ... ok
> test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/python-django_1.10.7-1_testing-i386.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 ---
On 20/04/17 at 09:29 +0200, Lucas Nussbaum wrote:
> On 20/04/17 at 06:54 +1000, Brian May wrote:
> > Chris Lamb  writes:
> > 
> > > Lucas Nussbaum wrote:
> > >
> > >> > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok
> > >> > E: Build killed with signal TERM after 150 minutes of inactivity
> > >
> > > Can't reproduce this locally alas...
> > 
> > I couldn't reproduce this locally. I use a 32bit schroot.
> 
> I tried on a smaller EC2 instance (m4.4xlarge, with 16 cores instead of
> 64) and it did not fail.
> 
> Lucas

Hi,

I did the archive rebuild that resulted in this bug on a machine with a
jessie kernel. I did another rebuild on a machine with a stretch
kernel, and this failure disappeared.

My best guess is that this has something to do with a stack overflow,
in a way similar to #750593 (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593#157 and #797530
(fixed in stretch, not jessie).

Given that this doesn't affect building on a machine with a stretch
kernel, I'm closing the bug.

Lucas--- End Message ---

Bug#860702: marked as done (pcl: FTBFS on i386: segmentation fault)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:27:25 +0200
with message-id <20170421092725.azlkkqo4zuvvg...@xanadu.blop.info>
and subject line Re: Bug#860702: pcl: FTBFS on i386: segmentation fault
has caused the Debian Bug report #860702,
regarding pcl: FTBFS on i386: segmentation fault
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.)


-- 
860702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcl
Version: 1.8.0+dfsg1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> make[3]: Entering directory '/<>/pcl-1.8.0+dfsg1/build'
> cd /<>/pcl-1.8.0+dfsg1/build/doc/doxygen && /usr/bin/doxygen 
> /<>/pcl-1.8.0+dfsg1/build/doc/doxygen/doxyfile
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_cloud.h:361: warning: 
> multiple use of section label 'getMatrixXfMap' while adding anchor, (first 
> occurrence: /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_cloud.h, 
> line 337)
> /<>/pcl-1.8.0+dfsg1/features/include/pcl/features/impl/intensity_gradient.hpp:238:
>  warning: Reached end of file while still inside a (nested) comment. Nesting 
> level 2 (probable line reference: 135, 95)
> /<>/pcl-1.8.0+dfsg1/filters/include/pcl/filters/impl/plane_clipper3D.hpp:229:
>  warning: Reached end of file while still inside a (nested) comment. Nesting 
> level 3 (probable line reference: 219, 215, 185)
> /<>/pcl-1.8.0+dfsg1/recognition/recognition.doxy:9: warning: 
> multiple use of section label 'secRecognitionRequirements' while adding 
> section, (first occurrence: 
> /<>/pcl-1.8.0+dfsg1/geometry/geometry.doxy, line 8)
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:139: warning: 
> Detected potential recursive class relation between class pcl::traits::name 
> and base class pcl::traits::name< POD< PointT >::type, Tag, dummy >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:139: warning: 
> Detected potential recursive class relation between class pcl::traits::name 
> and base class name< POD< PointT >::type, Tag, dummy >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:139: warning: 
> Detected potential recursive class relation between class pcl::traits::name 
> and base class pcl::traits::name< POD< PointT >::type, Tag, dummy >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:139: warning: 
> Detected potential recursive class relation between class pcl::traits::name 
> and base class name< POD< PointT >::type, Tag, dummy >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:163: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::datatype and base class pcl::traits::datatype< POD< PointT 
> >::type, Tag >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:163: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::datatype and base class datatype< POD< PointT >::type, Tag >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:163: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::datatype and base class pcl::traits::datatype< POD< PointT 
> >::type, Tag >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:163: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::datatype and base class datatype< POD< PointT >::type, Tag >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:177: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::fieldList and base class pcl::traits::fieldList< POD< PointT 
> >::type >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:177: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::fieldList and base class fieldList< POD< PointT >::type >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:177: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::fieldList and base class pcl::traits::fieldList< POD< PointT 
> >::type >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:177: warning: 
> Detected potential recursive class relation between class 
> pcl::traits::fieldList and base class fieldList< POD< PointT >::type >!
> 
> /<>/pcl-1.8.0+dfsg1/common/include/pcl/point_traits.h:151: warning: 
> Detected potential recursive class relation 

Bug#860708: marked as done (ruby-seamless-database-pool: FTBFS on i386: ERROR: Test "ruby2.3" failed: Failure/Error: pool_connection.to_s.should =~ /\A#

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:26:14 +0200
with message-id <20170421092614.7fnwdxn7oimkv...@xanadu.blop.info>
and subject line Re: Bug#860708: ruby-seamless-database-pool: FTBFS on i386: 
ERROR: Test "ruby2.3" failed: Failure/Error: pool_connection.to_s.should =~ 
/\A#\z/
has caused the Debian Bug report #860708,
regarding ruby-seamless-database-pool: FTBFS on i386: ERROR: Test "ruby2.3" 
failed: Failure/Error: pool_connection.to_s.should =~ 
/\A#\z/
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.)


-- 
860708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-seamless-database-pool
Version: 1.0.17-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>  Failure/Error: pool_connection.to_s.should =~ 
> /\A#  3 connections>\z/
> 
>expected: 
> /\A#  3 connections>\z/
> got: 
> "#  3 connections>" (using =~)
>Diff:
>@@ -1,2 +1,2 @@
>
> -/\A#  3 connections>\z/
>
> +"#  3 connections>"
>  # ./spec/seamless_database_pool_adapter_spec.rb:92:in `block (2 levels) 
> in '
> 
> Deprecation Warnings:
> 
> Using `should_receive` from rspec-mocks' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` instead. Called from 
> /<>/spec/connection_statistics_spec.rb:64:in `block (2 levels) 
> in '.
> 
> Using `should` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/connection_statistics_spec.rb:32:in `block (2 levels) 
> in '.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 2 deprecation warnings total
> 
> Finished in 0.78735 seconds (files took 1.27 seconds to load)
> 62 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/seamless_database_pool_adapter_spec.rb:91 # 
> SeamlessDatabasePoolAdapter should be able to be converted to a string
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/ruby-seamless-database-pool_1.0.17-1_testing-i386.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 ---
On 19/04/17 at 09:21 +0200, Lucas Nussbaum wrote:
> Source: ruby-seamless-database-pool
> Version: 1.0.17-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
> 
> Hi,
> 
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
> 
> Relevant part (hopefully):
> >  Failure/Error: pool_connection.to_s.should =~ 
> > /\A# >  3 connections>\z/
> > 
> >expected: 
> > /\A# >  3 connections>\z/
> > got: 
> > "# >  3 connections>" (using =~)
> >Diff:
> >@@ -1,2 +1,2 @@
> >  

Bug#860707: marked as done (ruby-timers: FTBFS on i386: ERROR: Test "ruby2.3" failed: Failure/Error: expect(timer.inspect).to match(/\A#<Timers::Timer:[\da-f]+ fires in [-\.\de]+ seconds>\Z/))

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:26:55 +0200
with message-id <20170421092655.txzx2wpkq6gpt...@xanadu.blop.info>
and subject line Re: Bug#860707: ruby-timers: FTBFS on i386: ERROR: Test 
"ruby2.3" failed: Failure/Error: expect(timer.inspect).to 
match(/\A#\Z/)
has caused the Debian Bug report #860707,
regarding ruby-timers: FTBFS on i386: ERROR: Test "ruby2.3" failed: 
Failure/Error: expect(timer.inspect).to match(/\A#\Z/)
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.)


-- 
860707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-timers
Version: 4.1.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>  Failure/Error: expect(timer.inspect).to 
> match(/\A#\Z/)
> 
>expected "#" to 
> match /\A#\Z/
>Diff:
>@@ -1,2 +1,2 @@
>-/\A#\Z/
>+"#"
>  # /usr/lib/ruby/vendor_ruby/rspec/support.rb:87:in `block in 
> '
>  # /usr/lib/ruby/vendor_ruby/rspec/support.rb:96:in `notify_failure'
>  # /usr/lib/ruby/vendor_ruby/rspec/expectations/fail_with.rb:27:in 
> `fail_with'
>  # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:38:in 
> `handle_failure'
>  # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:50:in `block 
> in handle_matcher'
>  # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:27:in 
> `with_matcher'
>  # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:48:in 
> `handle_matcher'
>  # 
> /usr/lib/ruby/vendor_ruby/rspec/expectations/expectation_target.rb:65:in `to'
>  # ./spec/group_spec.rb:209:in `block (3 levels) in '
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `instance_exec'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in `block in 
> with_around_and_singleton_context_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in `block in 
> with_around_example_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in 
> `run_around_example_hooks_for'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in 
> `with_around_example_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in 
> `with_around_and_singleton_context_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:627:in `block in 
> run_examples'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in `map'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in 
> `run_examples'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:589:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `block in 
> run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `map'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (3 
> levels) in run_specs'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `map'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (2 
> levels) in run_specs'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1835:in 
> `with_suite_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `block in 
> run_specs'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:77:in `report'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `run_specs'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
>  # /usr/bin/rspec:4:in `'
> 
> Finished in 26.33 seconds (files took 0.71465 seconds to load)
> 36 examples, 3 failures
> 
> Failed examples:
> 
> rspec 

Bug#860635: marked as done (octave-ltfat: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:20:37 +0200
with message-id <20170421092037.appyjydalei7q...@xanadu.blop.info>
and subject line Re: Bug#860635: octave-ltfat: FTBFS on i386: E: Build killed 
with signal TERM after 150 minutes of inactivity
has caused the Debian Bug report #860635,
regarding octave-ltfat: FTBFS on i386: E: Build killed with signal TERM after 
150 minutes of inactivity
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
860635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-ltfat
Version: 2.2.0+dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> = TEST DTWFB 
>  ===  TEST_AMBIGUITYFUNCTION ==
>  ===  TEST_WIGERVILLEDIST ==
>  === TEST_CONSTRUCTPHASE == 
>  ===  TEST_DGT 
>  ===  TEST_DWILT 
>  ===  TEST_WMDCT 
>  ===  TEST_DGT_FB 
>  ===  TEST_MULTIWIN 
>  ===  TEST_GABFIRTIGHT 
>  ===  TEST_PUREFREQ 
>  ===  TEST_ZAK 
>  ===  TEST_GABMULAPPR =
>  ===  TEST_DGT2 
>  ===  TEST_DWILT2 
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/octave-ltfat_2.2.0+dfsg-3_testing-i386.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 ---
On 19/04/17 at 09:16 +0200, Lucas Nussbaum wrote:
> Source: octave-ltfat
> Version: 2.2.0+dfsg-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
> 
> Hi,
> 
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
> 
> Relevant part (hopefully):
> > = TEST DTWFB 
> >  ===  TEST_AMBIGUITYFUNCTION ==
> >  ===  TEST_WIGERVILLEDIST ==
> >  === TEST_CONSTRUCTPHASE == 
> >  ===  TEST_DGT 
> >  ===  TEST_DWILT 
> >  ===  TEST_WMDCT 
> >  ===  TEST_DGT_FB 
> >  ===  TEST_MULTIWIN 
> >  ===  TEST_GABFIRTIGHT 
> >  ===  TEST_PUREFREQ 
> >  ===  TEST_ZAK 
> >  ===  TEST_GABMULAPPR =
> >  ===  TEST_DGT2 
> >  ===  TEST_DWILT2 
> > E: Build killed with signal TERM after 150 minutes of inactivity
> 
> The full build log is available from:
>
> http://aws-logs.debian.net/2017/04/18/octave-ltfat_2.2.0+dfsg-3_testing-i386.log

Hi,

I did the archive rebuild that resulted in this bug on a machine with a
jessie kernel. I did another rebuild on a machine with a stretch
kernel, and this failure disappeared.

My best guess is that this has something to do with a stack overflow,
in a way similar to #750593 (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593#157 and #797530
(fixed in stretch, not jessie).

Given that this doesn't affect building on a machine with a stretch 
kernel, I'm closing the bug.

Lucas--- End Message ---

Bug#860651: marked as done (ruby-awesome-print: FTBFS on i386: ERROR: Test "ruby2.3" failed: Failure/Error: expect(out.gsub(/0x([a-f\d]+)/, "0x01234567")).to eq(str))

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:23:40 +0200
with message-id <20170421092340.ynuwbk5an36u2...@xanadu.blop.info>
and subject line Re: Bug#860651: ruby-awesome-print: FTBFS on i386: ERROR: Test 
"ruby2.3" failed: Failure/Error: expect(out.gsub(/0x([a-f\d]+)/, 
"0x01234567")).to eq(str)
has caused the Debian Bug report #860651,
regarding ruby-awesome-print: FTBFS on i386: ERROR: Test "ruby2.3" failed: 
Failure/Error: expect(out.gsub(/0x([a-f\d]+)/, "0x01234567")).to eq(str)
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.)


-- 
860651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-awesome-print
Version: 1.6.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>  Failure/Error: expect(out.gsub(/0x([a-f\d]+)/, "0x01234567")).to eq(str)
> 
>expected: "# @scooby = 3,\nattr_accessor :dabra = 3,\nattr_reader :abra = 1,\n
> attr_writer :ca = 2\n>"
> got: "# @scooby = 3,\nattr_accessor :dabra = 3,\nattr_reader :abra = 1,\n
> attr_writer :ca = 2\n>"
> 
>(compared using ==)
> 
>Diff:
>@@ -1,4 +1,4 @@
>-#+# @doo = 1,
> @dooby = 2,
> @scooby = 3,
>  # ./spec/objects_spec.rb:81:in `block (3 levels) in '
> 
> Finished in 0.29284 seconds (files took 0.28149 seconds to load)
> 135 examples, 3 failures
> 
> Failed examples:
> 
> rspec ./spec/objects_spec.rb:13 # Objects Formatting an object attributes
> rspec ./spec/objects_spec.rb:37 # Objects Formatting an object instance 
> variables
> rspec ./spec/objects_spec.rb:57 # Objects Formatting an object attributes and 
> instance variables
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/ruby-awesome-print_1.6.1-2_testing-i386.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 ---
On 19/04/17 at 09:20 +0200, Lucas Nussbaum wrote:
> Source: ruby-awesome-print
> Version: 1.6.1-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
> 
> Hi,
> 
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
> 
> Relevant part (hopefully):
> >  Failure/Error: expect(out.gsub(/0x([a-f\d]+)/, "0x01234567")).to 
> > eq(str)
> > 
> >expected: "# > @scooby = 3,\nattr_accessor :dabra = 3,\nattr_reader :abra = 1,\n   
> >  attr_writer :ca = 2\n>"
> > got: "# > @scooby = 3,\nattr_accessor :dabra = 3,\nattr_reader :abra = 1,\n   
> >  attr_writer :ca = 2\n>"
> > 
> >(compared using ==)
> > 
> >Diff:
> >@@ -1,4 +1,4 @@
> >-# >+# > @doo = 1,
> > @dooby = 2,
> > @scooby = 3,
> >  # ./spec/objects_spec.rb:81:in `block (3 levels) in '
> > 
> > Finished in 0.29284 seconds (files took 0.28149 seconds to load)
> > 135 examples, 3 failures
> > 
> > Failed examples:
> > 
> > rspec ./spec/objects_spec.rb:13 # Objects Formatting an object attributes
> > rspec ./spec/objects_spec.rb:37 # Objects Formatting an object instance 
> > variables
> > rspec ./spec/objects_spec.rb:57 # Objects Formatting an object attributes 
> > and instance variables
> > 
> > /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
> > ERROR: Test "ruby2.3" failed: 
> 
> The full build log is available from:
>
> http://aws-logs.debian.net/2017/04/18/ruby-awesome-print_1.6.1-2_testing-i386.log

Hi,

I did the archive rebuild that resulted in this 

Bug#860693: marked as done (ruby-rspec: FTBFS on i386: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to match(/\A#<BasicObject:0x[0-9a-f]{14}>\z/))

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:25:48 +0200
with message-id <20170421092548.imqy4iw5ukvce...@xanadu.blop.info>
and subject line Re: Bug#860693: ruby-rspec: FTBFS on i386: ERROR: Test 
"ruby2.3" failed:  Failure/Error: expect(output).to 
match(/\A#\z/)
has caused the Debian Bug report #860693,
regarding ruby-rspec: FTBFS on i386: ERROR: Test "ruby2.3" failed:  
Failure/Error: expect(output).to match(/\A#\z/)
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.)


-- 
860693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec
Version: 3.5.0c3e0m0s0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>  Failure/Error: expect(output).to 
> match(/\A#\z/)
> 
>expected "#" to match 
> /\A#\z/
>Diff:
>@@ -1,2 +1,2 @@
>-/\A#\z/
>+"#"
>  # ./spec/rspec/support/object_formatter_spec.rb:191:in `block (3 levels) 
> in '
>  # debian/ruby-tests.rb:30:in `block (3 levels) in '
>  # debian/ruby-tests.rb:24:in `chdir'
>  # debian/ruby-tests.rb:24:in `block (2 levels) in '
>  # debian/ruby-tests.rb:23:in `fork'
>  # debian/ruby-tests.rb:23:in `block in '
>  # debian/ruby-tests.rb:22:in `each'
>  # debian/ruby-tests.rb:22:in `'
> 
> Finished in 0.98638 seconds (files took 0.49044 seconds to load)
> 458 examples, 1 failure, 2 pending
> 
> Failed examples:
> 
> rspec ./spec/rspec/support/object_formatter_spec.rb:190 # 
> RSpec::Support::ObjectFormatter.format with an object that does not respond 
> to #inspect such as BasicObject produces an output emulating MRI's 
> #inspect-like output generated by C implementation
> 
> Randomized with seed 4285
> 
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/ruby-rspec_3.5.0c3e0m0s0-1_testing-i386.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 ---
On 19/04/17 at 09:21 +0200, Lucas Nussbaum wrote:
> Source: ruby-rspec
> Version: 3.5.0c3e0m0s0-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
> 
> Hi,
> 
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
> 
> Relevant part (hopefully):
> >  Failure/Error: expect(output).to 
> > match(/\A#\z/)
> > 
> >expected "#" to match 
> > /\A#\z/
> >Diff:
> >@@ -1,2 +1,2 @@
> >-/\A#\z/
> >+"#"
> >  # ./spec/rspec/support/object_formatter_spec.rb:191:in `block (3 
> > levels) in '
> >  # debian/ruby-tests.rb:30:in `block (3 levels) in '
> >  # debian/ruby-tests.rb:24:in `chdir'
> >  # debian/ruby-tests.rb:24:in `block (2 levels) in '
> >  # debian/ruby-tests.rb:23:in `fork'
> >  # debian/ruby-tests.rb:23:in `block in '
> >  # debian/ruby-tests.rb:22:in `each'
> >  # debian/ruby-tests.rb:22:in `'
> > 
> > Finished in 0.98638 seconds (files took 0.49044 seconds to load)
> > 458 examples, 1 failure, 2 pending
> > 
> > Failed examples:
> > 
> > rspec ./spec/rspec/support/object_formatter_spec.rb:190 # 
> > RSpec::Support::ObjectFormatter.format with an object that does not respond 
> > to #inspect such as BasicObject produces an output emulating MRI's 
> > #inspect-like output generated by C implementation
> > 
> > Randomized with seed 4285
> > 
> > ERROR: Test "ruby2.3" failed: 
> 
> The full build log is available from:
>
> http://aws-logs.debian.net/2017/04/18/ruby-rspec_3.5.0c3e0m0s0-1_testing-i386.log

Hi,

I did the archive rebuild that resulted in this bug on a machine with a
jessie kernel. I did another rebuild on a machine with a 

Bug#860667: marked as done (u1db: FTBFS on i386: Test failures)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:27:19 +0200
with message-id <20170421092719.fqlnfk4pp2kzn...@xanadu.blop.info>
and subject line Re: Bug#860667: u1db: FTBFS on i386: Test failures
has caused the Debian Bug report #860667,
regarding u1db: FTBFS on i386: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
860667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: u1db
Version: 13.10-6.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> Ran 1595 tests in 10.401s
> FAILED (failures=304)
> CMakeFiles/check-nodoctests.dir/build.make:60: recipe for target 
> 'CMakeFiles/check-nodoctests' failed
> make[5]: *** [CMakeFiles/check-nodoctests] Error 1
> make[5]: Leaving directory '/<>/obj-i686-linux-gnu'
> CMakeFiles/Makefile2:172: recipe for target 
> 'CMakeFiles/check-nodoctests.dir/all' failed
> make[4]: *** [CMakeFiles/check-nodoctests.dir/all] Error 2
> make[4]: Leaving directory '/<>/obj-i686-linux-gnu'
> CMakeFiles/Makefile2:179: recipe for target 
> 'CMakeFiles/check-nodoctests.dir/rule' failed
> make[3]: *** [CMakeFiles/check-nodoctests.dir/rule] Error 2
> make[3]: Leaving directory '/<>/obj-i686-linux-gnu'
> Makefile:226: recipe for target 'check-nodoctests' failed
> make[2]: *** [check-nodoctests] Error 2
> make[2]: Leaving directory '/<>/obj-i686-linux-gnu'
> dh_auto_build: make -j1 check-nodoctests returned exit code 2
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/u1db_13.10-6.2_testing-i386.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 ---
On 19/04/17 at 09:24 +0200, Lucas Nussbaum wrote:
> Source: u1db
> Version: 13.10-6.2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
> 
> Hi,
> 
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
> 
> Relevant part (hopefully):
> > Ran 1595 tests in 10.401s
> > FAILED (failures=304)
> > CMakeFiles/check-nodoctests.dir/build.make:60: recipe for target 
> > 'CMakeFiles/check-nodoctests' failed
> > make[5]: *** [CMakeFiles/check-nodoctests] Error 1
> > make[5]: Leaving directory '/<>/obj-i686-linux-gnu'
> > CMakeFiles/Makefile2:172: recipe for target 
> > 'CMakeFiles/check-nodoctests.dir/all' failed
> > make[4]: *** [CMakeFiles/check-nodoctests.dir/all] Error 2
> > make[4]: Leaving directory '/<>/obj-i686-linux-gnu'
> > CMakeFiles/Makefile2:179: recipe for target 
> > 'CMakeFiles/check-nodoctests.dir/rule' failed
> > make[3]: *** [CMakeFiles/check-nodoctests.dir/rule] Error 2
> > make[3]: Leaving directory '/<>/obj-i686-linux-gnu'
> > Makefile:226: recipe for target 'check-nodoctests' failed
> > make[2]: *** [check-nodoctests] Error 2
> > make[2]: Leaving directory '/<>/obj-i686-linux-gnu'
> > dh_auto_build: make -j1 check-nodoctests returned exit code 2
> > debian/rules:13: recipe for target 'override_dh_auto_test' failed
> 
> The full build log is available from:
>http://aws-logs.debian.net/2017/04/18/u1db_13.10-6.2_testing-i386.log

Hi,

I did the archive rebuild that resulted in this bug on a machine with a
jessie kernel. I did another rebuild on a machine with a stretch
kernel, and this failure disappeared.

My best guess is that this has something to do with a stack overflow,
in a way similar to #750593 (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593#157 and #797530
(fixed in stretch, not jessie).

Given that this doesn't affect building on a machine with a stretch
kernel, I'm closing the bug.

Lucas--- End Message ---

Bug#860706: fvwm: FTBFS on i386: /bin/bash: line 2: 19651 Segmentation fault xsltproc --path "../../doc":"../../doc/commands" --xinclude ./../fvwm-man.xsl fvwm.1.tmp

[Lucas Nussbaum]

On 19/04/17 at 09:25 +0200, Lucas Nussbaum wrote:
> Source: fvwm
> Version: 1:2.6.7-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
> 
> Hi,
> 
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
> 
> Relevant part (hopefully):
> > make[4]: Entering directory '/<>/doc/fvwm'
> > xsltproc --path "../../doc":"../../doc/commands" \
> > --xinclude \
> > --stringparam profile.attribute output \
> > --stringparam profile.value man \
> > -o fvwm.1.tmp \
> > ./../docbook-xsl/profiling/profile.xsl "./fvwm.man.xml"
> > xsltproc --path "../../doc":"../../doc/commands" \
> > --xinclude \
> > ./../fvwm-man.xsl fvwm.1.tmp && rm fvwm.1.tmp
> > /bin/bash: line 2: 19651 Segmentation fault  xsltproc --path 
> > "../../doc":"../../doc/commands" --xinclude ./../fvwm-man.xsl fvwm.1.tmp
> > Makefile:690: recipe for target 'fvwm.1' failed
> > make[4]: *** [fvwm.1] Error 139
> 
> The full build log is available from:
>http://aws-logs.debian.net/2017/04/18/fvwm_2.6.7-3_testing-i386.log

Hi,

I did the archive rebuild that resulted in this bug on a machine with a
jessie kernel. I did another rebuild on a machine with a stretch
kernel, and this failure disappeared. That's consistent with 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593#157
and #797530 (fixed in stretch, not jessie).

Lucas

Bug#860675: marked as done (jlapack: FTBFS on i386: segfault)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:20:41 +0200
with message-id <20170421092041.5ey5ughodrwke...@xanadu.blop.info>
and subject line Re: Bug#860675: jlapack: FTBFS on i386: segfault
has caused the Debian Bug report #860675,
regarding jlapack: FTBFS on i386: segfault
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.)


-- 
860675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jlapack
Version: 0.8~dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> make[4]: Entering directory '/<>/jlapack-3.1.1/src/lapack'
> f2java -c .:obj:../../src/error_reporting/obj:../../src/blas/obj -p 
> org.netlib.lapack -o obj -s -d  lapack.f > /dev/null
> lapack.f:
>   dbdsdc:
>   dbdsqr:
>   ddisna:
>   dgbbrd:
>   dgbcon:
>   dgbequ:
>   dgbrfs:
>   dgbsv:
>   dgbsvx:
>   dgbtf2:
>   dgbtrf:
>   dgbtrs:
>   dgebak:
>   dgebal:
>   dgebd2:
>   dgebrd:
>   dgecon:
>   dgeequ:
>   dgees:
>   dgeesx:
>   dgeev:
>   dgeevx:
>   dgegs:
>   dgegv:
>   dgehd2:
>   dgehrd:
>   dgelq2:
>   dgelqf:
>   dgels:
>   dgelsd:
>   dgelss:
>   dgelsx:
>   dgelsy:
>   dgeql2:
>   dgeqlf:
>   dgeqp3:
>   dgeqpf:
>   dgeqr2:
>   dgeqrf:
>   dgerfs:
>   dgerq2:
>   dgerqf:
>   dgesc2:
>   dgesdd:
>   dgesv:
>   dgesvd:
>   dgesvx:
>   dgetc2:
>   dgetf2:
>   dgetrf:
>   dgetri:
>   dgetrs:
>   dggbak:
>   dggbal:
>   dgges:
>   dggesx:
>   dggev:
>   dggevx:
>   dggglm:
>   dgghrd:
>   dgglse:
>   dggqrf:
>   dggrqf:
>   dggsvd:
>   dggsvp:
>   dgtcon:
>   dgtrfs:
>   dgtsv:
>   dgtsvx:
>   dgttrf:
>   dgttrs:
>   dgtts2:
>   dhgeqz:
>   dhsein:
>   dhseqr:
>   disnan:
>   dlabad:
>   dlabrd:
>   dlacn2:
>   dlacon:
>   dlacpy:
>   dladiv:
>   dlae2:
>   dlaebz:
>   dlaed0:
>   dlaed1:
>   dlaed2:
>   dlaed3:
>   dlaed4:
>   dlaed5:
>   dlaed6:
>   dlaed7:
>   dlaed8:
>   dlaed9:
>   dlaeda:
>   dlaein:
>   dlaev2:
>   dlaexc:
>   dlag2:
>   dlag2s:
>   dlags2:
>   dlagtf:
>   dlagtm:
>   dlagts:
>   dlagv2:
>   dlahqr:
>   dlahr2:
>   dlahrd:
>   dlaic1:
>   dlaisnan:
>   dlaln2:
>   dlals0:
>   dlalsa:
>   dlalsd:
>   dlamrg:
>   dlaneg:
> Warning: IMPLICIT NONE ignored.
>   dlangb:
>   dlange:
>   dlangt:
>   dlanhs:
>   dlansb:
>   dlansp:
>   dlanst:
>   dlansy:
>   dlantb:
>   dlantp:
>   dlantr:
>   dlanv2:
>   dlapll:
>   dlapmt:
>   dlapy2:
>   dlapy3:
>   dlaqgb:
>   dlaqge:
>   dlaqp2:
>   dlaqps:
>   dlaqr0:
>   dlaqr1:
>   dlaqr2:
>   dlaqr3:
>   dlaqr4:
>   dlaqr5:
>   dlaqsb:
>   dlaqsp:
>   dlaqsy:
>   dlaqtr:
>   dlar1v:
>   dlar2v:
>   dlarf:
>   dlarfb:
>   dlarfg:
>   dlarft:
>   dlarfx:
>   dlargv:
>   dlarnv:
>   dlarra:
> Warning: IMPLICIT NONE ignored.
>   dlarrb:
>   dlarrc:
>   dlarrd:
>   dlarre:
> Warning: IMPLICIT NONE ignored.
>   dlarrf:
>   dlarrj:
>   dlarrk:
> Warning: IMPLICIT NONE ignored.
>   dlarrr:
>   dlarrv:
>   dlartg:
>   dlartv:
>   dlaruv:
>   dlarz:
>   dlarzb:
>   dlarzt:
>   dlas2:
>   dlascl:
>   dlasd0:
>   dlasd1:
>   dlasd2:
>   dlasd3:
>   dlasd4:
>   dlasd5:
>   dlasd6:
>   dlasd7:
>   dlasd8:
>   dlasda:
>   dlasdq:
>   dlasdt:
>   dlaset:
>   dlasq1:
>   dlasq2:
>   dlasq3:
>   dlasq4:
>   dlasq5:
>   dlasq6:
>   dlasr:
>   dlasrt:
>   dlassq:
>   dlasv2:
>   dlaswp:
>   dlasy2:
>   dlasyf:
>   dlatbs:
>   dlatdf:
>   dlatps:
>   dlatrd:
>   dlatrs:
>   dlatrz:
>   dlatzm:
>   dlauu2:
>   dlauum:
>   dlazq3:
>   dlazq4:
>   dopgtr:
>   dopmtr:
>   dorg2l:
>   dorg2r:
>   dorgbr:
>   dorghr:
>   dorgl2:
>   

Bug#860683: marked as done (ruby-liquid: FTBFS on i386: ERROR: Test "ruby2.3" failed: SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, unexpected '-', expecting '|')

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:24:41 +0200
with message-id <20170421092441.aznb7ph34mftz...@xanadu.blop.info>
and subject line Re: Bug#860683: ruby-liquid: FTBFS on i386: ERROR: Test 
"ruby2.3" failed: SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: 
syntax error, unexpected '-', expecting '|'
has caused the Debian Bug report #860683,
regarding ruby-liquid: FTBFS on i386: ERROR: Test "ruby2.3" failed: 
SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, 
unexpected '-', expecting '|'
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.)


-- 
860683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-liquid
Version: 3.0.6-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, 
> unexpected '-', expecting '|'
>   lambda do |*__spy_args_-70342088, |
>   ^
> /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:227:in `eval'
> /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:227:in `override_method'
> /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:55:in `hook'
> /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:315:in `on'
> /usr/lib/ruby/vendor_ruby/spy.rb:188:in `create_and_hook_spy'
> /usr/lib/ruby/vendor_ruby/spy.rb:52:in `block in on_instance_method'
> /usr/lib/ruby/vendor_ruby/spy.rb:51:in `map'
> /usr/lib/ruby/vendor_ruby/spy.rb:51:in `on_instance_method'
> /<>/test/unit/context_unit_test.rb:464:in 
> `test_use_empty_instead_of_any_in_interrupt_handling_to_avoid_lots_of_unnecessary_object_allocations'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:799:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:322:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:335:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:135:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:62:in `block in autorun'
> 
> 486 runs, 1185 assertions, 0 failures, 2 errors, 0 skips
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/ruby-liquid_3.0.6-1_testing-i386.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 ---
On 19/04/17 at 09:20 +0200, Lucas Nussbaum wrote:
> Source: ruby-liquid
> Version: 3.0.6-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
> 
> Hi,
> 
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
> 
> Relevant part (hopefully):
> > SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, 
> > unexpected '-', expecting '|'
> >   lambda do |*__spy_args_-70342088, |
> >   ^
> > 

Bug#860696: marked as done (ruby-spy: FTBFS on i386: ERROR: Test "ruby2.3" failed: SyntaxError: /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, unexpecte

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 11:24:41 +0200
with message-id <20170421092441.aznb7ph34mftz...@xanadu.blop.info>
and subject line Re: Bug#860683: ruby-liquid: FTBFS on i386: ERROR: Test 
"ruby2.3" failed: SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: 
syntax error, unexpected '-', expecting '|'
has caused the Debian Bug report #860683,
regarding ruby-spy: FTBFS on i386: ERROR: Test "ruby2.3" failed: SyntaxError: 
/<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229:
 syntax error, unexpected '-', expecting '|'
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.)


-- 
860683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-spy
Version: 0.4.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> SyntaxError: 
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229:
>  syntax error, unexpected '-', expecting '|'
>   lambda do |*__spy_args_-56954028, |
>   ^
> 
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:227:in
>  `eval'
> 
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:227:in
>  `override_method'
> 
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:55:in
>  `hook'
> 
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:315:in
>  `on'
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:188:in 
> `create_and_hook_spy'
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:22:in 
> `block in on'
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:21:in 
> `map'
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:21:in 
> `on'
> /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:144:in 
> `mock_all'
> /<>/test/integration/test_mocking.rb:22:in 
> `test_spy_mock_all'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:799:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:322:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:335:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:135:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:62:in `block in autorun'
> 
> 64 runs, 32 assertions, 0 failures, 33 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/integration/test_api.rb" "test/integration/test_constant_spying.rb" 
> "test/integration/test_instance_method.rb" "test/integration/test_mocking.rb" 
> "test/integration/test_subroutine_spying.rb" "test/spy/test_mock.rb" 
> "test/spy/test_subroutine.rb" "test/test_helper.rb" -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/ruby-spy_0.4.3-1_testing-i386.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.

Bug#860602: marked as done (ruby-net-ldap: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 09:05:21 +
with message-id 
and subject line Bug#860602: fixed in ruby-net-ldap 0.12.1-2
has caused the Debian Bug report #860602,
regarding ruby-net-ldap: FTBFS: ERROR: Test "ruby2.3" 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.)


-- 
860602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-net-ldap
Version: 0.12.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418 qa-ftbfs
Justification: FTBFS in stretch on amd64

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-test-files.yaml  
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-net-ldap/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-net-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ 
> \{\ \|f\|\ require\ f\ \}
> Loaded suite -e
> Started
> ..Deprecation warning: 
> Net::LDAP::ConnectionRefused will be deprecated. Use Errno::ECONNREFUSED 
> instead.
> .Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use 
> Errno::ECONNREFUSED instead.
> Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use 
> Errno::ECONNREFUSED instead.
> Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use 
> Errno::ECONNREFUSED instead.
> Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use 
> Errno::ECONNREFUSED instead.
> F
> ===
> Failure: test_unresponsive_host(TestLDAPConnection)
> /<>/test/test_ldap_connection.rb:64:in `test_unresponsive_host'
>  61:   end
>  62: 
>  63:   def test_unresponsive_host
>   => 64: assert_raise Net::LDAP::Error do
>  65:   Net::LDAP::Connection.new(:host => 'test.mocked.com', :port => 
> 636)
>  66: end
>  67:   end
> 
>  expected but was
> )>Deprecation warning: 
> Net::LDAP::ConnectionRefused will be deprecated. Use Errno::ECONNREFUSED 
> instead.
> 
> 
> diff:
> ? Net::LDAP::ConnectionRefusedError( "test.mocked.com" port 636>)
> ===
> .
> 
> Finished in 0.238979812 seconds.
> --
> 89 tests, 265 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
> notifications
> 98.8764% passed
> --
> 372.42 tests/s, 1108.88 assertions/s
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/ruby-net-ldap_0.12.1-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: ruby-net-ldap
Source-Version: 0.12.1-2

We believe that the bug you reported is fixed in the latest version of
ruby-net-ldap, 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 860...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated ruby-net-ldap 
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: Fri, 21 Apr 2017 

Bug#860625: marked as done (zimlib: FTBFS on i386: dh_makeshlibs: failing due to earlier errors)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 09:05:39 +
with message-id 
and subject line Bug#860625: fixed in zimlib 1.4-2.1
has caused the Debian Bug report #860625,
regarding zimlib: FTBFS on i386: dh_makeshlibs: failing due to earlier errors
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.)


-- 
860625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zimlib
Version: 1.4-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: Nothing to be done for 'install-exec-am'.
> make[3]: Nothing to be done for 'install-data-am'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
> touch debian/stamp-makefile-install
> Adding cdbs dependencies to debian/libzim0v5.substvars
> dh_installdirs -plibzim0v5 \
>   
> Adding cdbs dependencies to debian/libzim0v5-dbg.substvars
> dh_installdirs -plibzim0v5-dbg \
>   
> Adding cdbs dependencies to debian/libzim-dev.substvars
> dh_installdirs -plibzim-dev \
>   
> dh_installdocs -plibzim0v5 ./README ./NEWS ./AUTHORS
> dh_installexamples -plibzim0v5 
> dh_installman -plibzim0v5 
> dh_installinfo -plibzim0v5 
> dh_installmenu -plibzim0v5 
> dh_installcron -plibzim0v5 
> dh_systemd_enable -plibzim0v5 
> dh_installinit -plibzim0v5 
> dh_installdebconf -plibzim0v5 
> dh_installemacsen -plibzim0v5 
> dh_installcatalogs -plibzim0v5 
> dh_installpam -plibzim0v5 
> dh_installlogrotate -plibzim0v5 
> dh_installlogcheck -plibzim0v5 
> dh_installchangelogs -plibzim0v5 
> dh_installudev -plibzim0v5 
> dh_lintian -plibzim0v5 
> dh_bugfiles -plibzim0v5 
> dh_install -plibzim0v5 
> dh_systemd_start -plibzim0v5 
> dh_link -plibzim0v5 
> dh_buildinfo -plibzim0v5 
> dh_installmime -plibzim0v5 
> dh_installgsettings -plibzim0v5 
> dh_installdocs -plibzim-dev ./README ./NEWS ./AUTHORS
> dh_installexamples -plibzim-dev 
> dh_installman -plibzim-dev 
> dh_installinfo -plibzim-dev 
> dh_installmenu -plibzim-dev 
> dh_installcron -plibzim-dev 
> dh_systemd_enable -plibzim-dev 
> dh_installinit -plibzim-dev 
> dh_installdebconf -plibzim-dev 
> dh_installemacsen -plibzim-dev 
> dh_installcatalogs -plibzim-dev 
> dh_installpam -plibzim-dev 
> dh_installlogrotate -plibzim-dev 
> dh_installlogcheck -plibzim-dev 
> dh_installchangelogs -plibzim-dev 
> dh_installudev -plibzim-dev 
> dh_lintian -plibzim-dev 
> dh_bugfiles -plibzim-dev 
> dh_install -plibzim-dev 
> dh_systemd_start -plibzim-dev 
> dh_link -plibzim-dev 
> dh_buildinfo -plibzim-dev 
> dh_installmime -plibzim-dev 
> dh_installgsettings -plibzim-dev 
> d-shlibmove --commit \
>   --v5 \
>   --devunversioned \
>   --multiarch \
>   --exclude-la \
>   --override s/libzim0-dev/libzim-dev/ \
>   --override s/liblzma5-dev/liblzma-dev/ \
>   --movedev "debian/tmp/usr/include/*" usr/include/ \
>   debian/tmp/usr/lib/i386-linux-gnu/libzim.so
> Library package automatic movement utility
>  --> liblzma-dev package exists.
> set -e
> install -d -m 755 debian/libzim-dev/usr/lib/i386-linux-gnu
> install -d -m 755 debian/libzim0v5/usr/lib/i386-linux-gnu
> mv debian/tmp/usr/lib/i386-linux-gnu/libzim.a 
> debian/libzim-dev/usr/lib/i386-linux-gnu
> mv debian/tmp/usr/lib/i386-linux-gnu/libzim.so 
> debian/libzim-dev/usr/lib/i386-linux-gnu
> mv /<>/debian/tmp/usr/lib/i386-linux-gnu/libzim.so.0 
> debian/libzim0v5/usr/lib/i386-linux-gnu
> mv /<>/debian/tmp/usr/lib/i386-linux-gnu/libzim.so.0.0.0 
> debian/libzim0v5/usr/lib/i386-linux-gnu
> PKGDEV=libzim-dev
> PKGSHL=libzim0v5
> install -d -m 755 debian/libzim-dev/usr/include/
> mv debian/tmp/usr/include/* debian/libzim-dev/usr/include/
> touch debian/stamp-local-shlibs-libzim
> dh_installdocs -plibzim0v5-dbg ./README ./NEWS ./AUTHORS
> dh_installexamples -plibzim0v5-dbg 
> dh_installman -plibzim0v5-dbg 
> dh_installinfo -plibzim0v5-dbg 
> dh_installmenu -plibzim0v5-dbg 
> dh_installcron -plibzim0v5-dbg 
> dh_systemd_enable -plibzim0v5-dbg 
> dh_installinit -plibzim0v5-dbg 
> dh_installdebconf -plibzim0v5-dbg 
> dh_installemacsen -plibzim0v5-dbg 
> dh_installcatalogs -plibzim0v5-dbg 
> dh_installpam -plibzim0v5-dbg 
> dh_installlogrotate -plibzim0v5-dbg 
> dh_installlogcheck -plibzim0v5-dbg 
> dh_installchangelogs 

Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Niels Thykier]

Michael Stapelberg:
> On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier  wrote:
> 
>> [...]
>>>
>>
>> They seem to be arch:all packages.  We cannot binNMU arch:all packages,
>> only architecture dependent ones.  :-/
>>
> 
> Okay. How do you suggest we rectify this issue instead, then?
> 

A (possibly "no change") sourceful upload to force a rebuild of the
arch:all package.

Thanks,
~Niels

Bug#860876: reapr: FTBFS: Error in system call: R CMD BATCH 00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout

[Chris Lamb]

Source: reapr
Version: 1.0.18+dfsg-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

reapr fails to build from source in unstable/amd64:

  […]

  foo   810152  A   M   +
  foo   811506  G   R   +
  foo   813494  A   M   +
  foo   814035  G   T   -
  foo   814476  A   W   +
  foo   819399  T   K   +
  foo   820171  T   W   +
  foo   820445  G   C   -
  foo   822178  C   G   -
  foo   822504  C   T   -
  foo   823378  C   M   +
  foo   823591  CG  -   -
  foo   824229  C   M   +
  foo   824579  C   T   -
  foo   824858  C   M   +
  foo   826101  T   K   +
  foo   827593  C   G   -
  foo   827794  T   Y   +
  foo   828228  A   M   +
  foo   828367  T   K   +
  foo   828788  C   M   +
  foo   829002  C   Y   +
  foo   830345  C   M   +
  foo   831018  C   A   -
  foo   831459  T   K   +
  foo   832413  A   T   -
  foo   832782  T   Y   +
  foo   832908  T   Y   +
  foo   833130  T   -   -
  foo   833142  G   S   +
  foo   833241  G   A   -
  foo   836727  A   T   -
  foo   836829  G   S   +
  foo   838452  T   G   -
  foo   838543  A   T   -
  foo   838605  C   M   +
  foo   838954  G   C   -
  foo   841829  G   K   +
  foo   842324  -   TC  +
  foo   842996  -   C   +
  foo   844390  C   A   -
  foo   844793  A   C   -
  foo   844925  C   A   -
  foo   845082  G   C   -
  foo   846202  G   R   +
  foo   846707  A   G   -
  foo   848713  G   A   -
  foo   849372  C   S   +
  foo   849742  G   A   -
  foo   850499  C   -   -
  foo   850927  GT  -   -
  foo   851084  -   G   +
  foo   852247  A   R   +
  foo   852972  C   A   -
  foo   854808  T   W   +
  foo   855956  G   K   +
  foo   856225  G   A   -
  foo   856582  T   K   +
  foo   857351  C   M   +
  foo   857504  AC  -   -
  foo   858324  A   T   -
  foo   858858  T   C   -
  foo   859488  T   Y   +
  foo   862441  T   Y   +
  foo   863827  C   Y   +
  foo   864165  C   A   -
  foo   865997  C   M   +
  foo   866370  G   S   +
  foo   867653  G   S   +
  foo   867722  C   Y   +
  foo   868696  C   M   +
  foo   869005  T   W   +
  foo   869791  T   Y   +
  foo   875339  C   Y   +
  foo   875347  C   M   +
  foo   875584  T   G   -
  foo   876780  C   T   -
  foo   878368  A   C   -
  foo   878916  -   CAG +
  foo   879005  A   R   +
  foo   880112  G   T   -
  foo   881021  -   T   -
  foo   881175  T   W   +
  foo   882168  -   GGG +
  foo   882223  -   G   -
  foo   883033  TG  -   -
  foo   883381  C   G   -
  foo   884378  C   -   -
  foo   885075  A   M   +
  foo   885190  A   W   +
  foo   885568  A   W   +
  foo   885827  T   Y   +
  foo   887610  TG  -   -
  foo   889139  G   R   +
  foo   890978  T   -   -
  foo   891500  C   Y   +
  foo   892257  G   C   -
  foo   892642  G   R   +
  foo   892644  T   W   +
  foo   892757  C   A   -
  foo   893222  T   -   -
  foo   893348  T   W   +
  foo   894161  -   C   -
  foo   894447  A   G   -
  foo   894614  A   W   +
  foo   897817  T   W   +
  foo   899408  C   S   +
  foo   902450  A   T   -
  foo   902970  AT  -   -
  foo   905836  G   K   +
  foo   906524  GA  -   -
  foo   907484  A   W   +
  foo   907537  C   M   +
  foo   908515  G   R   +
  foo   908642  C   T   -
  foo   911145  T   C   -
  foo   912220  T   Y   +
  foo   912682  C   Y   +
  foo   914260  C   S   +
  foo   914757  T   Y   +
  foo   916413  G   C   -
  foo   916783  T   G   -
  foo   917033  G   C   -
  foo   917218  A   -   -
  foo   918225  G   -   -
  foo   918459  A   -   -
  foo   918732  A   M   +
  foo   919640  TC  -   -
  foo   920824  T   W   +
  foo   920836  G   C   -
  foo   924560  G   R   +
  foo   924659  GA  -   -
  foo   925868  T   A   -
  foo   928254  T   G   -
  foo   928369  -   A   -
  foo   928641  -   AG  +
  foo   929857  C   M   +
  foo   930211  T   W   +
  foo   

Bug#736732: marked as done ([src:jsonbot] Sourceless file)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 07:59:09 +
with message-id 
and subject line Bug#860757: Removed package(s) from unstable
has caused the Debian Bug report #625524,
regarding [src:jsonbot] Sourceless file
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.)


-- 
625524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jsonbot
Version:0.84.4-1 
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-javascript-object
X-Debbugs-CC: ftpmas...@debian.org

I could not find the source of:
jsonbot 0.84.4-1 (source)

jsb/data/static/js/jquery-1.6.2.min.js
jsb/data/static/js/jquery-ui-1.8.16.custom.min.js


Bastien
--- End Message ---
--- Begin Message ---
Version: 0.84.4-2+rm

Dear submitter,

as the package jsonbot has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/860757

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#799756: marked as done (core-network: Privilege escalation via core-gui)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 07:59:56 +
with message-id 
and subject line Bug#860516: Removed package(s) from unstable
has caused the Debian Bug report #799756,
regarding core-network: Privilege escalation via core-gui
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.)


-- 
799756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: core-network
Version: 4.8-1
Severity: critical
Tags: security
Justification: root security hole

This bug was found and reported by asaladin on OFTC #debian. As he has
yet to report a bug, I'm reporting it for him.

Steps to reproduce:
1. Start core-gui as a normal user.
2. Create a host from the toolbar on the left.
3. Start the session using the green button on the toolbar.
4. Double-click on the host

Now you get a root shell. I've tested it by adding a line to /etc/passwd
and by creating a file in /root/.

The bug is most probably in core-network-daemon, as that is the only
part that runs as root. The bug should be exploitable without using the
GUI, but I do not know enough about core-network to try to reproduce it
using the command-line tools.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages core-network depends on:
ii  core-network-daemon  4.8-1
ii  core-network-gui 4.8-1

core-network recommends no packages.

Versions of packages core-network suggests:
ii  tcpdump  4.7.4-1

-- no debconf information
-- 
Marius Gavrilescu


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 4.8-3+rm

Dear submitter,

as the package core-network has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/860516

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#625524: marked as done (jsonbot: missing source for jquery.js)

[Debian Bug Tracking System]

Your message dated Fri, 21 Apr 2017 07:59:09 +
with message-id 
and subject line Bug#860757: Removed package(s) from unstable
has caused the Debian Bug report #625524,
regarding jsonbot: missing source for jquery.js
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.)


-- 
625524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jsonbot
Version: 0.6.1.2-1
Severity: serious
Justification: missing source

Hi,

no source for ./jsb/upload/assets/{jquery.js,jquery-1.2.6.min.js} is
included in the package.

Note that jquery is already provided by libjs-jquery.

Regards,
Ansgar


--- End Message ---
--- Begin Message ---
Version: 0.84.4-2+rm

Dear submitter,

as the package jsonbot has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/860757

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Michael Stapelberg]

On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier  wrote:

> Michael Stapelberg:
> > On Wed, Apr 19, 2017 at 12:05 PM, Michael Hudson-Doyle <
> > michael.hud...@canonical.com> wrote:
> >
> >> [...]
> >>> 0.7.0+ds-3), golang-protobuf-extensions (= 0+git20150513.fc2b8d3-4)
> >>> --
> >>> Package: golang-github-gosexy-gettext-dev
> >>> Built-Using: golang (= 2:1.6.1-2)
> >>> --
> >>> Package: golang-github-hashicorp-go-msgpack-dev
> >>> Built-Using: golang (= 2:1.6.1-2)
> >>> --
> >>> Package: golang-github-stretchr-objx-dev
> >>> Built-Using: golang (= 2:1.6.1-2)
> >>> --
> >>> Package: golang-github-kr-pty-dev
> >>> Built-Using: golang (= 2:1.6.1-2)
> >>>
> >>> This case could be ignored by the rebuild scripts, or binnmus could be
> >>> trigerred to get rid of the other versions. I'm not sure it makes sense
> >>> to ship
> >>> that many copies of golang in stretch.
> >>>
> >>> I think I read something about an organized plan to get rid of such
> extra
> >>> packages using binnmus, but maybe I was dreaming. Ccing debian-release@
> .
> >>>
> >>
> >> [...]
> >>
> >
> > Updating or dropping the field seems fine with me. Could you do these 4
> > binNMUs so that we can close out this bug please? :)
> >
>
> They seem to be arch:all packages.  We cannot binNMU arch:all packages,
> only architecture dependent ones.  :-/
>

Okay. How do you suggest we rectify this issue instead, then?

-- 
Best regards,
Michael

Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Niels Thykier]

Michael Stapelberg:
> On Wed, Apr 19, 2017 at 12:05 PM, Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
> 
>> [...]
>>> 0.7.0+ds-3), golang-protobuf-extensions (= 0+git20150513.fc2b8d3-4)
>>> --
>>> Package: golang-github-gosexy-gettext-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>> --
>>> Package: golang-github-hashicorp-go-msgpack-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>> --
>>> Package: golang-github-stretchr-objx-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>> --
>>> Package: golang-github-kr-pty-dev
>>> Built-Using: golang (= 2:1.6.1-2)
>>>
>>> This case could be ignored by the rebuild scripts, or binnmus could be
>>> trigerred to get rid of the other versions. I'm not sure it makes sense
>>> to ship
>>> that many copies of golang in stretch.
>>>
>>> I think I read something about an organized plan to get rid of such extra
>>> packages using binnmus, but maybe I was dreaming. Ccing debian-release@.
>>>
>>
>> [...]
>>
> 
> Updating or dropping the field seems fine with me. Could you do these 4
> binNMUs so that we can close out this bug please? :)
> 

They seem to be arch:all packages.  We cannot binNMU arch:all packages,
only architecture dependent ones.  :-/

Thanks,
~Niels

Bug#857238: (no subject)

[Tobias Bengfort]

In case anyone is interested:

When libwww-dict-leo-org-perl stopped working I created my own python
script as a drop-in:

  https://gist.github.com/xi/8a2774c2e82682fa34a4cd1e621fcf5a

tobias

Bug#860634: fix for node-grunt-contrib-copy RC bug

[Paolo Greppi]

Hi team there is a RC bug on node-grunt-contrib-copy, I have provided a fix and 
uploaded that to alioth.

I have tested with pkg-ruby-extras/build and tested the reverse deps (node-rx) 
too.

These two packages have an impressive popcon count of ... 7+5 ! But anyway 
please someone sponsor the upload

Cheers,

Paolo 

Bug#860634: reproducible here

[Paolo Greppi]

This is easy to reproduce on stretch from the root of a source package against 
the currently installed package.

Just make sure the tmp directory created during the build process is not 
present:
  make -f debian/rules clean

or just:
  rm -rf tmp

then run the tests in the local environment (that's the easiest path as per 
https://ci.debian.net/doc/file.MAINTAINERS.html):
  adt-run --output-dir /tmp/output-dir ./ --- null

The reason for the failure is that when tests are run during the build process, 
they are run via the debian/rules override_dh_clean which does:
  rm -rf tmp
  mkdir -p tmp
  grunt copy
  nodeunit

whereas when they are run by adt-run and hence by debci the tests run as 
declared in debian/tests/control per DEP-8 spec, i.e. by running nodeunit 
straight.

Interestingly this package has no Testsuite: autopkgtest or XS-Testsuite: 
autopkgtest entries in the source stanza in debian/control, but debci runs the 
tests anyway.

A fix is to make both tests run via the supplied ./debian/tests/run_tests 
script.

Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Michael Stapelberg]

On Wed, Apr 19, 2017 at 12:05 PM, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:

> On 19 April 2017 at 20:55, Lucas Nussbaum  wrote:
>
>> On 19/04/17 at 09:05 +0200, Michael Stapelberg wrote:
>> > This is the third time an FTBFS report against this package (which was
>> > removed from Debian) was submitted.
>> >
>> > The other two times were
>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855926 and
>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848806, both were
>> closed
>> > asking for an explanation as to why the issue was filed in the first
>> place.
>>
>> ... And none sending the question to the bug submitter.
>
>
> Defeated by the Debian BTS, I didn't realize that you had to email the
> submitter separately when closing a bug...
>
>
>>
>> > lucas, is this a bug in your rebuild infrastructure, or did something go
>> > wrong with the removal?
>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839364 (same issue
>> as the
>> > one you’re reporting) was closed by ftpmaster due to package removal.
>>
>> In my local Sources file, I have:
>
>
> [...]
>
>
>> 'Extra-Source-Only' means that there are still binary packages in the
>> archive
>> that were built using that version of the golang package.
>>
>> In fact, for that version:
>> $ grep -e Package -e Using 127.0.0.1\:_debian_dists_t
>> esting_main_binary-amd64_Packages |grep -B1 'golang (= 2:1.6.1-2)'
>> Package: golang-github-armon-go-metrics-dev
>> Built-Using: golang (= 2:1.6.1-2), golang-github-datadog-datadog-go (=
>> 0.0~git20150930.0.b050cd8-1), golang-github-prometheus-common (=
>> 0+git20160321.4045694-1), golang-goprotobuf (= 0.0~git20160330-1),
>> golang-procfs (= 0+git20150616.c91d8ee-1), golang-prometheus-client (=
>> 0.7.0+ds-3), golang-protobuf-extensions (= 0+git20150513.fc2b8d3-4)
>> --
>> Package: golang-github-gosexy-gettext-dev
>> Built-Using: golang (= 2:1.6.1-2)
>> --
>> Package: golang-github-hashicorp-go-msgpack-dev
>> Built-Using: golang (= 2:1.6.1-2)
>> --
>> Package: golang-github-stretchr-objx-dev
>> Built-Using: golang (= 2:1.6.1-2)
>> --
>> Package: golang-github-kr-pty-dev
>> Built-Using: golang (= 2:1.6.1-2)
>>
>> This case could be ignored by the rebuild scripts, or binnmus could be
>> trigerred to get rid of the other versions. I'm not sure it makes sense
>> to ship
>> that many copies of golang in stretch.
>>
>> I think I read something about an organized plan to get rid of such extra
>> packages using binnmus, but maybe I was dreaming. Ccing debian-release@.
>>
>
> I think I heard something about that. FWIW, though, these Built-Using
> fields are bogus, golang -dev packages just ship source and so do not
> actually contain anything built by the mentioned version of the compiler. I
> think I've managed to hammer this into everyone's heads now but I guess
> there are plenty of packages in the archive that haven't had an upload
> since then (so I guess the binNMUs could just drop the field?).
>

Updating or dropping the field seems fine with me. Could you do these 4
binNMUs so that we can close out this bug please? :)

-- 
Best regards,
Michael

Bug#860662: mlucas: FTBFS on i386: dh_auto_test: make -j64 check VERBOSE=1 returned exit code 2

[Alex Vong]

Thanks for the bug report.

Upon inspection, it seems the problem is caused by some serious memory
leaks:
>> executipthread_create:: Cannot allocate memory
>> FAIL self_test.test (exit status: 139)

Building with '-fsanitize=leak' seems to confirm it:
> make[1]: Leaving directory '/home/alexvong1995/c/mlucas'
>
> Mlucas 14.2
>
> http://hogranch.com/mayer/README.html
> 
> INFO: testing qfloat routines...
> CPU Family = x86_64, OS = Linux, 64-bit Version, compiled with Gnu C [or 
> other compatible], Version 6.3.0.
> INFO: Build uses SSE2 instruction set.
> INFO: Using inline-macro form of MUL_LOHI64.
> INFO: MLUCAS_PATH is set to ""
> INFO: using 64-bit-significand form of floating-double rounding constant for 
> scalar-mode DNINT emulation.
> INFO: testing IMUL routines...
> INFO: System has 2 available processor cores.
> INFO: testing FFT radix tables...
> 
>Mlucas selftest running.
> 
> 
>  You will need to manually verify that the Res64s output
>  for this user-set p match for all FFT radix combinations!!
> 
> 
> //
> 
> INFO: Unable to find/open mlucas.cfg file in r+ mode ... creating from 
> scratch.
>  looking for number of threads to use in nthreads.ini file...
> Using NTHREADS = #CPUs = 2.
> M2047: using FFT length 1024K = 1048576 8-byte floats.
>  this gives an average   19.073531150817871 bits per digit
> Using complex FFT radices  10241632
> executing worker thread id 0, syscall_id = 18883
> syscall_id = 18883, setaffinity[0] = 0, ISSET[0] = 1
> executing worker thread id 1, syscall_id = 18884
> syscall_id = 18884, setaffinity[1] = 0, ISSET[1] = 1
> Mers_mod_square: Init threadpool of 2 threads
> radix16_dif_dit_pass pfetch_dist = 8
> executing worker thread id 0, syscall_id = 18885
> syscall_id = 18885, setaffinity[0] = 0, ISSET[0] = 1
> executing worker thread id 1, syscall_id = 18886
> Using 2 threads in carry step
> syscall_id = 18886, setaffinity[1] = 0, ISSET[1] = 1
> 100 iterations of M2047 with FFT length 1048576 = 1024 K
> Res64: DD61B3E031F1E0BA. AvgMaxErr = 0.265625000. MaxErr = 0.265625000. 
> Program: E14.2
> Res mod 2^36 =837935290
> Res mod 2^35 - 1 =   6238131189
> Res mod 2^36 - 1 =  41735145962
> Clocks = 00:00:03.193
> 
> NTHREADS = 2
> M2047: using FFT length 1024K = 1048576 8-byte floats.
>  this gives an average   19.073531150817871 bits per digit
> Using complex FFT radices  10243216
> executing worker thread id 0, syscall_id = 18887
> syscall_id = 18887, setaffinity[0] = 0, ISSET[0] = 1
> executing worker thread id 1, syscall_id = 1
> Mers_mod_square: Init threadpool of 2 threads
> syscall_id = 1, setaffinity[1] = 0, ISSET[1] = 1
> ERROR: at line 1197 of file ./src/radix1024_ditN_cy_dif1.c
> Assertion failed: thread-local memcheck fail!
> 
> =
> ==18881==ERROR: LeakSanitizer: detected memory leaks
> 
> Direct leak of 4100 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 
> (/gnu/store/lambsaqkzrvpa1j5h2rr615sm4y1z0xc-gcc-6.3.0-lib/lib/liblsan.so.0+0xd26e)
> #1 0x562c4b in mers_mod_square src/mers_mod_square.c:1143
> 
> Direct leak of 4096 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 
> (/gnu/store/lambsaqkzrvpa1j5h2rr615sm4y1z0xc-gcc-6.3.0-lib/lib/liblsan.so.0+0xd26e)
> #1 0x562f95 in mers_mod_square src/mers_mod_square.c:1268
> 
> Direct leak of 4096 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 
> (/gnu/store/lambsaqkzrvpa1j5h2rr615sm4y1z0xc-gcc-6.3.0-lib/lib/liblsan.so.0+0xd26e)
> #1 0x562f74 in mers_mod_square src/mers_mod_square.c:1267
> 
> Direct leak of 4096 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 
> (/gnu/store/lambsaqkzrvpa1j5h2rr615sm4y1z0xc-gcc-6.3.0-lib/lib/liblsan.so.0+0xd26e)
> #1 0x562f32 in mers_mod_square src/mers_mod_square.c:1265
> 
> Direct leak of 4096 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 
> (/gnu/store/lambsaqkzrvpa1j5h2rr615sm4y1z0xc-gcc-6.3.0-lib/lib/liblsan.so.0+0xd26e)
> #1 0x562f11 in mers_mod_square src/mers_mod_square.c:1264
> 
> Direct leak of 4096 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 
> (/gnu/store/lambsaqkzrvpa1j5h2rr615sm4y1z0xc-gcc-6.3.0-lib/lib/liblsan.so.0+0xd26e)
> #1 0x562ef0 in mers_mod_square src/mers_mod_square.c:1263
> 
> Direct leak of 4096 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 
> (/gnu/store/lambsaqkzrvpa1j5h2rr615sm4y1z0xc-gcc-6.3.0-lib/lib/liblsan.so.0+0xd26e)
> #1 0x562fb6 in mers_mod_square src/mers_mod_square.c:1269
> 
> Direct leak of 4096 byte(s) in 1 object(s) allocated from:
> #0 0x7f839d4af26e in __interceptor_calloc 

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote:
> Hi,
> 
> I lost internet connectivity where I am right now, so probably unable to get
> this done until Monday. Could maybe use the previous debdiff for Jessie if
> you're ok with closing the bug manually.
> Also, I think we still don't have any active members in the maintainer team
> with upload access for 5.5

Okay, I will look if I can take care of the upload for
jessie-security.

Regards,
Salvatore