Processing commands for cont...@bugs.debian.org:
severity 794913 important
Bug #794913 [libphonenumber6] libphonenumber6: please use libboost-date-time
1.57 or 1.58
Severity set to 'important' from 'normal'
tag 794913 - security
Bug #794913 [libphonenumber6] libphonenumber6: please use
severity 794913 important
tag 794913 - security
forcemerge 794900 794913
thanks
[ I am not the maintainer, but... ]
Hi,
On Sun, Aug 09, 2015 at 03:22:08PM +0200, Christoph Anton Mitterer wrote:
Simon McVittie was so kind to disable libphonenumber6 in evolution for
now and rebuild the package
Processing control commands:
severity -1 normal
Bug #794913 [libphonenumber6] libphonenumber6: please use libboost-date-time
1.57 or 1.58 ASAP
Severity set to 'normal' from 'critical'
retitle -1 libphonenumber6: please use libboost-date-time 1.57 or 1.58
Bug #794913 [libphonenumber6
Control: severity -1 normal
Control: retitle -1 libphonenumber6: please use libboost-date-time 1.57 or 1.58
Simon McVittie was so kind to disable libphonenumber6 in evolution for
now and rebuild the package with that.
So I guess the severity of this can be lowered again, as this doesn't
block
Subject: libphonenumber6: please use libboost-date-time 1.57 or 1.58 ASAP
Package: libphonenumber6
Version: 0.5.0-2
Severity: important
Hi.
libphonenumber6, depended upon by whole evolution, depends on
libboost-date-time1.55.0 which itself is not compatible
with the new libstdc++6 from GCC5.
Processing commands for cont...@bugs.debian.org:
notfound 794913 0.5.0-2
Bug #794913 [libphonenumber6] libphonenumber6: please use libboost-date-time
1.57 or 1.58 ASAP
There is no source info for the package 'libphonenumber6' at version '0.5.0-2'
with architecture ''
Unable to make a source
Control: severity -1 critical
Control: tags -1 + security
As described in the bug report, the libboost-date-time1.55.0 package is
incompatible with GCC5 and will not be fixed, requiring a transition to
1.57 or 1.58. Unfortunately the GCC5 transition has already been taking
place on Sid (with
Hey.
I appreciate that you try to push in that matter,... but strictly
speaking, there is no security issue in this package, and also the
severity wouldn't be justified.
Some maintainers may not be too happy about that...
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
__
Hey. Although there may not be security issues within this package
itself, and while the descriptions of severity [1] may not perfectly
cover this unfortunate scenario, an update to this package (and others)
is urgently needed in order for Sid users to be able to install
critical security patches
9 matches
Mail list logo
