Processing commands for cont...@bugs.debian.org:
> fixed 825084 1:1.11.0~alpha8-1
Bug #825084 [src:resiprocate] Package links against libmysqlclient_r
Bug #841603 [src:resiprocate] resiprocate: FTBFS: ld: cannot find
-lmysqlclient_r
Marked as fixed in versions resiprocate/1:1.11.0~alpha8-1.
Marke
Processing commands for cont...@bugs.debian.org:
> severity 848493 grave
Bug #848493 [src:squid3] squid3: SQUID-2016:11: Information disclosure in HTTP
Request processing
Severity set to 'grave' from 'important'
> severity 848491 grave
Bug #848491 [src:squid3] squid3: SQUID-2016:10: Information d
Processing control commands:
> tags -1 + patch
Bug #848339 [libunbound2] unbound-anchor: libunbound.so.2 unknown symbol
fake_dsa
Added tag(s) patch.
--
848339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
On Sat, Dec 17, 2016 at 08:15:44AM +0100, Helmut Grohne wrote:
> This bug makes gnutls28 fail to build from source (it detects unbound as
> missing and fails installing its dane components). Raising severity to
> prevent testing migration and warn others.
It turns out tha
Le 18/12/2016 à 02:18, tony mancill a écrit :
> If someone else on the Java Team could give it a once over, I'd appreciate it.
Hi Tony,
Thank you for the fix, it looks good to me. There won't be links for the
Java EE APIs though, but that's not important.
Emmanuel Bourg
Will look into this before stretch "soft" freeze. Are you aware of the
fix for this?
Thanks,
Rahul.
On Friday 16 December 2016 10:39 PM, P'tit g wrote:
Package: calendarserver
Version: 7.0+dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Regression in python-sq
Package: kwin-wayland
Version: 4:5.8.4-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since kwin-x11 was being even crashier than usual, I tried the other
Plasma (wayland) entry for a change.
To my great joy, it worked flawlessly ... for the first several minutes.
Af
Package: kwin-x11
Version: 4:5.8.4-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
With some recent upgrade, kwin-x11 fails to start properly. Usually I
track testing, but .
I can see the process *running*, but it doesn't actually decorate any
windows (if I manually e.
Hello,
this is to let you know I will start working on the RC bugs in the
packages
src:libapache-mod-encoding (popcon 384)
#817519 libapache-mod-encoding: Removal of debhelper compat 4
src:dpkg-sig (popcon 361)
#817437 dpkg-sig: Removal of debhelper compat 4
src:cramfsswap (popc
Your message dated Sun, 18 Dec 2016 01:19:50 +
with message-id
and subject line Bug#848291: fixed in mysql-connector-python 2.1.5-1
has caused the Debian Bug report #848291,
regarding mysql-connector-python: build-depends on mysql-{client,server}
to be marked as done.
This means that you clai
On Fri, 16 Dec 2016 21:57:44 -0500 Jeremy Bicha wrote:
> Package: derby
> Version: 10.13.1.1-1
> Severity: serious
>
> derby fails to build from source. It looks to me like it's failing
> because it's trying to connect to an external website and fails when
> it can't load the URL.
>
> I recommend
Your message dated Sun, 18 Dec 2016 01:19:50 +
with message-id
and subject line Bug#841677: fixed in mysql-connector-python 2.1.5-1
has caused the Debian Bug report #841677,
regarding mysql-connector-python: CVE-2016-5598
to be marked as done.
This means that you claim that the problem has be
tag 841677 pending
thanks
Hello,
Bug #841677 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=python-modules/packages/mysql-connector-python.git;a=commitdiff;h=9f578de
---
commit 9f578d
Processing commands for cont...@bugs.debian.org:
> tag 848291 pending
Bug #848291 [src:mysql-connector-python] mysql-connector-python: build-depends
on mysql-{client,server}
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
848291: http://bugs
tag 848291 pending
thanks
Hello,
Bug #848291 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=python-modules/packages/mysql-connector-python.git;a=commitdiff;h=db62b41
---
commit db62b4
Processing commands for cont...@bugs.debian.org:
> tag 841677 pending
Bug #841677 [src:mysql-connector-python] mysql-connector-python: CVE-2016-5598
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
841677: http://bugs.debian.org/cgi-bin/bugrep
Your message dated Sun, 18 Dec 2016 00:50:07 +
with message-id
and subject line Bug#812023: fixed in hhvm 3.12.11+dfsg-1
has caused the Debian Bug report #812023,
regarding hhvm: FTBFS with GCC 6: flexible array member...
to be marked as done.
This means that you claim that the problem has be
Your message dated Sun, 18 Dec 2016 00:50:07 +
with message-id
and subject line Bug#828340: fixed in hhvm 3.12.11+dfsg-1
has caused the Debian Bug report #828340,
regarding hhvm: FTBFS with openssl 1.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 18 Dec 2016 00:49:17 +
with message-id
and subject line Bug#837448: fixed in farstream-0.2 0.2.8-2
has caused the Debian Bug report #837448,
regarding farstream-0.2: FTBFS with bindnow and PIE enabled
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 18 Dec 2016 00:50:07 +
with message-id
and subject line Bug#845852: fixed in hhvm 3.12.11+dfsg-1
has caused the Debian Bug report #845852,
regarding hhvm: switch to build depend on the metapackage
default-libmysqlclient-dev
to be marked as done.
This means that you cl
Your message dated Sun, 18 Dec 2016 00:50:07 +
with message-id
and subject line Bug#839303: fixed in hhvm 3.12.11+dfsg-1
has caused the Debian Bug report #839303,
regarding hhvm: FTBFS: BoostContextCompatibility.h:35:41: error: 'fcontext_t'
in namespace 'boost::context' does not name a type
t
Your message dated Sun, 18 Dec 2016 00:50:07 +
with message-id
and subject line Bug#825077: fixed in hhvm 3.12.11+dfsg-1
has caused the Debian Bug report #825077,
regarding Package links against libmysqlclient_r
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Sun, 18 Dec 2016 00:50:07 +
with message-id
and subject line Bug#835032: fixed in hhvm 3.12.11+dfsg-1
has caused the Debian Bug report #835032,
regarding hhvm: Various CVEs (CVE-2014-9709 CVE-2015-8865 CVE-2016-1903
CVE-2016-4070 CVE-2016-4539 CVE-2016-6870 CVE-2016-6871 CV
Processing commands for cont...@bugs.debian.org:
> notfound 848345 0.7.0
Bug #848345 [gpsshogi] [gpsshogi] 0.7.0 not installable due to dependency
There is no source info for the package 'gpsshogi' at version '0.7.0' with
architecture ''
Unable to make a source version for version '0.7.0'
No long
Dear owncloud-client maintainers,
owncloud-client is scheduled for removal from testing on 2016-12-21,
because #844937 is not yet fixed in testing. And since packages will
not be allowed to enter back testing after 2017-01-06, there is a
significant risk that owncloud-client will not be part of st
Control: severity -1 important
On Thu, 15 Dec 2016 22:46:02 +0200 Adrian Bunk wrote:
> node-yargs build-depends on docbook-ebnf,
> which is not in stretch due to #817433
I just QA'ed docbook-ebnf, so that should get back into stretch in 10
days ...
Andreas
Processing control commands:
> severity -1 important
Bug #848271 [src:docbook-defguide] docbook-defguide FTBFS in stretch due to
missing docbook-ebnf
Severity set to 'important' from 'serious'
--
848271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848271
Debian Bug Tracking System
Contact
Hi Stefan,
On Tue, 8 Nov 2016 21:58:02 +0100 Stefan Potyra wrote:
> Hi Balint,
>
> thanks for the bug report.
>
> I think this is in fact a problem with PIE: FAUmachine uses a just-in-time
> compiler based on qemu. This is where the error happens:
>
> dyngen: unsupported X86_64 relocation (4
Mattia Rizzolo wrote...
> On Sat, Dec 17, 2016 at 03:04:10PM +0100, Christoph Biedl wrote:
> > Find below the debdiff for a NMU I've prepared for ooolib-perl
> > (versioned as 0.1.9-1.1), upload to DELAYED/2 will follow shortly.
> > Please feel free to tell me if I should delay it longer.
>
> I'm
Hi Greg,
the Debian packaged biom-format received a bug report which leaves me
clueless how to track it down. Is there possibly some way to make the
test suite more verbose to find out what part might cause the random
failure which you can see in the buil logs linked from the bug page
https:/
Am 05.12.2016 um 19:52 schrieb Dr. Tobias Quathamer:
I'd be happy to sponsor Joseph's upload, but there are many changes to
the package, including a split into more binary packages, so I think it
might be best if either you or Fredrik could do the upload, because
you're familiar with the package.
Control: severity -1 normal
Control: tag -1 -moreinfo
Control: close -1
On Dec 17, Christian Hofstaedtler wrote:
> usrmerge reports that various symlinks installed by systemd are "broken"
> and cannot be properly converted:
Because they are, so the program cannot magically guess how to resolve
Processing control commands:
> severity -1 normal
Bug #848504 [usrmerge] usrmerge breaks various systemd symlinks
Severity set to 'normal' from 'serious'
> tag -1 -moreinfo
Bug #848504 [usrmerge] usrmerge breaks various systemd symlinks
Removed tag(s) moreinfo.
> close -1
Bug #848504 [usrmerge] us
Your message dated Sat, 17 Dec 2016 22:20:44 +
with message-id
and subject line Bug#784610: fixed in frescobaldi
3.0.0~git20161001.0.eec60717+ds1-1
has caused the Debian Bug report #784610,
regarding [frescobaldi] Qt4's WebKit removal
to be marked as done.
This means that you claim that the
Your message dated Sat, 17 Dec 2016 22:20:16 +
with message-id
and subject line Bug#817433: fixed in docbook-ebnf 1.2~cr1-6
has caused the Debian Bug report #817433,
regarding docbook-ebnf: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 17 Dec 2016 22:05:48 +
with message-id
and subject line Bug#848034: fixed in hovercraft 2.1-2
has caused the Debian Bug report #848034,
regarding hovercraft: FTBFS with docutils 0.13, hardcodes 0.12 version number
to be marked as done.
This means that you claim that th
Your message dated Sat, 17 Dec 2016 22:06:28 +
with message-id
and subject line Bug#842881: fixed in openmpi 2.0.2~git.20161225-8
has caused the Debian Bug report #842881,
regarding libmpich12: extraneous - and possibly wrong - symbolic link:
/usr/lib/libmpich.so.12 -> libmpi.so
to be marked
Your message dated Sat, 17 Dec 2016 22:02:13 +
with message-id
and subject line Bug#842093: fixed in libupnp 1:1.6.19+git20141001-1+deb8u1
has caused the Debian Bug report #842093,
regarding libupnp: CVE-2016-8863
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 17 Dec 2016 22:02:13 +
with message-id
and subject line Bug#831857: fixed in libupnp 1:1.6.19+git20141001-1+deb8u1
has caused the Debian Bug report #831857,
regarding libupnp: CVE-2016-6255: write files via POST
to be marked as done.
This means that you claim that the
Control: severity -1 normal
Reopened because this appeared again in reproducible builds CI. However, this
failure is only
hardly reproducible. Currently it builds fine throughout. Therefore, I'm
lowering the severity
of this bug report.
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.or
Processing control commands:
> severity -1 normal
Bug #835531 [src:theano] theano: FTBFS on amd64 (fail of
test_csr_correct_output_faster_than_scipy)
Severity set to 'normal' from 'serious'
--
835531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835531
Debian Bug Tracking System
Contact ow.
Control: found -1 13
* Michael Biebl [161217 21:35]:
> Am 17.12.2016 um 21:08 schrieb Michael Biebl:
...
> > So it seems, usrmerge resolved those to the symlink target.
> >
> > I don't see anything broken in systemd here though, so
> > reassigning to usrmerge (and bumping the severity, as this
Processing control commands:
> found -1 13
Bug #848504 [usrmerge] usrmerge breaks various systemd symlinks
Marked as found in versions usrmerge/13.
--
848504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 17 Dec 2016 21:09:53 +
with message-id
and subject line Bug#828497: fixed in pgpool2 3.6.0-1
has caused the Debian Bug report #828497,
regarding pgpool2: FTBFS with openssl 1.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Package: dirmngr
Version: 2.1.16-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the at
Le sam. 17 déc. 2016 11:45, Andreas Tille a écrit :
> Hi Aaron,
>
> I guess that's due to the new version of ncbi-tools+. Any suggested
> patch for this problem?
>
By the way, adding dbtype with prot or nuc value should do the job.
If dataset_201401/MFO/goasp.fasta contains only acgtn chars it i
control: severity -1 important
control: unblock 827061 by -1
Eric, it seems you moved to openssl 1.0. In general you should have
close this bug with your upload and cloned this bug with severity
important so it can be addressed in Buster cycle.
For now I unblocked the transition bug and lowered th
Processing control commands:
> severity -1 important
Bug #828471 [src:opensc] opensc: FTBFS with openssl 1.1.0
Severity set to 'important' from 'serious'
> unblock 827061 by -1
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 828290 828348 828342 828599 828561 828296 844
Le sam. 17 déc. 2016 11:45, Andreas Tille a écrit :
> Hi Aaron,
>
> I guess that's due to the new version of ncbi-tools+. Any suggested
> patch for this problem?
>
Looks indeed related to a modification with formatdb.
I do not know the tool itself but looking at executed command and formatdb
he
On 2016-12-02 10:43:17 [+0100], Raphaël Hertzog wrote:
> Currently openvas is not buildable because it build-depends on libssh-dev
> which depends on libssl1.0-dev and libsnmp-dev which depends on
> libssl-dev (and both libssl*-dev are not co-installable).
>
> I believe we might be able to fix thi
Control: tags -1 + moreinfo unreproducible
Am 17.12.2016 um 21:08 schrieb Michael Biebl:
> Am 17.12.2016 um 19:55 schrieb Michael Biebl:
>> On Sat, 17 Dec 2016 19:46:03 +0100 Christian Hofstaedtler
>> wrote:
>>> Package: systemd
>>> Version: 232-7
>>>
>>> usrmerge reports that various symlinks in
Processing control commands:
> tags -1 + moreinfo unreproducible
Bug #848504 [usrmerge] usrmerge breaks various systemd symlinks
Added tag(s) moreinfo and unreproducible.
--
848504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848504
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Package: obs-api
Version: 2.7.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the att
Your message dated Sat, 17 Dec 2016 15:10:32 -0500
with message-id
and subject line Also fixed in 1.9-3
has caused the Debian Bug report #834412,
regarding barnowl: FTBFS with '.' removed from perl's @INC
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Processing control commands:
> reassign -1 usrmerge
Bug #848504 [systemd] usrmerge breaks various systemd symlinks
Bug reassigned from package 'systemd' to 'usrmerge'.
No longer marked as found in versions systemd/232-7.
Ignoring request to alter fixed versions of bug #848504 to the same values
p
Your message dated Sat, 17 Dec 2016 19:52:20 +
with message-id
and subject line Bug#846113: fixed in polygraph 4.3.2-5
has caused the Debian Bug report #846113,
regarding polygraph loses SSL support when compiled with OpenSSL 1.1
to be marked as done.
This means that you claim that the proble
On Sat, Dec 17, 2016 at 03:04:10PM +0100, Christoph Biedl wrote:
> Find below the debdiff for a NMU I've prepared for ooolib-perl
> (versioned as 0.1.9-1.1), upload to DELAYED/2 will follow shortly.
> Please feel free to tell me if I should delay it longer.
I'm not actually convinced that there is
Even with python-pkg-resources installed, the package does not work,
as pep8 has been renamed to pycodestyle and autopep8 now fails like
this:
% autopep8
Traceback (most recent call last):
File "/usr/bin/autopep8", line 5, in
from pkg_resources import load_entry_point
File "/usr/lib/pytho
Your message dated Sat, 17 Dec 2016 19:20:06 +
with message-id
and subject line Bug#822502: fixed in nemiver 0.9.6-1.1
has caused the Debian Bug report #822502,
regarding nemiver: FTBFS: error: cannot convert 'const sigc::slot_base' to
'bool' in return
to be marked as done.
This means that y
Package: src:julia
Version: 0.4.7-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
control: severity -1 normal
control: tags -1 +moreinfo
On Mon, Dec 12, 2016 at 12:48 PM, Sandro Tosi wrote:
> On Mon, Dec 12, 2016 at 12:37 PM, Akkana Peck wrote:
>> These scripts all work fine on Jessie, and used to work until quite
>> recently on Stretch/Sid.
>
> did you upgrade something on y
Processing control commands:
> severity -1 normal
Bug #847975 [python-matplotlib] python-matplotlib: All attempts to plot fail
with "OverflowError: Python int too large to convert to C long"
Severity set to 'normal' from 'grave'
> tags -1 +moreinfo
Bug #847975 [python-matplotlib] python-matplotli
Processing commands for cont...@bugs.debian.org:
> block 848307 with 848503
Bug #848307 {Done: Héctor Orón Martínez } [src:gdb-doc]
gdb-doc has no binaries on any arch
848307 was not blocked by any bugs.
848307 was not blocking any bugs.
Added blocking bug(s) of 848307: 848503
> thanks
Stopping p
Your message dated Sat, 17 Dec 2016 19:00:10 +
with message-id
and subject line Bug#848307: fixed in gdb-doc 7.12-2
has caused the Debian Bug report #848307,
regarding gdb-doc has no binaries on any arch
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2016 19:00:14 +
with message-id
and subject line Bug#811907: fixed in music 1.0.7-1.3
has caused the Debian Bug report #811907,
regarding music: FTBFS with GCC 6: invalid conversion
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 17 Dec 2016 19:00:14 +
with message-id
and subject line Bug#822005: fixed in music 1.0.7-1.3
has caused the Debian Bug report #822005,
regarding music: Build arch:all+arch:any but is missing build-{arch,indep}
targets
to be marked as done.
This means that you claim th
Your message dated Sat, 17 Dec 2016 19:00:14 +
with message-id
and subject line Bug#805951: fixed in music 1.0.7-1.3
has caused the Debian Bug report #805951,
regarding music: FTBFS when built with dpkg-buildpackage -A (no binary
artifacts)
to be marked as done.
This means that you claim tha
Hi Thorsten,
On Wed, Nov 16, 2016 at 03:12:39PM +0100, Thorsten Glaser wrote:
> On Wed, 16 Nov 2016, Salvatore Bonaccorso wrote:
>
> > FWIW, from security-team side I was planning to work on those after
> > 2.9.4+dfsg1-2.1 was now exposed enought in unstable first (unless
>
> OK, thank you.
>
>
Package: src:tycho2
Version: 2-3
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
---
Processing commands for cont...@bugs.debian.org:
> severity 848154 serious
Bug #848154 [keepalived] Cannot be installed because unable to open
'keepalived.service.dpkg-new'
Severity set to 'serious' from 'normal'
> found 848154 1:1.2.24-1
Bug #848154 [keepalived] Cannot be installed because unabl
On יום שבת, 17 בדצמבר 2016 2:03:17 IST Andreas Beckmann wrote:
> Hi,
>
> I just uploaded 304.134 to sid, it should appear on the mirrors later
> today. Please test it to see whether this bug is now fixed.
>
> Thanks
>
>
> Andreas
Program has been running fine. Bug should have been closed befor
Your message dated Sat, 17 Dec 2016 18:20:49 +
with message-id
and subject line Bug#844647: fixed in validator.js 4.7.1+dfsg1-1.1
has caused the Debian Bug report #844647,
regarding validator.js FTBFS: build dependency node-contextify was removed
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> severity 848503 normal
Bug #848503 [ftp.debian.org] gdb-doc: please cleanup from NEW queue
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
848503: http://bugs.debian.org/cgi-b
Your message dated Sat, 17 Dec 2016 18:03:55 +
with message-id
and subject line Bug#848195: fixed in nvidia-graphics-drivers 375.26-1
has caused the Debian Bug report #848195,
regarding nvidia-graphics-drivers: CVE-2016-8826
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 17 Dec 2016 18:03:33 +
with message-id
and subject line Bug#837843: fixed in colord-gtk 0.1.26-1.1
has caused the Debian Bug report #837843,
regarding colord-gtk: FTBFS due to undeclared build dependencies
to be marked as done.
This means that you claim that the proble
Processing control commands:
> tags -1 + fixed-upstream patch
Bug #844927 [src:yafc] yafc: FTBFS: src/syshdr.h:164:9: error: unknown type
name 'CPPFunction'
Added tag(s) patch and fixed-upstream.
> forwarded -1
> https://github.com/sebastinas/yafc/commit/f7272cd757517be2befe600c7566728c310f3d55
Control: tags -1 + fixed-upstream patch
Control: forwarded -1
https://github.com/sebastinas/yafc/commit/f7272cd757517be2befe600c7566728c310f3d55
Hello!
Apparently readline has deprecated CPPFunction and in libedit (which
the debian package is built against) it has recently been removed.
In rece
Your message dated Sat, 17 Dec 2016 17:49:07 +
with message-id
and subject line Bug#848293: fixed in postgresql-mysql-fdw 2.1.2-4
has caused the Debian Bug report #848293,
regarding postgresql-9.6-mysql-fdw: update mysql dependencies for mariadb
to be marked as done.
This means that you claim
Package: ftp.debian.org
Severity: grave
Hello,
gdb-doc is non-free due to GFDL license, it is not set for autobuild, but
it was uploaded as source-only upload. That caused the binary package to be
removed from the archive. So, uploading new version of it (7.12-2) ended up
in NEW queue. An
Processing control commands:
> severity -1 important
Bug #848149 [nvidia-driver] nvidia-driver: System error (GDM/Gnome) error after
installing nvidia-driver and rebooting
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #848149 [nvidia-driver] nvidia-driver: System error (GDM/Gn
Control: severity -1 important
Control: tag -1 moreinfo
On 2016-12-14 17:33, TheBrokenGod wrote:
> after checking that my graphic card is supported by the proprietary graphic
> driver and installing it through the nvidia-driver package, I am no longer
> able
> to login. Instead a low-resolution f
Le 17/12/2016 à 17:31, Alastair McKinstry a écrit :
> I say leave until post-stretch release. I'm fixing the multiarch now
> (which fixes #833728, #842881;
> tagged as mpich and ldconfig bugs but in practice due to mpich being
> multiarch and openmpi not).
> Getting this in place by the freeze on J
Processing control commands:
> tags -1 + patch
Bug #841532 [src:libgit2] libgit2: FTBFS under some timezones (eg. GMT-14)
Added tag(s) patch.
--
841532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
Hello!
For the record, I've proposed a patch for review upstream:
https://github.com/libgit2/libgit2/pull/4033
Regards,
Andreas Henriksson
Your message dated Sat, 17 Dec 2016 17:04:12 +
with message-id
and subject line Bug#848346: fixed in libio-socket-ssl-perl 2.040-1
has caused the Debian Bug report #848346,
regarding libio-socket-ssl-perl: default certificate path lost with libssl1.1
to be marked as done.
This means that you
Your message dated Sat, 17 Dec 2016 17:03:44 +
with message-id
and subject line Bug#846415: fixed in captagent 6.1.0.20-2
has caused the Debian Bug report #846415,
regarding captagent: add libfl-dev to Build-Depends
to be marked as done.
This means that you claim that the problem has been dea
Processing commands for cont...@bugs.debian.org:
> forcemerge 848293 845897
Bug #848293 [postgresql-9.6-mysql-fdw] postgresql-9.6-mysql-fdw: update mysql
dependencies for mariadb
Unable to merge bugs because:
package of #845897 is 'postgresql-mysql-fdw' not 'postgresql-9.6-mysql-fdw'
Failed to fo
Your message dated Sat, 17 Dec 2016 16:49:11 +
with message-id
and subject line Bug#846856: fixed in syslog-nagios-bridge 1.0.2-1
has caused the Debian Bug report #846856,
regarding syslog-nagios-bridge: Don't depend on nagios3 which has been removed
from unstable
to be marked as done.
This
On Sat, 17 Dec 2016 16:23:38 +0100, Steffen Ullrich wrote:
> Thanks for the analysis that the problem is caused by a change in the
> SSLEAY_DIR/OPENSSL_DIR constant with OpenSSL 1.1. I've adapted
> IO::Socket::SSL in 2.040 (just released) to try both constants so the
> problem should hopefully be
Your message dated Sat, 17 Dec 2016 16:35:09 +
with message-id
and subject line Bug#848427: fixed in libanyevent-perl 7.130-2
has caused the Debian Bug report #848427,
regarding libanyevent-perl: FTBFS with openssl 1.1: t/80_ssltest.t failure
to be marked as done.
This means that you claim th
Your message dated Sat, 17 Dec 2016 16:35:04 +
with message-id
and subject line Bug#846852: fixed in ganglia-nagios-bridge 1.2.0-1
has caused the Debian Bug report #846852,
regarding ganglia-nagios-bridge: Don't depend on nagios3 which has been removed
from unstable
to be marked as done.
Thi
> I actually meant the 2.0.2~gitsomething in experimental, but that
> question was already answered by an upload to unstable around the time I
> wrote that mail.
>
> I was primarily asking, if I was to look into improving that
> "conditional install stuff" - should I do it in experimental or sid
>
On 2016-12-17 15:26, Alastair McKinstry wrote:
>> What are the plans regarding 2.0.2? Do you expect that version to reach
>
>> stretch in time? Or will it be be delayed to stretch+1?
>
> 2.0.2 unfortunately has a SOVERSION change in two libraries, which means
> it missed the transition
> for str
tag 848427 + pending
thanks
Some bugs in the libanyevent-perl package are closed in revision
f088c629625f549ba0d5214d1236672fb7955c2a in branch 'master' by gregor
herrmann
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libanyevent-perl.git/commit/?id=f088c62
Commi
before I start wasting time by repeating something already tested:
has anyone tried building that package on a porterbox and debug this issue?
Andreas
Processing commands for cont...@bugs.debian.org:
> tag 848427 + pending
Bug #848427 [libanyevent-perl] libanyevent-perl: FTBFS with openssl 1.1:
t/80_ssltest.t failure
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
848427: http://bugs.debia
Otto,
On 12 December 2016 at 15:18, Dirk Eddelbuettel wrote:
|
| Hi Otto,
|
| On 12 December 2016 at 23:02, Otto Kekäläinen wrote:
| | Hello!
| |
| | Have you tried compiling both with libmariadb-dev and
| | libmariadbclient18-dev, does it fail with only with libmariadb-dev?
| |
| | The libma
Go ahead. Thank you.
On 17/12/2016 9:37 PM, Christoph Biedl wrote:
> Control: tags 817561 patch pending
>
> Dear maintainer,
>
> Find below the debdiff for a NMU I've prepared for
> libwww-indexparser-perl (versioned as 0.91-1.1), upload to DELAYED/2
> will follow shortly. Please feel free to tel
Thanks for the analysis that the problem is caused by a change in the
SSLEAY_DIR/OPENSSL_DIR constant with OpenSSL 1.1. I've adapted IO::Socket::SSL
in 2.040 (just released) to try both constants so the problem should hopefully
be solved by simply upgrading to 2.040.
Apart from that the proble
Your message dated Sat, 17 Dec 2016 15:20:42 +
with message-id
and subject line Bug#817596: fixed in libdata-dumpxml-perl 1.06-2
has caused the Debian Bug report #817596,
regarding libdata-dumpxml-perl: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the pro
1 - 100 of 168 matches
Mail list logo