Bug#863673: [Pkg-freeradius-maintainers] Bug#863673: CVE-2017-9148: FreeRADIUS TLS resumption authentication bypass

[Salvatore Bonaccorso]

Hi Michael

Looks it was good we had first the issue settle a bit with respect for
a jessie(-security) upload:

On Thu, Jun 01, 2017 at 11:09:17PM +0200, Michael Stapelberg wrote:
> The original question of how to proceed still stands. I sent the patch in
> my previous message; do you want me to upload it, or do you want to upload
> it? If I should do it, let me state for the record that I have no idea what
> I’m doing (I never uploaded to anything but unstable/experimental).

I learned of http://www.openwall.com/lists/oss-security/2017/06/06/5 .
Can you confirm, is this assessment correct (for us as well in
stable)? We have a 2.2.5 based version in jessie, and according to
upstream for the EOL versions only 2.1.1 through 2.1.7 are affected by
the problem.

I do not have a way to test the vulnerability on my own.

Regards,
Salvatore

Processed: tagging 864319

[Debian Bug Tracking System]

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

> tags 864319 + upstream fixed-upstream
Bug #864319 [otrs] CVE-2017-9324
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#858269: marked as done (Fails to build, test try things not allowed as non-root)

[Debian Bug Tracking System]

Your message dated Wed, 07 Jun 2017 03:33:55 +
with message-id 
and subject line Bug#858269: fixed in docker.io 1.13.1~ds1-2
has caused the Debian Bug report #858269,
regarding Fails to build, test try things not allowed as non-root
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.)


-- 
858269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 1.13.0~ds1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Trying to build docker.io in a pbuilder seems to fails with quite a few
occurances of EPERM in the testsuite. I wonder how this could have build under
fakeroot or similar (anything not running as root really).

Relevant log:

---> Making bundle: test-unit (in bundles/1.13.0/test-unit)
Mon Mar 20 15:45:32 CET 2017
ok  github.com/docker/docker/api0.251s  coverage: 87.3% of statements
?   github.com/docker/docker/api/errors [no test files]
ok  github.com/docker/docker/api/server 0.015s  coverage: 6.5% of 
statements
ok  github.com/docker/docker/api/server/httputils   0.013s  coverage: 18.5% 
of statements
ok  github.com/docker/docker/api/server/middleware  0.012s  coverage: 19.0% 
of statements
?   github.com/docker/docker/api/server/router  [no test files]
?   github.com/docker/docker/api/server/router/build[no test files]
?   github.com/docker/docker/api/server/router/checkpoint   [no test files]
?   github.com/docker/docker/api/server/router/container[no test files]
?   github.com/docker/docker/api/server/router/image[no test files]
?   github.com/docker/docker/api/server/router/network  [no test files]
?   github.com/docker/docker/api/server/router/plugin   [no test files]
?   github.com/docker/docker/api/server/router/swarm[no test files]
?   github.com/docker/docker/api/server/router/system   [no test files]
?   github.com/docker/docker/api/server/router/volume   [no test files]
?   github.com/docker/docker/api/types  [no test files]
?   github.com/docker/docker/api/types/backend  [no test files]
?   github.com/docker/docker/api/types/blkiodev [no test files]
?   github.com/docker/docker/api/types/container[no test files]
?   github.com/docker/docker/api/types/events   [no test files]
ok  github.com/docker/docker/api/types/filters  0.005s  coverage: 96.7% 
of statements
?   github.com/docker/docker/api/types/mount[no test files]
?   github.com/docker/docker/api/types/network  [no test files]
ok  github.com/docker/docker/api/types/reference0.009s  coverage: 
100.0% of statements
?   github.com/docker/docker/api/types/registry [no test files]
ok  github.com/docker/docker/api/types/strslice 0.012s  coverage: 90.0% 
of statements
?   github.com/docker/docker/api/types/swarm[no test files]
ok  github.com/docker/docker/api/types/time 0.006s  coverage: 100.0% of 
statements
ok  github.com/docker/docker/api/types/versions 0.012s  coverage: 75.0% 
of statements
?   github.com/docker/docker/api/types/versions/v1p19   [no test files]
?   github.com/docker/docker/api/types/versions/v1p20   [no test files]
?   github.com/docker/docker/api/types/volume   [no test files]
--- FAIL: TestMakeRemoteContext (0.01s)
remote_test.go:185: Error when executing DetectContextFromRemoteURL: 
Error processing tar file(exit status 1): Error creating mount namespace before 
pivot: operation not permitted
--- FAIL: TestMakeTarSumContext (0.07s)
tarsum_test.go:212: Error when executing MakeTarSumContext: Error 
processing tar file(exit status 1): Error creating mount namespace before 
pivot: operation not permitted
FAIL
coverage: 64.2% of statements
FAILgithub.com/docker/docker/builder0.093s
--- FAIL: TestDispatch (0.03s)
evaluator_test.go:164: Error when creating tar context: Error 
processing tar file(exit status 1): Error creating mount namespace before 
pivot: operation not permitted
--- FAIL: TestEmptyDockerfile (0.01s)
internals_test.go:71: Error when creating tar context: Error processing 
tar file(exit status 1): Error creating mount namespace before pivot: operation 
not permitted
--- FAIL: TestSymlinkDockerfile (0.01s)
internals_test.go:71: Error when creating tar context: Error processing 
tar file(exit status 1): Error creating mount 

Bug#850952: marked as done (CVE-2016-9962)

[Debian Bug Tracking System]

Your message dated Wed, 07 Jun 2017 03:33:55 +
with message-id 
and subject line Bug#850952: fixed in docker.io 1.13.1~ds1-2
has caused the Debian Bug report #850952,
regarding CVE-2016-9962
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.)


-- 
850952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Severity: grave
Tags: security

Please see:
https://bugzilla.suse.com/show_bug.cgi?id=1012568
https://github.com/docker/docker/compare/v1.12.5...v1.12.6
https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5

Cheers,
Moritz

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 1.13.1~ds1-2

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

Debian distribution maintenance software
pp.
Tim Potter  (supplier of updated docker.io package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Jun 2017 11:43:14 +1000
Source: docker.io
Binary: docker.io vim-syntax-docker golang-github-docker-docker-dev 
golang-docker-dev docker-doc
Architecture: source all amd64
Version: 1.13.1~ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Tim Potter 
Changed-By: Tim Potter 
Description:
 docker-doc - Linux container runtime -- documentation
 docker.io  - Linux container runtime
 golang-docker-dev - Transitional package for golang-github-docker-docker-dev
 golang-github-docker-docker-dev - Externally reusable Go packages included 
with Docker
 vim-syntax-docker - Docker container engine - Vim highlighting syntax files
Closes: 850952 858269
Changes:
 docker.io (1.13.1~ds1-2) unstable; urgency=medium
 .
   * Make test suite pass by using assorted patches to fix or disable
 tests that don't work under pbuilder. (Closes: #858269)
   * Suppress some unfixable Lintian warnings.
   * Verify CVE-2016-9962 is fixed. (Closes: #850952)
Checksums-Sha1:
 452ddf852eb9fb6a597d4dc2a2744f2eba1978ea 6734 docker.io_1.13.1~ds1-2.dsc
 7186d5d85a53c792806ebcea286e60fd9970c7de 2981951 
docker.io_1.13.1~ds1.orig.tar.gz
 266ce8118cf3d8f6db7312f06f44675eb7d506e3 34140 
docker.io_1.13.1~ds1-2.debian.tar.xz
 f728617328bf4257d2d0f698519675aff601a9ed 657360 docker-doc_1.13.1~ds1-2_all.deb
 9899616cc3a22ed6807c11bbae35114f3c7bd072 658910 
docker.io-dbgsym_1.13.1~ds1-2_amd64.deb
 fb2e47c02ebe1b5a68294eacf60b6e08b3f42154 21928 
docker.io_1.13.1~ds1-2_amd64.buildinfo
 6d2d02f503c1462234607f3a8d9f079266abaa92 11026876 
docker.io_1.13.1~ds1-2_amd64.deb
 0309bb699e0470b972cbf7887187dcc2a5a2dbd0 62562 
golang-docker-dev_1.13.1~ds1-2_all.deb
 0d1e6bf8f9082c7a1c89f63b294ad88f5d5b5263 444212 
golang-github-docker-docker-dev_1.13.1~ds1-2_all.deb
 ee7499caa0c055a84c065b0106a61f67d15811de 63742 
vim-syntax-docker_1.13.1~ds1-2_all.deb
Checksums-Sha256:
 d2ad8d1f0ad53b6d76f15f2520ef1dbd9a475c13540e388d1d4efed7155fbae1 6734 
docker.io_1.13.1~ds1-2.dsc
 794dd083884aa964a76eb15a63c1c55a307c3a8867aaf1a0b86459608a6115b8 2981951 
docker.io_1.13.1~ds1.orig.tar.gz
 c73b56678e99f19ac3011dd9e817415a2d6cbf6d2b7e76e6aba3a539bd47baf0 34140 
docker.io_1.13.1~ds1-2.debian.tar.xz
 ae407ed410b3316346a049e7ef7621409a1a558417c5b4a8f386c372ae21ee7a 657360 
docker-doc_1.13.1~ds1-2_all.deb
 bdebcad550d7b05c8054c7ff015773477813d60e877dae3c0c0da65322787bf2 658910 
docker.io-dbgsym_1.13.1~ds1-2_amd64.deb
 5d551c5a2adffa4961138a3df1f4e3a3ffa326cb3023a88a84071d89ab52d9e9 21928 
docker.io_1.13.1~ds1-2_amd64.buildinfo
 f62c43081db2feef7b212228c70d9b14a4b58fe253e736bc8573eaac2d9e2bc2 11026876 
docker.io_1.13.1~ds1-2_amd64.deb
 

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 861552 1.13.1~ds1-1
Bug #861552 {Done: "Potter, Tim" } [docker.io] 
docker.io: FTBFS with latest golang-go.crypto
Marked as fixed in versions docker.io/1.13.1~ds1-1.
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 861552 1.13.0~ds1-1
Bug #861552 {Done: "Potter, Tim" } [docker.io] 
docker.io: FTBFS with latest golang-go.crypto
Marked as fixed in versions docker.io/1.13.0~ds1-1.
> fixed 835686 1.13.0~ds1-1
Bug #835686 {Done: "Potter, Tim" } [src:docker.io] 
docker.io: FTBFS: 
.gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot 
use _API_CreateContainer_Handler (type func(interface {}, 
"golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
error)) as type grpc.methodHandler in field value
Marked as fixed in versions docker.io/1.13.0~ds1-1.
>
End of message, stopping processing here.

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

Bug#855407: marked as done (docker.io: Dependency missmatch (docker.io 1.11.2~ds1-6 vs. containerd 0.2.3~git20161117.78.03e5862~ds1-1))

[Debian Bug Tracking System]

Your message dated Wed, 7 Jun 2017 02:06:34 +
with message-id <9036477b-b8ae-40f9-b03b-f0ff65086...@hpe.com>
and subject line 
has caused the Debian Bug report #855407,
regarding docker.io: Dependency missmatch (docker.io 1.11.2~ds1-6 vs. 
containerd 0.2.3~git20161117.78.03e5862~ds1-1)
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.)


-- 
855407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 1.11.2~ds1-6
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After the upgrade docker does not start anymore. Starting it manually produces
the following output:

sudo docker daemon --debug
DEBU[] docker group found. gid: 125
DEBU[] Listener created for HTTP on unix (/var/run/docker.sock)
INFO[] New containerd process, pid: 15658

DEBU[] containerd connection state change: CONNECTING
DEBU[] containerd connection state change: TRANSIENT_FAILURE
WARN[] containerd: low RLIMIT_NOFILE changing to max  current=1024 max=65536
DEBU[] containerd: read past events  count=0
DEBU[] containerd: supervisor runningcpus=4 memory=7826
runtime=runc runtimeArgs=[] stateDir="/run/containerd"
FATA[] bad listen address format
/var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address

This is caused by a very well known mismatch between docker and containerd of
current sid. See for example [1].

[1] https://github.com/docker/containerd/issues/299#issuecomment-240618355

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 
'testing-debug')
Architecture: amd64 (x86_64)

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

Versions of packages docker.io depends on:
ii  adduser  3.115
ii  containerd   0.2.3~git20161117.78.03e5862~ds1-1
ii  init-system-helpers  1.47
ii  iptables 1.6.0+snapshot20161117-5
ii  libapparmor1 2.11.0-2
ii  libc62.24-9
ii  libdevmapper1.02.1   2:1.02.137-1
ii  libsqlite3-0 3.16.2-2
ii  libsystemd0  232-15
ii  runc 0.1.1+dfsg1-2

Versions of packages docker.io recommends:
ii  ca-certificates  20161130
ii  cgroupfs-mount   1.3
ii  git  1:2.11.0-2
ii  xz-utils 5.2.2-1.2

Versions of packages docker.io suggests:
pn  aufs-tools   
pn  btrfs-progs  
ii  debootstrap  1.0.88
pn  docker-doc   
pn  rinse
pn  zfs-fuse | zfsutils  

-- Configuration Files:
/etc/default/docker changed:
DOCKER_OPTS="--storage-driver=devicemapper -H unix:///var/run/docker.sock"


-- no debconf information
--- End Message ---
--- Begin Message ---


signature.asc
Description: Message signed with OpenPGP using GPGMail
--- End Message ---

Bug#835686: marked as done (docker.io: FTBFS: .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot use _API_CreateContainer_Handler (type func(interface {}, "golang.org/x/net

[Debian Bug Tracking System]

Your message dated Wed, 7 Jun 2017 01:57:20 +
with message-id <2caad332-eea9-4f3f-b7cb-76a1f3562...@hpe.com>
and subject line 
has caused the Debian Bug report #835686,
regarding docker.io: FTBFS: 
.gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot 
use _API_CreateContainer_Handler (type func(interface {}, 
"golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
error)) as type grpc.methodHandler in field value
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.)


-- 
835686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docker.io
Version: 1.11.2~ds1-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> # build
> ./hack/make.sh dynbinary
> # WARNING! I don't seem to be running in a Docker container.
> # The result of this command might be an incorrect build, and will not be
> # officially supported.
> #
> # Try this instead: make all
> #
> 
> ---> Making bundle: dynbinary (in bundles/1.11.2/dynbinary)
> Building: bundles/1.11.2/dynbinary/docker-1.11.2
> # github.com/docker/containerd/api/grpc/types
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: 
> cannot use _API_CreateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1141: 
> cannot use _API_UpdateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1145: 
> cannot use _API_Signal_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1149: 
> cannot use _API_UpdateProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1153: 
> cannot use _API_AddProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1157: 
> cannot use _API_CreateCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1161: 
> cannot use _API_DeleteCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1165: 
> cannot use _API_ListCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1169: 
> cannot use _API_State_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: 
> cannot use _API_Stats_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: too 
> many errors
> debian/rules:60: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/docker.io_1.11.2~ds1-6_unstable.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 

Bug#861552: marked as done (docker.io: FTBFS with latest golang-go.crypto)

[Debian Bug Tracking System]

Your message dated Wed, 7 Jun 2017 01:55:30 +
with message-id 
and subject line Re: nmu: golang-go.crypto
has caused the Debian Bug report #861552,
regarding docker.io: FTBFS with latest golang-go.crypto
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.)


-- 
861552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Bug #859655 [3] has been fixed in unstable. This addresses a CVE bug, but also
requires all reverse build dependencies be rebuilt. After this package has
migrated to testing, there will be 62-64 packages that need rebuilding as well.

I have run build tests in both unstable and testing for this update using an
amd64 sbuild environment. For reference, the results:

testing:
  success: 62,  failed: 2 (being addressed)
unstable
  success: 107, failed: 7 (unchecked)


For the moment, I need the 107 packages in this list [1] to rebuilt in unstable.
... wanna build? :)

[1]

nmu mtail_0.0+git20161231.ae129e9-1 . ANY all . unstable . -m 'Rebuild against 
fixed golang-go.crypto; #859655'
nmu tendermint-ed25519_0.0~git20160723.0.1f52c6f-1 . ANY all . unstable . -m 
'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-rsc-letsencrypt_0.0~git20160929.0.76104d2-2 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-docker-leadership_0.1.0-1 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu sia_1.0.4-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-samalba-dockerclient_0.0~git20160531.0.a303626-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-golang-x-net-dev_1:0.0+git20160110.4fd4a9f-1 . ANY all . unstable . 
-m 'Rebuild against fixed golang-go.crypto; #859655'
nmu gocryptfs_1.2-2 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-blevesearch-bleve_0.5.0+git20170324.202.4702785f-1 . ANY all 
. unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-endophage-gotuf_0.0~git20151020.0.2df1c8e-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu cadvisor_0.25.0+dfsg-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu dnss_0.0~git20161126.0.162090e-1 . ANY all . unstable . -m 'Rebuild against 
fixed golang-go.crypto; #859655'
nmu golang-gopkg-dancannon-gorethink.v2_2.0.4-1 . ANY all . unstable . -m 
'Rebuild against fixed golang-go.crypto; #859655'
nmu mongo-tools_3.2.11-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-docker-go-connections_0.2.1+git20161115.12.4ccf312-1 . ANY 
all . unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-fsouza-go-dockerclient_0.0+git20160622-1 . ANY all . unstable 
. -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-go-macaron-macaron_1.2.1+git20170219.2.8be5635-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu rkt_1.21.0+dfsg-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-coreos-go-systemd_14-1 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu chasquid_0.01+git20161124.6479138-2 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu minica_1.0-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-pkg-sftp_0.0~git20160930.0.4d0e916-1 . ANY all . unstable . 
-m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-spf13-afero_0.0~git20161226.0.90dd71e-1 . ANY all . unstable 
. -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-azure-go-ntlmssp_0.0~git20160412.e0b63eb-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-opencontainers-image-spec_1.0.0~rc2+dfsg-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-couchbase-moss_0.0~git20170330.0.d2258a2-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu tendermint-go-p2p_0.0~git20170113.0.3d98f67-1 . ANY all . unstable . -m 
'Rebuild 

Bug#864298: marked as done (mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' does not name a type)

[Debian Bug Tracking System]

Your message dated Wed, 07 Jun 2017 00:51:09 +
with message-id 
and subject line Bug#864298: fixed in mariadb-10.1 10.1.24-3
has caused the Debian Bug report #864298,
regarding mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' does not name a type
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.)


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

https://buildd.debian.org/status/package.php?p=mariadb-10.1=unstable

mips and mipsel failed, mips64el is still building

In file included from /«PKGBUILDDIR»/storage/innobase/lock/lock0wait.cc:29:0:
/«PKGBUILDDIR»/storage/innobase/include/srv0mon.h:649:8: error: 'ib_mutex_t' 
does not name a type
 extern ib_mutex_t monitor_mutex;
^~


Andreas
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.24-3

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated mariadb-10.1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Jun 2017 02:23:44 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.24-3
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database, shared library
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.1 - MariaDB database client binaries
 mariadb-client-core-10.1 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.1 - MariaDB database server binaries
 mariadb-server-core-10.1 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 864298
Changes:
 mariadb-10.1 (10.1.24-3) unstable; urgency=medium
 .
   * Team upload.
   * Add mips-innobase-atomic.patch, fixing FTBFS on 32-bit mips*, thanks to
 James Cowgill.  (Closes: #864298)
Checksums-Sha1:
 1d9f787b4d63f3116fbff4bd6394e613672ae71c 4258 mariadb-10.1_10.1.24-3.dsc
 1d281ffa38ba385975f5aa9f770aef1be7925585 221552 
mariadb-10.1_10.1.24-3.debian.tar.xz
 b3f88c0b31a3e55872f3925e4922adf40d2b0d5a 8439 
mariadb-10.1_10.1.24-3_source.buildinfo

Bug#864298: mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' does not name a type

[Andreas Beckmann]

On Tue, 6 Jun 2017 17:53:32 +0100 James Cowgill  wrote:
> On 06/06/17 16:42, Andreas Beckmann wrote:
> > /«PKGBUILDDIR»/storage/innobase/include/srv0mon.h:649:8: error: 
> > 'ib_mutex_t' does not name a type

> The attached patch fixes this for me. The bug affects architectures
> without lock-free 64-bit atomics. I think these are: mips, mipsel,
> powerpc and m68k (mips64el is not affected).

Thanks, preparing an upload.


Andreas

Processed: tagging 832862

[Debian Bug Tracking System]

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

> tags 832862 - sid stretch
Bug #832862 {Done: gregor herrmann } 
[src:libgraph-writer-dsm-perl] libgraph-writer-dsm-perl: FTBFS: Tests failures
Bug #834468 {Done: gregor herrmann } 
[src:libgraph-writer-dsm-perl] libgraph-writer-dsm-perl: FTBFS: Failed 2/2 test 
programs. 0/0 subtests failed.
Removed tag(s) stretch and sid.
Removed tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Processed: tagging 832845

[Debian Bug Tracking System]

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

> tags 832845 - sid stretch
Bug #832845 {Done: Andreas Tille } [src:libbio-das-lite-perl] 
libbio-das-lite-perl: FTBFS: Tests failures
Removed tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Processed: Re: Bug#864296: throws StopIteration exception, then immediately dies

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #864296 {Done: Apollon Oikonomopoulos } 
[python-socketio-client] throws StopIteration exception, then immediately dies
Bug reopened
Ignoring request to alter fixed versions of bug #864296 to the same values 
previously set
> tags -1 upstream
Bug #864296 [python-socketio-client] throws StopIteration exception, then 
immediately dies
Added tag(s) upstream.
> severity -1 wishlist
Bug #864296 [python-socketio-client] throws StopIteration exception, then 
immediately dies
Severity set to 'wishlist' from 'grave'
> retitle -1 Misleading error message when encountering older protocol versions
Bug #864296 [python-socketio-client] throws StopIteration exception, then 
immediately dies
Changed Bug title to 'Misleading error message when encountering older protocol 
versions' from 'throws StopIteration exception, then immediately dies'.

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

Bug#864296: throws StopIteration exception, then immediately dies

[Apollon Oikonomopoulos]

Control: reopen -1
Control: tags -1 upstream
Control: severity -1 wishlist
Control: retitle -1 Misleading error message when encountering older protocol 
versions

On 23:45 Tue 06 Jun , Steinar H. Gunderson wrote:
> On Wed, Jun 07, 2017 at 12:37:27AM +0300, Apollon Oikonomopoulos wrote:
> > Looking at the message emitted by notification2.chess24.com ("Welcome to 
> > socket.io."), it uses the old 0.9 socket.io protocol. Major socket.io 
> > protocols are not backwards compatible and this version of 
> > python-socketio-client supports only the 1.x socket.io protocol.
> 
> Compatibility or not, throwing a random internal exception isn't a good 
> way of going about this, no? Shouldn't it then be some error message?
> 
> I agree that having an error message isn't RC, though.

Agreed. I'm reopening this as wishlist then.

Thanks!

Bug#864296: throws StopIteration exception, then immediately dies

[Steinar H. Gunderson]

On Wed, Jun 07, 2017 at 12:37:27AM +0300, Apollon Oikonomopoulos wrote:
> Looking at the message emitted by notification2.chess24.com ("Welcome to 
> socket.io."), it uses the old 0.9 socket.io protocol. Major socket.io 
> protocols are not backwards compatible and this version of 
> python-socketio-client supports only the 1.x socket.io protocol.

Compatibility or not, throwing a random internal exception isn't a good 
way of going about this, no? Shouldn't it then be some error message?

I agree that having an error message isn't RC, though.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#862576: etoys: Doesn't get beyond Squeak security key generation

[Bert Freudenberg]

@James: You can press alt-. (period) in Etoys to see what it's doing - this
should also create a SqueakDebug.log file which you can attach. However,
this sounds like a squeak-vm bug, not Etoys.

@Adrian: Thanks for finding a work-around!

​CC'ing Dave Lewis, our ​VM guy ...

​- Bert -​

On Tue, Jun 6, 2017 at 11:28 AM, Adrian Bunk  wrote:

> Control: reassign -1 squeak-vm 4.10.2.2614-4
> Control: affects -1 etoys
>
> On Sun, Jun 04, 2017 at 10:23:51PM +0200, Petter Reinholdtsen wrote:
> > This issue is going to cause etags to be removed from Stretch.  Anyone
> have any idea what is wrong?
>
> It seems better optimization in recent gcc versions exposes bugs
> in squeak-vm.
>
> The following workaround to use less optimization works for me:
>
> --- debian/rules.old2017-06-06 09:04:49.0 +
> +++ debian/rules2017-06-06 09:20:17.0 +
> @@ -6,6 +6,9 @@
>  # This has to be exported to make some magic below work.
>  export DH_OPTIONS
>
> +# workaround for #862576
> +export DEB_CFLAGS_MAINT_APPEND = -O1
> +
>  include /usr/share/cdbs/1/rules/upstream-tarball.mk
>  include /usr/share/cdbs/1/class/cmake.mk
>  include /usr/share/cdbs/1/rules/debhelper.mk
>
>
> This is a short-term workaround for stretch.
>
> Additionally adding -Wall gives tons of warnings for non-harmless
> issues, that's a good starting point when searching for a proper fix.
>
>
> > Happy hacking
> > Petter Reinholdtsen
>
> cu
> Adrian
>
> --
>
>"Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
>"Only a promise," Lao Er said.
>Pearl S. Buck - Dragon Seed
>
>

Bug#864296: marked as done (throws StopIteration exception, then immediately dies)

[Debian Bug Tracking System]

Your message dated Wed, 7 Jun 2017 00:37:27 +0300
with message-id <20170606213726.ydxjf3qc3r5eb...@marvin.dmesg.gr>
and subject line Re: Bug#864296: throws StopIteration exception, then 
immediately dies
has caused the Debian Bug report #864296,
regarding throws StopIteration exception, then immediately dies
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.)


-- 
864296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-socketio-client
Version: 0.6.5-0.1
Severity: grave

Hi,

Since upgrading to stretch, python-socketio-client no longer works for me at 
all.
I have code looking roughly this:

  #! /usr/bin/python
  from __future__ import print_function
  from socketIO_client import SocketIO
  from socketIO_client.exceptions import TimeoutError
  with SocketIO('https://notification2.chess24.com', 
transports=['xhr-polling'], verify=True) as socketIO:
pass

But all I get is this:

  DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTPS connection 
(1): notification2.chess24.com
  
DEBUG:requests.packages.urllib3.connectionpool:https://notification2.chess24.com:443
 "GET /socket.io/?EIO=3=polling=1496761595949-0 HTTP/1.1
  " 200 None
  Traceback (most recent call last):
File "./chess24.py", line 198, in 
  with SocketIO('https://notification2.chess24.com', verify=True) as 
socketIO:
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
331, in __init__
  resource, hurry_interval_in_seconds, **kw)
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
51, in __init__
  self._transport
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
59, in _transport
  self._engineIO_session = self._get_engineIO_session()
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
73, in _get_engineIO_session
  transport.recv_packet())
  StopIteration

It seems there is indeed a stray “break” on line 73 that isn't caught by any
exception handler. Downgrading to jessie immediately fixes the problem.
WebSockets vs. XHR transport doesn't make a difference.

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

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

Versions of packages python-socketio-client depends on:
ii  python2.7.13-2
ii  python-requests   2.12.4-1
ii  python-six1.10.0-3
ii  python-websocket  0.37.0-2

python-socketio-client recommends no packages.

python-socketio-client suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Hi,

On 17:18 Tue 06 Jun , Steinar H. Gunderson wrote:
> Package: python-socketio-client
> Version: 0.6.5-0.1
> Severity: grave
> 
> Hi,
> 
> Since upgrading to stretch, python-socketio-client no longer works for me at 
> all.
> I have code looking roughly this:
> 
>   #! /usr/bin/python
>   from __future__ import print_function
>   from socketIO_client import SocketIO
>   from socketIO_client.exceptions import TimeoutError
>   with SocketIO('https://notification2.chess24.com', 
> transports=['xhr-polling'], verify=True) as socketIO:
> pass

Thanks for the report!

Looking at the message emitted by notification2.chess24.com ("Welcome to 
socket.io."), it uses the old 0.9 socket.io protocol. Major socket.io 
protocols are not backwards compatible and this version of 
python-socketio-client supports only the 1.x socket.io protocol.

Unfortunately there's not much we can do about this since it's 
upstream's decision to only support 1.x at this time. You should instead 
use 0.5.7.2 (e.g. via pip) to talk to sites using the 0.9 protocol 
version.

I'm closing this bug since the incompatibility is documented in the 
package's changelog.

Regards,
Apollon--- End Message ---

Bug#864320: multiple critical problems booting

[gofloss gofloss]

Subject: base: multiple critical problems booting
Package: base
Justification: breaks the whole system
Severity: critical

Dear Maintainer,

below i describe multiple bugs in booting in jessie, which
might be relevant to stretch.

most are grave or critical.  many are accessibility-related.

please forgive any solecisms, such as putting more than one
thing into a bug report.  i am limited in computer use.

i provide suggested fixes where possible. however, i am just
an ordinary user.

===

notes:

just to be clear, i have never used lvm.

i have no /dev/mapper/sda7_crypt.  i do not
hibernate my desktop.

===

i want to document that my user experience booting in jessie
is broken.  separate bugs will not accomplish this.

it has taken me more than 3 months to debug this far -- 3
months of broken booting.  i still cannot boot to jessie.
(update much later: i finally was able to.)

the experience was unexpectedly hostile.  here are examples.

they are in sequence.

0.

i upgraded to jessie and found out that x won't work due to
modesetting something or other, unlike in wheezy.  turning
off or on modesetting introduces different bugs, which i
will not report here.  after months of debugging, i figured
out i might need nonfree firmware.  i tried forever to avoid
that, but nothing worked and nothing was documented.  so i
guessed that i need the firmware.

bug fix: document this in release notes

1.

rebooted, and discovered that the font was unreadably small,
unlike wheezy.

after difficulty, i figured out i had to change grub.  did
so.  that worked.  FOR A WHILE.

this is an accessibility bug.  it means that i cannot use
the computer.

bug fix: accessible defaults
bug fix: say how to change fonts

2.

booted.

after saying one line, it said "cryptsetup: lvm is not
available" repeatedly.

it was not possible to stop.

I HAVE NEVER RUN LVM.  i avoid lvm to avoid bugs.  and now
it is STILL causing bugs.  :(

to me as an ordinary user, this error message could be
improved to tell me what the problem is or give me a chance
to fix it.

there is nothing intelligible on the web about this.

bug fix: defensive programming
bug fix: meaningful error message please with sugar on top?
bug fix: ask the user for the partition
bug fix: don't assume it's lvm
bug fix: say what partition you tried

i don't think the ordinary user should be made to debug his
own initramfs.  or even know what an initramfs is.

2.5

update: [2017-02-11 Sat 12:41] it is absolutely confirmed
that the lvm is not available bug is intermittent.  just
now, i booted and got the bug.  then i booted again and it
was ok.  on previous occasions, it would not book.

3.

after those 3 months of debugging, i figured out that the
"lvm is not available" message means "you used
/dev/disk/by-id to specify partitions in fstab/crypttab and
we no longer support that in jessie, for unknown reasons".

i was told this was definitely fine to do.  furthermore, it
works on wheezy.

by-id notation is user friendly because you know what drive
you are on, unlike with uuid, and you don't have to screw
around with labels.  when you are new to debugging booting,
you want the information that by-id provides to fix
problems.  sometimes you have to reboot to find out what
drive it is.

arch wiki recommends it too.

however, on jessie, apparently the symlinks are not set up
at boot time.  but uuid and label symlinks are.

as of [2017-01-14 Sat] i do not use by-id, precisely because
of this bug.  HOWEVER, I STILL GET THE BUG.

bug fix: set up the symlinks.  why is by-id bad here?
bug fix: error message saying that /dev/disk/by-id symlink target not found
bug fix: document that they work or don't work
bug fix: offer a shell to set them up
bug fix: set them up as a special customer service if there is a bug
bug fix: have update-initramfs fail loudly instead of silently

4.

one of my goals is to set up a new drive as a backup -- with
accessibility fixed as much as possible -- in case there are
problems booting to my main drive.  however, this is
problematic.

with or without this:

i have had many, many, runins with update-initramfs.  i
finally settled on something that seemed to work:

# of course i looked for error messages
update-initramfs -u -k all &&
echo update-initramfs returned normal exit code. like i believe that.
# fixme update-grub should, but does not, create /boot/grub/grub.cfg
update-grub
# we do either grub-install or dpkg-reconfigure
# dpkg-reconfigure says what future upgrades should install to
echo enter argument to grub-install like /dev/sdb and sacrifice a goat:
grub-install `line`

maybe this is totally wrong.  i am an ordinary person just
trying to get my computer to work.  i tried dpkg-reconfigure
grub-pc also.

in order to put in the brittle, hardcoded partition syntax,
i did the above.

but guess what?  update-initramfs silently failed to change
initrd/conf/conf.d/cryptroot!

in the past it silently failed to create it at 

Bug#864319: CVE-2017-9324

[Moritz Muehlenhoff]

Package: otrs
Severity: grave
Tags: security

Hi,
details are sparse on this one, could you get in touch with upstream to
isolate this to the change in question?
https://www.otrs.com/security-advisory-2017-03-security-update-otrs-versions/

Cheers,
Moritz

Bug#864316: libapache2-mod-perl: FTBFS in jessie due to apache2 changes

[Niko Tyni]

Package: libapache2-mod-perl2
Version: 2.0.9~1624218-2+deb8u1
Severity: serious

As per

 
http://perl.debian.net/rebuild-logs/jessie/libapache2-mod-perl2_2.0.9~1624218-2+deb8u1/libapache2-mod-perl2_2.0.9~1624218-2+deb8u1_amd64-2017-06-05T19:42:17Z.build

this package currently fails to build in jessie.

  Test Summary Report
  ---
  t/apache/read.t   (Wstat: 0 Tests: 1 Failed: 1)
Failed test:  1
  t/filter/in_bbs_inject_header.t   (Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan.  You planned 36 tests but ran 0.
 
This is very similar to #849082 and was most probably caused by 

 apache2 (2.4.10-10+deb8u8) jessie-security; urgency=medium
 .
   * CVE-2016-8743: Enforce more HTTP conformance for request lines and
 request headers, to prevent response splitting and cache pollution
 by malicious clients or downstream proxies.
 If this causes problems with non-conforming clients, some checks can
 be relaxed by adding the new directive 'HttpProtocolOptions unsafe'
 to the configuration.
 Differently than the upstream 2.4.25 release which will also be in the
 Debian 9 (stretch) release, this update for Debian 8 (jessie) accepts
 underscores in host and domain names even while 'HttpProtocolOptions
 strict' is in effect.
 More information is available at
 http://httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions

so 370_http_syntax.patch and 380_inject_header_line_terminators.patch
from stretch/sid should help (untested).
-- 
Niko Tyni   nt...@debian.org

Bug#864188: libbpp-core2v5: symbols removed without soname bump

[Andreas Tille]

Hi Julien,

On Tue, Jun 06, 2017 at 09:43:22PM +0200, Julien Yann Dutheil wrote:
> Thanks a lot for your answers. I understand. We will increase the interface
> number.

Thanks.

> Is it ok to move the release tag on the git repository or is it
> better to make a new (distinct) one?

Please use a new release tag.  There might be other people who have
downloaded the current one and will not realise the fix you are
intending to do.
 
Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#864188: [Debian-med-packaging] Bug#864188: libbpp-core2v5: symbols removed without soname bump

[Julien Yann Dutheil]

Thanks a lot for your answers. I understand. We will increase the interface
number. Is it ok to move the release tag on the git repository or is it
better to make a new (distinct) one?

I apologize for the "dummy" questions.

Julien.

On Tue, Jun 6, 2017 at 9:14 PM, Vincent Danjean  wrote:

> Le 06/06/2017 à 12:47, Julien Yann Dutheil a écrit :
> > Dear Adrian,
> >
> > These functions are now inline in the corresponding .h files, but their
> > interfaces have not changed as far as I know. Does making a function
> > inline break the interface??
>
>   It is the difference between the API and the ABI. The API
> (interface for the programmer) did not change. But the ABI
> (binary interface) changed.
>   Both (API and ABI) are related but not tightly coupled.
>
>   The API has a backward incompatibility when sources that
> compiled with the previous API do not compile any more with
> the new API (this is not the case here).
>   The ABI has a backward incompatibility when a program/lib
> compiled against an old library will not work with the new
> library. This is the case here: a (previously compiled) program
> can try to use symbols that are not present anymore in the
> new library. Recompiling the program would workaround the
> problem (as the API did not change and the new compiled program
> will not try to use the symbols anymore) but the correct fix is
> to bump the soname so that the user knows without looking for
> bugs if the program and the library are compatible.
>
>   Regards,
> Vincent
>
> > J.
> >
> > -- Forwarded message --
> > From: *Adrian Bunk* >
> > Date: Tue, Jun 6, 2017 at 11:48 AM
> > Subject: Re: Bug#864188: libbpp-core2v5: symbols removed without soname
> bump
> > To: Julien Yann Dutheil >
> > Cc: Andreas Tille >,
> 864...@bugs.debian.org , GINDRAUD FRANCOIS
> >
> >
> >
> > On Tue, Jun 06, 2017 at 11:35:57AM +0200, Julien Yann Dutheil wrote:
> >> Dear Andreas, Adrian,
> >>...
> >> - This error actually revealed an interface breakdown (essentially due
> to
> >> our upgrade to c++11), and your suggestion is to reflect this change by
> >> increasing the interface number (which would result in a change in
> package
> >> name, such as libbpp-core2 -> libbpp-core3), am I correct?
> >
> > This ABI breakage is unrelated to the C++ version used.
> >
> > RandomTools::lnGamma() was removed from src/Bpp/Numeric/Random/
> RandomTools.cpp
> > TextTools::startsWith() was removed from src/Bpp/Text/TextTools.cpp
> > ApplicationTools::parameterExists() was removed from
> src/Bpp/App/ApplicationTools.cpp
> > ...
> >
> > Removing any such function breaks the ABI in an incompatible way,
> > and therefore requires a soname bump.
> >
> >> Best,
> >>
> >> Julien.
> >
> > cu
> > Adrian
> >
> >> On Mon, Jun 5, 2017 at 9:50 AM, Andreas Tille  > wrote:
> >>
> >> > Hi Julien,
> >> >
> >> > while I made a mistake to upload libbpp-core to unstable rather than
> >> > experimental as it was planed this has probably lead to spot a bug
> >> > earlier.  The problem is that the soversion needs to be bumped due to
> >> > the ABI change.
> >> >
> >> >$ objdump -p ./libbpp-core.so.2.0.4   | sed -n 's/^.*SONAME *//p'
> >> >libbpp-core.so.2
> >> >
> >> > I think you should bump the SOVERSION to reflect that change.
> >> >
> >> > Kind regards
> >> >
> >> >  Andreas.
> >> >
> >> > On Mon, Jun 05, 2017 at 02:42:58AM +0300, Adrian Bunk wrote:
> >> > > Package: libbpp-core2v5
> >> > > Version: 2.3.0-1~exp1
> >> > > Severity: serious
> >> > > Control: affects -1 libbpp-seq9v5 src:libbpp-phyl
> >> > >
> >> > > 2.3.0-1~exp1 in unstable (sic) removes symbols without changing
> soname,
> >> > > causing the following FTBFS in libbpp-phyl:
> >> > >
> >> > > https://tests.reproducible-builds.org/debian/rb-pkg/ <
> https://tests.reproducible-builds.org/debian/rb-pkg/>
> >> > unstable/amd64/libbpp-phyl.html
> >> > >
> >> > > ...
> >> > > [ 93%] Linking CXX executable test_bowker
> >> > > cd /build/1st/libbpp-phyl-2.2.0/obj-x86_64-linux-gnu/test &&
> >> > /usr/bin/cmake -E cmake_link_script CMakeFiles/test_bowker.dir/
> link.txt
> >> > --verbose=1
> >> > > /usr/bin/c++   -Wall -Wshadow -Weffc++ -Wconversion  -Wl,-z,relro
> >> > CMakeFiles/test_bowker.dir/test_bowker.cpp.o  -o test_bowker
> -rdynamic
> >> > -lbpp-seq -lbpp-core -L../src -lbpp-phyl
> >> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
> libbpp-seq.so:
> >> > undefined reference to `bpp::RandomTools::lnGamma(double)'
> >> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
> libbpp-seq.so:
> >> > undefined reference to `bpp::TextTools::startsWith(
> >> > std::__cxx11::basic_string >> > std::allocator > 

Bug#864188: [Debian-med-packaging] Bug#864188: libbpp-core2v5: symbols removed without soname bump

[Vincent Danjean]

Le 06/06/2017 à 12:47, Julien Yann Dutheil a écrit :
> Dear Adrian,
> 
> These functions are now inline in the corresponding .h files, but their
> interfaces have not changed as far as I know. Does making a function
> inline break the interface??

  It is the difference between the API and the ABI. The API
(interface for the programmer) did not change. But the ABI
(binary interface) changed.
  Both (API and ABI) are related but not tightly coupled.

  The API has a backward incompatibility when sources that
compiled with the previous API do not compile any more with
the new API (this is not the case here).
  The ABI has a backward incompatibility when a program/lib
compiled against an old library will not work with the new
library. This is the case here: a (previously compiled) program
can try to use symbols that are not present anymore in the
new library. Recompiling the program would workaround the
problem (as the API did not change and the new compiled program
will not try to use the symbols anymore) but the correct fix is
to bump the soname so that the user knows without looking for
bugs if the program and the library are compatible.

  Regards,
Vincent

> J.
> 
> -- Forwarded message --
> From: *Adrian Bunk* >
> Date: Tue, Jun 6, 2017 at 11:48 AM
> Subject: Re: Bug#864188: libbpp-core2v5: symbols removed without soname bump
> To: Julien Yann Dutheil  >
> Cc: Andreas Tille >, 
> 864...@bugs.debian.org , GINDRAUD FRANCOIS 
> >
> 
> 
> On Tue, Jun 06, 2017 at 11:35:57AM +0200, Julien Yann Dutheil wrote:
>> Dear Andreas, Adrian,
>>...
>> - This error actually revealed an interface breakdown (essentially due to
>> our upgrade to c++11), and your suggestion is to reflect this change by
>> increasing the interface number (which would result in a change in package
>> name, such as libbpp-core2 -> libbpp-core3), am I correct?
> 
> This ABI breakage is unrelated to the C++ version used.
> 
> RandomTools::lnGamma() was removed from src/Bpp/Numeric/Random/RandomTools.cpp
> TextTools::startsWith() was removed from src/Bpp/Text/TextTools.cpp
> ApplicationTools::parameterExists() was removed from 
> src/Bpp/App/ApplicationTools.cpp
> ...
> 
> Removing any such function breaks the ABI in an incompatible way,
> and therefore requires a soname bump.
> 
>> Best,
>>
>> Julien.
> 
> cu
> Adrian
> 
>> On Mon, Jun 5, 2017 at 9:50 AM, Andreas Tille > > wrote:
>>
>> > Hi Julien,
>> >
>> > while I made a mistake to upload libbpp-core to unstable rather than
>> > experimental as it was planed this has probably lead to spot a bug
>> > earlier.  The problem is that the soversion needs to be bumped due to
>> > the ABI change.
>> >
>> >$ objdump -p ./libbpp-core.so.2.0.4   | sed -n 's/^.*SONAME *//p'
>> >libbpp-core.so.2
>> >
>> > I think you should bump the SOVERSION to reflect that change.
>> >
>> > Kind regards
>> >
>> >  Andreas.
>> >
>> > On Mon, Jun 05, 2017 at 02:42:58AM +0300, Adrian Bunk wrote:
>> > > Package: libbpp-core2v5
>> > > Version: 2.3.0-1~exp1
>> > > Severity: serious
>> > > Control: affects -1 libbpp-seq9v5 src:libbpp-phyl
>> > >
>> > > 2.3.0-1~exp1 in unstable (sic) removes symbols without changing soname,
>> > > causing the following FTBFS in libbpp-phyl:
>> > >
>> > > https://tests.reproducible-builds.org/debian/rb-pkg/ 
>> > > 
>> > unstable/amd64/libbpp-phyl.html
>> > >
>> > > ...
>> > > [ 93%] Linking CXX executable test_bowker
>> > > cd /build/1st/libbpp-phyl-2.2.0/obj-x86_64-linux-gnu/test &&
>> > /usr/bin/cmake -E cmake_link_script CMakeFiles/test_bowker.dir/link.txt
>> > --verbose=1
>> > > /usr/bin/c++   -Wall -Wshadow -Weffc++ -Wconversion  -Wl,-z,relro
>> > CMakeFiles/test_bowker.dir/test_bowker.cpp.o  -o test_bowker -rdynamic
>> > -lbpp-seq -lbpp-core -L../src -lbpp-phyl
>> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
>> > undefined reference to `bpp::RandomTools::lnGamma(double)'
>> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
>> > undefined reference to `bpp::TextTools::startsWith(
>> > std::__cxx11::basic_string> > std::allocator > const&, std::__cxx11::basic_string> > std::char_traits, std::allocator > const&)'
>> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
>> > undefined reference to `bpp::ApplicationTools::
>> > parameterExists(std::__cxx11::basic_string> > std::allocator > const&, std::map> > std::char_traits, std::allocator >, 
>> > std::__cxx11::basic_string> > std::char_traits, std::allocator >,
>> > 

Processed: fixed 864299 in 0.31-1

[Debian Bug Tracking System]

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

> fixed 864299 0.31-1
Bug #864299 [src:libclass-c3-perl] libclass-c3-perl: FTBFS due to base.pm 
changes in July 2016
Marked as fixed in versions libclass-c3-perl/0.31-1.
> thanks
Stopping processing here.

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

Bug#863686: [f5b05df] Fix for Bug#863686 committed to git

[Anton Gladky]

tags 863686 + pending
thanks

Hello,

 The following change has been committed for this bug by
 Anton Gladky  on Tue, 6 Jun 2017 20:45:03 +0200.
 The fix will be in the next upload. 
=
Import Debian changes 4.2+dfsg1-4

freemat (4.2+dfsg1-4) unstable; urgency=medium

  [ Graham Inggs ]
  * [d62fa98] Fix Vcs-Git URI

  [ Anton Gladky ]
  * [51ba71b] Disable LLVM-support. (Closes: #863686)
=

You can check the diff of the fix at:

;a=commitdiff;h=f5b05df

Bug#863686: [f5b05df] Fix for Bug#863686 committed to git

[Anton Gladky]

tags 863686 + pending
thanks

Hello,

 The following change has been committed for this bug by
 Anton Gladky  on Tue, 6 Jun 2017 20:45:03 +0200.
 The fix will be in the next upload. 
=
Import Debian changes 4.2+dfsg1-4

freemat (4.2+dfsg1-4) unstable; urgency=medium

  [ Graham Inggs ]
  * [d62fa98] Fix Vcs-Git URI

  [ Anton Gladky ]
  * [51ba71b] Disable LLVM-support. (Closes: #863686)
=

You can check the diff of the fix at:

;a=commitdiff;h=f5b05df

Processed: [f5b05df] Fix for Bug#863686 committed to git

[Debian Bug Tracking System]

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

> tags 863686 + pending
Bug #863686 {Done: Anton Gladky } [freemat] freemat: fails to 
start with llvm error
Ignoring request to alter tags of bug #863686 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: [f5b05df] Fix for Bug#863686 committed to git

[Debian Bug Tracking System]

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

> tags 863686 + pending
Bug #863686 {Done: Anton Gladky } [freemat] freemat: fails to 
start with llvm error
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: retitle 863290 to src:linux: no warning that btrfs RAID5/6 is broken

[Debian Bug Tracking System]

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

> retitle 863290 src:linux: no warning that btrfs RAID5/6 is broken
Bug #863290 {Done: Ben Hutchings } [src:linux] src:linux: 
no warning that btrfs RAID5/6 is buggered up
Changed Bug title to 'src:linux: no warning that btrfs RAID5/6 is broken' from 
'src:linux: no warning that btrfs RAID5/6 is buggered up'.
> thanks
Stopping processing here.

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

Processed: tagging 860064

[Debian Bug Tracking System]

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

> tags 860064 + stretch-ignore
Bug #860064 {Done: Simon Kelley } [dnsmasq] [dnsmasq] 
startup failue when dns-root-data installed
Bug #863896 {Done: Simon Kelley } [dnsmasq] dnsmasq: 
systemd appends junk to the dnsmasq commandline
Added tag(s) stretch-ignore.
Added tag(s) stretch-ignore.
> thanks
Stopping processing here.

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

Bug#864309: Bug: #864309: pgloader: crashes on startup if libssl1.0.2 is not installed

[Michael Banck]

On Tue, Jun 06, 2017 at 07:54:41PM +0200, Michael Banck wrote:
> If I install libssl1.0.2, it no longer crashes.  
[...]
> Maybe a band-aid for stretch would be to manually add the libssl1.0.2
> Depends?

Probably still the best idea.

> Just rebuilding the package does not help, as libssl1.0.2 get dragged
> in via Build-Depends.  I tried to rebuild cl-plus-ssl as well, but
> that does not help either.

If I patch cl-plus-ssl's src/reload.lisp to also try libssl1.1 and
rebuild pgloader against that, it no longer crashes.  Though I just
smoke-tested it, no idea whether SSL support would actually work then...


Michael 

Processed: limit source to gdm3, tagging 781535

[Debian Bug Tracking System]

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

> limit source gdm3
Limiting to bugs with field 'source' containing at least one of 'gdm3'
Limit currently set to 'source':'gdm3'

> tags 781535 + pending
Bug #781535 [libgdm1] libgdm1: missing Breaks+Replaces: gdm
Ignoring request to alter tags of bug #781535 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: limit source to gdm3, tagging 781535

[Debian Bug Tracking System]

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

> limit source gdm3
Limiting to bugs with field 'source' containing at least one of 'gdm3'
Limit currently set to 'source':'gdm3'

> tags 781535 + pending
Bug #781535 [libgdm1] libgdm1: missing Breaks+Replaces: gdm
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#864025: marked as done (ganeti-instance-debootstrap: illegal option for fgrep)

[Debian Bug Tracking System]

Your message dated Tue, 06 Jun 2017 18:03:38 +
with message-id 
and subject line Bug#864025: fixed in ganeti-instance-debootstrap 0.16-2.1
has caused the Debian Bug report #864025,
regarding ganeti-instance-debootstrap: illegal option for fgrep
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.)


-- 
864025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ganeti-instance-debootstrap
Severity: grave
Version: 0.16-2

Dear Maintainer,

stretch system with ganeti-2.15 and g-i-d, trying to setup a new debian
vm I get:

Sat Jun  3 13:21:27 2017 * running the instance OS create scripts...
Failure: command execution error:
Could not add os for instance XY on node AA: OS create script failed (exited 
with exit code 1), last lines in the log file:
grep: unrecognized option '--no-reread'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
This disk is currently in use - repartitioning is probably a bad idea.
Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no-reread flag to suppress this check.

sfdisk: Use the --force flag to overrule all checks.


It does seem to be in common.sh, where the fgrep call wants a "--"
before the "--no-reread" search pattern, that was all it took to make it
work again.

-- 
bye, Joerg
--- End Message ---
--- Begin Message ---
Source: ganeti-instance-debootstrap
Source-Version: 0.16-2.1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated ganeti-instance-debootstrap 
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, 06 Jun 2017 17:00:39 +0100
Source: ganeti-instance-debootstrap
Binary: ganeti-instance-debootstrap
Architecture: source all
Version: 0.16-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Chris Lamb 
Description:
 ganeti-instance-debootstrap - debootstrap-based instance OS definition for 
ganeti
Closes: 864025
Changes:
 ganeti-instance-debootstrap (0.16-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "illegal option for fgrep" error by using "--" to escape the search
 needle. (Closes: #864025)
Checksums-Sha1:
 e92bf41bfcfca15974e74c21f05d6c6a340abca2 2220 
ganeti-instance-debootstrap_0.16-2.1.dsc
 c0664650f18de7f34f315ba5c22b278c9793341a 23020 
ganeti-instance-debootstrap_0.16.orig.tar.gz
 1d6357e2694743683a738cf4c7eaaf38fcb75014 8576 
ganeti-instance-debootstrap_0.16-2.1.debian.tar.xz
 9ca45ce65aaa147530563b6fded13d616619a698 19706 
ganeti-instance-debootstrap_0.16-2.1_all.deb
 5bfc1ca8bc9a386bb83bfe5b876ddc1cd7109219 6027 
ganeti-instance-debootstrap_0.16-2.1_amd64.buildinfo
Checksums-Sha256:
 941b99d64ec0bd902dd6604afa3d0435d6a23b1311f7491b615d2c7edcdbd390 2220 
ganeti-instance-debootstrap_0.16-2.1.dsc
 4338cdcbebafbab8b4b20ff503fa890a040f15f1ac36219d38840359cf6bed16 23020 
ganeti-instance-debootstrap_0.16.orig.tar.gz
 c7efc2c3483851a997108eb70a12798663e9ee4bc75fa9dd5663d92184470ec7 8576 
ganeti-instance-debootstrap_0.16-2.1.debian.tar.xz
 94fb7d760b86df2b9fa795899fe3c046b14ba59f3948c7072c7887ecd050ade5 19706 
ganeti-instance-debootstrap_0.16-2.1_all.deb
 d8af26c885bccfeaa94650c33fc5c87315096a71cd2cab96e5dbe89a1bed1e75 6027 
ganeti-instance-debootstrap_0.16-2.1_amd64.buildinfo
Files:
 c58ca046de20507c46f1bba9a58bd584 2220 admin extra 
ganeti-instance-debootstrap_0.16-2.1.dsc
 dac2d619a15567919e1064effcf4691f 23020 admin extra 
ganeti-instance-debootstrap_0.16.orig.tar.gz
 631cf39266c0f1ca66931570f846cd05 8576 admin extra 
ganeti-instance-debootstrap_0.16-2.1.debian.tar.xz
 81f1e190423f8238996f8ed4876ee84a 19706 admin extra 
ganeti-instance-debootstrap_0.16-2.1_all.deb
 b8141eb64e972e6f0d5d9df024520d36 6027 admin extra 
ganeti-instance-debootstrap_0.16-2.1_amd64.buildinfo

Bug#864309: pgloader: crashes on startup if libssl1.0.2 is not installed

[Michael Banck]

Package: pgloader
Version: 3.3.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

in a fresh stretch chroot, apt-get installing pgloader and running it
without arguments results in:

(stretch_amd64-dchroot)mbanck@barriere:~$ pgloader

debugger invoked on a SIMPLE-ERROR in thread
#:
  Error opening shared object "libssl.so.1.0.2":
  libssl.so.1.0.2: cannot open shared object file: No such file or
directory.

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE   ] Skip this shared object and continue.
  1: [RETRY  ] Retry loading this shared object.
  2: [CHANGE-PATHNAME] Specify a different pathname to load the shared
object from.

(SB-SYS:DLOPEN-OR-LOSE #S(SB-ALIEN::SHARED-OBJECT :PATHNAME
#P"libssl.so.1.0.2" :NAMESTRING "libssl.so.1.0.2" :HANDLE NIL :DONT-SAVE
NIL))
0] (SB-EXT:EXIT)
(stretch_amd64-dchroot)mbanck@barriere:~$ 

If I install libssl1.0.2, it no longer crashes.  Just rebuilding the
package does not help, as libssl1.0.2 get dragged in via Build-Depends.
I tried to rebuild cl-plus-ssl as well, but that does not help either.

Maybe a band-aid for stretch would be to manually add the libssl1.0.2
Depends?


Michael

Processed: tagging 859421

[Debian Bug Tracking System]

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

> # tagged sid, -ignore is unnecessary
> tags 859421 - stretch-ignore
Bug #859421 {Done: Alastair McKinstry } [src:python-tz] 
src:python-tz: Please orphan python-tz
Removed tag(s) stretch-ignore.
> thanks
Stopping processing here.

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

Bug#864025: ganeti-instance-debootstrap: illegal option for fgrep

[Chris Lamb]

Hi,

> ganeti-instance-debootstrap: illegal option for fgrep

< ivodd> lamby: ganeti-instance-debootstrap is in delayed, if you
 want us to consider it, upload it now, otherwise it will be
 too late

I've therefore run:


  $ dcut reschedule ganeti-instance-debootstrap_0.16-2.1_amd64.changes 0-day


Regards,

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

Processed: Re: Bug#864269: radvd: FTFBS in sid (but not in stretch)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #864269 [radvd] radvd: FTFBS in sid (but not in stretch)
Added tag(s) confirmed.

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

Bug#864269: radvd: FTFBS in sid (but not in stretch)

[Geert Stappers]

Control: tags -1 confirmed

Seen FTBFS
attached a concept patch  
thrusdaynight (UTC+2)  I have time for it.


Groeten
Geert Stappers
-- 
Leven en laten leven
>From 793b5598af236b11c5df0171289295e6c0536870 Mon Sep 17 00:00:00 2001
From: Geert Stappers 
Date: Tue, 6 Jun 2017 18:54:57 +0200
Subject: [PATCH] in a hurry

---
 debian/patches/fixFTBFSpoc | 12 
 debian/patches/series  |  1 +
 2 files changed, 13 insertions(+)
 create mode 100644 debian/patches/fixFTBFSpoc

diff --git a/debian/patches/fixFTBFSpoc b/debian/patches/fixFTBFSpoc
new file mode 100644
index 000..9aac086
--- /dev/null
+++ b/debian/patches/fixFTBFSpoc
@@ -0,0 +1,12 @@
+Index: radvd/configure.ac
+===
+--- radvd.orig/configure.ac
 radvd/configure.ac
+@@ -156,7 +156,6 @@ AC_HEADER_STDC
+ AC_CHECK_HEADERS( \
+ 	getopt.h \
+ 	ifaddrs.h \
+-	linux/if_arp.h \
+ 	machine/limits.h \
+ 	machine/param.h \
+ 	net/if_arp.h \
diff --git a/debian/patches/series b/debian/patches/series
index 33ebe29..b4d79dd 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,4 +2,5 @@
 # reminder TODO remove unused patches
 #  so cleaning up the debian/patches/ directory
 #
+fixFTBFSpoc
 kfreebsd.patch
-- 
2.11.0

Bug#864298: mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' does not name a type

[James Cowgill]

Control: tags -1 upstream patch
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-13009

On 06/06/17 16:42, Andreas Beckmann wrote:
> Package: mariadb-10.1
> Version: 10.1.24-2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> https://buildd.debian.org/status/package.php?p=mariadb-10.1=unstable
> 
> mips and mipsel failed, mips64el is still building
> 
> In file included from /«PKGBUILDDIR»/storage/innobase/lock/lock0wait.cc:29:0:
> /«PKGBUILDDIR»/storage/innobase/include/srv0mon.h:649:8: error: 'ib_mutex_t' 
> does not name a type
>  extern ib_mutex_t monitor_mutex;
> ^~

The attached patch fixes this for me. The bug affects architectures
without lock-free 64-bit atomics. I think these are: mips, mipsel,
powerpc and m68k (mips64el is not affected).

Thanks,
James
--- a/storage/innobase/include/os0sync.h
+++ b/storage/innobase/include/os0sync.h
@@ -37,6 +37,7 @@ Created 9/6/1995 Heikki Tuuri
 
 #include "univ.i"
 #include "ut0lst.h"
+#include "sync0types.h"
 
 /** CPU cache line size */
 #ifdef __powerpc__


signature.asc
Description: OpenPGP digital signature

Processed: Bug#864298 mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' does not name a type

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream patch
Bug #864298 [mariadb-10.1] mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' 
does not name a type
Added tag(s) upstream and patch.
> forwarded -1 https://jira.mariadb.org/browse/MDEV-13009
Bug #864298 [mariadb-10.1] mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' 
does not name a type
Set Bug forwarded-to-address to 'https://jira.mariadb.org/browse/MDEV-13009'.

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

Bug#864302: request-tracker4: FTBFS due to base.pm changes in July 2016

[Dominic Hargreaves]

Source: request-tracker4
Version: 4.2.8-3+deb8u1
Severity: serious
Justification: ftbfs
Tags: jessie patch

As per

http://perl.debian.net/rebuild-logs/jessie/request-tracker4_4.2.8-3+deb8u1/request-tracker4_4.2.8-3+deb8u1_amd64-2017-06-05T20:11:50Z.build

building this package was broken by the changes in perl to fix the '.'
in @INC vulnerability.

The breakage doesn't appear in the version in unstable, though it's
not immediately obvious why. There is a proposed fix in

https://anonscm.debian.org/cgit/pkg-request-tracker/request-tracker4.git/log/?h=ntyni/jessie-base-pm

Dominic.

Processed: Re: ganeti-instance-debootstrap: illegal option for fgrep

[Debian Bug Tracking System]

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

> tags 864025 + pending patch
Bug #864025 [ganeti-instance-debootstrap] ganeti-instance-debootstrap: illegal 
option for fgrep
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#864025: ganeti-instance-debootstrap: illegal option for fgrep

[Chris Lamb]

tags 864025 + pending patch
thanks

I've uploaded ganeti-instance-debootstrap 0.16-2.1 to DELAYED/5:
  
  ganeti-instance-debootstrap (0.16-2.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Fix "illegal option for fgrep" error by using "--" to escape the search
  needle. (Closes: #864025)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for ganeti-instance-debootstrap-0.16 ganeti-instance-debootstrap-0.16

 changelog  |8 
 patches/fix-sfdisk-BLKRRPART.patch |8 
 2 files changed, 12 insertions(+), 4 deletions(-)

diff -Nru ganeti-instance-debootstrap-0.16/debian/changelog 
ganeti-instance-debootstrap-0.16/debian/changelog
--- ganeti-instance-debootstrap-0.16/debian/changelog   2017-05-03 
14:44:54.0 +0100
+++ ganeti-instance-debootstrap-0.16/debian/changelog   2017-06-06 
17:00:39.0 +0100
@@ -1,3 +1,11 @@
+ganeti-instance-debootstrap (0.16-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "illegal option for fgrep" error by using "--" to escape the search
+needle. (Closes: #864025)
+
+ -- Chris Lamb   Tue, 06 Jun 2017 17:00:39 +0100
+
 ganeti-instance-debootstrap (0.16-2) unstable; urgency=medium
 
   * Skip newer sfdisk's check using the BLKRRPART ioctl (Closes: #853167).
diff -Nru 
ganeti-instance-debootstrap-0.16/debian/patches/fix-sfdisk-BLKRRPART.patch 
ganeti-instance-debootstrap-0.16/debian/patches/fix-sfdisk-BLKRRPART.patch
--- ganeti-instance-debootstrap-0.16/debian/patches/fix-sfdisk-BLKRRPART.patch  
2017-05-03 14:44:54.0 +0100
+++ ganeti-instance-debootstrap-0.16/debian/patches/fix-sfdisk-BLKRRPART.patch  
2017-06-06 17:00:39.0 +0100
@@ -11,15 +11,15 @@
 Forwarded: no
 Last-Update: 2017-05-03
 Bug-Debian: https://bugs.debian.org/853167
 a/common.sh.in
-+++ b/common.sh.in
-@@ -94,6 +94,11 @@
+--- ganeti-instance-debootstrap-0.16.orig/common.sh.in
 ganeti-instance-debootstrap-0.16/common.sh.in
+@@ -94,6 +94,11 @@ format_disk0() {
if sfdisk --help | grep -q -e '--cylinders'; then
  ARGS="-H 64 -S 32 -u S --Linux"
fi
 +  # Some versions of sfdisk need to be told to skip checking using ioctl(dev,
 +  # BLKRRPART), as this always fails for DRBD and LVM devices.
-+  if sfdisk --help | fgrep -q '--no-reread'; then
++  if sfdisk --help | fgrep -q -- '--no-reread'; then
 +ARGS="--no-reread $ARGS"
 +  fi
sfdisk $ARGS --quiet "$1" <

Processed: Re: ganeti-instance-debootstrap: illegal option for fgrep

[Debian Bug Tracking System]

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

> tags 864025 + patch
Bug #864025 [ganeti-instance-debootstrap] ganeti-instance-debootstrap: illegal 
option for fgrep
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#864025: ganeti-instance-debootstrap: illegal option for fgrep

[Chris Lamb]

tags 864025 + patch
thanks

Hi,

This was a regression from ganeti-instance-debootstrap (0.16-2):

  3   * Skip newer sfdisk's check using the BLKRRPART ioctl (Closes: #853167).
  4 This check will always fail with non-partitionable devices, such as DRBD
  5 and LVM, completely breaking disk partitioning. Thanks to Martin Weinelt
  6  for testing and feedback!


Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/patches/fix-sfdisk-BLKRRPART.patch 
b/debian/patches/fix-sfdisk-BLKRRPART.patch
index 040fd1f..fd54ba8 100644
--- a/debian/patches/fix-sfdisk-BLKRRPART.patch
+++ b/debian/patches/fix-sfdisk-BLKRRPART.patch
@@ -19,7 +19,7 @@ Bug-Debian: https://bugs.debian.org/853167
fi
 +  # Some versions of sfdisk need to be told to skip checking using ioctl(dev,
 +  # BLKRRPART), as this always fails for DRBD and LVM devices.
-+  if sfdisk --help | fgrep -q '--no-reread'; then
++  if sfdisk --help | fgrep -q -- '--no-reread'; then
 +ARGS="--no-reread $ARGS"
 +  fi
sfdisk $ARGS --quiet "$1" <

Bug#864299: libclass-c3-perl: FTBFS due to base.pm changes in July 2016

[Dominic Hargreaves]

Source: libclass-c3-perl
Version: 0.26-1
Severity: serious
Justification: ftbfs
Tags: jessie patch

As per

http://perl.debian.net/rebuild-logs/jessie/libclass-c3-perl_0.26-1/libclass-c3-perl_0.26-1_amd64-2017-06-05T20:11:30Z.build

building this package was broken by the changes in perl to fix the '.'
in @INC vulnerability.

The package was fixed in unstable by the upstream version 0.31 by 
commit

https://anonscm.debian.org/cgit/pkg-perl/packages/libclass-c3-perl.git/commit/?id=47a367d0930224e392be71678bddff77e4ddee82

Dominic.

Processed: base.pm for jessie

[Debian Bug Tracking System]

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

> unarchive 832862
Bug #832862 {Done: gregor herrmann } 
[src:libgraph-writer-dsm-perl] libgraph-writer-dsm-perl: FTBFS: Tests failures
Bug #834468 {Done: gregor herrmann } 
[src:libgraph-writer-dsm-perl] libgraph-writer-dsm-perl: FTBFS: Failed 2/2 test 
programs. 0/0 subtests failed.
Unarchived Bug 832862
Unarchived Bug 834468
> tags 832862 + jessie
Bug #832862 {Done: gregor herrmann } 
[src:libgraph-writer-dsm-perl] libgraph-writer-dsm-perl: FTBFS: Tests failures
Bug #834468 {Done: gregor herrmann } 
[src:libgraph-writer-dsm-perl] libgraph-writer-dsm-perl: FTBFS: Failed 2/2 test 
programs. 0/0 subtests failed.
Added tag(s) jessie.
Added tag(s) jessie.
> unarchive 832866
Bug #832866 {Done: gregor herrmann } 
[src:libclass-c3-xs-perl] libclass-c3-xs-perl: FTBFS: Tests failures
Unarchived Bug 832866
> tags 832866 + jessie
Bug #832866 {Done: gregor herrmann } 
[src:libclass-c3-xs-perl] libclass-c3-xs-perl: FTBFS: Tests failures
Added tag(s) jessie.
> # libclass-c3-perl had no prior bug, was fixed in May 2016
> unarchive 832845
Bug #832845 {Done: Andreas Tille } [src:libbio-das-lite-perl] 
libbio-das-lite-perl: FTBFS: Tests failures
Unarchived Bug 832845
> tags 832845 + jessie
Bug #832845 {Done: Andreas Tille } [src:libbio-das-lite-perl] 
libbio-das-lite-perl: FTBFS: Tests failures
Added tag(s) jessie.
>
End of message, stopping processing here.

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

Bug#864298: mariadb-10.1: FTBFS on mips*: error: 'ib_mutex_t' does not name a type

[Andreas Beckmann]

Package: mariadb-10.1
Version: 10.1.24-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/package.php?p=mariadb-10.1=unstable

mips and mipsel failed, mips64el is still building

In file included from /«PKGBUILDDIR»/storage/innobase/lock/lock0wait.cc:29:0:
/«PKGBUILDDIR»/storage/innobase/include/srv0mon.h:649:8: error: 'ib_mutex_t' 
does not name a type
 extern ib_mutex_t monitor_mutex;
^~


Andreas

Bug#864296: throws StopIteration exception, then immediately dies

[Steinar H. Gunderson]

Package: python-socketio-client
Version: 0.6.5-0.1
Severity: grave

Hi,

Since upgrading to stretch, python-socketio-client no longer works for me at 
all.
I have code looking roughly this:

  #! /usr/bin/python
  from __future__ import print_function
  from socketIO_client import SocketIO
  from socketIO_client.exceptions import TimeoutError
  with SocketIO('https://notification2.chess24.com', 
transports=['xhr-polling'], verify=True) as socketIO:
pass

But all I get is this:

  DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTPS connection 
(1): notification2.chess24.com
  
DEBUG:requests.packages.urllib3.connectionpool:https://notification2.chess24.com:443
 "GET /socket.io/?EIO=3=polling=1496761595949-0 HTTP/1.1
  " 200 None
  Traceback (most recent call last):
File "./chess24.py", line 198, in 
  with SocketIO('https://notification2.chess24.com', verify=True) as 
socketIO:
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
331, in __init__
  resource, hurry_interval_in_seconds, **kw)
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
51, in __init__
  self._transport
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
59, in _transport
  self._engineIO_session = self._get_engineIO_session()
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line 
73, in _get_engineIO_session
  transport.recv_packet())
  StopIteration

It seems there is indeed a stray “break” on line 73 that isn't caught by any
exception handler. Downgrading to jessie immediately fixes the problem.
WebSockets vs. XHR transport doesn't make a difference.

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

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

Versions of packages python-socketio-client depends on:
ii  python2.7.13-2
ii  python-requests   2.12.4-1
ii  python-six1.10.0-3
ii  python-websocket  0.37.0-2

python-socketio-client recommends no packages.

python-socketio-client suggests no packages.

-- debconf-show failed

Bug#864276: [request-tracker-maintainers] Bug#864276: rt4-extension-sla: not installable in sid

[Dominic Hargreaves]

On Tue, Jun 06, 2017 at 08:41:39AM +0200, Ralf Treinen wrote:
> Package: rt4-extension-sla
> Version: 1.04-2
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-uninstallable
> 
> Hi,
> 
> rt4-extension-sla is not installable in sid on any architecture. This is
> the case since at least 2017-01-21. The reason is that it depends on
> request-tracker4 (< 4.4.0), however the version of that package in sid
> is 4.4.1-3.

Thanks. As per #851986 this was left in to aid backporting(?) but the
reasoning in that bug is not too clear. Joost, any objections to just
removing this?

Dominic.

Processed: libraw

[Debian Bug Tracking System]

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

> fixed 864183 libraw/0.18.2-1
Bug #864183 [src:libraw] CVE-2017-6886 CVE-2017-6887
Marked as fixed in versions libraw/0.18.2-1.
> forwarded 864183 https://github.com/LibRaw/LibRaw/issues/90
Bug #864183 [src:libraw] CVE-2017-6886 CVE-2017-6887
Set Bug forwarded-to-address to 'https://github.com/LibRaw/LibRaw/issues/90'.
> thanks
Stopping processing here.

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

Processed: Re: lepton: Upstream requires sse4.1 in Intel platform which is not available in all build machines

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #864012 [lepton] lepton: Upstream requires sse4.1 in Intel platform which 
is not available in all build machines
Severity set to 'serious' from 'normal'

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

Bug#864159: marked as done (mariadb-server-10.1: needs Conflicts: cqrlog (<< 1.9.0-5~))

[Debian Bug Tracking System]

Your message dated Tue, 06 Jun 2017 13:06:49 +
with message-id 
and subject line Bug#864159: fixed in mariadb-10.1 10.1.24-2
has caused the Debian Bug report #864159,
regarding mariadb-server-10.1: needs Conflicts: cqrlog (<< 1.9.0-5~)
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.)


-- 
864159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-server-5.6
Version: 5.6.27-2
Severity: important

cqrlog's bug #801755: "cqrlog: prompting due to modified conffiles which
were not modified by the user: /etc/apparmor.d/usr.sbin.mysqld" was just
fixed by using /etc/apparmor.d/local/usr.sbin.mysqld for its additions
instead of modifying the conffile owned by mysql-server-5.6.

It needs a little cooperation from mysql-server-5.6 to ensure cqrlog
gets upgraded first (it will undo the conffile modifications on
upgrades) and mysql afterwards (with an again pristine usr.sbin.mysqld).

Please add a versioned Conflicts: cqrlog (<< 1.9.0-5~) to
mysql-server-5.6. Yes, this must be a versioned Conflicts, you may add a
lintian override for this. A Breaks is not sufficient since it would
allow to just deconfigure the cqrlog package, but we must ensure that it
is either removed or upgraded (the conffile modifications will be undone
in both cases) before mysql gets upgraded.

I verified in piuparts with a patched mysql-server that this actually
fixes the upgrade path of cqrlog.


Andreas
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.24-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated mariadb-10.1 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, 06 Jun 2017 14:29:52 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.24-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Ondřej Surý 
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database, shared library
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.1 - MariaDB database client binaries
 mariadb-client-core-10.1 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.1 - MariaDB database server binaries
 mariadb-server-core-10.1 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB 

Bug#855344: marked as done (thunderbird: retains mails from removed IMAP accounts)

[Debian Bug Tracking System]

Your message dated Tue, 06 Jun 2017 13:00:39 +
with message-id 
and subject line Bug#855344: fixed in icedove 1:52.1.1-1
has caused the Debian Bug report #855344,
regarding thunderbird: retains mails from removed IMAP accounts
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.)


-- 
855344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:45.7.1-1
Severity: grave
Tags: security
Justification: user security hole

Hi!
I'm afraid that, similar to the current debian-devel thread about leaving
old (possibly subsequently purged) mails on .icedove->.thunderbird
transition, Icedove/Thunderbird leaves the whole IMAP cache on the disk
when you delete an account.  It is completely gone from the user interface,
so any user who doesn't look "under the hood" will be wrongly assured the
data is actually gone.  Then, when that user crosses a border or is under
investigation for any reason, such mails are the first target government
agents look for.

And this is not a hypothetical situation, I just found such sensitive
"deleted" mails on my disk.  Fortunately, this didn't end in a police raid
-- this machine is a desktop not a laptop, but then, using Tor is a sure
proof I must run a commercial kiddie-porn site and donate the proceeds to
ISIS -- or, far worse, offer tech advice to someone who thinks bad about the
ruling party.

As you seem to have doubts about gravity of such scenarios, I'll mail you an
anonymized rough outline of the contents privately.  For other readers of
this bug report: it's nothing child porn level bad, but it still could land
someone I (vaguely) know in jail.  (For agents reading this bug report:
these mails are now, to the best of my knowledge, actually purged, including
backups -- and it was nothing subversive.)


As it takes a simple look at the filesystem to find this, I assume makers of
forensics software already know of this bug (perhaps even not noticing
anything is amiss -- they don't use the user interface), thus I'm reporting
it openly.


Meow!
-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.0-rc8-debug+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages thunderbird depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7
ii  libasound21.1.3-5
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-9
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.14-1.0nosystemd1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:7-20170129-1
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-1
ii  libgtk2.0-0   2.24.31-2
ii  libhunspell-1.4-0 1.4.1-2+b1
ii  libicu57  57.1-5
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libpango-1.0-01.40.3-3
ii  libpangocairo-1.0-0   1.40.3-3
ii  libpangoft2-1.0-0 1.40.3-3
ii  libpixman-1-0 0.34.0-1
ii  libsqlite3-0  3.16.2-2
ii  libstartup-notification0  0.12-4
ii  libstdc++67-20170129-1
ii  libvpx4   1.6.1-2
ii  libx11-6  2:1.6.4-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-7
ii  lightning 1:45.7.1-1

Versions of packages thunderbird suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.15-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: icedove
Source-Version: 1:52.1.1-1

We believe that the bug you reported is fixed in the latest version of
icedove, which is due to be installed in the Debian FTP 

Bug#861480: marked as done (ImportError: No module named QtWebKit)

[Debian Bug Tracking System]

Your message dated Tue, 06 Jun 2017 13:00:39 +
with message-id 
and subject line Bug#861480: fixed in icedove 1:52.1.1-1
has caused the Debian Bug report #861480,
regarding ImportError: No module named QtWebKit
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.)


-- 
861480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: series60-remote
Version: 0.4.80+dfsg.1-2
Severity: critical



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

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

Versions of packages series60-remote depends on:
ii  libqt4-sql-mysql   4:4.8.7+dfsg-11
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-11
ii  python 2.7.13-2
ii  python-bluez   0.22-1
ii  python-qt4 4.11.4+dfsg-2+b1
ii  python-qt4-sql 4.11.4+dfsg-2+b1

Versions of packages series60-remote recommends:
ii  python-matplotlib  2.0.0+dfsg1-2
ii  python-obexftp 0.24-5+b1

series60-remote suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: icedove
Source-Version: 1:52.1.1-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated icedove 
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: Sat, 03 Jun 2017 19:54:43 +0200
Source: icedove
Binary: thunderbird icedove thunderbird-dev icedove-dev thunderbird-dbg 
icedove-dbg lightning iceowl-extension calendar-google-provider 
thunderbird-l10n-all thunderbird-l10n-ar thunderbird-l10n-ast 
thunderbird-l10n-be thunderbird-l10n-bg thunderbird-l10n-bn-bd 
thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs thunderbird-l10n-da 
thunderbird-l10n-de thunderbird-l10n-dsb thunderbird-l10n-el 
thunderbird-l10n-en-gb thunderbird-l10n-es-ar thunderbird-l10n-es-es 
thunderbird-l10n-et thunderbird-l10n-eu thunderbird-l10n-fi thunderbird-l10n-fr 
thunderbird-l10n-fy-nl thunderbird-l10n-ga-ie thunderbird-l10n-gd 
thunderbird-l10n-gl thunderbird-l10n-he thunderbird-l10n-hr 
thunderbird-l10n-hsb thunderbird-l10n-hu thunderbird-l10n-hy-am 
thunderbird-l10n-id thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-ko thunderbird-l10n-lt 
thunderbird-l10n-nb-no thunderbird-l10n-nl thunderbird-l10n-nn-no 
thunderbird-l10n-pa-in
 thunderbird-l10n-pl thunderbird-l10n-pt-br thunderbird-l10n-pt-pt 
thunderbird-l10n-rm thunderbird-l10n-ro thunderbird-l10n-ru thunderbird-l10n-si 
thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq thunderbird-l10n-sr 
thunderbird-l10n-sv-se thunderbird-l10n-ta-lk thunderbird-l10n-tr 
thunderbird-l10n-uk thunderbird-l10n-vi thunderbird-l10n-zh-cn 
thunderbird-l10n-zh-tw icedove-l10n-all icedove-l10n-ar icedove-l10n-ast 
icedove-l10n-be icedove-l10n-bg icedove-l10n-bn-bd icedove-l10n-br 
icedove-l10n-ca icedove-l10n-cs icedove-l10n-da icedove-l10n-de 
icedove-l10n-dsb icedove-l10n-el icedove-l10n-en-gb icedove-l10n-es-ar 
icedove-l10n-es-es icedove-l10n-et icedove-l10n-eu icedove-l10n-fi 
icedove-l10n-fr icedove-l10n-fy-nl icedove-l10n-ga-ie icedove-l10n-gd 
icedove-l10n-gl icedove-l10n-he icedove-l10n-hr icedove-l10n-hsb 
icedove-l10n-hu icedove-l10n-hy-am icedove-l10n-id icedove-l10n-is 
icedove-l10n-it icedove-l10n-ja icedove-l10n-kab icedove-l10n-ko icedove-l10n-lt
 icedove-l10n-nb-no icedove-l10n-nl icedove-l10n-nn-no icedove-l10n-pa-in 
icedove-l10n-pl icedove-l10n-pt-br icedove-l10n-pt-pt icedove-l10n-rm 
icedove-l10n-ro icedove-l10n-ru icedove-l10n-si icedove-l10n-sk icedove-l10n-sl 
icedove-l10n-sq icedove-l10n-sr icedove-l10n-sv-se icedove-l10n-ta-lk 
icedove-l10n-tr icedove-l10n-uk icedove-l10n-vi icedove-l10n-zh-cn 

Bug#864159: [debian-mysql] fixing #864159 in mariadb-10.1

[Andreas Beckmann]

On 2017-06-06 14:42, Ondřej Surý wrote:
> Hi Andreas,
> 
> done, uploaded as 10.1.24-2; Sorry I missed that, but it happens for me
> with the reassigned bugs, that I miss the emails about those.

Thanks!

I hadn't realized that you made all the recent mariadb uploads,
otherwise I would have pinged you as well ...

The bts had some hickup when reopening/cloning/reassigning the bug (Don
knows about it, but does not really know why that happened), so my
additional commentary didn't come after the reassigment ...


Andreas

Bug#864159: [debian-mysql] fixing #864159 in mariadb-10.1

[Ondřej Surý]

Hi Andreas,

done, uploaded as 10.1.24-2; Sorry I missed that, but it happens for me
with the reassigned bugs, that I miss the emails about those.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Tue, Jun 6, 2017, at 14:01, Otto Kekäläinen wrote:
> Hello!
> 
> I don't have time right now to fix this one, so if you can help,
> please do so. Please coordinate on
> pkg-mysql-ma...@lists.alioth.debian.org what you intend to do, so that
> others (e.g. Ondrej) don't do conflicting changes with you.
> 
> 
> mariadb-server-10.1: needs Conflicts: cqrlog (<< 1.9.0-5~)
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864159
> 
> 
> 2017-06-06 1:03 GMT+03:00 Andreas Beckmann :
> > Hi Otto,
> >
> > do you want to fix #864159 for stretch? Should I take care of it?
> >
> >
> > Andreas
> 
> ___
> pkg-mysql-maint mailing list
> pkg-mysql-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#862742: marked as done (filetea: Wrong version of jQuery gets installed)

[Debian Bug Tracking System]

Your message dated Tue, 06 Jun 2017 12:20:26 +
with message-id 
and subject line Bug#862742: fixed in filetea 0.1.16-4
has caused the Debian Bug report #862742,
regarding filetea: Wrong version of jQuery gets installed
to be marked as done.

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

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


-- 
862742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: filetea
Version: 0.1.16-3+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The package uses the function live which has been removed in jQuery 1.9.
The source in the upstream depends on 1.7.2 and no version has been
mentioned in the control file of the packaging for libjs-jquery. Hence
the latest version(3.1.1) is fetched which breaks it and makes it unusable
for everyone.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: filetea
Source-Version: 0.1.16-4

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

Debian distribution maintenance software
pp.
Alberto Garcia  (supplier of updated filetea 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, 06 Jun 2017 12:01:04 +0300
Source: filetea
Binary: filetea
Architecture: source
Version: 0.1.16-4
Distribution: unstable
Urgency: high
Maintainer: Alberto Garcia 
Changed-By: Alberto Garcia 
Description:
 filetea- Web-based file sharing system
Closes: 862742 864101
Changes:
 filetea (0.1.16-4) unstable; urgency=high
 .
   * debian/control:
 - Replace build dependency on libgcrypt11-dev with libgcrypt20-dev
   (Closes: #864101).
 - Update Homepage URL.
 - Update Standards-Version to 3.9.8 (no changes).
 - Depend on lsb-base (>= 3.0-6).
   * debian/patches/jquery-compat.patch:
 - Make Filetea work with libjs-jquery 3.x (Closes: #862742).
   * debian/patches/systemd.patch:
 - Add missing Documentation key.
   * debian/copyright:
 - Update copyright years.
Checksums-Sha1:
 8118c0ce712e5ce7939a0557bf2e0406e37725eb 1816 filetea_0.1.16-4.dsc
 2e9491f65c2661c01ce04d33dc3552a0297848e7 8452 filetea_0.1.16-4.debian.tar.xz
 c3d6b2acbdf6a1328f065146e40bd36f4d951dfd 6231 filetea_0.1.16-4_source.buildinfo
Checksums-Sha256:
 5f01c5d6d8b7c0841f9b8a563da74f28b4cab536282639aead59b6548080268b 1816 
filetea_0.1.16-4.dsc
 3390f548c2cbe4b2d53d92f721242454c3f22abe98ac9630b43f4b0fae725491 8452 
filetea_0.1.16-4.debian.tar.xz
 d82fedc3b55c791657abfd7efd96d2735cc7c09c52c28d82aaa703b864cbb3f8 6231 
filetea_0.1.16-4_source.buildinfo
Files:
 e7f67593532b21977a1069ea2d5a5743 1816 net optional filetea_0.1.16-4.dsc
 3bcfd15d465907079da012d54e3c2f74 8452 net optional 
filetea_0.1.16-4.debian.tar.xz
 da6a89582f00dcbeb1fddf307bfcbfdb 6231 net optional 
filetea_0.1.16-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEG4Kq8pR5Ln9Vhk8+vjIZrz7UE0EFAlk2l+MACgkQvjIZrz7U
E0EcORAApWE29S30pOwSz8F9IELuIud+oJJxjWykZzFYThX9I9vfhd3K2Ls0x66v
MFULhdp1ZXGwJf0K31BMi6FeY8uhnkQ1mcNbBPQa1Et6d45hUSOZQLpJrBbQi7fq
viOrjnyR8pF+twPOLOFRCNYnJ/Ztqj/rRmE4yVJz+WgPzN8giMVHbL582dvlwe/4
0pcV5GMsOdgI+Y84ixBM3fJqbcJMAgDZLKTUdFrfaTD7Tql18VhkEvUl8i4a4dox
Hp+EAy/GYwU3ZxYCY5iN+zasu/B8KzYz18pQG5AB7zQ/LeCh1h/+UfKvyu50Fcm0
b3sSzIxeKvmTu71f5f4L0ov4Ms83jJVB3p/nqqIgufWTKh6jvWOsmmmW47Kt788c
QClSdl+bz/kiyeLjYpORkHdxqudNZl5nPd2bO/Wk4BBcqjYfTqd3lGTJ/t66TqM3
ydoenq9mp0OJ4wnI+kk9duHupA9QvWS9eVSAMz941+DF5RuE5mQUYZ/844TcDpFf
EY5riIr4MwBfTwFq+IZqs8qn5DZP3l+ZJt4CTucLAooKJSkELv4r+D32PvoobPkP
z9l9Ah+ZsKUzxOrCg99vFsG7gsWrZSPI8JLXs2426eVE8zuh8Hak7vO1fAFi01d1
DgkWXgBDEHFTJelpnjBJH00Hh+nvkIGEfhnmDJqowmZM9ciJ870=
=JY4M
-END PGP SIGNATURE End Message ---

Bug#863802: systemd unit breaks ferm in some setups in jessie->stretch upgrade

[Moritz Muehlenhoff]

On Wed, May 31, 2017 at 02:08:35PM +0200, Alexander Wirt wrote:
> Someone should decide, which is not me. Therefore I don't think this is
> grave.

Feel free to downgrade. I've only marked it RC due to possible jessie->
stretch upgrade problems.

I'm attaching a service unit which waits for name resolution (for people
rebuilding the package or dropping that one into /etc/systemd/system)

Cheers,
Moritz
[Unit]
Description=ferm firewall configuration
After=nss-lookup.target network-online.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/etc/init.d/ferm start
ExecReload=/etc/init.d/ferm reload
ExecStop=/etc/init.d/ferm stop

[Install]
WantedBy=multi-user.target

Bug#864183: [Pkg-phototools-devel] Bug#864183: CVE-2017-6886 CVE-2017-6887

[David Bremner]

Moritz Muehlenhoff  writes:

> Source: libraw
> Severity: grave
> Tags: security
>
> Please see
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6886
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6887

I started to look at this, but gave up on (me) fixing it for the initial
stretch release.

1. Between the version in stretch and the version being patched,
upstream has run the 15k line dcraw.c through clang-format, which means
the patch referenced in the CVE would need to move about 2k lines to
apply :(.

2. As I started to try to hand apply upstream d7c3d2cb460be10, I
realized there are security related changes from some other commit

-  if (len > 256 || !(cbuf = (char *)malloc(len)))
+  if (len < 1 || len > 256 || !(cbuf = (char *)malloc(len)))

in particular the (len > 256) is not present in the code in stretch.

It seems to come from upstream commit 8d0935 [3 files changed, 208
insertions(+), 154 deletions(-)], which also would need hand applying,
or some other cleverness.

Bug#864016: marked as done (dns-root-data: Upgrade breaks dnsmasq)

[Debian Bug Tracking System]

Your message dated Tue, 06 Jun 2017 11:18:38 +
with message-id 
and subject line Bug#864016: fixed in dns-root-data 2017041102
has caused the Debian Bug report #864016,
regarding dns-root-data: Upgrade breaks dnsmasq
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.)


-- 
864016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dns-root-data
Version: 2017041101
Severity: serious

Upgraded dns-root-data should declare "Breaks: dnsmasq (<< 2.77-1~)",
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863896#15

Regards,
robert


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (200, 'unstable')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dns-root-data
Source-Version: 2017041102

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated dns-root-data 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, 06 Jun 2017 12:54:28 +0200
Source: dns-root-data
Binary: dns-root-data
Architecture: source
Version: 2017041102
Distribution: unstable
Urgency: high
Maintainer: Debian DNS Maintainers 
Changed-By: Ondřej Surý 
Description:
 dns-root-data - DNS root data including root zone and DNSSEC key
Closes: 864016
Changes:
 dns-root-data (2017041102) unstable; urgency=high
 .
   [ Robert Edmonds ]
   * Change DS creation to omit TTL and use spaces instead of tabs
 (Closes: #864016)
Checksums-Sha1:
 081dacc5c75b027d0dfa561113f9692b89ff4954 1905 dns-root-data_2017041102.dsc
 141238e10aa94d20751b91f4d5362f6565e1ab30 14364 dns-root-data_2017041102.tar.xz
 e5dd2dc5bc5a3676d639a89381a5b1a75b0e1fa7 5946 
dns-root-data_2017041102_amd64.buildinfo
Checksums-Sha256:
 c121cfc7f20f73e18eb813d088c6b556c9f2a4c985ac08cd3e584b67cf106f38 1905 
dns-root-data_2017041102.dsc
 5c8d8a434e957a8c3b9e8e4ad92575157fa200a592201abb466a55d031973f55 14364 
dns-root-data_2017041102.tar.xz
 b7ad622bb887182c6381ab3415b21fca25e81b2162c4276dc12f929c48b07d08 5946 
dns-root-data_2017041102_amd64.buildinfo
Files:
 6e5ac6266ccc00c52ff20f63e7b9 1905 misc optional 
dns-root-data_2017041102.dsc
 22198cdf516f1ff5ed9b3dbfa61b7c8a 14364 misc optional 
dns-root-data_2017041102.tar.xz
 b5f1147276175ded4e0f159086eac90e 5946 misc optional 
dns-root-data_2017041102_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEMLkz2A/OPZgaLTj7DJm3DvT8uwcFAlk2i1lfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDMw
QjkzM0Q4MEZDRTNEOTgxQTJEMzhGQjBDOTlCNzBFRjRGQ0JCMDcACgkQDJm3DvT8
uwemOw/9Eva/e7kceDRzb6u1qx81KJYMxQGFlpNOokGXSNFtFSVFui5Q5BG2efxv
u7vz92KEaZU0F4ER/R4ZNsYl5ywAeyb3FvHwB2IlFrj2WmZin3LBTrQpIgQqOG/a
sZ1oo5u/CLmjXfFUocFsPRI4Nnw2WTDNb/xHGrQGxCoFak8PC01ZVHceqsALiR48
vBs3nhzlqbzlQXZSpiMGSebiKS5zllvKSKiNyiNUeFh82YgrWX/330iKRTItMnwP
cOlli6zbFbnhzTGCnRiymnzot1olaZ6xHa26pJ/8hdHjVRfBot26sOnwqJR+oF8x
ufc3vwosRt8VIssmYjtheC+qktNWV8eWZGNwpdSZ/1ph19+w7M0SMJytBLctuECy
nHtouLPDB6/JYW0RZZlBbK59YM8WlTnDo45wjoRbgKFJgfcqKTgH42RdN0mbliEo
+xx+/f42p8SfRQHKHthBmUWBFE8deSFGgIYiH/u5wCzjY0A0sgYNP9fn6o6tDLbw
Ps9JD4kInBVoVv7pzdQ4r4/NgkWw5VN6xYh6MKulClCqWiSeDsdphhYX7SJiYCuy
nv1u+zJ8kV6AvI78b7VAxf0usqc+U3oFbGPk1G6ZEaZcrF3O87F9xLEAjTZZh99D
yzWXD1wVhP+5N0so14HHxiM7QW+iFX73wGKnGpQdhMipSDEEQHc=
=dgww
-END PGP SIGNATURE End Message ---

Bug#864188: libbpp-core2v5: symbols removed without soname bump

[Adrian Bunk]

Dear Julien,

making a function inline does not break the API - compiling software 
against the library still works as before.

But making a function inline does break the ABI requiring a soname bump,
since it breaks software that was compiled against an older version of
the library.

Adrian


On Tue, Jun 06, 2017 at 12:47:38PM +0200, Julien Yann Dutheil wrote:
> Dear Adrian,
> 
> These functions are now inline in the corresponding .h files, but their
> interfaces have not changed as far as I know. Does making a function inline
> break the interface??
> 
> J.
> 
> -- Forwarded message --
> From: Adrian Bunk 
> Date: Tue, Jun 6, 2017 at 11:48 AM
> Subject: Re: Bug#864188: libbpp-core2v5: symbols removed without soname bump
> To: Julien Yann Dutheil 
> Cc: Andreas Tille , 864...@bugs.debian.org, GINDRAUD
> FRANCOIS 
> 
> 
> On Tue, Jun 06, 2017 at 11:35:57AM +0200, Julien Yann Dutheil wrote:
> > Dear Andreas, Adrian,
> >...
> > - This error actually revealed an interface breakdown (essentially due to
> > our upgrade to c++11), and your suggestion is to reflect this change by
> > increasing the interface number (which would result in a change in package
> > name, such as libbpp-core2 -> libbpp-core3), am I correct?
> 
> This ABI breakage is unrelated to the C++ version used.
> 
> RandomTools::lnGamma() was removed from src/Bpp/Numeric/Random/
> RandomTools.cpp
> TextTools::startsWith() was removed from src/Bpp/Text/TextTools.cpp
> ApplicationTools::parameterExists() was removed from
> src/Bpp/App/ApplicationTools.cpp
> ...
> 
> Removing any such function breaks the ABI in an incompatible way,
> and therefore requires a soname bump.
> 
> > Best,
> >
> > Julien.
> 
> cu
> Adrian
> 
> > On Mon, Jun 5, 2017 at 9:50 AM, Andreas Tille  wrote:
> >
> > > Hi Julien,
> > >
> > > while I made a mistake to upload libbpp-core to unstable rather than
> > > experimental as it was planed this has probably lead to spot a bug
> > > earlier.  The problem is that the soversion needs to be bumped due to
> > > the ABI change.
> > >
> > >$ objdump -p ./libbpp-core.so.2.0.4   | sed -n 's/^.*SONAME *//p'
> > >libbpp-core.so.2
> > >
> > > I think you should bump the SOVERSION to reflect that change.
> > >
> > > Kind regards
> > >
> > >  Andreas.
> > >
> > > On Mon, Jun 05, 2017 at 02:42:58AM +0300, Adrian Bunk wrote:
> > > > Package: libbpp-core2v5
> > > > Version: 2.3.0-1~exp1
> > > > Severity: serious
> > > > Control: affects -1 libbpp-seq9v5 src:libbpp-phyl
> > > >
> > > > 2.3.0-1~exp1 in unstable (sic) removes symbols without changing
> soname,
> > > > causing the following FTBFS in libbpp-phyl:
> > > >
> > > > https://tests.reproducible-builds.org/debian/rb-pkg/
> > > unstable/amd64/libbpp-phyl.html
> > > >
> > > > ...
> > > > [ 93%] Linking CXX executable test_bowker
> > > > cd /build/1st/libbpp-phyl-2.2.0/obj-x86_64-linux-gnu/test &&
> > > /usr/bin/cmake -E cmake_link_script CMakeFiles/test_bowker.dir/link.txt
> > > --verbose=1
> > > > /usr/bin/c++   -Wall -Wshadow -Weffc++ -Wconversion  -Wl,-z,relro
> > > CMakeFiles/test_bowker.dir/test_bowker.cpp.o  -o test_bowker -rdynamic
> > > -lbpp-seq -lbpp-core -L../src -lbpp-phyl
> > > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
> libbpp-seq.so:
> > > undefined reference to `bpp::RandomTools::lnGamma(double)'
> > > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
> libbpp-seq.so:
> > > undefined reference to `bpp::TextTools::startsWith(
> > > std::__cxx11::basic_string > > std::allocator > const&, std::__cxx11::basic_string > > std::char_traits, std::allocator > const&)'
> > > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
> libbpp-seq.so:
> > > undefined reference to `bpp::ApplicationTools::
> > > parameterExists(std::__cxx11::basic_string > > std::allocator > const&, std::map > > std::char_traits, std::allocator >,
> std::__cxx11::basic_string > > std::char_traits, std::allocator >,
> > > std::less > > std::allocator > >, std::allocator > > std::char_traits, std::allocator > const,
> > > std::__cxx11::basic_string > > std::allocator > > > >&)'
> > > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
> libbpp-seq.so:
> > > undefined reference to `bpp::ApplicationTools::
> getStringParameter(std::__cxx11::basic_string > > std::char_traits, std::allocator > const&,
> > > std::map > > std::allocator >, std::__cxx11::basic_string > > std::char_traits, std::allocator >,
> > > std::less > > std::allocator > >, std::allocator 

Bug#864188: libbpp-core2v5: symbols removed without soname bump

[Julien Yann Dutheil]

Dear Adrian,

These functions are now inline in the corresponding .h files, but their
interfaces have not changed as far as I know. Does making a function inline
break the interface??

J.

-- Forwarded message --
From: Adrian Bunk 
Date: Tue, Jun 6, 2017 at 11:48 AM
Subject: Re: Bug#864188: libbpp-core2v5: symbols removed without soname bump
To: Julien Yann Dutheil 
Cc: Andreas Tille , 864...@bugs.debian.org, GINDRAUD
FRANCOIS 


On Tue, Jun 06, 2017 at 11:35:57AM +0200, Julien Yann Dutheil wrote:
> Dear Andreas, Adrian,
>...
> - This error actually revealed an interface breakdown (essentially due to
> our upgrade to c++11), and your suggestion is to reflect this change by
> increasing the interface number (which would result in a change in package
> name, such as libbpp-core2 -> libbpp-core3), am I correct?

This ABI breakage is unrelated to the C++ version used.

RandomTools::lnGamma() was removed from src/Bpp/Numeric/Random/
RandomTools.cpp
TextTools::startsWith() was removed from src/Bpp/Text/TextTools.cpp
ApplicationTools::parameterExists() was removed from
src/Bpp/App/ApplicationTools.cpp
...

Removing any such function breaks the ABI in an incompatible way,
and therefore requires a soname bump.

> Best,
>
> Julien.

cu
Adrian

> On Mon, Jun 5, 2017 at 9:50 AM, Andreas Tille  wrote:
>
> > Hi Julien,
> >
> > while I made a mistake to upload libbpp-core to unstable rather than
> > experimental as it was planed this has probably lead to spot a bug
> > earlier.  The problem is that the soversion needs to be bumped due to
> > the ABI change.
> >
> >$ objdump -p ./libbpp-core.so.2.0.4   | sed -n 's/^.*SONAME *//p'
> >libbpp-core.so.2
> >
> > I think you should bump the SOVERSION to reflect that change.
> >
> > Kind regards
> >
> >  Andreas.
> >
> > On Mon, Jun 05, 2017 at 02:42:58AM +0300, Adrian Bunk wrote:
> > > Package: libbpp-core2v5
> > > Version: 2.3.0-1~exp1
> > > Severity: serious
> > > Control: affects -1 libbpp-seq9v5 src:libbpp-phyl
> > >
> > > 2.3.0-1~exp1 in unstable (sic) removes symbols without changing
soname,
> > > causing the following FTBFS in libbpp-phyl:
> > >
> > > https://tests.reproducible-builds.org/debian/rb-pkg/
> > unstable/amd64/libbpp-phyl.html
> > >
> > > ...
> > > [ 93%] Linking CXX executable test_bowker
> > > cd /build/1st/libbpp-phyl-2.2.0/obj-x86_64-linux-gnu/test &&
> > /usr/bin/cmake -E cmake_link_script CMakeFiles/test_bowker.dir/link.txt
> > --verbose=1
> > > /usr/bin/c++   -Wall -Wshadow -Weffc++ -Wconversion  -Wl,-z,relro
> > CMakeFiles/test_bowker.dir/test_bowker.cpp.o  -o test_bowker -rdynamic
> > -lbpp-seq -lbpp-core -L../src -lbpp-phyl
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
libbpp-seq.so:
> > undefined reference to `bpp::RandomTools::lnGamma(double)'
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
libbpp-seq.so:
> > undefined reference to `bpp::TextTools::startsWith(
> > std::__cxx11::basic_string > std::allocator > const&, std::__cxx11::basic_string > std::char_traits, std::allocator > const&)'
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
libbpp-seq.so:
> > undefined reference to `bpp::ApplicationTools::
> > parameterExists(std::__cxx11::basic_string > std::allocator > const&, std::map > std::char_traits, std::allocator >,
std::__cxx11::basic_string > std::char_traits, std::allocator >,
> > std::less > std::allocator > >, std::allocator std::char_traits, std::allocator > const,
> > std::__cxx11::basic_string > std::allocator > > > >&)'
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/
libbpp-seq.so:
> > undefined reference to `bpp::ApplicationTools::
getStringParameter(std::__cxx11::basic_string > std::char_traits, std::allocator > const&,
> > std::map > std::allocator >, std::__cxx11::basic_string > std::char_traits, std::allocator >,
> > std::less > std::allocator > >, std::allocator std::char_traits, std::allocator > const,
> > std::__cxx11::basic_string > std::allocator > > > >&, std::__cxx11::basic_string > std::char_traits, std::allocator > const&,
> > std::__cxx11::basic_string > std::allocator > const&, bool, int)'
> > > collect2: error: ld returned 1 exit status
> > > test/CMakeFiles/test_bowker.dir/build.make:99: recipe for target
> > 'test/test_bowker' failed
> > > make[3]: *** [test/test_bowker] Error 1
> >
> > --
> > http://fam-tille.de
> >
>
>
>
> --
> Julien Y. Dutheil, Ph-D
> 0 (+49) 4522 763 298
>
> § Max Planck Institute for Evolutionary Biology
> 

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.

This patch does not apply cleanly on the version of Filetea available
in Debian (0.1.16).

I'll try to backport it.

Berto

Bug#864188: libbpp-core2v5: symbols removed without soname bump

[Julien Yann Dutheil]

Dear Andreas, Adrian,

Just to be sure I get everything right:
- The error you found before was due to building against a previous version
of bpp-core
- This error actually revealed an interface breakdown (essentially due to
our upgrade to c++11), and your suggestion is to reflect this change by
increasing the interface number (which would result in a change in package
name, such as libbpp-core2 -> libbpp-core3), am I correct?

Best,

Julien.

On Mon, Jun 5, 2017 at 9:50 AM, Andreas Tille  wrote:

> Hi Julien,
>
> while I made a mistake to upload libbpp-core to unstable rather than
> experimental as it was planed this has probably lead to spot a bug
> earlier.  The problem is that the soversion needs to be bumped due to
> the ABI change.
>
>$ objdump -p ./libbpp-core.so.2.0.4   | sed -n 's/^.*SONAME *//p'
>libbpp-core.so.2
>
> I think you should bump the SOVERSION to reflect that change.
>
> Kind regards
>
>  Andreas.
>
> On Mon, Jun 05, 2017 at 02:42:58AM +0300, Adrian Bunk wrote:
> > Package: libbpp-core2v5
> > Version: 2.3.0-1~exp1
> > Severity: serious
> > Control: affects -1 libbpp-seq9v5 src:libbpp-phyl
> >
> > 2.3.0-1~exp1 in unstable (sic) removes symbols without changing soname,
> > causing the following FTBFS in libbpp-phyl:
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/libbpp-phyl.html
> >
> > ...
> > [ 93%] Linking CXX executable test_bowker
> > cd /build/1st/libbpp-phyl-2.2.0/obj-x86_64-linux-gnu/test &&
> /usr/bin/cmake -E cmake_link_script CMakeFiles/test_bowker.dir/link.txt
> --verbose=1
> > /usr/bin/c++   -Wall -Wshadow -Weffc++ -Wconversion  -Wl,-z,relro
> CMakeFiles/test_bowker.dir/test_bowker.cpp.o  -o test_bowker -rdynamic
> -lbpp-seq -lbpp-core -L../src -lbpp-phyl
> > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> undefined reference to `bpp::RandomTools::lnGamma(double)'
> > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> undefined reference to `bpp::TextTools::startsWith(
> std::__cxx11::basic_string std::allocator > const&, std::__cxx11::basic_string std::char_traits, std::allocator > const&)'
> > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> undefined reference to `bpp::ApplicationTools::
> parameterExists(std::__cxx11::basic_string std::allocator > const&, std::map std::char_traits, std::allocator >, 
> std::__cxx11::basic_string std::char_traits, std::allocator >,
> std::less std::allocator > >, 
> std::allocator std::char_traits, std::allocator > const,
> std::__cxx11::basic_string std::allocator > > > >&)'
> > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> undefined reference to 
> `bpp::ApplicationTools::getStringParameter(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> std::map std::allocator >, std::__cxx11::basic_string std::char_traits, std::allocator >,
> std::less std::allocator > >, 
> std::allocator std::char_traits, std::allocator > const,
> std::__cxx11::basic_string std::allocator > > > >&, std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> std::__cxx11::basic_string std::allocator > const&, bool, int)'
> > collect2: error: ld returned 1 exit status
> > test/CMakeFiles/test_bowker.dir/build.make:99: recipe for target
> 'test/test_bowker' failed
> > make[3]: *** [test/test_bowker] Error 1
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 4522 763 298

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#864188: libbpp-core2v5: symbols removed without soname bump

[Adrian Bunk]

On Tue, Jun 06, 2017 at 11:35:57AM +0200, Julien Yann Dutheil wrote:
> Dear Andreas, Adrian,
>...
> - This error actually revealed an interface breakdown (essentially due to
> our upgrade to c++11), and your suggestion is to reflect this change by
> increasing the interface number (which would result in a change in package
> name, such as libbpp-core2 -> libbpp-core3), am I correct?

This ABI breakage is unrelated to the C++ version used.

RandomTools::lnGamma() was removed from src/Bpp/Numeric/Random/RandomTools.cpp
TextTools::startsWith() was removed from src/Bpp/Text/TextTools.cpp
ApplicationTools::parameterExists() was removed from 
src/Bpp/App/ApplicationTools.cpp
...

Removing any such function breaks the ABI in an incompatible way,
and therefore requires a soname bump.

> Best,
> 
> Julien.

cu
Adrian

> On Mon, Jun 5, 2017 at 9:50 AM, Andreas Tille  wrote:
> 
> > Hi Julien,
> >
> > while I made a mistake to upload libbpp-core to unstable rather than
> > experimental as it was planed this has probably lead to spot a bug
> > earlier.  The problem is that the soversion needs to be bumped due to
> > the ABI change.
> >
> >$ objdump -p ./libbpp-core.so.2.0.4   | sed -n 's/^.*SONAME *//p'
> >libbpp-core.so.2
> >
> > I think you should bump the SOVERSION to reflect that change.
> >
> > Kind regards
> >
> >  Andreas.
> >
> > On Mon, Jun 05, 2017 at 02:42:58AM +0300, Adrian Bunk wrote:
> > > Package: libbpp-core2v5
> > > Version: 2.3.0-1~exp1
> > > Severity: serious
> > > Control: affects -1 libbpp-seq9v5 src:libbpp-phyl
> > >
> > > 2.3.0-1~exp1 in unstable (sic) removes symbols without changing soname,
> > > causing the following FTBFS in libbpp-phyl:
> > >
> > > https://tests.reproducible-builds.org/debian/rb-pkg/
> > unstable/amd64/libbpp-phyl.html
> > >
> > > ...
> > > [ 93%] Linking CXX executable test_bowker
> > > cd /build/1st/libbpp-phyl-2.2.0/obj-x86_64-linux-gnu/test &&
> > /usr/bin/cmake -E cmake_link_script CMakeFiles/test_bowker.dir/link.txt
> > --verbose=1
> > > /usr/bin/c++   -Wall -Wshadow -Weffc++ -Wconversion  -Wl,-z,relro
> > CMakeFiles/test_bowker.dir/test_bowker.cpp.o  -o test_bowker -rdynamic
> > -lbpp-seq -lbpp-core -L../src -lbpp-phyl
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> > undefined reference to `bpp::RandomTools::lnGamma(double)'
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> > undefined reference to `bpp::TextTools::startsWith(
> > std::__cxx11::basic_string > std::allocator > const&, std::__cxx11::basic_string > std::char_traits, std::allocator > const&)'
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> > undefined reference to `bpp::ApplicationTools::
> > parameterExists(std::__cxx11::basic_string > std::allocator > const&, std::map > std::char_traits, std::allocator >, 
> > std::__cxx11::basic_string > std::char_traits, std::allocator >,
> > std::less > std::allocator > >, 
> > std::allocator > std::char_traits, std::allocator > const,
> > std::__cxx11::basic_string > std::allocator > > > >&)'
> > > /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libbpp-seq.so:
> > undefined reference to 
> > `bpp::ApplicationTools::getStringParameter(std::__cxx11::basic_string > std::char_traits, std::allocator > const&,
> > std::map > std::allocator >, std::__cxx11::basic_string > std::char_traits, std::allocator >,
> > std::less > std::allocator > >, 
> > std::allocator > std::char_traits, std::allocator > const,
> > std::__cxx11::basic_string > std::allocator > > > >&, std::__cxx11::basic_string > std::char_traits, std::allocator > const&,
> > std::__cxx11::basic_string > std::allocator > const&, bool, int)'
> > > collect2: error: ld returned 1 exit status
> > > test/CMakeFiles/test_bowker.dir/build.make:99: recipe for target
> > 'test/test_bowker' failed
> > > make[3]: *** [test/test_bowker] Error 1
> >
> > --
> > http://fam-tille.de
> >
> 
> 
> 
> -- 
> Julien Y. Dutheil, Ph-D
> 0 (+49) 4522 763 298
> 
> § Max Planck Institute for Evolutionary Biology
> Molecular Systems Evolution
> Department of Evolutionary Genetics
> Plön -- GERMANY
> 
> § Institute of Evolutionary Sciences - Montpellier
> University of Montpellier 2 -- FRANCE

Processed: I missed the epoch in the found version

[Debian Bug Tracking System]

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

> notfound 862576 4.10.2.2614-4
Bug #862576 [squeak-vm] etoys: Doesn't get beyond Squeak security key generation
There is no source info for the package 'squeak-vm' at version '4.10.2.2614-4' 
with architecture ''
Unable to make a source version for version '4.10.2.2614-4'
No longer marked as found in versions 4.10.2.2614-4.
> found 862576 1:4.10.2.2614-4
Bug #862576 [squeak-vm] etoys: Doesn't get beyond Squeak security key generation
Marked as found in versions squeak-vm/1:4.10.2.2614-4.
> thanks
Stopping processing here.

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

Bug#862576: etoys: Doesn't get beyond Squeak security key generation

[Adrian Bunk]

Control: reassign -1 squeak-vm 4.10.2.2614-4
Control: affects -1 etoys

On Sun, Jun 04, 2017 at 10:23:51PM +0200, Petter Reinholdtsen wrote:
> This issue is going to cause etags to be removed from Stretch.  Anyone have 
> any idea what is wrong?

It seems better optimization in recent gcc versions exposes bugs
in squeak-vm.

The following workaround to use less optimization works for me:

--- debian/rules.old2017-06-06 09:04:49.0 +
+++ debian/rules2017-06-06 09:20:17.0 +
@@ -6,6 +6,9 @@
 # This has to be exported to make some magic below work.
 export DH_OPTIONS
 
+# workaround for #862576
+export DEB_CFLAGS_MAINT_APPEND = -O1
+
 include /usr/share/cdbs/1/rules/upstream-tarball.mk
 include /usr/share/cdbs/1/class/cmake.mk
 include /usr/share/cdbs/1/rules/debhelper.mk


This is a short-term workaround for stretch.

Additionally adding -Wall gives tons of warnings for non-harmless 
issues, that's a good starting point when searching for a proper fix.


> Happy hacking
> Petter Reinholdtsen

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

Processed: Re: Bug#862576: etoys: Doesn't get beyond Squeak security key generation

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 squeak-vm 4.10.2.2614-4
Bug #862576 [etoys] etoys: Doesn't get beyond Squeak security key generation
Bug reassigned from package 'etoys' to 'squeak-vm'.
No longer marked as found in versions etoys/5.0.2408-1.
Ignoring request to alter fixed versions of bug #862576 to the same values 
previously set
Bug #862576 [squeak-vm] etoys: Doesn't get beyond Squeak security key generation
There is no source info for the package 'squeak-vm' at version '4.10.2.2614-4' 
with architecture ''
Unable to make a source version for version '4.10.2.2614-4'
Marked as found in versions 4.10.2.2614-4.
> affects -1 etoys
Bug #862576 [squeak-vm] etoys: Doesn't get beyond Squeak security key generation
Added indication that 862576 affects etoys

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

Bug#864221: firefox: Cannot open link from gnome-terminal anymore

[Laurent Bigonville]

On Mon, 05 Jun 2017 14:25:55 +0200 Laurent Bigonville  
wrote:


> Hi,
>
> When clicking on a link in gnome-terminal, the page is not being opened.
>
> In the journal I can see the following message:
>
> gnome-terminal-server[3319]: Error: GDK_BACKEND does not match 
available displays

>
> If I'm setting an other default browser (ie epiphany) it's working as
> expected.
>
> Not too sure what's happening here.

The problem apparently is that the DISPLAY and WAYLAND_DISPLAY 
environment variable is not present when /usr/bin/gnome-session is 
called and then are then obviously not exported by the call of 
dbus-update-activation-environment.

Processed: severity of 864221 is serious

[Debian Bug Tracking System]

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

> severity 864221 serious
Bug #864221 [gnome-session] DISPLAY and WAYLAND_DISPLAY not set in systemd 
--user env
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 851986 rt4-extension-sla
Bug #851986 [rt-extension-sla] rt-extension-sla: Obsolete with RT 4.4
Bug reassigned from package 'rt-extension-sla' to 'rt4-extension-sla'.
Ignoring request to alter found versions of bug #851986 to the same values 
previously set
Ignoring request to alter fixed versions of bug #851986 to the same values 
previously set
> forcemerge 851986 864276
Bug #851986 [rt4-extension-sla] rt-extension-sla: Obsolete with RT 4.4
Bug #864276 [rt4-extension-sla] rt4-extension-sla: not installable in sid
Added indication that 864276 affects rt4-extension-sla
Bug #851986 [rt4-extension-sla] rt-extension-sla: Obsolete with RT 4.4
Marked as found in versions rt-extension-sla/1.04-2.
Merged 851986 864276
>
End of message, stopping processing here.

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

Bug#862742: Error report for filetea

[Alberto Garcia]

On Tue, Jun 06, 2017 at 11:32:43AM +0300, Adrian Bunk 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.
> 
> If filetea should not be removed from stretch, a fix has to be in
> unstable no later than tomorrow morning.

Thanks for pinging me, I'll try to upload the fixed version today.

Berto

Bug#862742: Error report for filetea

[Adrian Bunk]

On Tue, May 23, 2017 at 05:02:17PM +0200, Alberto Garcia wrote:
> 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.

If filetea should not be removed from stretch, a fix has to be in 
unstable no later than tomorrow morning.

> Berto

cu
Adrian

-- 

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

Processed (with 1 error): reassign

[Debian Bug Tracking System]

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

> reassign 851986 rt-extension-sla
Bug #851986 [src:rt-extension-sla] rt-extension-sla: Obsolete with RT 4.4
Bug reassigned from package 'src:rt-extension-sla' to 'rt-extension-sla'.
No longer marked as found in versions rt-extension-sla/1.04-2.
Ignoring request to alter fixed versions of bug #851986 to the same values 
previously set
> forcemerge 851986 864276
Bug #851986 [rt-extension-sla] rt-extension-sla: Obsolete with RT 4.4
Unable to merge bugs because:
package of #864276 is 'rt4-extension-sla' not 'rt-extension-sla'
Failed to forcibly merge 851986: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Processed (with 1 error): forcibly merging 851986 864276

[Debian Bug Tracking System]

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

> forcemerge 851986 864276
Bug #851986 [src:rt-extension-sla] rt-extension-sla: Obsolete with RT 4.4
Unable to merge bugs because:
package of #864276 is 'rt4-extension-sla' not 'src:rt-extension-sla'
Failed to forcibly merge 851986: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#863929: Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

[Andreas Tille]

Hi Afif,

On Tue, Jun 06, 2017 at 03:10:46AM -0400, Afif Elghraoui wrote:
> 
> It actually does not even make sense to have this package available for
> a 32-bit architecture since, for any actual use (de novo genome
> assembly), it will require more memory than would be addressable on a
> 32-bit system. It's not really worth the time and effort to debug that.
> I don't know of an alias like !32bit for the Architecture field in
> debian/control to exclude that.

What about explicitly stating all 64bit architectures?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#861536: Also Removes 'systemd-sysv'

[Martin Nicholas]

As far as I remember used also to remove the above (with warnings).

'systemd-sysv' should be removed as it overwrites /sbin/init with a
link to somewhere or other, breaking the bootup method of runit-init
which installs a symlink: /sbin/init -> runit-init

Having package runit-init is a good thing IMHO.

-- 
Regards,

Martin Nicholas.

E-mail: m...@mgn.org.uk (This address must not be passed on to third
parties)

Bug#864161: marked as done (ceph-mon: missing Breaks+Replaces: ceph-common (<< 10))

[Debian Bug Tracking System]

Your message dated Tue, 06 Jun 2017 07:33:45 +
with message-id 
and subject line Bug#864161: fixed in ceph 10.2.5-7.1
has caused the Debian Bug report #864161,
regarding ceph-mon: missing Breaks+Replaces: ceph-common (<< 10)
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.)


-- 
864161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph-mon
Version: 10.2.5-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 10.2.5-6~bpo8+1
Control: affects -1 + ceph

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'jessie-backports' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

The same could happen in stretch, since the Breaks+Replaces are missing
there, too. apt just seems to use a different unpacking order for the
upgrades from jessie to stretch, but that will depend on the set of
installed packages ...

According to snapshot.d.o ceph-rest-api disappeared from ceph-common between
0.94.5-1.1 and 10.2.5-1

Once that is fixed in stretch, please also update the package in
jessie-backports.


See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../ceph_10.2.5-6~bpo8+1_amd64.deb ...
  Unpacking ceph (10.2.5-6~bpo8+1) over (0.80.7-2+deb8u2) ...
  dpkg: warning: unable to delete old directory '/etc/pm/sleep.d': Directory 
not empty
  dpkg: warning: unable to delete old directory '/etc/pm': Directory not empty
  dpkg: warning: unable to delete old directory '/etc/ceph': Directory not empty
  Selecting previously unselected package ceph-mon.
  Preparing to unpack .../ceph-mon_10.2.5-6~bpo8+1_amd64.deb ...
  Unpacking ceph-mon (10.2.5-6~bpo8+1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ceph-mon_10.2.5-6~bpo8+1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/ceph-rest-api', which is also in package 
ceph-common 0.80.7-2+deb8u2


cheers,

Andreas


ceph_10.2.5-7.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 10.2.5-7.1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated ceph 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, 06 Jun 2017 09:08:30 +0200
Source: ceph
Binary: ceph ceph-base rbd-mirror rbd-nbd ceph-common ceph-mds ceph-mon 
ceph-osd ceph-fuse rbd-fuse ceph-fs-common ceph-resource-agents librados2 
librados-dev libradosstriper1 libradosstriper-dev librbd1 librbd-dev libcephfs1 
libcephfs-dev librgw2 librgw-dev radosgw ceph-test python-ceph python-rados 
python-rbd python-cephfs libcephfs-java libcephfs-jni
Architecture: source
Version: 10.2.5-7.1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Maintainers 
Changed-By: Andreas Beckmann 
Description:
 ceph   - distributed storage and file system
 ceph-base  - common ceph daemon libraries and management tools
 ceph-common - common utilities to mount and interact with a ceph storage cluste
 ceph-fs-common - common utilities to mount and interact with a ceph file system
 ceph-fuse  - FUSE-based client for the Ceph distributed file system
 ceph-mds   - metadata server for the ceph distributed file system
 ceph-mon   - monitor server for the ceph storage system
 ceph-osd   - OSD server for the ceph storage system
 ceph-resource-agents - OCF-compliant resource agents for Ceph
 ceph-test  - Ceph test and benchmarking tools
 libcephfs-dev - Ceph distributed file system client library (development files)
 libcephfs-java - Java library for the Ceph File System
 libcephfs-jni - Java Native Interface library for CephFS Java bindings
 libcephfs1 - 

Bug#863929: [Debian-med-packaging] Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

[Afif Elghraoui]

على الجمعـة  2 حزيران 2017 ‫15:40، كتب Adrian Bunk:
> On Fri, Jun 02, 2017 at 03:52:51PM +0200, Graham Inggs wrote:
>> According to the reproducible build history [1], this package has FTBFS on
>> i386 for a long time.
>>
>> It also never successfully built on i386 in Ubuntu [2].
>>
>> If there are no objections, I will file a bug requesting removal of the i386
>> binary package.
>> ...
> 
> It always failed on the reproducible builds, but even after the first 
> failures there the build succeeded more than once on i386.
> 
> It does therefore not even make sense to remove the i386 binary since
> it would be expected that any new upload (including after the release) 
> would re-introduce the binary.
> 

It actually does not even make sense to have this package available for
a 32-bit architecture since, for any actual use (de novo genome
assembly), it will require more memory than would be addressable on a
32-bit system. It's not really worth the time and effort to debug that.
I don't know of an alias like !32bit for the Architecture field in
debian/control to exclude that.

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#864276: rt4-extension-sla: not installable in sid

[Ralf Treinen]

Package: rt4-extension-sla
Version: 1.04-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

rt4-extension-sla is not installable in sid on any architecture. This is
the case since at least 2017-01-21. The reason is that it depends on
request-tracker4 (< 4.4.0), however the version of that package in sid
is 4.4.1-3.

-Ralf.

Processed: severity of 863928 is important, tagging 863928

[Debian Bug Tracking System]

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

> severity 863928 important
Bug #863928 [src:postgresql-9.6] postgresql-9.6: FTBFS: test failures
Severity set to 'important' from 'serious'
> tags 863928 + unreproducible
Bug #863928 [src:postgresql-9.6] postgresql-9.6: FTBFS: test failures
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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