Bug#861282: packer: FTBFS

[JD Friedrikson]

Thanks for the patch! I'm having a bit of trouble with the build:


"""
?   github.com/mitchellh/packer/version[no test files]
dh_auto_test: go test -v -p 1 -timeout 30m -run 
^Test([^M]|M[^u]|Mu[^x]|Mux[^B]|MuxB[^r]|MuxBr[^o]|MuxBro[^k]|MuxBrok[^e]|MuxBroke[^r])
 github.com/mitchellh/packer github.com/mitchellh/packer/builder/amazon/chroot 
github.com/mitchellh/packer/builder/amazon/common 
github.com/mitchellh/packer/builder/amazon/ebs 
github.com/mitchellh/packer/builder/amazon/instance 
github.com/mitchellh/packer/builder/azure/arm 
github.com/mitchellh/packer/builder/azure/common 
github.com/mitchellh/packer/builder/azure/common/constants 
github.com/mitchellh/packer/builder/azure/common/lin 
github.com/mitchellh/packer/builder/azure/common/logutil 
github.com/mitchellh/packer/builder/azure/pkcs12 
github.com/mitchellh/packer/builder/azure/pkcs12/rc2 
github.com/mitchellh/packer/builder/digitalocean 
github.com/mitchellh/packer/builder/docker 
github.com/mitchellh/packer/builder/file 
github.com/mitchellh/packer/builder/googlecompute 
github.com/mitchellh/packer/builder/null 
github.com/mitchellh/packer/builder/openstack
  github.com/mitchellh/packer/builder/parallels/common 
github.com/mitchellh/packer/builder/parallels/iso 
github.com/mitchellh/packer/builder/parallels/pvm 
github.com/mitchellh/packer/builder/qemu 
github.com/mitchellh/packer/builder/virtualbox/common 
github.com/mitchellh/packer/builder/virtualbox/iso 
github.com/mitchellh/packer/builder/virtualbox/ovf 
github.com/mitchellh/packer/builder/vmware/common 
github.com/mitchellh/packer/builder/vmware/iso 
github.com/mitchellh/packer/builder/vmware/vmx 
github.com/mitchellh/packer/command github.com/mitchellh/packer/common 
github.com/mitchellh/packer/common/json github.com/mitchellh/packer/common/ssh 
github.com/mitchellh/packer/common/uuid 
github.com/mitchellh/packer/communicator/none 
github.com/mitchellh/packer/communicator/ssh 
github.com/mitchellh/packer/communicator/winrm github.com/mitchellh/packer/fix 
github.com/mitchellh/packer/helper/builder/testing 
github.com/mitchellh/packer/helper/communicator 
github.com/mitchellh/packer/helper/config g
 ithub.com/mitchellh/packer/helper/flag-kv 
github.com/mitchellh/packer/helper/flag-slice 
github.com/mitchellh/packer/packer github.com/mitchellh/packer/packer/plugin 
github.com/mitchellh/packer/packer/rpc 
github.com/mitchellh/packer/plugin/example 
github.com/mitchellh/packer/post-processor/amazon-import 
github.com/mitchellh/packer/post-processor/artifice 
github.com/mitchellh/packer/post-processor/atlas 
github.com/mitchellh/packer/post-processor/compress 
github.com/mitchellh/packer/post-processor/docker-import 
github.com/mitchellh/packer/post-processor/docker-push 
github.com/mitchellh/packer/post-processor/docker-save 
github.com/mitchellh/packer/post-processor/docker-tag 
github.com/mitchellh/packer/post-processor/shell-local 
github.com/mitchellh/packer/post-processor/vagrant 
github.com/mitchellh/packer/post-processor/vagrant-cloud 
github.com/mitchellh/packer/post-processor/vsphere 
github.com/mitchellh/packer/provisioner 
github.com/mitchellh/packer/provisioner/ansible github.com/mitche
 llh/packer/provisioner/ansible-local 
github.com/mitchellh/packer/provisioner/chef-client 
github.com/mitchellh/packer/provisioner/chef-solo 
github.com/mitchellh/packer/provisioner/file 
github.com/mitchellh/packer/provisioner/powershell 
github.com/mitchellh/packer/provisioner/puppet-masterless 
github.com/mitchellh/packer/provisioner/puppet-server 
github.com/mitchellh/packer/provisioner/salt-masterless 
github.com/mitchellh/packer/provisioner/shell 
github.com/mitchellh/packer/provisioner/shell-local 
github.com/mitchellh/packer/provisioner/windows-restart 
github.com/mitchellh/packer/provisioner/windows-shell 
github.com/mitchellh/packer/scripts github.com/mitchellh/packer/template 
github.com/mitchellh/packer/template/interpolate 
github.com/mitchellh/packer/version returned exit code 1
debian/rules:17: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/tmp/packer'
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1116:
dpkg-buildpackage -rfakeroot -us -uc -i -b failed
"""


Am I doing something wrong here?

JD

> 
> Thanks for your info!
> I pushed a commit to new branch fix_861282, that applied:
> ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b
> a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd
> 
> (https://anonscm.debian.org/cgit/pkg-go/packages/packer.git/log/?h=fix_861282)
> 
> Please help to test whether it fixes your problem.
> 
> Cheers,
> --
> Roger Shimizu, GMT +9 Tokyo
> PGP/GPG: 4096R/6C6ACD6417B3ACB1
> 

Processed: Re: Bug#863223: maven-plugin-tools: FTBFS: maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported exception java.io.IOException; must be caught or declared to be thrown

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 plexus-utils2 3.0.24-1
Bug #863223 [src:maven-plugin-tools] maven-plugin-tools: FTBFS: 
maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported 
exception java.io.IOException; must be caught or declared to be thrown
Bug reassigned from package 'src:maven-plugin-tools' to 'plexus-utils2'.
No longer marked as found in versions maven-plugin-tools/3.3-5.
Ignoring request to alter fixed versions of bug #863223 to the same values 
previously set
Bug #863223 [plexus-utils2] maven-plugin-tools: FTBFS: 
maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported 
exception java.io.IOException; must be caught or declared to be thrown
There is no source info for the package 'plexus-utils2' at version '3.0.24-1' 
with architecture ''
Unable to make a source version for version '3.0.24-1'
Marked as found in versions 3.0.24-1.
> affects -1 maven-plugin-tools
Bug #863223 [plexus-utils2] maven-plugin-tools: FTBFS: 
maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported 
exception java.io.IOException; must be caught or declared to be thrown
Added indication that 863223 affects maven-plugin-tools

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

Bug#863223: maven-plugin-tools: FTBFS: maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported exception java.io.IOException; must be caught or declared to be thrown

[Emmanuel Bourg]

Control: reassign -1 plexus-utils2 3.0.24-1
Control: affects -1 maven-plugin-tools

Thank you for the report Chris. This issue was introduced with the
upload of plexus-utils2/3.0.24-1 in unstable (should have been in
experimental, sorry). The PropertyUtils.loadProperties() method now
throws an IOException that must be caught. It may affect a few other
maven related libraries. I'll fix that in plexus-utils2 by replacing the
IOException with an unchecked runtime exception.

Emmanuel Bourg

Bug#861952: marked as done (libcgi-validop-perl: FTBFS on May 1st (?))

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 00:44:30 +
with message-id 
and subject line Bug#863073: Removed package(s) from unstable
has caused the Debian Bug report #861952,
regarding libcgi-validop-perl: FTBFS on May 1st (?)
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.)


-- 
861952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcgi-validop-perl
Version: 0.56-2
Severity: important

Hello Gregor et al.

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]

#   Failed test 't/16check_date.t : 246'
#   at lib/CGI/ValidOp/Test.pm line 108.
#  got: undef
# expected: '2017-04-31'
# Looks like you failed 1 test of 607.
t/16check_date.t .. 

[...]

Test Summary Report
---
t/16check_date.t(Wstat: 256 Tests: 607 Failed: 1)
  Failed test:  506
  Non-zero exit status: 1
Files=24, Tests=3133,  3 wallclock secs ( 0.39 usr  0.13 sys +  2.26 cusr  0.36 
csys =  3.14 CPU)
Result: FAIL
Failed 1/24 test programs. 1/3133 subtests failed.
Makefile:844: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made on 2017-05-01 and the error says

expected: '2017-04-31'

which does not exist, as April has only 30 days.

This suggests a date-related bug.

I have not tried to reproduce it by building it again on May 1st.
Maybe this could be done by using libfaketime, but I think a better
strategy would be to look at the code and the error message and try to
guess how it may happen.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.56-2+rm

Dear submitter,

as the package libcgi-validop-perl 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/863073

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 811325 src:sigx
Bug #811325 [sigx] FTBFS: error: expected identifier before 'static_assert'
Bug reassigned from package 'sigx' to 'src:sigx'.
No longer marked as found in versions 2.0.2-5.
Ignoring request to alter fixed versions of bug #811325 to the same values 
previously set
> forcemerge 805208 811325
Bug #805208 [src:sigx] sigx: FTBFS: ./sigx/tunnel_context.h:145:18: error: 
using invalid field 'sigx::tunnel_context<(sigx::sync_type)1u, T_return, 
T_unary_functor>::m_bound_result'
Bug #811325 [src:sigx] FTBFS: error: expected identifier before 'static_assert'
Marked as found in versions sigx/2.0.2-5.
Merged 805208 811325
> thanks
Stopping processing here.

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

Bug#740893: Patch for python-coverage bug #740893

[Ben Finney]

On 23-May-2017, Eevel Weezel wrote:

> I'm attaching a patch.  This will remove the bundled version of the js
> libraries, allowing python-coverage to use the system libraries.

Thank you for the patch. Is that needed, though? The package already
omits those files from the HTML report, via an existing patch
.

Also, I think this bug report is asking that the system libraries
should be different.

> Heather

(Could you change your “From” field on your outgoing messages, so they
have your name? Thanks!)

-- 
 \   “Philosophy is questions that may never be answered. Religion |
  `\  is answers that may never be questioned.” —anonymous |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#859703: marked as done (tendermint-go-merkle: FTBFS: go_level_db.go:7:2: cannot find package "github.com/syndtr/goleveldb/leveldb")

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 01:49:45 +0300
with message-id <20170523224945.gd5oqs5velkhablw@localhost>
and subject line This bug was fixed in 0.0~git20170302.0.3c5717c-3
has caused the Debian Bug report #859703,
regarding tendermint-go-merkle: FTBFS: go_level_db.go:7:2: cannot find package 
"github.com/syndtr/goleveldb/leveldb"
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.)


-- 
859703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tendermint-go-merkle
Version: 0.1~20170131~0git7a86b44-1
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,

tendermint-go-merkle fails to build from source in unstable/amd64:

  […]

 debian/rules override_dh_auto_test
  
  
**
  ** Starting build 
  **
  
**
  
   Package:  tendermint-go-merkle
   Version:  0.1~20170131~0git7a86b44-1
   Build architecture:   amd64
   Date: Thu, 06 Apr 2017 09:28:19 +0200
   Hostname: bcc95f78fe80
   Uname:Linux bcc95f78fe80 4.9.0-2-amd64 #1 SMP Debian 
4.9.13-1 (2017-02-27) x86_64 GNU/Linux
   /etc/timezone:Europe/Amsterdam
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'tendermint-go-merkle-build-deps' in 
'../tendermint-go-merkle-build-deps_0.1~20170131~0git7a86b44-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package tendermint-go-merkle-build-deps.
  (Reading database ... 23700 files and directories currently installed.)
  Preparing to unpack 
tendermint-go-merkle-build-deps_0.1~20170131~0git7a86b44-1_all.deb ...
  Unpacking tendermint-go-merkle-build-deps (0.1~20170131~0git7a86b44-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-golang golang-1.7-go golang-1.7-src golang-any
golang-github-davecgh-go-spew-dev golang-github-go-stack-stack-dev
golang-github-golang-snappy-dev golang-github-mattn-go-colorable-dev
golang-github-mattn-go-isatty-dev golang-github-pmezard-go-difflib-dev
golang-github-stretchr-objx-dev golang-github-stretchr-testify-dev
golang-github-syndtr-goleveldb-dev golang-github-tendermint-go-common-dev
golang-github-tendermint-go-db-dev golang-github-tendermint-go-logger-dev
golang-github-tendermint-go-wire-dev golang-github-tendermint-log15-dev
golang-go golang-golang-x-crypto-dev golang-golang-x-net-dev
golang-golang-x-text-dev golang-golang-x-tools-dev golang-goleveldb-dev
golang-src golang-x-text-dev
  Suggested packages:
bzr ca-certificates mercurial subversion
  Recommended packages:
pkg-config
  The following NEW packages will be installed:
dh-golang golang-1.7-go golang-1.7-src golang-any
golang-github-davecgh-go-spew-dev golang-github-go-stack-stack-dev
golang-github-golang-snappy-dev golang-github-mattn-go-colorable-dev
golang-github-mattn-go-isatty-dev golang-github-pmezard-go-difflib-dev
golang-github-stretchr-objx-dev golang-github-stretchr-testify-dev
golang-github-syndtr-goleveldb-dev golang-github-tendermint-go-common-dev
golang-github-tendermint-go-db-dev golang-github-tendermint-go-logger-dev
golang-github-tendermint-go-wire-dev golang-github-tendermint-log15-dev
golang-go golang-golang-x-crypto-dev golang-golang-x-net-dev
golang-golang-x-text-dev golang-golang-x-tools-dev golang-goleveldb-dev
golang-src golang-x-text-dev
  0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to 

Processed: This was a bug in golang-goleveldb

[Debian Bug Tracking System]

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

> reassign 859703 golang-goleveldb 0.0~git20170302.0.3c5717c-2
Bug #859703 [src:tendermint-go-merkle] tendermint-go-merkle: FTBFS: 
go_level_db.go:7:2: cannot find package "github.com/syndtr/goleveldb/leveldb"
Bug reassigned from package 'src:tendermint-go-merkle' to 'golang-goleveldb'.
No longer marked as found in versions 
tendermint-go-merkle/0.1~20170131~0git7a86b44-1.
Ignoring request to alter fixed versions of bug #859703 to the same values 
previously set
Bug #859703 [golang-goleveldb] tendermint-go-merkle: FTBFS: go_level_db.go:7:2: 
cannot find package "github.com/syndtr/goleveldb/leveldb"
There is no source info for the package 'golang-goleveldb' at version 
'0.0~git20170302.0.3c5717c-2' with architecture ''
Unable to make a source version for version '0.0~git20170302.0.3c5717c-2'
Marked as found in versions 0.0~git20170302.0.3c5717c-2.
> affects 859703 src:tendermint-go-merkle
Bug #859703 [golang-goleveldb] tendermint-go-merkle: FTBFS: go_level_db.go:7:2: 
cannot find package "github.com/syndtr/goleveldb/leveldb"
Added indication that 859703 affects src:tendermint-go-merkle
> thanks
Stopping processing here.

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

Bug#740893: Patch for python-coverage bug #740893

[Eevel Weezel]

Hello Maintainer,

I'm attaching a patch.  This will remove the bundled version of the js
libraries, allowing python-coverage to use the system libraries.

Best,
Heather


python-coverage_diff
Description: Binary data

Bug#855058: marked as done (gtk-vnc FTBFS on amd64/mipsel/mips64el/s390x: vncconnectiontest.c:64:test_send_u16: assertion failed)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 01:19:24 +0300
with message-id <20170523221924.5eidxdc3or3shdsy@localhost>
and subject line Looks as if this was a transient failure
has caused the Debian Bug report #855058,
regarding gtk-vnc FTBFS on amd64/mipsel/mips64el/s390x: 
vncconnectiontest.c:64:test_send_u16: assertion failed
to be marked as done.

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

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


-- 
855058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk-vnc
Version: 0.6.0-3
Severity: serious

https://buildd.debian.org/status/package.php?p=gtk-vnc

...
.. contents:: :depth: 2

FAIL: vncconnectiontest
===

/conn/validation/rre: OK
/conn/validation/copyrect: OK
/conn/validation/hextile: OK
/conn/validation/unexpectedcmap: **
ERROR:../../../src/vncconnectiontest.c:64:test_send_u16: assertion failed: 
(g_output_stream_write_all(os, , 2, NULL, NULL, NULL))
FAIL vncconnectiontest (exit status: 134)


Testsuite summary for gtk-vnc 0.6.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See src/test-suite.log
Please report to https://bugzilla.gnome.org/enter_bug.cgi?product=gtk-vnc

Makefile:1754: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
After retries the builds succeeded a few days later on the buildds.

The reproducible builds [1] do unfortunately not contain any builds from 
the relevant timespan, but based on the fact that the build never failed 
there before or after I'll assume this was a transient failure that is
long gone.

cu
Adrian

[1] https://tests.reproducible-builds.org/debian/history/gtk-vnc.html

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#863223: maven-plugin-tools: FTBFS: maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported exception java.io.IOException; must be caught or declared to be thrown

[Chris Lamb]

Source: maven-plugin-tools
Version: 3.3-5
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,

maven-plugin-tools fails to build from source in unstable/amd64:

  […]

  Setting up default-jre-headless (2:1.8-58) ...
  Setting up default-jdk-headless (2:1.8-58) ...
  Setting up openjdk-8-jdk:amd64 (8u131-b11-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer 
to provide /usr/bin/appletviewer (appletviewer) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to 
provide /usr/bin/jconsole (jconsole) in auto mode
  Setting up default-jre (2:1.8-58) ...
  Setting up ant-optional (1.9.9-1) ...
  Setting up libxbean-java (4.5-4) ...
  Setting up default-jdk (2:1.8-58) ...
  Setting up libplexus-containers-java (1.0~beta3.0.7-8) ...
  Setting up libplexus-build-api-java (0.0.7-1) ...
  Setting up libplexus-io-java (1.0~alpha5-2) ...
  Setting up libplexus-interactivity-api-java (1.0-alpha-6-7) ...
  Setting up libplexus-container-default1.5-java (1.6-3) ...
  Setting up libwagon-java (1.0.0-9) ...
  Setting up libplexus-i18n-java (1.0-beta-10-3) ...
  Setting up libplexus-cli-java (1.2-5) ...
  Setting up libwagon2-java (2.10-6) ...
  Setting up libplexus-velocity-java (1.2-1) ...
  Setting up libplexus-archiver-java (2.2-1) ...
  Setting up libdoxia-java (1.1.4-6) ...
  Setting up libmaven2-core-java (2.2.1-26) ...
  Setting up libeclipse-aether-java (1.0.2-1) ...
  Setting up libmodello-java (1.8.3-3) ...
  Setting up libmaven-common-artifact-filters-java (1.4-1) ...
  Setting up libmodello-maven-plugin-java (1.8.3-1) ...
  Setting up libdoxia-sitetools-java (1.1.4-1.1) ...
  Setting up libmaven3-core-java (3.3.9-4) ...
  Setting up libmaven-filtering-java (1.1-1) ...
  Setting up libmaven-clean-plugin-java (2.5-1) ...
  Setting up maven (3.3.9-4) ...
  update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn 
(mvn) in auto mode
  Setting up libplexus-compiler-java (2.4-3) ...
  Setting up libplexus-component-metadata-java (1.6-3) ...
  Setting up libmaven-resources-plugin-java (2.6-1) ...
  Setting up libmaven-archiver-java (2.6-3) ...
  Setting up libmaven-shared-incremental-java (1.1-1) ...
  Setting up libmaven-doxia-tools-java (1.2.1-2) ...
  Setting up libmaven-compiler-plugin-java (3.2-5) ...
  Setting up libmaven-site-plugin-java (2.1-4) ...
  Setting up libmaven-jar-plugin-java (2.4-1) ...
  Processing triggers for sgml-base (1.29) ...
  Setting up libmaven-reporting-impl-java (2.3-1) ...
  Setting up libmaven-plugin-tools-java (3.3-5) ...
  Setting up libsurefire-java (2.17-3) ...
  Setting up maven-debian-helper (2.1.3) ...
  Setting up maven-plugin-tools-build-deps (3.3-5) ...
  Processing triggers for libc-bin (2.24-10) ...
  Processing triggers for systemd (232-23) ...
  Processing triggers for ca-certificates (20161130) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  done.
  done.
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=63b9f2da964e
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  DEB_BUILD_PROFILES=
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20170523225408.mDMW4OzuJ6.db.maven-plugin-tools/maven-plugin-tools-3.3
  OLDPWD=/home/lamby/temp/cdt.20170523225408.mDMW4OzuJ6.db.maven-plugin-tools
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building maven-plugin-tools 3.3-5 on amd64 
  **
  
**
  
   dpkg-buildpackage -rfakeroot -us -uc -b
  dpkg-buildpackage: info: source package maven-plugin-tools
  dpkg-buildpackage: info: source version 3.3-5
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Emmanuel Bourg 
   dpkg-source --before-build maven-plugin-tools-3.3
  dpkg-buildpackage: info: host architecture 

Bug#849555: marked as done (python-restless: FTBFS: ImportError: No module named itty)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 00:42:34 +0300
with message-id <20170523214234.xzl5ru5kf5xmgn2q@localhost>
and subject line python-restless seems to build now
has caused the Debian Bug report #849555,
regarding python-restless: FTBFS: ImportError: No module named itty
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.)


-- 
849555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-restless
Version: 2.0.3-1
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,

python-restless fails to build from source in unstable/amd64:

  […]

  writing output... [100%] tutorial
  
  generating indices... genindex py-modindex
  writing additional pages... search
  copying static files... WARNING: html_static_path entry 
u'«BUILDDIR»/docs/_static' does not exist
  done
  copying extra files... done
  dumping search index in English (code: en) ... done
  dumping object inventory... done
  build succeeded, 3 warnings.
  make[1]: Leaving directory '«BUILDDIR»'
 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: cd «BUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
unittest discover -v 
  test_as_detail (tests.test_it.IttyResourceTestCase) ... skipped 'itty is not 
available'
  test_as_list (tests.test_it.IttyResourceTestCase) ... skipped 'itty is not 
available'
  test_build_response (tests.test_it.IttyResourceTestCase) ... skipped 'itty is 
not available'
  test_is_debug (tests.test_it.IttyResourceTestCase) ... skipped 'itty is not 
available'
  test_setup_urls (tests.test_it.IttyResourceTestCase) ... skipped 'itty is not 
available'
  test_basic_resource_detail (tests.test_tnd.FuncTrimTestCase) ... ok
  test_basic_resource_list (tests.test_tnd.FuncTrimTestCase) ... ok
  test_empty_resource (tests.test_tnd.FuncTrimTestCase) ... ok
  test_inheritance_resource_detail (tests.test_tnd.FuncTrimTestCase) ... ok
  test_body (tests.test_tnd.InternalTestCase) ... ok
  test_class (tests.test_tnd.InternalTestCase)
  test the generated tornado.web.RequestHandler ... ok
  test_is_debug (tests.test_tnd.InternalTestCase) ... ok
  test_method (tests.test_tnd.InternalTestCase) ... ok
  test_var (tests.test_tnd.InternalTestCase)
  make sure variable from tornado is correctly passed. ... ok
  test_as_detail (tests.test_tnd.TndAsyncResourceTestCase) ... ok
  test_as_list (tests.test_tnd.TndAsyncResourceTestCase) ... ok
  test_as_detail (tests.test_tnd.TndResourceTestCase) ... ok
  test_as_list (tests.test_tnd.TndResourceTestCase) ... ok
  test_not_authenticated (tests.test_tnd.TndResourceTestCase) ... 
WARNING:tornado.access:401 POST /fake (127.0.0.1) 4.37ms
  ok
  test_bubble_exceptions (tests.test_resources.ResourceTestCase) ... ok
  test_build_error (tests.test_resources.ResourceTestCase) ... ok
  test_build_response (tests.test_resources.ResourceTestCase) ... ok
  test_create (tests.test_resources.ResourceTestCase) ... ok
  test_create_detail (tests.test_resources.ResourceTestCase) ... ok
  test_delete (tests.test_resources.ResourceTestCase) ... ok
  test_delete_list (tests.test_resources.ResourceTestCase) ... ok
  test_deserialize (tests.test_resources.ResourceTestCase) ... ok
  test_deserialize_detail (tests.test_resources.ResourceTestCase) ... ok
  test_deserialize_list (tests.test_resources.ResourceTestCase) ... ok
  test_detail (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_create (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_create_detail (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_delete (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_delete_list (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_detail (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_list (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_update (tests.test_resources.ResourceTestCase) ... ok
  test_endpoint_update_list (tests.test_resources.ResourceTestCase) ... ok
  test_init (tests.test_resources.ResourceTestCase) ... ok
  test_is_authenticated (tests.test_resources.ResourceTestCase) ... ok
  test_is_debug (tests.test_resources.ResourceTestCase) ... ok
  test_list (tests.test_resources.ResourceTestCase) ... ok
  test_prepare (tests.test_resources.ResourceTestCase) ... ok
  test_request_body (tests.test_resources.ResourceTestCase) ... ok
  test_request_method (tests.test_resources.ResourceTestCase) ... ok
  

Bug#851001: marked as done (python-restless: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 00:42:34 +0300
with message-id <20170523214234.xzl5ru5kf5xmgn2q@localhost>
and subject line python-restless seems to build now
has caused the Debian Bug report #849555,
regarding python-restless: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 3.5 returned exit code 13
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.)


-- 
849555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-restless
Version: 2.0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/it.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/data.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/preparers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/dj.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/constants.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/pyr.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/utils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/resources.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/exceptions.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/fl.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/tnd.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/serializers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/it.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/data.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/preparers.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/dj.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/constants.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/pyr.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/utils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/resources.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/exceptions.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/fl.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/tnd.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/serializers.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html
> Running Sphinx v1.4.9
> making output directory...
> loading pickled environment... not yet created
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 23 source files that are out of date
> updating environment: 23 added, 0 changed, 0 removed
> reading sources... [  4%] contributing
> reading sources... [  8%] cookbook
> reading sources... [ 13%] extending
> reading sources... [ 17%] index
> reading sources... [ 21%] philosophy
> reading sources... [ 26%] reference/constants
> reading sources... [ 30%] reference/data
> reading sources... [ 34%] reference/exceptions
> reading sources... [ 39%] reference/preparers
> reading sources... [ 43%] reference/resources
> reading sources... [ 47%] reference/serializers
> reading sources... [ 52%] reference/utils
> reading sources... [ 56%] releasenotes/v1.0.0
> reading sources... [ 60%] releasenotes/v1.1.0
> reading sources... [ 65%] releasenotes/v1.2.0
> reading sources... [ 69%] releasenotes/v1.3.0
> reading sources... [ 73%] releasenotes/v1.4.0
> reading sources... [ 78%] releasenotes/v2.0.0
> reading sources... [ 82%] releasenotes/v2.0.1
> reading sources... [ 86%] releasenotes/v2.0.2
> reading sources... [ 91%] releasenotes/v2.0.3
> reading sources... [ 95%] security
> reading sources... [100%] tutorial
> 
> /<>/docs/reference/resources.rst:42: WARNING: autodoc: failed to 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 849555 851001
Bug #849555 [src:python-restless] python-restless: FTBFS: ImportError: No 
module named itty
Bug #849555 [src:python-restless] python-restless: FTBFS: ImportError: No 
module named itty
Added tag(s) sid and stretch.
Bug #851001 [src:python-restless] python-restless: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 3.5 returned exit code 13
Merged 849555 851001
> thanks
Stopping processing here.

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

Bug#863106: marked as done (quadrapassel: segfaults when unpausing a paused finished game)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 21:06:49 +
with message-id 
and subject line Bug#863106: fixed in quadrapassel 1:3.22.0-1.1
has caused the Debian Bug report #863106,
regarding quadrapassel: segfaults when unpausing a paused finished game
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.)


-- 
863106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quadrapassel
Version: 1:3.22.0-1
Severity: important

Steps to reproduce:

 - End a game (eg. by dropping every block on top of the next)
 - It will say "Game over"
 - Pause the game via the keyboard shortcut (which makes no sense)
 - It will say "Paused"
 - Unpause the game via the keyboard shortcut
 - The quadrapassel will backtrace approximately one second later.


Thread 1 "quadrapassel" received signal SIGSEGV, Segmentation fault.
0x55561544 in game_land_shape (self=0x55ce8b00) at game.c:1744
1744game.c: No such file or directory.
(gdb) bt
#0  0x55561544 in game_land_shape (self=0x55ce8b00) at game.c:1744
#1  game_fall_timeout_cb (self=0x55ce8b00) at game.c:894
#2  0x75a2e123 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x75a2d6aa in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x75a2da60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x75a2db0c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x75fe972d in g_application_run () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0xeda9 in quadrapassel_main (args=, 
args_length1=) at quadrapassel.c:2832
#8  0x754482b1 in __libc_start_main (main=0xa580 , 
argc=1, argv=0x7fffe798, init=, fini=, 
rtld_fini=, 
stack_end=0x7fffe788) at ../csu/libc-start.c:291
#9  0xa5ba in _start ()


Regards,

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

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated quadrapassel 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: Tue, 23 May 2017 19:48:01 +0100
Source: quadrapassel
Binary: quadrapassel
Architecture: source amd64
Version: 1:3.22.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Chris Lamb 
Description:
 quadrapassel - popular Russian game, similar to Tetris
Closes: 863106
Changes:
 quadrapassel (1:3.22.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix segfault when unpausing a paused game that has finished.
 (Closes: #863106)
Checksums-Sha1:
 46652ac96c75084fd6e0bee16b48588a17a61153 2360 quadrapassel_3.22.0-1.1.dsc
 f6ef202edbc8952560dbf9cafc772aca04448a4c 1737252 
quadrapassel_3.22.0.orig.tar.xz
 95ee9d3c5f909728bf0ee4002bf9db949b1bdbbc 27236 
quadrapassel_3.22.0-1.1.debian.tar.xz
 e2015c7f1317e64cdc509356c8c31653af3d1bf5 194974 
quadrapassel-dbgsym_3.22.0-1.1_amd64.deb
 f0aadec44e96052e9af7098e7230f1e3d97e01fe 15224 
quadrapassel_3.22.0-1.1_amd64.buildinfo
 45c9e8cb46900ccb192511535d865212e381db0a 1050692 
quadrapassel_3.22.0-1.1_amd64.deb
Checksums-Sha256:
 41bc81e9926ee058b4c7b9d8a9649b89aa2b6e10cc5f8a1dd0a06eae27156c8a 2360 
quadrapassel_3.22.0-1.1.dsc
 0ed44ef73c8811cbdfc3b44c8fd80eb6e2998d102d59ac324e4748f5d9dddb55 1737252 
quadrapassel_3.22.0.orig.tar.xz
 887e34f6e520a4c05f3b15c47528e0ceed989049ea97dbd557977344336ea342 27236 
quadrapassel_3.22.0-1.1.debian.tar.xz
 4e8931709157649c07dde273f4c3a9bef68d0ae41c9754f35ffe284b02fae3c2 194974 
quadrapassel-dbgsym_3.22.0-1.1_amd64.deb
 fcc172d761c6006c4931f83ec76fe686741e319da49edd1865103d86bd01531b 15224 

Bug#863212: marked as done (puppet: CVE-2017-2295: unsafe YAML deserialization)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 21:06:38 +
with message-id 
and subject line Bug#863212: fixed in puppet 4.8.2-5
has caused the Debian Bug report #863212,
regarding puppet: CVE-2017-2295: unsafe YAML deserialization
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.)


-- 
863212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppet
Version: 3.7.2-1
Severity: grave
Tags: upstream security patch

Hi,

the following vulnerability was published for puppet.

CVE-2017-2295[0]:
Unsafe YAML deseralization

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-2017-2295
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2295
[1] https://puppet.com/security/cve/cve-2017-2295
[2] 
https://github.com/puppetlabs/puppet/commit/06d8c51367ca932b9da5d9b01958cfc0adf0f2ea

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: puppet
Source-Version: 4.8.2-5

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated puppet 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: Tue, 23 May 2017 23:17:46 +0300
Source: puppet
Binary: puppet puppet-master puppetmaster puppet-master-passenger 
puppetmaster-passenger puppet-common
Architecture: source all
Version: 4.8.2-5
Distribution: unstable
Urgency: high
Maintainer: Puppet Package Maintainers 

Changed-By: Apollon Oikonomopoulos 
Description:
 puppet - configuration management system
 puppet-common - transitional dummy package
 puppet-master - configuration management system, master service
 puppet-master-passenger - configuration management system, scalable master 
service
 puppetmaster - configuration management system, master service - transitional 
pa
 puppetmaster-passenger - configuration management system, scalable master 
service - transi
Closes: 863212
Changes:
 puppet (4.8.2-5) unstable; urgency=high
 .
   * master: accept facts only in PSON format (CVE-2017-2295) (Closes:
 #863212).
Checksums-Sha1:
 bf4e28dfd0c09a509a3a2e7c27b6aea5718df293 2524 puppet_4.8.2-5.dsc
 e2f8c013316dadf0923b191243615ef428cffc21 37756 puppet_4.8.2-5.debian.tar.xz
 fe7cabdc8b629045ff89e917a38bc9c3259f0396 23590 puppet-common_4.8.2-5_all.deb
 47122b89d464dcc8f3e2fc17c73f33691ba18276 27226 
puppet-master-passenger_4.8.2-5_all.deb
 7ffcf144c1e7f7a1202bbb62746313432a3f515c 26140 puppet-master_4.8.2-5_all.deb
 b134e72ebf28718171edb009d14da8766f0952a8 1122848 puppet_4.8.2-5_all.deb
 b393786913df378127863782a67675d350af2b7d 8054 puppet_4.8.2-5_amd64.buildinfo
 9692ef7d80d27d5977e4bffa7d6933a6464e0e80 22916 
puppetmaster-passenger_4.8.2-5_all.deb
 04f0cbd9721eeaac3f208c4da389ba823739cb00 23092 puppetmaster_4.8.2-5_all.deb
Checksums-Sha256:
 13925c5d2f4093e8e5ae1c5e672bcf50306bedff6a13b392287cb4ccbbbd382a 2524 
puppet_4.8.2-5.dsc
 02916abb3e20c698279b837f32ca880a75c1d5d656c695854e9f34f318bf59c6 37756 
puppet_4.8.2-5.debian.tar.xz
 759506391f933af9feb8253b7aaa5989185eae6fe127fdd8e47567af204a79fb 23590 
puppet-common_4.8.2-5_all.deb
 e08faae64542326cd46f5564d3fd27615681aa29ae8de112018ba242ce142650 27226 
puppet-master-passenger_4.8.2-5_all.deb
 3aab5db2d6cb4556068c3f3a402b5c438cadaca57f8696036b77def28c7a82a2 26140 
puppet-master_4.8.2-5_all.deb
 6e00516561dc120e94697bab66cd55b63ec2e4f5fcf61e534b06ff8f6cc6b895 1122848 
puppet_4.8.2-5_all.deb
 7ff0c6d01b7c518ba84b60a60700ce428cafe9cebf778d84779529bcc70cc076 8054 
puppet_4.8.2-5_amd64.buildinfo
 ef17a6b742c43edc176111350f407be674c94484cdebc89a3208b4d7988dc065 22916 
puppetmaster-passenger_4.8.2-5_all.deb
 277d226ef1816a428009e887f7abfcf2fea47499e102177078f646396a1536ef 23092 
puppetmaster_4.8.2-5_all.deb
Files:

Bug#863106: quadrapassel: segfaults when unpausing an paused finished gmae

[Chris Lamb]

Emilio Pozuelo Monfort wrote:

> > I've uploaded quadrapassel 3.22.0-1.1 to DELAYED/5:
>
> Please feel free to reschedule this to DELAYED/0.

Sure:

Log of processing your commands file 
/dcut.Chris_Lamb__lamby_debian_org_.1495569691.2608.commands:

reschedule quadrapassel_3.22.0-1.1_amd64.changes 0-day
quadrapassel_3.22.0-1.1_amd64.changes moved to 0-day
quadrapassel_3.22.0-1.1.dsc moved to 0-day
quadrapassel_3.22.0.orig.tar.xz moved to 0-day
quadrapassel_3.22.0-1.1.debian.tar.xz moved to 0-day
quadrapassel-dbgsym_3.22.0-1.1_amd64.deb moved to 0-day
quadrapassel_3.22.0-1.1_amd64.buildinfo moved to 0-day
quadrapassel_3.22.0-1.1_amd64.deb moved to 0-day

> Also if you can forward the patch upstream at [1] that'd be great.

Will get on this :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#849099: marked as done (llvm-toolchain-3.7: Please add ELF symbols versions to the libraries)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 19:36:00 +
with message-id <44113756-52ee-2d02-8af1-8c1af06d8...@thykier.net>
and subject line Re: llvm-toolchain-3.7: Please add ELF symbols versions to the 
libraries
has caused the Debian Bug report #849099,
regarding llvm-toolchain-3.7: Please add ELF symbols versions to the libraries
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.)


-- 
849099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-3.9
Version: 1:3.9.1-1
Severity: wishlist

As can be seen in #846410 having no ELF-versioned symbols leads to unexpected
crashes when two LLVM versions are used in the same process.

Adding ELF symbols versions would allow avoiding this crashes as long as
no data is interchanged between both versions of LLVM-related libs.

Thanks for considering, Lisandro.

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Fri, 16 Dec 2016 15:55:49 -0300
=?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?=
  wrote:
> Source: llvm-toolchain-3.9
> Version: 1:3.9.1-1
> Severity: wishlist
> 
> As can be seen in #846410 having no ELF-versioned symbols leads to unexpected
> crashes when two LLVM versions are used in the same process.
> 
> Adding ELF symbols versions would allow avoiding this crashes as long as
> no data is interchanged between both versions of LLVM-related libs.
> 
> Thanks for considering, Lisandro.
> 
> [...]

Closing the 3.7 variant of this bug. :)  It won't be necessary for
stretch (and llvm-toolchain-3.7 will be removed in buster).

Thanks,
~Niels--- End Message ---

Bug#863106: quadrapassel: segfaults when unpausing an paused finished gmae

[Emilio Pozuelo Monfort]

Hi Chris,

On 23/05/17 21:05, Chris Lamb wrote:
> tags 863106 + pending patch
> retitle 863106 quadrapassel: segfaults when unpausing a paused finished game
> thanks
> 
> I've uploaded quadrapassel 3.22.0-1.1 to DELAYED/5:
>   
>   quadrapassel (1:3.22.0-1.1) unstable; urgency=medium
>   
> * Non-maintainer upload.
> * Fix segfault when unpausing a paused game that has finished.
>   (Closes: #863106)
> 
> The full debdiff is attached.

Please feel free to reschedule this to DELAYED/0.

Also if you can forward the patch upstream at [1] that'd be great.

Thanks,
Emilio

[1] https://bugzilla.gnome.org/page.cgi?id=browse.html=quadrapassel

Processed: Re: Bug#859262: closed by Paul Gevers <elb...@debian.org> (Bug#859262: fixed in gnome-orca 3.22.2-3)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #859262 {Done: Paul Gevers } [gnome-orca] gnome-orca: 
Gets stuck if target app is busy
'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 gnome-orca/3.22.2-3.

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

Processed: Re: quadrapassel: segfaults when unpausing a paused finished game

[Debian Bug Tracking System]

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

> severity 863106 serious
Bug #863106 [quadrapassel] quadrapassel: segfaults when unpausing a paused 
finished game
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#859262: closed by Paul Gevers <elb...@debian.org> (Bug#859262: fixed in gnome-orca 3.22.2-3)

[Paul Gevers]

Control: reopen -1

Hi Mika,

On 23-05-17 20:57, Mika Hanhijärvi wrote:
> Unfortunately this did not fix the problem. The problem still exists. I
> still have noticed this only when using Synaptic.

That is a shame. Could you please try to get the debugging information
needed by Joanmarie on your system? It was difficult to provide her with
this information as I don't use orca myself nor experience the exact
problem you are having. Without the debugging info, there is not much we
can do.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#859262: closed by Paul Gevers <elb...@debian.org> (Bug#859262: fixed in gnome-orca 3.22.2-3)

[Mika Hanhijärvi]

Unfortunately this did not fix the problem. The problem still exists. I 
still have noticed this only when using Synaptic.



One interesting thing is that if it happens when I do this:



/) Go to eg virtual desktop 2 on Gnome/

2) start Synaptic on that virtual desktop

3) click Reload button

4) Go to e.g virtual desktop 1 and do something else like browse the web 
using firefox or something else



5) Let Synaptic to finish reloading the repository information,

6) Go back to virtual desktop 2 where Synaptic is running and where it's 
window is open



Orca stops speaking when you do the step 6. That happened again some 
minutes ago and that has happened many times. Synaptic was running and 
reloading on one virtual desktop and I was browsing facebook on another 
virtual desktop. Everything worked just fine until I did goback to that 
virtual desktop where Synaptic was running. When I did that Orca 
immediately stopped to speak. When I closed the Synaptic using alt + f4 
then Orca started to speak again.



And by the way I do not remember if this problem existed in Debian 
Jessie. Both of my laptops are quite new. I first installed Debian 
Jessien on those laptops, but I upgraded to Stretch soon after that. My 
desktop computer is still running Debian 7.0 "Wheezy". I did not really 
use Debian 8.0 "Jessie" much on those laptops so you can say that I 
jumped from Wheezy to Stretch. This problem does not exist in Wheezy and 
I really can not say if it existed in Jessie, but it does still exist in 
Stretch. I do not know if this problem exists in new Stretch 
installations. I am going to make a clean Stretch install when I buy the 
new SSD disk, but I can not do that right now.











On 05/03/2017 09:51 PM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the gnome-orca package:

#859262: gnome-orca: Gets stuck if target app is busy

It has been closed by Paul Gevers .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Paul Gevers 
 by
replying to this email.

Bug#863059: marked as done (libgit2: FTBFS on armhf and mips64el: thread tests segfault)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 21:36:11 +0300
with message-id <20170523183611.mczn5o7yrfktlhd4@localhost>
and subject line This bug is "fixed" in 0.25.1+really0.24.6-1
has caused the Debian Bug report #863059,
regarding libgit2: FTBFS on armhf and mips64el: thread tests 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.)


-- 
863059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgit2
Version: 0.25.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The armhf and mips64el builds of libgit2 both segfaulted in thread
tests, per the excerpted log output below (armhf first).  Could you
please take a look?

Thanks!

  submodule::status...
  submodule::update...
  threads::basic
  
  
  75% tests passed, 1 tests failed out of 4
  
  Total Test time (real) =  58.85 sec
  
  The following tests FAILED:
1 - libgit2_clar (SEGFAULT)

--

  submodule::update...
  threads::basic
  threads::diff..
  
  
  75% tests passed, 1 tests failed out of 4
  
  Total Test time (real) =  65.07 sec
  
  The following tests FAILED:
1 - libgit2_clar (SEGFAULT)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Version: 0.25.1+really0.24.6-1

This bug is "fixed" in 0.25.1+really0.24.6-1 by going back to 0.24,
and shouldn't prevent the testing migration of this version.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

[Niels Thykier]

On Thu, 27 Apr 2017 18:10:17 +0200 Andreas Beckmann  wrote:
> Followup-For: Bug #854554
> Control: found -1 2.9.2-4
> Control: affects -1 + libcrypt-cracklib-perl
> 
> Hi,
> 

Hi Jan,

Thanks for fixing the original part of this bug.

Andreas noticed a deficiency in the suggested implementation that
affects the current version.  Could I convince you to apply the
following fix as well?

Thanks,
~Niels

> this problem has been solved completely, yet, since nothing prevents the
> old cracklib-runtime from being triggered during the upgrade. (Could be
> a problem in jessie's apt and therefore needs to worked around.)
> I just verified that this can be solved by the following change:
> 
>   Package: libcrack2
>   Breaks: cracklib-runtime (<< 2.9.2-4)
> 
> This will cause the old cracklib-runtime to be either deconfigured or
> the new cracklib-runtime be unpacked (but not configured) before the new
> libcrack2 gets unpacked, preventing the old triggers from being run.
> 
> (The problem was
> 
>   dpkg: error processing package cracklib-runtime (--configure):
>dependency problems - leaving triggers unprocessed
>   dpkg: dependency problems prevent processing triggers for cracklib-runtime:
>cracklib-runtime depends on libcrack2 (>= 2.9.2-1); however:
> Package libcrack2:i386 is not configured yet.
> 
> i.e. that's cracklib-runtime from jessie)
> 
> 
> 
> Andreas
> 
> 

Processed: tagging 839575

[Debian Bug Tracking System]

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

> tags 839575 + upstream fixed-upstream
Bug #839575 [openssl] hangs waiting for openssl
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#863212: puppet: CVE-2017-2295: unsafe YAML deserialization

[Salvatore Bonaccorso]

Source: puppet
Version: 3.7.2-1
Severity: grave
Tags: upstream security patch

Hi,

the following vulnerability was published for puppet.

CVE-2017-2295[0]:
Unsafe YAML deseralization

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-2017-2295
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2295
[1] https://puppet.com/security/cve/cve-2017-2295
[2] 
https://github.com/puppetlabs/puppet/commit/06d8c51367ca932b9da5d9b01958cfc0adf0f2ea

Regards,
Salvatore

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

[John Paul Adrian Glaubitz]

Control: severity -1 normal

On 05/04/2017 07:22 PM, John Paul Adrian Glaubitz wrote:
> I'd be tempted to lower the severity to 'normal'.

Downgrading this now because it is not relevant for the Stretch release.

I also just noticed that you are actually not running Debian but a spin
called "BunsenLabs GNU/Linux", so I'm not sure why you are reporting this
bug to Debian in the first place.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: Re: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #861536 [runit-init] runit-init: Cannot reboot or shutdown after installing 
(or removing) the package.
Severity set to 'normal' from 'grave'

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

Bug#861282: packer: FTBFS

[Roger Shimizu]

On Mon, 22 May 2017 12:22:18 -0400 (EDT) JD Friedrikson  
wrote:
> Here are the four patches that are related to this issue:
> 
> https://github.com/hashicorp/packer/commit/28ee60d216e49d565d654443b57295ce37197db1
> https://github.com/hashicorp/packer/commit/249cb690e04477582aefadf4350a087bf4e33a87
> https://github.com/hashicorp/packer/commit/ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b
> https://github.com/hashicorp/packer/commit/a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd
> 
> 28ee60d216e49d565d654443b57295ce37197db1 is the patch that is currently 
> packaged with debian
> 
> 249cb690e04477582aefadf4350a087bf4e33a87 concerns vendor files which Debian 
> doesn't appear to carry as part of the source package
> 
> ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b and 
> a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd both concern drivers to proprietary 
> software (which Debian also does not seem to carry) so both need to be 
> trimmed before applying
> 
> After removing the references to missing files, 
> a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd works just fine.
> 
> ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b is the one I'm having trouble with 
> currently as it's failing for openstack's and amazon's ssh.go files. Not sure 
> what changes we're carrying for those as I haven't dug too deep, but that's 
> where I'm at now.

Thanks for your info!
I pushed a commit to new branch fix_861282, that applied:
  ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b
  a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd
(https://anonscm.debian.org/cgit/pkg-go/packages/packer.git/log/?h=fix_861282)

Please help to test whether it fixes your problem.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


pgpub9wA77KlN.pgp
Description: PGP signature

Bug#861282: Pending fixes for bugs in the packer package

[pkg-go-maintainers]

tag 861282 + pending
thanks

Some bugs in the packer package are closed in revision
5af0896f302edc98991832d1f0856c7c2215bca7 in branch '  fix_861282' by
Roger Shimizu

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/packer.git/commit/?id=5af0896

Commit message:

deb/patches: Backport two more patches

(again) to handle ABI change of golang-golang-x-crypto-dev

Closes: #861282

Processed: Pending fixes for bugs in the packer package

[Debian Bug Tracking System]

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

> tag 861282 + pending
Bug #861282 [packer] packer: FTBFS
Bug #861548 [packer] packer: FTBFS with latest golang-go.crypto
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#863202: adonthell-data frequently FTBFS in parallel builds

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #863202 [src:adonthell-data] adonthell-data frequently FTBFS in parallel 
builds
Severity set to 'normal' from 'serious'

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

Bug#863202: adonthell-data frequently FTBFS in parallel builds

[Markus Koschany]

Control: severity -1 normal

Am 23.05.2017 um 15:43 schrieb Adrian Bunk:
> Source: adonthell-data
> Version: 0.3.6-1
> Severity: serious
> Tags: patch
> 
> https://tests.reproducible-builds.org/debian/history/adonthell-data.html
> https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/adonthell-data.html
> 
> ...
> make[4]: Entering directory '/build/adonthell-data-0.3.6'
> rm -Rf 
> /build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge
>  /bin/mkdir -p '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/games'
>  /bin/mkdir -p 
> '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/applications'
>  /bin/mkdir -p 
> '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge'
>  /bin/mkdir -p 
> '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/man/man6'
>  /usr/bin/install -c adonthell-wastesedge 
> '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/games'
>  /usr/bin/install -c -m 644 wastesedge.desktop 
> '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/applications'
>  /usr/bin/install -c -m 644 gamename.txt achievements.data character.data 
> mapengine.data quest.data audio.data 
> '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge'
> /usr/bin/install: target 
> '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge'
>  is not a directory
> Makefile:517: recipe for target 'install-dist_pkgdataDATA' failed
> make[4]: *** [install-dist_pkgdataDATA] Error 1
> 
> 
> The proper fix would be to fix the dependencies in Makefile.am
> 
> As workaround the following to disable parallel building
> (which is default with debhelper compat 10) is sufficient:
> 
> --- debian/rules.old  2017-05-23 13:39:47.0 +
> +++ debian/rules  2017-05-23 13:39:56.0 +
> @@ -2,7 +2,7 @@
>  #export DH_VERBOSE=1
>  
>  %:
> - dh $@
> + dh $@ --no-parallel
>  
>  override_dh_auto_configure:
>   dh_auto_configure -- \


I cannot confirm that adonthell-data frequently fails to build from
source. After ten iterations on my system it still builds without fail.
Since it also can be built on the amd64 autobuilder, this is not a
release critical issue. I can pass the --no-parallel option to dh after
the freeze, if it helps.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#847651: marked as done (doomsday: Segfaults at startup)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 15:18:46 +
with message-id 
and subject line Bug#847651: fixed in doomsday 1.15.8-4
has caused the Debian Bug report #847651,
regarding doomsday: Segfaults at startup
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.)


-- 
847651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: doomsday
Version: 1.15.8-3
Severity: important

Dear Maintainer,

Doomsday just segfaults at startup, producting to following output :

$ doomsday
zsh: segmentation fault  doomsday

And I can't compile the dev version or the official source package. Good luck.

Regards,

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (500, 
'oldstable-updates'), (500, 'oldstable'), (90, 'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages doomsday depends on:
ii  doomsday-common   1.15.8-3
ii  doomsday-data 1.15.8-3
ii  libc6 2.24-7
ii  libgcc1   1:6.2.1-5
ii  libgl1-mesa-glx [libgl1]  13.0.2-1
ii  libqt4-network4:4.8.7+dfsg-11
ii  libqt4-opengl 4:4.8.7+dfsg-11
ii  libqtcore44:4.8.7+dfsg-11
ii  libqtgui4 4:4.8.7+dfsg-11
ii  libsdl2-2.0-0 2.0.5+dfsg1-1
ii  libsdl2-mixer-2.0-0   2.0.1+dfsg1-1
ii  libstdc++66.2.1-5

Versions of packages doomsday recommends:
ii  fluid-soundfont-gm  3.1-5.1

doomsday suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: doomsday
Source-Version: 1.15.8-4

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated doomsday 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, 23 May 2017 15:08:36 +0200
Source: doomsday
Binary: doomsday doomsday-server doomsday-common doomsday-data
Architecture: source
Version: 1.15.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 doomsday   - enhanced version of the legendary DOOM game
 doomsday-common - enhanced version of the legendary DOOM game - common files
 doomsday-data - enhanced version of the legendary DOOM game - data files
 doomsday-server - enhanced version of the legendary DOOM game - server
Closes: 847651
Changes:
 doomsday (1.15.8-4) unstable; urgency=medium
 .
   * Team upload.
   * Add Node-parent-NULL-pointer.patch and fix startup crash.
 Thanks to Bernhard Übelacker for the patch. (Closes: #847651)
Checksums-Sha1:
 1879275eb516f1036af5429e9e172e2c1c44b0ef 3050 doomsday_1.15.8-4.dsc
 e605b305d35cab9d6e7a2dac91f8d6cd2a246be5 16304 doomsday_1.15.8-4.debian.tar.xz
 8ffc2dddcf99b81f824d161db77454cfea08d149 13710 
doomsday_1.15.8-4_amd64.buildinfo
Checksums-Sha256:
 74a3b0beebacf6775e0012eb9d4d07fd21fe1a41098650e0b70a828e08367834 3050 
doomsday_1.15.8-4.dsc
 6e5becbe07d73c549042dff9e8b5305a188eaf26ee3e483d4bda03cb75e28777 16304 
doomsday_1.15.8-4.debian.tar.xz
 db8362d0e49a9f3ebdc231130a1a7faa0c6963f68fb4484574f20e09e613f537 13710 
doomsday_1.15.8-4_amd64.buildinfo
Files:
 5364e5687615e69bd4e89597f642c3a0 3050 games optional doomsday_1.15.8-4.dsc
 c10496e8562a57978acda5c2ee0d10b0 16304 games optional 
doomsday_1.15.8-4.debian.tar.xz
 8b7b300e3944336f1139c3e8bf95d826 13710 games optional 
doomsday_1.15.8-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlkkRchfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD

Bug#858143: Gets killed by logind kills user processes

[Paul van Tilburg]

Version: 0.9.1-9

Dear all,

I would like to report a problem with the fix in 0.9.1-9 and
I hope you would consider reopening this bug report.

The first issue is that it seems that when a user logs in now, the
xrdp-sesman main process is moved to scope of the first session! 
(This did not used to happen before.)

  $ systemctl status xrdp-sesman.service
● xrdp-sesman.service - xrdp session manager
   Loaded: loaded (/lib/systemd/system/xrdp-sesman.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2017-05-15 10:49:28 CEST; 1 weeks 1 
days ago
 Docs: man:xrdp-sesman(8)
   man:sesman.ini(5)
 Main PID: 3050 (xrdp-sesman)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/xrdp-sesman.service
   ‣ 3050 /usr/sbin/xrdp-sesman

  $ loginctl
 SESSIONUID USER SEAT TTY 
 426   1001 paul  
  c4   1002 other.user

  $ systemctl status session-c4.scope
● session-c4.scope - Session c4 of user corry.kosters
   Loaded: loaded (/run/systemd/transient/session-c4.scope; transient; 
vendor preset: enabled)
Transient: yes
   Active: active (running) since Mon 2017-05-15 10:49:43 CEST; 1 weeks 1 
days ago
   CGroup: /user.slice/user-10016.slice/session-c4.scope
   ├─ 3050 /usr/sbin/xrdp-sesman
   …

We have a deployment where we have configured systemd-logind to
kill user process when there are no more sessions for said user (via
both Xrdp and ssh).  So, now, not only his/her session is killed but also the
main xrdp-sessman process (!), after which Xrdp becomes unavailable.

A workaround is to login with a user that just disconnects, but that
is not exactly ideal.

A secondary effect of the fix that I see is that loginctl also
only reports a session for the first user that logged in.
For example, see the loginctl output above.  The session of my
user (c5) is not visible at all.

Both issues indicate that there is still an issue with properly
registering the sessions.  I have confirmed that going back to 0.9.1-7
fixes both issues.

Kind regards,
Paul

-- 
Using the Power of Debian GNU/Linux  | E-mail: pau...@debian.org
Jabber/XMPP: p...@luon.net   | GnuPG key ID: 0x50064181

Bug#863208: mash sometimes FTBFS in parallel builds

[Adrian Bunk]

Source: mash
Version: 1.1.1-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=mash=ppc64el=1.1.1-1=1472296851=0

...
dh_auto_build
make -j4
make[2]: Entering directory '/«PKGBUILDDIR»'
cd src/mash/capnp;export 
PATH=/usr/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp
 compile -I /usr/include -oc++ MinHash.capnp
cd src/mash/capnp;export 
PATH=/usr/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp
 compile -I /usr/include -oc++ MinHash.capnp
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/capnp/MinHash.capnp.o src/mash/capnp/MinHash.capnp.c++
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/Command.o src/mash/Command.cpp
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/CommandBounds.o src/mash/CommandBounds.cpp
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/CommandContain.o src/mash/CommandContain.cpp
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected primary-expression at 
end of input
   9,   0,   0,   0,   0,   0,   0,   0,
   ^
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘,’ or ‘;’ at end of 
input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
Makefile:47: recipe for target 'src/mash/capnp/MinHash.capnp.o' failed
make[2]: *** [src/mash/capnp/MinHash.capnp.o] Error 1


This is caused by "capnp compile" running twice in parallel,
fix is attached.
Description: Fix parallel build failures
 "capnp compile" ran twice, and in parallel builds twice in parallel.
 This resulted in occasional build failures caused by corrupt output files.
 .
 Fix the Makefile to only run "capnp compile" once.
Author: Adrian Bunk 

--- mash-1.1.1.orig/Makefile.in
+++ mash-1.1.1/Makefile.in
@@ -46,7 +46,9 @@ libmash.a : $(OBJECTS)
 %.o : %.c++
$(CXX) -c $(CXXFLAGS) $(CPPFLAGS) -o $@ $<
 
-src/mash/capnp/MinHash.capnp.c++ src/mash/capnp/MinHash.capnp.h : 
src/mash/capnp/MinHash.capnp
+src/mash/capnp/MinHash.capnp.c++ : src/mash/capnp/MinHash.capnp.h
+
+src/mash/capnp/MinHash.capnp.h : src/mash/capnp/MinHash.capnp
cd src/mash/capnp;export PATH=@capnp@/bin/:${PATH};capnp compile -I 
@capnp@/include -oc++ MinHash.capnp
 
 install : mash

Bug#861744: [Pkg-privacy-maintainers] Bug#861744: Bug#861744: Bug#861744: torbrowser-launcher: Should not be part of Stretch

[Holger Levsen]

On Tue, May 23, 2017 at 09:13:59AM +0200, intrigeri wrote:
> > So of course what I shall do is to disable those mails to me, after all
> > I'm one of the maintainers of jenkins.d.n :) But then I fear that
> > torbrowser-launcher will bitrot even more…
> Perhaps Ulrike would want to be the recipient of those email?
 
she is, since 2016-11-09.

I won't comment on the rest.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#862742: Error report for filetea

[Alberto Garcia]

On Tue, May 23, 2017 at 09:24:31AM +, Hari Krishna wrote:

> This is the patch for making filetea to work with jQuery v3.2.x. Hope this
> helps. Apply to upstream if needed.

Thanks for the patch, I'll forward it to upstream and discuss it with
him.

I guess another simpler possibility for the Debian case is to use the
libjs-jquery-migrate-1 package.

Berto

Processed: Re: Bug#847651: doomsday: Segfaults at startup

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #847651 [doomsday] doomsday: Segfaults at startup
Added tag(s) pending.

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

Bug#847651: doomsday: Segfaults at startup

[Markus Koschany]

Control: tags -1 pending

Am 23.05.2017 um 13:00 schrieb Bernhard Übelacker:
> Hello,
> tried to reproduce the issue.
> 
> I think the problem is that in de::File::parent the method maybeAs()
> is called on a NULL pointer.
> 
> With the attached patch the crash does not happen.

Hello,

thank you for the patch! It seems to do the trick. I have just uploaded
a new revision of doomsday to unstable.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Processed: Re: Network Manager, Stretch and ipv6

[Debian Bug Tracking System]

Processing control commands:

> severity 854801 serious
Bug #854801 [installation-reports] No network after netinst Stretch RC2
Bug #862416 [installation-reports] installation-reports: stretch standard 
installation does not install a network manager
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> reassign 854801 netcfg
Bug #854801 [installation-reports] No network after netinst Stretch RC2
Bug #862416 [installation-reports] installation-reports: stretch standard 
installation does not install a network manager
Bug reassigned from package 'installation-reports' to 'netcfg'.
Bug reassigned from package 'installation-reports' to 'netcfg'.
Ignoring request to alter found versions of bug #854801 to the same values 
previously set
Ignoring request to alter found versions of bug #862416 to the same values 
previously set
Ignoring request to alter fixed versions of bug #854801 to the same values 
previously set
Ignoring request to alter fixed versions of bug #862416 to the same values 
previously set

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

Bug#863202: adonthell-data frequently FTBFS in parallel builds

[Adrian Bunk]

Source: adonthell-data
Version: 0.3.6-1
Severity: serious
Tags: patch

https://tests.reproducible-builds.org/debian/history/adonthell-data.html
https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/adonthell-data.html

...
make[4]: Entering directory '/build/adonthell-data-0.3.6'
rm -Rf 
/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge
 /bin/mkdir -p '/build/adonthell-data-0.3.6/debian/adonthell-data/usr/games'
 /bin/mkdir -p 
'/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/applications'
 /bin/mkdir -p 
'/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge'
 /bin/mkdir -p 
'/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/man/man6'
 /usr/bin/install -c adonthell-wastesedge 
'/build/adonthell-data-0.3.6/debian/adonthell-data/usr/games'
 /usr/bin/install -c -m 644 wastesedge.desktop 
'/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/applications'
 /usr/bin/install -c -m 644 gamename.txt achievements.data character.data 
mapengine.data quest.data audio.data 
'/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge'
/usr/bin/install: target 
'/build/adonthell-data-0.3.6/debian/adonthell-data/usr/share/games/adonthell/games/wastesedge'
 is not a directory
Makefile:517: recipe for target 'install-dist_pkgdataDATA' failed
make[4]: *** [install-dist_pkgdataDATA] Error 1


The proper fix would be to fix the dependencies in Makefile.am

As workaround the following to disable parallel building
(which is default with debhelper compat 10) is sufficient:

--- debian/rules.old2017-05-23 13:39:47.0 +
+++ debian/rules2017-05-23 13:39:56.0 +
@@ -2,7 +2,7 @@
 #export DH_VERBOSE=1
 
 %:
-   dh $@
+   dh $@ --no-parallel
 
 override_dh_auto_configure:
dh_auto_configure -- \

Bug#863195: golang-1.8 FTBFS: format_test.go:264: ParseInLocation(Feb 01 2013 AST, Baghdad) = 2013-02-01 00:00:00 +0000 AST, want 2013-02-01 00:00:00 +0300 +03

[Hilko Bengen]

Hi,

two weeks ago I requested unblocking of golang-1.8/1.8.1-1 (#862158)
which if granted would solve the issue.

Cheers,
-Hilko

Bug#863201: libpam-ldap not longer installs the file /usr/share/pam-configs/ldap needed for pam-auth-update

[Lucas Castro]

Thanks, I'm going to fix that.


Em 23-05-2017 09:06, Carlos Alberto Lopez Perez escreveu:
> Package: libpam-ldap
> Version: 186-3
> Severity: grave
>
>
> libpam-ldap 184-8.7 (Jessie) installed a config file on 
> /usr/share/pam-configs/ldap
> telling pam-auth-update how it should re-configure the files on /etc/pam.d 
> when the
> command pam-auth-update is executed (that the package libpam-ldap executes on 
> the
> postinstall)
>
> libpam-ldap 186-3 (Stretch) not longer installs this file
>
> jessie $ dpkg --contents libpam-ldap_184-8.7+b1_amd64.deb | grep 
> pam-configs/ldap
> -rw-r--r-- root/root   518 2014-11-08 18:35 ./usr/share/pam-configs/ldap
>
> stretch $ dpkg --contents libpam-ldap_186-3_amd64.deb | grep pam-configs
> # nothing
>
> Therefore the package on Stretch is pretty much useless for new installs.
>
> The workaround is to copy this file manually from libpam-ldap=184-8.7 
> and manually execute pam-auth-update.
>
>
> Please, bring /usr/share/pam-configs/ldap back into libpam-ldap
>

Bug#860656: marked as done (python-biplist: FTBFS on i386: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 12:35:33 +
with message-id 
and subject line Bug#860656: fixed in python-biplist 1.0.2-1
has caused the Debian Bug report #860656,
regarding python-biplist: FTBFS on i386: dh_auto_test: pybuild --test 
--test-nose -i python{version} -p 2.7 returned exit code 13
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.)


-- 
860656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biplist
Version: 1.0.1-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):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/biplist
> running egg_info
> writing biplist.egg-info/PKG-INFO
> writing top-level names to biplist.egg-info/top_level.txt
> writing dependency_links to biplist.egg-info/dependency_links.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/biplist
> running egg_info
> writing dependency_links to biplist.egg-info/dependency_links.txt
> writing biplist.egg-info/PKG-INFO
> writing top-level names to biplist.egg-info/top_level.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m nose tests
> .F...
> ==
> FAIL: testIntBoundaries (test_write.TestWritePlist)
> --
> Traceback (most recent call last):
>   File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_write.py", 
> line 272, in testIntBoundaries
> self.roundTrip(cases)
>   File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_write.py", 
> line 41, in roundTrip
> self.assertEqual(repr(case if expected is None else expected), 
> repr(readResult))
> AssertionError: '[4294967295L, 4294967294L, 4294967296L, 4294967293L, 
> 4294967297L, 8589934590L, 2147483647L]' != '[4294967295L, 4294967294L, 
> 4294967296L, 4294967293L, 4294967297L, 8589934590L, 2147483647]'
> 
> --
> Ran 41 tests in 0.128s
> 
> FAILED (failures=1)
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
> exit code 13

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/python-biplist_1.0.1-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: python-biplist
Source-Version: 1.0.2-1

We believe that the bug you reported is fixed in the latest version of
python-biplist, 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 

Bug#863201: libpam-ldap not longer installs the file /usr/share/pam-configs/ldap needed for pam-auth-update

[Carlos Alberto Lopez Perez]

Package: libpam-ldap
Version: 186-3
Severity: grave


libpam-ldap 184-8.7 (Jessie) installed a config file on 
/usr/share/pam-configs/ldap
telling pam-auth-update how it should re-configure the files on /etc/pam.d when 
the
command pam-auth-update is executed (that the package libpam-ldap executes on 
the
postinstall)

libpam-ldap 186-3 (Stretch) not longer installs this file

jessie $ dpkg --contents libpam-ldap_184-8.7+b1_amd64.deb | grep 
pam-configs/ldap
-rw-r--r-- root/root   518 2014-11-08 18:35 ./usr/share/pam-configs/ldap

stretch $ dpkg --contents libpam-ldap_186-3_amd64.deb | grep pam-configs
# nothing

Therefore the package on Stretch is pretty much useless for new installs.

The workaround is to copy this file manually from libpam-ldap=184-8.7 
and manually execute pam-auth-update.


Please, bring /usr/share/pam-configs/ldap back into libpam-ldap



signature.asc
Description: OpenPGP digital signature

Processed: actually...

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #860656 [src:python-biplist] python-biplist: FTBFS on i386: dh_auto_test: 
pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13
Added tag(s) patch.

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

Bug#860656: actually...

[Hans-Christoph Steiner]

Control: tags -1 patch

Actually, upstream responded after looking into the details.  I was
wrong, we should just fix the tests.

Processed: Also mark the version in experimental as fixed

[Debian Bug Tracking System]

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

> fixed 831860 4.19.2+dfsg-1
Bug #831860 {Done: Dmitry Shachnev } [src:sip4] 
python{,3}-sip shouldn't provide more than one sip api
Bug #846956 {Done: Dmitry Shachnev } [src:sip4] 
python{,3}-sip shouldn't provide more than one sip api
Marked as fixed in versions sip4/4.19.2+dfsg-1.
Marked as fixed in versions sip4/4.19.2+dfsg-1.
> thanks
Stopping processing here.

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

Bug#847651: doomsday: Segfaults at startup

[Bernhard Übelacker]

Hello,
tried to reproduce the issue.

I think the problem is that in de::File::parent the method maybeAs()
is called on a NULL pointer.

With the attached patch the crash does not happen.

Kind regards,
Bernhard



# apt install doomsday doomsday-dbgsym doomsday-common-dbgsym
$ gdb -q --args doomsday
Reading symbols from doomsday...Reading symbols from 
/usr/lib/debug/.build-id/41/6978915c5c4686da064c7ff3a539ef4336958c.debug...done.
done.
(gdb) run
Starting program: /usr/games/doomsday 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".


  
Program received signal SIGSEGV, Segmentation fault.

  
0x7476092d in __dynamic_cast () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
 
(gdb) bt

  
#0  0x7476092d in __dynamic_cast () at 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   
#1  0x77574d95 in de::filesys::Node::maybeAs() 
(this=) at include/de/filesys/../filesys/node.h:88   
   
#2  0x77574d95 in de::File::parent() const (this=) at 
src/filesys/file.cpp:114
 
#3  0x7757572b in de::File::description() const 
(this=this@entry=0x560e5850) at src/filesys/file.cpp:146
#4  0x7757a40e in de::FileSystem::interpret(de::File*) (this=, sourceData=sourceData@entry=0x560e5850) at 
src/filesys/filesystem.cpp:147
#5  0x77573415 in de::DirectoryFeed::populateFile(de::Folder&, 
de::String const&) (this=this@entry=0x5605e410, folder=..., entryName=...) 
at src/filesys/directoryfeed.cpp:120
#6  0x77573849 in de::DirectoryFeed::populate(de::Folder&) 
(this=0x5605e410, folder=...) at src/filesys/directoryfeed.cpp:77
#7  0x7757f011 in de::Folder::populate(de::Folder::PopulationBehavior) 
(this=0x560dcc80, behavior=de::Folder::PopulateFullTree) at 
src/filesys/folder.cpp:193
#8  0x7757f069 in de::Folder::populate(de::Folder::PopulationBehavior) 
(this=0x56145070, behavior=behavior@entry=de::Folder::PopulateFullTree) at 
src/filesys/folder.cpp:203
#9  0x7757c24d in de::FileSystem::refresh() 
(this=this@entry=0x560b2a50) at src/filesys/filesystem.cpp:66
#10 0x775e9be9 in de::App::Instance::initFileSystem(bool) 
(this=0x560b2910, allowPlugins=) at src/core/app.cpp:242
#11 0x775e5faa in 
de::App::initSubsystems(QFlags) 
(this=this@entry=0x7fffdd80, flags=...) at src/core/app.cpp:592
#12 0x76a43115 in 
de::BaseGuiApp::initSubsystems(QFlags) 
(this=0x7fffdd70, flags=...) at src/baseguiapp.cpp:106
#13 0x555e48a5 in ClientApp::initialize() (this=0x7fffdd70) at 
src/clientapp.cpp:350
#14 0x555c8605 in main(int, char**) (argc=, 
argv=) at src/main_client.cpp:75
From 1e5dcb1be8049b9169e53e44b9085f9a2c4707fe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?= 
Date: Tue, 23 May 2017 12:07:38 +0200
Subject: Avoid crash after parent() returning NULL pointer.

https://bugs.debian.org/847651

Program received signal SIGSEGV, Segmentation fault.
0x7476092d in __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x7476092d in __dynamic_cast () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x77574d95 in de::filesys::Node::maybeAs() (this=) at include/de/filesys/../filesys/node.h:88
#2  0x77574d95 in de::File::parent() const (this=) at src/filesys/file.cpp:114
#3  0x7757572b in de::File::description() const (this=this@entry=0x560e5850) at src/filesys/file.cpp:146
#4  0x7757a40e in de::FileSystem::interpret(de::File*) (this=, sourceData=sourceData@entry=0x560e5850) at src/filesys/filesystem.cpp:147
#5  0x77573415 in de::DirectoryFeed::populateFile(de::Folder&, de::String const&) (this=this@entry=0x5605e410, folder=..., entryName=...) at src/filesys/directoryfeed.cpp:120
#6  0x77573849 in de::DirectoryFeed::populate(de::Folder&) (this=0x5605e410, folder=...) at src/filesys/directoryfeed.cpp:77
#7  0x7757f011 in de::Folder::populate(de::Folder::PopulationBehavior) (this=0x560dcc80, behavior=de::Folder::PopulateFullTree) at src/filesys/folder.cpp:193
#8  0x7757f069 in 

Bug#862742: Error report for filetea

[Hari Krishna]

This is the patch for making filetea to work with jQuery v3.2.x. Hope this
helps. Apply to upstream if needed.


On Tue, May 23, 2017 at 2:26 PM Alberto Garcia  wrote:

Control: tags -1 - unreproducible moreinfo

On Tue, May 23, 2017 at 07:14:39AM +, Hari Krishna wrote:

> ".live" method has been removed in jQuery version 1.9+. Please refer
> https://jquery.com/upgrade-guide/1.9/#live-removed

Yeah, I'm not sure how it worked last time I tried but I managed to
reproduce the problem now, thanks.

Berto


0001-Made-compatible-with-latest-jquery-v3.2.x.patch
Description: Binary data

Bug#846956: marked as done (python{,3}-sip shouldn't provide more than one sip api)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 09:08:33 +
with message-id 
and subject line Bug#831860: fixed in sip4 4.18.1+dfsg-2
has caused the Debian Bug report #831860,
regarding python{,3}-sip shouldn't provide more than one sip 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.)


-- 
831860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: veusz
Version: 1.21.1-1
Severity: important

Dear Maintainer,

After an upgrade Veusz stopped working : splash pic appears, veusz checks for 
astropy and sampy, then segfaults before the main window appears. Dmesg shows 
"veusz[19034]: segfault at 0 ip   (null) sp bf92869c error 14 in 
python2.7[8048000+347000]".

Cheers,

-- 

Pierre

-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux unstable (ceres)
Release:unstable
Codename:   ceres
Architecture: i686

Kernel: Linux 4.0.0-2-rt-686-pae (SMP w/1 CPU core; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages veusz depends on:
ii  python 2.7.11-2
ii  python-numpy   1:1.11.2-1
ii  python-qt4 4.11.4+dfsg-2
ii  veusz-helpers  1.21.1-1

veusz recommends no packages.

Versions of packages veusz suggests:
ii  python-dbus1.2.4-1
pn  python-h5py
pn  python-pyfits  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sip4
Source-Version: 4.18.1+dfsg-2

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated sip4 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: Tue, 23 May 2017 10:57:38 +0300
Source: sip4
Binary: python-sip python-sip-dbg python-sip-dev sip-dev sip-dbg python-sip-doc 
python3-sip python3-sip-dev python3-sip-dbg
Architecture: source
Version: 4.18.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-sip - Python/C++ bindings generator runtime library
 python-sip-dbg - Python/C++ bindings generator runtime library (debug 
extension)
 python-sip-dev - Python/C++ bindings generator development files
 python-sip-doc - Python/C++ bindings generator documentation
 python3-sip - Python 3/C++ bindings generator runtime library
 python3-sip-dbg - Python 3/C++ bindings generator runtime library (debug 
extension)
 python3-sip-dev - Python 3/C++ bindings generator development files
 sip-dbg- Debug symbols for Python/C++ bindings generator application
 sip-dev- Python/C++ bindings generator code generator application
Closes: 831860 841465
Changes:
 sip4 (4.18.1+dfsg-2) unstable; urgency=medium
 .
   [ Scott Kitterman ]
   * Remove Michael Casadevall from uploaders due to retirement from Debian
 (Closes: #841465)
 - Thanks Michael for all your work on sip4
 .
   [ Dmitry Shachnev ]
   * Drop 11.0 and 11.1 API versions, as there was an unintended ABI break
 between 11.1 and 11.2 (Closes: #831860). Still provide 11.2 and 11.3.
Checksums-Sha1:
 fd0c4132bc12c864defcbce708a9a0ece94aed91 2689 sip4_4.18.1+dfsg-2.dsc
 9aab7a33c1bd53b3df31c4f8f5f75f059ebadb1f 18720 sip4_4.18.1+dfsg-2.debian.tar.xz
 0cd1a11bc618fdd46ac74ab55c5225c21df77d7b 6938 
sip4_4.18.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 850dceecffc9ceb878cf018b1371818045a0fde07598fa493cbdce80e9414e73 2689 
sip4_4.18.1+dfsg-2.dsc
 24f8b8bfd305dd43471fd736f448f4ce931f83eb76b240687ce69762751714b6 18720 
sip4_4.18.1+dfsg-2.debian.tar.xz
 55ec374f4be389e9d3fdc0b493f23b11d7bc6e347c2a90f05392c6dc21f74a59 6938 
sip4_4.18.1+dfsg-2_source.buildinfo
Files:
 f9871e74b0d57d787d8470b24188be4c 2689 devel optional sip4_4.18.1+dfsg-2.dsc
 16686946e086c7211ba9775afd0d9f44 18720 devel optional 
sip4_4.18.1+dfsg-2.debian.tar.xz
 

Bug#831860: marked as done (python{,3}-sip shouldn't provide more than one sip api)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 09:08:33 +
with message-id 
and subject line Bug#831860: fixed in sip4 4.18.1+dfsg-2
has caused the Debian Bug report #831860,
regarding python{,3}-sip shouldn't provide more than one sip 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.)


-- 
831860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: veusz
Version: 1.21.1-1
Severity: important

Dear Maintainer,

veusz segfaults at start when run either from the GUI or from a
terminal with lines in dmesg such as:

veusz[17481]: segfault at 0 ip   (null) sp 7fff79d31568
error 14 in python2.7[40+2e9000]

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages veusz depends on:
ii  python 2.7.11-2
ii  python-numpy   1:1.11.1~rc1-1
ii  python-qt4 4.11.4+dfsg-2
ii  veusz-helpers  1.21.1-1

veusz recommends no packages.

Versions of packages veusz suggests:
ii  python-dbus1.2.4-1
pn  python-h5py
pn  python-pyfits  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sip4
Source-Version: 4.18.1+dfsg-2

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated sip4 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: Tue, 23 May 2017 10:57:38 +0300
Source: sip4
Binary: python-sip python-sip-dbg python-sip-dev sip-dev sip-dbg python-sip-doc 
python3-sip python3-sip-dev python3-sip-dbg
Architecture: source
Version: 4.18.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-sip - Python/C++ bindings generator runtime library
 python-sip-dbg - Python/C++ bindings generator runtime library (debug 
extension)
 python-sip-dev - Python/C++ bindings generator development files
 python-sip-doc - Python/C++ bindings generator documentation
 python3-sip - Python 3/C++ bindings generator runtime library
 python3-sip-dbg - Python 3/C++ bindings generator runtime library (debug 
extension)
 python3-sip-dev - Python 3/C++ bindings generator development files
 sip-dbg- Debug symbols for Python/C++ bindings generator application
 sip-dev- Python/C++ bindings generator code generator application
Closes: 831860 841465
Changes:
 sip4 (4.18.1+dfsg-2) unstable; urgency=medium
 .
   [ Scott Kitterman ]
   * Remove Michael Casadevall from uploaders due to retirement from Debian
 (Closes: #841465)
 - Thanks Michael for all your work on sip4
 .
   [ Dmitry Shachnev ]
   * Drop 11.0 and 11.1 API versions, as there was an unintended ABI break
 between 11.1 and 11.2 (Closes: #831860). Still provide 11.2 and 11.3.
Checksums-Sha1:
 fd0c4132bc12c864defcbce708a9a0ece94aed91 2689 sip4_4.18.1+dfsg-2.dsc
 9aab7a33c1bd53b3df31c4f8f5f75f059ebadb1f 18720 sip4_4.18.1+dfsg-2.debian.tar.xz
 0cd1a11bc618fdd46ac74ab55c5225c21df77d7b 6938 
sip4_4.18.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 850dceecffc9ceb878cf018b1371818045a0fde07598fa493cbdce80e9414e73 2689 
sip4_4.18.1+dfsg-2.dsc
 24f8b8bfd305dd43471fd736f448f4ce931f83eb76b240687ce69762751714b6 18720 
sip4_4.18.1+dfsg-2.debian.tar.xz
 55ec374f4be389e9d3fdc0b493f23b11d7bc6e347c2a90f05392c6dc21f74a59 6938 
sip4_4.18.1+dfsg-2_source.buildinfo
Files:
 f9871e74b0d57d787d8470b24188be4c 2689 devel optional sip4_4.18.1+dfsg-2.dsc
 16686946e086c7211ba9775afd0d9f44 18720 devel optional 
sip4_4.18.1+dfsg-2.debian.tar.xz
 51df5d5aae47cda0783850b5f17fc1a2 6938 devel optional 
sip4_4.18.1+dfsg-2_source.buildinfo

Bug#862988: marked as done (dante-server: Job for danted.service failed because the control process exited with error code during installation)

[Debian Bug Tracking System]

Your message dated Tue, 23 May 2017 09:04:33 +
with message-id 
and subject line Bug#862988: fixed in dante 1.4.1+dfsg-5
has caused the Debian Bug report #862988,
regarding dante-server: Job for danted.service failed because the control 
process exited with error code during installation
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.)


-- 
862988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dante-server
Version: 1.4.1+dfsg-4
Severity: important

Dear Maintainer,

I am trying to install dante-server in Debian Stretch but the
installations fails with the following error:

---
root@defiant:~# aptitude install dante-server
Se instalarán los siguiente paquetes NUEVOS:
  dante-server
0 paquetes actualizados, 1 nuevos instalados, 0 para eliminar y 0 sin 
actualizar.
Necesito descargar 0 B/373 kB de ficheros. Después de desempaquetar se usarán 
993 kB.
Seleccionando el paquete dante-server previamente no seleccionado.
(Leyendo la base de datos ... 157294 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../dante-server_1.4.1+dfsg-4_amd64.deb ...
Desempaquetando dante-server (1.4.1+dfsg-4) ...
Procesando disparadores para systemd (232-23) ...
Configurando dante-server (1.4.1+dfsg-4) ...
Job for danted.service failed because the control process exited with error 
code.
See "systemctl status danted.service" and "journalctl -xe" for details.
invoke-rc.d: initscript danted, action "start" failed.
● danted.service - SOCKS (v4 and v5) proxy daemon (danted)
   Loaded: loaded (/lib/systemd/system/danted.service; disabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Fri 2017-05-19 13:21:14 -03; 14ms 
ago
 Docs: man:danted(8)
   man:danted.conf(5)
  Process: 15761 ExecStart=/usr/sbin/danted -D (code=exited, status=1/FAILURE)
  Process: 15755 ExecStartPre=/bin/sh -cuid=`sed -n -e 
"s/[[:space:]]//g" -e "s/#.*//" -e "/^user\.privileged/{s/[^:]*://p;q;}" 
/etc/danted.conf`;
if [ -n "$uid" ]; then  touch /var/run/danted.pid;  
chown $uid /var/run/danted.pid; fi   (code=exited, 
status=0/SUCCESS)

may 19 13:21:14 defiant systemd[1]: Starting SOCKS (v4 and v5) proxy daemon 
(danted)...
may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811468) 
danted[15761]: warning: checkconfig(): no socks authentication metho…t intended?
may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811545) 
danted[15761]: error: checkconfig(): no internal address given for s… clients on
may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811565) 
danted[15761]: alert: mother[1/1]: shutting down
may 19 13:21:14 defiant systemd[1]: danted.service: Control process exited, 
code=exited status=1
may 19 13:21:14 defiant systemd[1]: Failed to start SOCKS (v4 and v5) proxy 
daemon (danted).
may 19 13:21:14 defiant systemd[1]: danted.service: Unit entered failed state.
may 19 13:21:14 defiant systemd[1]: danted.service: Failed with result 
'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error al procesar el paquete dante-server (--configure):
 el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
 Procesando disparadores para man-db (2.7.6.1-2) ...
 Procesando disparadores para systemd (232-23) ...
 Se encontraron errores al procesar:
 dante-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
Configurando dante-server (1.4.1+dfsg-4) ...
Job for danted.service failed because the control process exited with error 
code.
See "systemctl status danted.service" and "journalctl -xe" for details.
invoke-rc.d: initscript danted, action "start" failed.
● danted.service - SOCKS (v4 and v5) proxy daemon (danted)
   Loaded: loaded (/lib/systemd/system/danted.service; disabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Fri 2017-05-19 13:21:16 -03; 16ms 
ago
 Docs: man:danted(8)
   man:danted.conf(5)
  Process: 15865 ExecStart=/usr/sbin/danted -D (code=exited, status=1/FAILURE)
  Process: 15859 ExecStartPre=/bin/sh -cuid=`sed -n -e 
"s/[[:space:]]//g" -e "s/#.*//" -e "/^user\.privileged/{s/[^:]*://p;q;}" 
/etc/danted.conf`;
if [ -n "$uid" ]; then  touch /var/run/danted.pid;  
chown $uid /var/run/danted.pid; fi   (code=exited, 
status=0/SUCCESS)

may 

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 863042 0.3.1-3
Bug #863042 [src:dehydrated] dehydrated: insecure file permissions by default
Marked as found in versions dehydrated/0.3.1-3.
> thanks
Stopping processing here.

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

Processed: Re: Bug#862742: Error report for filetea

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - unreproducible moreinfo
Bug #862742 [filetea] filetea: Wrong version of jQuery gets installed
Removed tag(s) moreinfo and unreproducible.

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

Bug#862742: Error report for filetea

[Alberto Garcia]

Control: tags -1 - unreproducible moreinfo

On Tue, May 23, 2017 at 07:14:39AM +, Hari Krishna wrote:

> ".live" method has been removed in jQuery version 1.9+. Please refer
> https://jquery.com/upgrade-guide/1.9/#live-removed

Yeah, I'm not sure how it worked last time I tried but I managed to
reproduce the problem now, thanks.

Berto

Bug#863195: golang-1.8 FTBFS: format_test.go:264: ParseInLocation(Feb 01 2013 AST, Baghdad) = 2013-02-01 00:00:00 +0000 AST, want 2013-02-01 00:00:00 +0300 +03

[Adrian Bunk]

Source: golang-1.8
Version: 1.8~rc3-1
Severity: serious
Control: fixed -1 1.8.1-1

https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/golang-1.8.html

...
ok  text/template   1.376s
ok  text/template/parse 0.048s
--- FAIL: TestParseInLocation (0.00s)
format_test.go:264: ParseInLocation(Feb 01 2013 AST, Baghdad) = 
2013-02-01 00:00:00 + AST, want 2013-02-01 00:00:00 +0300 +03
FAIL
FAILtime6.017s
ok  unicode 0.042s
ok  unicode/utf16   0.056s
...
FAILED
debian/rules:57: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 1

Processed: golang-1.8 FTBFS: format_test.go:264: ParseInLocation(Feb 01 2013 AST, Baghdad) = 2013-02-01 00:00:00 +0000 AST, want 2013-02-01 00:00:00 +0300 +03

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.8.1-1
Bug #863195 [src:golang-1.8] golang-1.8 FTBFS: format_test.go:264: 
ParseInLocation(Feb 01 2013 AST, Baghdad) = 2013-02-01 00:00:00 + AST, want 
2013-02-01 00:00:00 +0300 +03
Marked as fixed in versions golang-1.8/1.8.1-1.

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

Bug#857085: [Pkg-d-devel] Bug#857085: terminix FTBFS on armhf: Error executing /usr/bin/ldc2: Segmentation fault

[Julien Cristau]

On 05/23/2017 10:22 AM, Sylvestre Ledru wrote:
> Looks like similar to #862360?

That was an arm64 issue, terminix was failing on armhf instead.

Cheers,
Julien

Bug#857085: [Pkg-d-devel] Bug#857085: terminix FTBFS on armhf: Error executing /usr/bin/ldc2: Segmentation fault

[Sylvestre Ledru]

Looks like similar to #862360?
According to
https://buildd.debian.org/status/logs.php?pkg=terminix=armhf
the last 3 failures are only on hartmann

S


Le 23/05/2017 à 10:16, Matthias Klumpp a écrit :
> Cc Sylvestre Ledru as he maintains LLVM and might know best about
> changes done in the LLVM toolchain in Debian.
> 
> I uploaded an LDC to unstable yesterday with no changes but it's LLVM
> dependency changed to build against LLVM 4.0. With that version, the
> bug did not happen at all on the buildds.
> To be really certain it was gone, I used the harris porterbox again to
> see if it compiles the exact version of Terminix correctly now, and
> indeed it does.
> Then, I tried to build Terminix with the exact LDC version from
> Stretch before, and the bug also didn't show (4 builds in a row, just
> to be sure - the bug did *always* happen on harris before). I had a
> manually compiled version of LDC on that machine still, from previous
> attempts to debug the issue, that was compiled with LLVM 3.8 last, and
> building with that also didn't show the bug anymore.
> 
> So, LDC 1.1.1 built with LLVM 3.8, 3.9 and 4.0 in Stretch and Sid does
> not actually show this bug anymore. When jcristau removed LDC from
> Stretch (yes, I am still not happy with the amount of
> non-communication that was going on here!), the copy in there was
> actually already working, because something else in the toolchain
> changed and resolved the issue.
> 
> So, this of course might be a bug in LDC that now just doesn't get
> triggered anymore because something else has changed, but given the
> amount of work put in this bug to find the issue in LDC and the code
> where this bug actually happens in LDC, I think it's justified to
> assume that this is not actually a bug in LDC at all.
> 
> So, what's broken? LLVM 3.9 and 3.8 in Stretch received changes
> lately, but I do fail to see anything in the changelog that would have
> impacted this bug at all:
> 
> ```
> llvm-toolchain-3.9 (1:3.9.1-8) unstable; urgency=medium
> 
>   * Really fix "use versioned symbols" for llvm
> Thanks to Julien Cristau for the patch (Closes: #849098)
> 
>  -- Sylvestre Ledru   Tue, 25 Apr 2017 15:10:10 +0200
> 
> llvm-toolchain-3.9 (1:3.9.1-7) unstable; urgency=medium
> 
>   * Limit the archs where the ocaml binding is built
> Should fix the FTBFS
> Currently amd64 arm64 armel armhf i386
> 
>  -- Sylvestre Ledru   Sat, 15 Apr 2017 12:03:30 +0200
> 
> llvm-toolchain-3.9 (1:3.9.1-6) unstable; urgency=medium
> 
>   * Upload in unstable
>   * Bring back ocaml. Thanks to Cyril Soldani (Closes: #858626)
> 
>  -- Sylvestre Ledru   Fri, 14 Apr 2017 10:02:03 +0200
> 
> llvm-toolchain-3.9 (1:3.9.1-6~exp2) experimental; urgency=medium
> 
>   * Add override_dh_makeshlibs for the libllvm or liblldb versions
> Thanks to Julien Cristau for the patch
>   * change the min version of the libclang1 symbols to 1:3.9.1-6~
>   * Fix the symlink on scan-build-py
> 
>  -- Sylvestre Ledru   Tue, 28 Mar 2017 06:32:40 +0200
> 
> llvm-toolchain-3.9 (1:3.9.1-6~exp1) experimental; urgency=medium
> 
>   [ Rebecca N. Palmer ]
>   * Allow '!pointer' in OpenCL (Closes: #857623)
>   * Add missing liblldb symlink (Closes: #857683)
>   * Use versioned symbols (Closes: #848368)
> 
>  -- Sylvestre Ledru   Sun, 19 Mar 2017 10:12:03 +0100
> 
> llvm-toolchain-3.9 (1:3.9.1-5) unstable; urgency=medium
> 
>   * Fix the incorrect symlink to scan-build-py (Closes: #856869)
> 
>  -- Sylvestre Ledru   Sun, 12 Mar 2017 10:01:10 +0100
> ```
> 
> There were also GCC updates, and quite a bit of other stuff has
> changed as well, but since LDC now compiles the code correctly without
> being recompiled itself, I think it's safe to rule out any bug in GCC
> (as that's only used to build the C++ parts of LDC, and a
> wrong-codegen bug would have persisted in the binaries).
> 
> Not exactly sure where to go from here, but unless some major
> revelation about this bug happens, I am very inclined to just close it
> in a few weeks (and in case something like this happens again, we can
> file a new bug).
> 
> @Sylvestre: I know it's a long shot, but do you maybe know about
> anything in LLVM that could have altered the codegen in any way,
> recently in Stretch? From the changelogs, it doesn't really look like
> it, but maybe I am missing something. Context on this bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857085#41
> 
> Cheers,
> Matthias
> 

Bug#857085: [Pkg-d-devel] Bug#857085: terminix FTBFS on armhf: Error executing /usr/bin/ldc2: Segmentation fault

[Matthias Klumpp]

Cc Sylvestre Ledru as he maintains LLVM and might know best about
changes done in the LLVM toolchain in Debian.

I uploaded an LDC to unstable yesterday with no changes but it's LLVM
dependency changed to build against LLVM 4.0. With that version, the
bug did not happen at all on the buildds.
To be really certain it was gone, I used the harris porterbox again to
see if it compiles the exact version of Terminix correctly now, and
indeed it does.
Then, I tried to build Terminix with the exact LDC version from
Stretch before, and the bug also didn't show (4 builds in a row, just
to be sure - the bug did *always* happen on harris before). I had a
manually compiled version of LDC on that machine still, from previous
attempts to debug the issue, that was compiled with LLVM 3.8 last, and
building with that also didn't show the bug anymore.

So, LDC 1.1.1 built with LLVM 3.8, 3.9 and 4.0 in Stretch and Sid does
not actually show this bug anymore. When jcristau removed LDC from
Stretch (yes, I am still not happy with the amount of
non-communication that was going on here!), the copy in there was
actually already working, because something else in the toolchain
changed and resolved the issue.

So, this of course might be a bug in LDC that now just doesn't get
triggered anymore because something else has changed, but given the
amount of work put in this bug to find the issue in LDC and the code
where this bug actually happens in LDC, I think it's justified to
assume that this is not actually a bug in LDC at all.

So, what's broken? LLVM 3.9 and 3.8 in Stretch received changes
lately, but I do fail to see anything in the changelog that would have
impacted this bug at all:

```
llvm-toolchain-3.9 (1:3.9.1-8) unstable; urgency=medium

  * Really fix "use versioned symbols" for llvm
Thanks to Julien Cristau for the patch (Closes: #849098)

 -- Sylvestre Ledru   Tue, 25 Apr 2017 15:10:10 +0200

llvm-toolchain-3.9 (1:3.9.1-7) unstable; urgency=medium

  * Limit the archs where the ocaml binding is built
Should fix the FTBFS
Currently amd64 arm64 armel armhf i386

 -- Sylvestre Ledru   Sat, 15 Apr 2017 12:03:30 +0200

llvm-toolchain-3.9 (1:3.9.1-6) unstable; urgency=medium

  * Upload in unstable
  * Bring back ocaml. Thanks to Cyril Soldani (Closes: #858626)

 -- Sylvestre Ledru   Fri, 14 Apr 2017 10:02:03 +0200

llvm-toolchain-3.9 (1:3.9.1-6~exp2) experimental; urgency=medium

  * Add override_dh_makeshlibs for the libllvm or liblldb versions
Thanks to Julien Cristau for the patch
  * change the min version of the libclang1 symbols to 1:3.9.1-6~
  * Fix the symlink on scan-build-py

 -- Sylvestre Ledru   Tue, 28 Mar 2017 06:32:40 +0200

llvm-toolchain-3.9 (1:3.9.1-6~exp1) experimental; urgency=medium

  [ Rebecca N. Palmer ]
  * Allow '!pointer' in OpenCL (Closes: #857623)
  * Add missing liblldb symlink (Closes: #857683)
  * Use versioned symbols (Closes: #848368)

 -- Sylvestre Ledru   Sun, 19 Mar 2017 10:12:03 +0100

llvm-toolchain-3.9 (1:3.9.1-5) unstable; urgency=medium

  * Fix the incorrect symlink to scan-build-py (Closes: #856869)

 -- Sylvestre Ledru   Sun, 12 Mar 2017 10:01:10 +0100
```

There were also GCC updates, and quite a bit of other stuff has
changed as well, but since LDC now compiles the code correctly without
being recompiled itself, I think it's safe to rule out any bug in GCC
(as that's only used to build the C++ parts of LDC, and a
wrong-codegen bug would have persisted in the binaries).

Not exactly sure where to go from here, but unless some major
revelation about this bug happens, I am very inclined to just close it
in a few weeks (and in case something like this happens again, we can
file a new bug).

@Sylvestre: I know it's a long shot, but do you maybe know about
anything in LLVM that could have altered the codegen in any way,
recently in Stretch? From the changelogs, it doesn't really look like
it, but maybe I am missing something. Context on this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857085#41

Cheers,
Matthias

Bug#862297: Install fails if SMTP server is running on port 25, rendering console unuseable

[Michael Meskes]

On Wed, May 10, 2017 at 03:36:21PM -0500, John Goerzen wrote:
>   
> If you don't want citadel to provide these 
> services, turn them off in WebCit via: "Admin->System Preferences->Network".

It appears this is now the only way to make it not listen on port 25, meaning
it cannot be done during install. I'm not sure what the best way is to handle
this situation. Merging citadel-mta with citadel-server and make it conflict
with other mtas? And assume that people who want to run citadel with for
instance postfix need to manually change things and know how to handle with it?

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#861744: [Pkg-privacy-maintainers] Bug#861744: Bug#861744: Bug#861744: torbrowser-launcher: Should not be part of Stretch

[intrigeri]

Hi,

Holger Levsen:
> On Mon, May 22, 2017 at 12:12:39PM +0200, intrigeri wrote:
>> Fundamentally, do you disagree with the main point this bug report is
>> about i.e. "Should not be part of Stretch"?

> yes, somewhat, but I acknowledge that it's not my call.

>> And if you indeed do want to see this package in Stretch, how do you
>> plan to be involved on maintaining it via stable-security or
>> stable-updates?

> I don't plan to be involved.

> My trigger to send this mail are those mails generated through the failures
> on https://jenkins.debian.net/view/torbrowser/ - I get a daily mail that
> torbrowser-launcher in jessie is broken, and weekly mails about the breakage
> in wheezy-backports and jessie-backports.

> So of course what I shall do is to disable those mails to me, after all
> I'm one of the maintainers of jenkins.d.n :) But then I fear that
> torbrowser-launcher will bitrot even more…

Perhaps Ulrike would want to be the recipient of those email?

> So, in summary, yes, I disagree with this bugreport that I think that the
> package is supportable in stable and then I realized that I also question
> the plan to support it in stretch-backports, cause I'm very aware of the
> status of the package in stable-backports and oldstable-backports today.

Thanks for clarifying.

The way I see it:

1. We (collectively) did a poor job during the Jessie cycle; this
   applies to stable, backports and to some extent even to
   testing/sid.

2. AFAIK we won't have more resources to put into this package during
   the Stretch cycle, and quite the opposite actually: Holger took
   a step back, Ulrike has other priorities with stronger commitments,
   and I am not in a position to promise anything at this point.

With these 2 points in mind, the only reasonable course of action
I can think of is to *lower* the bar, i.e. stop trying to do
everything as it could be done with an infinite amount of resources:
surely this package is "supportable in stable" in theory, but that's
only theory until someone commits to do it… and actually does.

This is what Ulrike and I have been trying to do with this bug report.
Preventing the package from being in Stretch might not be the best way
to do it though; I would welcome other, realistic options (taking
#1 and #2 into account) if someone has any.

Note: even the "maintaining the package in backports" part is
something we should start doing very carefully IMO, not too early in
the Buster cycle, and only after making sure we are ready to maintain
it there for many years. It's similar to, and a bit cheaper than
maintaining the package in stable, so it'll be a good start and will
help us assess whether we're ready to have the package in Buster :)

> I realize that my position is not the most helpful one, but I thought and
> think that it's also not helpful to be aware of problems and stay silent on
> them.

Thanks.

Cheers,
-- 
intrigeri

Bug#862742: Error report for filetea

[Hari Krishna]

".live" method has been removed in jQuery version 1.9+. Please refer
https://jquery.com/upgrade-guide/1.9/#live-removed

On Tue, May 23, 2017 at 12:36 PM Hari Krishna 
wrote:

> I've installed filetea on Debian Unstable. Following are the versions of
> filetea and jquery installed.
> filetea0.1.16-3+b1 amd64
> libjs-jquery 3.1.1-2 all
>
> The error I am getting is attached. This is in concordance to the
> aforementioned bug.
>
> [image: Screen Shot 2017-05-23 at 12.29.36 PM.png]
>

Bug#862742: Error report for filetea

[Hari Krishna]

I've installed filetea on Debian Unstable. Following are the versions of
filetea and jquery installed.
filetea0.1.16-3+b1 amd64
libjs-jquery 3.1.1-2 all

The error I am getting is attached. This is in concordance to the
aforementioned bug.

[image: Screen Shot 2017-05-23 at 12.29.36 PM.png]