Bug#845037: libschroedinger-1.0-0: is this package fit for stretch?

On Sun, 2016-11-20 at 11:57 +0100, Moritz Muehlenhoff wrote: > > Thus I think stretch would be better of without this library. > > > > As replacement, ffmpeg has a decent dirac decoder and also a > > vc2 encoder, which is the intra-only subset of dirac that > > got standardized by the SMPTE. >

Processed: Sent upstream

Processing commands for cont...@bugs.debian.org: > forwarded 844233 > https://bitbucket.org/ecollins/passlib/issues/82/non-deterministic-test-failure Bug #844233 [src:python-passlib] python-passlib: FTBFS with probability of 0.46% due to non-deterministic testsuite Set Bug forwarded-to-address

Processed: Re: Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

Processing control commands: > severity -1 important Bug #844239 [request-tracker4] request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure Bug #844842 [request-tracker4] rt-authen-externalauth: FTBFS: build-dependency not installable: request-tracker4 Severity set to 'important'

Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

Control: severity -1 important Control: tag -1 unreproducible On Mon, Nov 21, 2016 at 12:45:19AM +0100, Emilio Pozuelo Monfort wrote: > On 20/11/16 21:32, Niko Tyni wrote: > > On Sun, Nov 13, 2016 at 07:13:54PM +0200, Niko Tyni wrote: > >> Package: request-tracker4 > >> Version: 4.2.13-3 > >>

Bug#845182: yaskkserv: systemd support are broken

Package: yaskkserv Version: 1.1.0-1 Severity: grave Dear Maintainer, 1. This version provide "yaskkserv.service", but missing Build-Depends "libsystemd-dev", need /usr/include/systemd/sd-daemon.h Thus this daemon does not provide the feature of systemd socket activation. 2. The

Bug#844834: marked as done (libapache2-mod-auth-openid: FTBFS: build-dependency not installable: libopkele-dev (>= 2.0.4+git20140305.9651b55))

Your message dated Mon, 21 Nov 2016 06:48:36 + with message-id and subject line Bug#844834: fixed in libapache2-mod-auth-openid 0.8-3 has caused the Debian Bug report #844834, regarding libapache2-mod-auth-openid: FTBFS: build-dependency not installable:

Bug#844975: courier: FTBFS with openssl 1.1.0

Control: retitle -1 courier: FTBFS with openssl 1.1.0 Control: block 827061 by -1 The root cause of this bug seems to be: ... checking openssl/ssl.h usability... yes checking openssl/ssl.h presence... yes checking for openssl/ssl.h... yes checking for SSL_load_error_strings in -lssl... no

Processed: courier: FTBFS with openssl 1.1.0

Processing control commands: > retitle -1 courier: FTBFS with openssl 1.1.0 Bug #844975 [src:courier] courier: FTBFS: dh_install: missing files, aborting Changed Bug title to 'courier: FTBFS with openssl 1.1.0' from 'courier: FTBFS: dh_install: missing files, aborting'. > block 827061 by -1 Bug

Processed: tagging 844293

Processing commands for cont...@bugs.debian.org: > tags 844293 + help Bug #844293 [src:criu] criu: FTBFS: ld: unrecognized option '-specs=/usr/share/dpkg/no-pie-link.specs' Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 844293:

Bug#755632: marked as done (python-django-voting: Please ensure it works with Django 1.7)

Your message dated Mon, 21 Nov 2016 06:18:57 + with message-id and subject line Bug#845118: Removed package(s) from unstable has caused the Debian Bug report #755632, regarding python-django-voting: Please ensure it works with Django 1.7 to be marked as

Bug#844188: marked as done (pdf2htmlex: FTBFS with fontforge due to use of library_version_configuration structure)

Your message dated Mon, 21 Nov 2016 07:09:56 +0100 with message-id <147970859652.8302.4011811217099121731@localhost> and subject line Re: pdf2htmlex: FTBFS with fontforge due to use of library_version_configuration structure has caused the Debian Bug report #844188, regarding pdf2htmlex: FTBFS

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

20.11.2016 в 22:35:26 +0100 Jan Niehusmann написал: > On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote: > > So far I do not know why using libssl1.1 together with a > > libssl1.0.2-using Qt wouldn't work. > > Well I don't know enough about the dynamic linker and about the

Bug#833288: marked as done (would FTBFS now with cython 0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int')

Your message dated Mon, 21 Nov 2016 00:31:39 -0500 with message-id <20161121053139.yuaj7jowd5ov4...@hopa.kiewit.dartmouth.edu> and subject line Re: [Python-apps-team] Bug#833288: would FTBFS now with cython 0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int' has caused the

Bug#835674: marked as done (macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation.)

Your message dated Mon, 21 Nov 2016 00:31:39 -0500 with message-id <20161121053139.yuaj7jowd5ov4...@hopa.kiewit.dartmouth.edu> and subject line Re: [Python-apps-team] Bug#833288: would FTBFS now with cython 0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int' has caused the

Bug#845179: FTBFS with super-fresh cython -- seems to carry pre-cythoned sources which get rebuilt during clean

Source: slixmpp Version: 1.2.1-2 Severity: serious Justification: fails to build from source While preparing for upload of fresh cython (0.25.2~b0-1) and running build of rdepends python-aiohttp failed to build with fakeroot debian/rules clean dh clean --with python3,sphinxdoc

Bug#845178: FTBFS with super-fresh cython -- seems to carry pre-cythoned sources which get rebuilt during clean

Source: python-aiohttp Version: 1.1.5-1 Severity: serious Justification: fails to build from source (but built successfully in the past) While preparing for upload of fresh cython (0.25.2~b0-1) and running build of rdepends python-aiohttp failed to build with dh_auto_clean I: pybuild base:184:

Bug#845173: Cannot handle new debs with data component XZ compressed in parallel

My fixes based on the latest git repo are available in the bugfixes branch of https://github.com/e7appew/debdelta.git. My fixes based on the latest version in sid are represented in the attached debdiff patch. diff -Nru debdelta-0.55/debdelta debdelta-0.55+nmu1/debdelta --- debdelta-0.55/debdelta

Bug#841575: [pkg-go] Bug#841575: docker-registry: FTBFS: Tests failures

On 20 November 2016 at 20:31, Tianon Gravi wrote: > I wasn't able to dig into the details yet, but looking at the log I > noticed the following which I believe is the real test failure output: That being said, I currently get the (more severe IMO) failure when trying to build

Bug#844872: marked as done (libreadline-java: FTBFS: org_gnu_readline_Readline.c:700:37: error: 'CPFunction' undeclared (first use in this function))

Your message dated Mon, 21 Nov 2016 04:33:27 + with message-id and subject line Bug#844872: fixed in libreadline-java 0.8.0.1+dfsg-5 has caused the Debian Bug report #844872, regarding libreadline-java: FTBFS: org_gnu_readline_Readline.c:700:37: error:

Bug#841575: [pkg-go] Bug#841575: docker-registry: FTBFS: Tests failures

On 21 October 2016 at 06:10, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. I wasn't able to dig into the details yet, but looking at the log I noticed the following which I believe is the real test failure output: >

Bug#844872: Pending fixes for bugs in the libreadline-java package

tag 844872 + pending thanks Some bugs in the libreadline-java package are closed in revision ba9c39e58e62271dbae11a3a0938b5bd6c4d19fc in branch 'master' by tony mancill The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/libreadline-java.git/commit/?id=ba9c39e Commit message:

Processed: Pending fixes for bugs in the libreadline-java package

Processing commands for cont...@bugs.debian.org: > tag 844872 + pending Bug #844872 [src:libreadline-java] libreadline-java: FTBFS: org_gnu_readline_Readline.c:700:37: error: 'CPFunction' undeclared (first use in this function) Added tag(s) pending. > thanks Stopping processing here. Please

Bug#837480: marked as done (gb: FTBFS with bindnow and PIE enabled)

Your message dated Mon, 21 Nov 2016 04:18:19 + with message-id and subject line Bug#837480: fixed in gb 0.4.2-2 has caused the Debian Bug report #837480, regarding gb: FTBFS with bindnow and PIE enabled to be marked as done. This means that you claim that

Bug#837480: Pending fixes for bugs in the gb package

tag 837480 + pending thanks Some bugs in the gb package are closed in revision 032c421a524ba63c18483d058eb931bc188a2e37 in branch 'master' by Tianon Gravi The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/gb.git/commit/?id=032c421 Commit message: Backport

Processed: Pending fixes for bugs in the gb package

Processing commands for cont...@bugs.debian.org: > tag 837480 + pending Bug #837480 [src:gb] gb: FTBFS with bindnow and PIE enabled Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 837480:

Bug#835686: 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".Contex

On 28 August 2016 at 03:23, Lucas Nussbaum wrote: >> ---> 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 >>

Bug#845173: Cannot handle new debs with data component XZ compressed in parallel

Package: debdelta Version: 0.55 Severity: grave Tags: patch Ever since dpkg 1.18.14 or 1.18.15 was released there haven't been too many usable debdeltas available for download. The reason being that debs that have their data component compressed in XZ format are now being done so in parallel,

Bug#842806: docker.io: Can't connect to the daemon

On 2 November 2016 at 00:25, Kurt Roeckx wrote: > I'm guessing this is something systemd sets up, but that I might > need to manually set up if not using it? Ah yeah, sounds like it -- did you install recommends when installing docker.io? That should've pulled in the

Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

severity 843530 important thanks On 8 November 2016 at 09:52, Tianon Gravi wrote: > Ouch, looks like we're now hitting > https://github.com/opencontainers/runc/issues/1175, which doesn't > appear to have a Docker or runc workaround yet (although adding >

Processed: Re: Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

Processing commands for cont...@bugs.debian.org: > severity 843530 important Bug #843530 [docker.io] docker.io: docker broken: oci runtime error: could not synchronize with container process Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you

Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

severity 832103 important thanks On 31 August 2016 at 12:02, Felipe Sateler wrote: > Ack. > > Anyway, isn't this a condition docker can detect (mismatch between > binaries and the running daemon)? In that case it could print a > suitable help message for the user. Yeah, I

Processed: Re: Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

Processing commands for cont...@bugs.debian.org: > severity 832103 important Bug #832103 [docker.io] docker.io: Can't run images after upgrading to 1.11.2~ds1-6 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 832103:

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

On 7 September 2016 at 14:18, Andreas Beckmann wrote: > Preparing to unpack .../golang-go_2%3a1.7~1_i386.deb ... > dpkg-maintscript-helper: error: directory '/usr/lib/go' contains files not > owned by package golang-go:i386, cannot switch to symlink > dpkg: error

Bug#845171: wine-development: FTBFS: ld aborts or segfaults

Source: wine-development Version: 1.9.22-1 Justification: FTBFS on i386, armel and armhf Severity: serious Tags: help wine-development 1.9.22-1 (in stretch) built successfully on all architectures when it was uploaded to unstable, but fails to build in a stretch environment on i386 now (amd64 is

Bug#843898: Something to try

On Sun, 20 Nov 2016 21:01:08 +, Tobias Hansen wrote: [...] >> $ ls -alh ~/.local/lib/python2.7/site-packages/backports/ total 12K >> drwxr-xr-x 3 sluque sluque 4.0K Oct 30 16:16 . drwx-- 20 sluque >> sluque 4.0K Oct 30 16:18 .. drwxr-xr-x 2 sluque sluque 4.0K Oct

Bug#845169: ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure')

Package: src:ruby-carrierwave Version: 0.10.0+gh-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:

Bug#845167: lemonldap-ng: FTBFS randomly (failing tests)

Package: src:lemonldap-ng Version: 1.9.5-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:

Bug#845164: ruby-spy: FTBFS randomly (failing tests)

Package: src:ruby-spy Version: 0.4.3-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:

Bug#828589: uw-imap: FTBFS with openssl 1.1.0

torsdag 3 november 2016 kl. 00:23:37 CET skrev Sebastian Andrzej Siewior: > On 2016-09-12 17:00:28 [+0200], Kurt Roeckx wrote: > > > But this problem existed before 1.1.0 support (this patch). > > > What do you recommend here? The builtin usage > > > (X509_VERIFY_PARAM_set_hostflags()) looks

Bug#844239: [request-tracker-maintainers] Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

On 20/11/16 21:32, Niko Tyni wrote: > On Sun, Nov 13, 2016 at 07:13:54PM +0200, Niko Tyni wrote: >> Package: request-tracker4 >> Version: 4.2.13-3 >> Severity: serious >> >> This package failed to build on the 'all' buildd: >> >> >>

Bug#845143: marked as done (cross-toolchain-base: FTBFS in stage1 gcc: libiberty uses libc headers)

Your message dated Mon, 21 Nov 2016 00:33:17 +0100 with message-id <6f5e8018-4a94-fb0a-8bd6-0b871eb38...@debian.org> and subject line Re: Bug#845143: cross-toolchain-base: FTBFS in stage1 gcc: libiberty uses libc headers has caused the Debian Bug report #845143, regarding cross-toolchain-base:

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

in-line :- On 21/11/2016, Guillem Jover wrote: > Hi! > > On Mon, 2016-11-21 at 01:47:45 +0530, shirish शिरीष wrote: >> The patch didn't work :( > > Well that it didn't work was actually also very useful! Because in > your case it should not have worked due to having debug

Processed: Here is a working patch, provided by Teppo Mäenpää

Processing commands for cont...@bugs.debian.org: > tag 725768 patch Bug #725768 [tkcvs] tkcvs: depends on tk8.4|tk8.5 and calls /usr/bin/wish Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 725768:

Bug#725768: Here is a working patch, provided by Teppo Mäenpää

tag 725768 patch thanks Hello, attached is a trival patch (provided by Teppo Mäenpää). I just tested, and it works rather well: the package builds and installs like a charm with this change. Once installed, tkdiff seems to work (at least, it starts). Tim, could you please take care of this

Bug#838228: marked as done (src:lakai: maintainer address bounces)

Your message dated Sun, 20 Nov 2016 23:18:20 + with message-id and subject line Bug#838228: fixed in lakai 0.1-2 has caused the Debian Bug report #838228, regarding src:lakai: maintainer address bounces to be marked as done. This means that you claim that

Processed: Part of the OpenSSL transition

Processing commands for cont...@bugs.debian.org: > block 827061 by 845016 845030 845106 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 844311 835804 828549 828334 828500 835797 828389 828586 828275 828409 828406 828139 828420 828272 828286 828512 828271 828577 828397

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

Hi! On Mon, 2016-11-21 at 01:47:45 +0530, shirish शिरीष wrote: > The patch didn't work :( Well that it didn't work was actually also very useful! Because in your case it should not have worked due to having debug output enabled. If you retry it again w/o debugging enabled it should work, and the

Bug#844914: rsyslog: FTBFS: Tests failures

Am 20.11.2016 um 23:24 schrieb Michael Biebl: > Am 20.11.2016 um 17:55 schrieb Rainer Gerhards: >> 2016-11-20 17:45 GMT+01:00 Michael Biebl : >>> Am 20.11.2016 um 16:17 schrieb Rainer Gerhards: Lucas found the right root cause: It looks like the preload lib is not

Bug#844914: rsyslog: FTBFS: Tests failures

Am 20.11.2016 um 17:55 schrieb Rainer Gerhards: > 2016-11-20 17:45 GMT+01:00 Michael Biebl : >> Am 20.11.2016 um 16:17 schrieb Rainer Gerhards: >>> Lucas found the right root cause: It looks like the preload lib is not >>> loaded on that platform. See >>>

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

at bottom :- On 21/11/2016, shirish शिरीष wrote: > at bottom :- > Trying with the new versions got this (again) - > > [$] sudo aptitude reinstall cme libconfig-model-perl > libconfig-model-dpkg-perl fonts-arphic-uming > [1:46:39] > The following packages will be

Bug#841606: marked as done (dleyna-server: FTBFS: upnp.h:119:1: error: unknown type name 'GUPnPContextManager')

Your message dated Sun, 20 Nov 2016 22:18:59 + with message-id and subject line Bug#841606: fixed in dleyna-server 0.4.0-1.1 has caused the Debian Bug report #841606, regarding dleyna-server: FTBFS: upnp.h:119:1: error: unknown type name

Processed: nfstrace: googletest related build failure

Processing control commands: > retitle -1 nfstrace: googletest related build failure Bug #844859 [src:nfstrace] nfstrace: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create' Changed Bug title to 'nfstrace: googletest related build

Bug#844859: nfstrace: googletest related build failure

Control: retitle -1 nfstrace: googletest related build failure The actual error is: ... CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock" because another target with the same name already exists. The

Processed: cppformat: googletest related build failure

Processing control commands: > retitle -1 cppformat: googletest related build failure Bug #844843 [src:cppformat] cppformat: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create' Changed Bug title to 'cppformat: googletest related build

Bug#844843: cppformat: googletest related build failure

Control: retitle -1 cppformat: googletest related build failure The actual error is: ... CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock" because another target with the same name already exists. The

Bug#844874: opensurgsim: googletest related build failure

Control: retitle -1 opensurgsim: googletest related build failure The actual error is: ... -- Found GoogleMock: /usr/src/gmock CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock" because another target with the

Processed: opensurgsim: googletest related build failure

Processing control commands: > retitle -1 opensurgsim: googletest related build failure Bug #844874 [src:opensurgsim] opensurgsim: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create' Changed Bug title to 'opensurgsim: googletest

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote: > So far I do not know why using libssl1.1 together with a > libssl1.0.2-using Qt wouldn't work. Well I don't know enough about the dynamic linker and about the internals of openssl to know if (indirectly) linking to both libraries

Bug#844393: blhc: diff for NMU version 0.07-0.2

Control: tags 844393 + patch Control: tags 844393 + pending Dear maintainer, I've prepared an NMU for blhc (versioned as 0.07-0.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru blhc-0.07/debian/changelog

Processed: blhc: diff for NMU version 0.07-0.2

Processing control commands: > tags 844393 + patch Bug #844393 [blhc] blhc still uses dpkg architecture triplets Added tag(s) patch. > tags 844393 + pending Bug #844393 [blhc] blhc still uses dpkg architecture triplets Added tag(s) pending. -- 844393:

Processed: bug 842205 is forwarded to https://github.com/alastair/python-musicbrainzngs/issues/211

Processing commands for cont...@bugs.debian.org: > forwarded 842205 https://github.com/alastair/python-musicbrainzngs/issues/211 Bug #842205 [src:musicbrainzngs] musicbrainzngs: FTBFS: UsageError: authorization required; use auth(user, pass) first Set Bug forwarded-to-address to

Bug#844835: orthanc: FTBFS: build-dependency not installable: libssl-dev

Dear Gert, orthnac build depends on libdcmtk-dev, and this pulls in libssl1.0-dev (since dcmtk (a) does not yet support openssl-1.1 and (b) it is used by programs that require QT which conflicts with openssl-1.1). libssl1.0-dev conflicts with libssl-dev, and hence the build failure. The

Bug#844794: marked as done (zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1))

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1) to be

Bug#844791: marked as done (openmeeg: FTBFS: build-dependency not installable: libvtk6-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding openmeeg: FTBFS: build-dependency not installable: libvtk6-dev to be marked as done.

Bug#844832: marked as done (yade: FTBFS: build-dependency not installable: libvtk6-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding yade: FTBFS: build-dependency not installable: libvtk6-dev to be marked as done. This

Bug#844714: marked as done (pycparser needs sourceful upload for new python-ply)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding pycparser needs sourceful upload for new python-ply to be marked as done. This means

Bug#844823: marked as done (swift-plugin-s3: FTBFS: build-dependency not installable: python-swift)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding swift-plugin-s3: FTBFS: build-dependency not installable: python-swift to be marked as

Bug#844811: marked as done (therion: FTBFS: build-dependency not installable: libvtk6-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding therion: FTBFS: build-dependency not installable: libvtk6-dev to be marked as done.

Bug#844827: marked as done (swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4))

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4) to be marked as

Bug#844814: marked as done (swauth: FTBFS: build-dependency not installable: swift-proxy (>= 2.2.0))

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding swauth: FTBFS: build-dependency not installable: swift-proxy (>= 2.2.0) to be marked

Bug#844840: marked as done (python-autobahn: FTBFS: unsatisfiable build-dependencies: python-nacl, python3-nacl)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding python-autobahn: FTBFS: unsatisfiable build-dependencies: python-nacl, python3-nacl

Bug#844808: marked as done (nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev to be marked as

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

20.11.2016 в 21:29:35 +0100 Jan Niehusmann написал: > On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote: > > It would be a grave bug in such application if it does not have a > > working version, yes. Whether or not it would be a serious bug in > > lubcurl3 depends on how many and

Bug#843898: Something to try

On 11/20/2016 08:29 PM, Sebastian P. Luque wrote: > On Sun, 20 Nov 2016 19:17:49 +, > Tobias Hansen wrote: > >> If you google this you see that tons of people have similar issues: >> https://github.com/ipython/ipython/issues/9656 >>

Bug#844796: gnome-shell: FTBFS: /<>/src/tmp-introspect2qs0g0tu/.libs/ShellMenu-0.1: error while loading shared libraries: libmutter-clutter-1.0.so: cannot open shared object file: No such

On 20/11/16 14:08, Michael Biebl wrote: > Am 20.11.2016 um 08:31 schrieb Lucas Nussbaum: >> Hi, >> >> On 20/11/16 at 01:33 +0100, Michael Biebl wrote: >>> Builds fine in a stretch chroot. >> >> Have you tried in a sid chroot? I just tried and can still reproduce it. >> (but I did not manage to

Processed: Bug#844714 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 844714 pending Bug #844714 [python-pycparser] pycparser needs sourceful upload for new python-ply Bug #844791 [python-pycparser] openmeeg: FTBFS: build-dependency not installable: libvtk6-dev Bug #844794 [python-pycparser] zaqar: FTBFS:

Bug#844714: marked as pending

tag 844714 pending thanks Hello, Bug #844714 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/pycparser.git;a=commitdiff;h=96eddb4 --- commit

Bug#845152: systemd-docker FTBFS in stretch due to missing golang-github-docker-docker-dev

Source: systemd-docker Version: 0.2.1+dfsg-2 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 systemd-docker build-depends on golang-github-docker-docker-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Processed: systemd-docker FTBFS in stretch due to missing golang-github-docker-docker-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845152 [src:systemd-docker] systemd-docker FTBFS in stretch due to missing golang-github-docker-docker-dev 845152 was not blocked by any bugs. 845152 was not blocking any bugs. Added blocking bug(s) of 845152: 842806,

Processed: nomad FTBFS in stretch due to missing golang-github-docker-docker-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845151 [src:nomad] nomad FTBFS in stretch due to missing golang-github-docker-docker-dev 845151 was not blocked by any bugs. 845151 was not blocking any bugs. Added blocking bug(s) of 845151: 842806, 835686, 843530, and

Bug#845151: nomad FTBFS in stretch due to missing golang-github-docker-docker-dev

Source: nomad Version: 0.4.0+dfsg-1 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 nomad build-depends on golang-github-docker-docker-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Processed: containerd FTBFS in stretch due to missing golang-github-docker-docker-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845149 [src:containerd] containerd FTBFS in stretch due to missing golang-github-docker-docker-dev 845149 was not blocked by any bugs. 845149 was not blocking any bugs. Added blocking bug(s) of 845149: 843530, 835686,

Processed: gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845150 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev 845150 was not blocked by any bugs. 845150 was not blocking any bugs. Added blocking bug(s) of

Bug#845149: containerd FTBFS in stretch due to missing golang-github-docker-docker-dev

Source: containerd Version: 0.2.1~ds1-3 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 containerd build-depends on golang-github-docker-docker-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Bug#845150: gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev

Source: gitlab-ci-multi-runner Version: 1.7.1+dfsg-2 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 gitlab-ci-multi-runner build-depends on golang-github-docker-docker-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Bug#845148: consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev

Source: consul Version: 0.6.4~dfsg-3 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 consul build-depends on golang-github-fsouza-go-dockerclient-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Processed: consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845148 [src:consul] consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev 845148 was not blocked by any bugs. 845148 was not blocking any bugs. Added blocking bug(s) of 845148: 843530, 835686,

Bug#845147: golang-github-appc-docker2aci FTBFS on i386 and arm*: error calling MarshalJSON for type types.Labels: bad arch

Source: golang-github-appc-docker2aci Version: 0.14.0+dfsg-1 Severity: serious https://buildd.debian.org/status/package.php?p=golang-github-appc-docker2aci ... --- FAIL: TestFetchingMultipleLayersV22 (0.00s) server.go:16: path requested: /v2/ server.go:16: path requested:

Bug#844239: [request-tracker-maintainers] Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

On Sun, Nov 13, 2016 at 07:13:54PM +0200, Niko Tyni wrote: > Package: request-tracker4 > Version: 4.2.13-3 > Severity: serious > > This package failed to build on the 'all' buildd: > > > https://buildd.debian.org/status/fetch.php?pkg=request-tracker4=all=4.2.13-3=1477439960 > > # Failed

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote: > It would be a grave bug in such application if it does not have a > working version, yes. Whether or not it would be a serious bug in > lubcurl3 depends on how many and how important such applications are. > (And how difficult

Processed: pike8.0: build-depends on heimdal-dev, which is to be removed from testing

Processing control commands: > block 837728 with -1 Bug #837728 [release.debian.org] RM: heimdal/1.7~git20150920+dfsg-4 837728 was blocked by: 837628 806264 837716 836885 837724 837728 was not blocking any bugs. Added blocking bug(s) of 837728: 845146 -- 837728:

Bug#843898: Something to try

On Sun, 20 Nov 2016 19:17:49 +, Tobias Hansen wrote: > If you google this you see that tons of people have similar issues: > https://github.com/ipython/ipython/issues/9656 > https://github.com/ipython/ipython/issues/9815 >

Bug#845146: pike8.0: build-depends on heimdal-dev, which is to be removed from testing

Source: pike8.0 Version: 8.0.276-1 Severity: serious Control: block 837728 with -1 Hi, Your package build-depends on heimdal-dev, but heimdal is going to be removed from testing (and possibly from the archive). See bugs #837728 and #834654 for the reasoning. You should stop build-depending on

Processed: Re: Bug#836597: lightspark: FTBFS on powerpc: segmentation fault during configure

Processing commands for cont...@bugs.debian.org: > severity 836597 important Bug #836597 [src:lightspark] lightspark: FTBFS on powerpc: segmentation fault during configure Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

at bottom :- On 20/11/2016, Guillem Jover wrote: > Control: retitle -1 dpkg-maintscript-helper: Version comparison fails for > supposedly valid versions > Control: severity -1 serious > > Hi! > > On Fri, 2016-11-18 at 14:02:39 +0530, shirish शिरीष wrote: >> Package: dpkg >>

Bug#836597: lightspark: FTBFS on powerpc: segmentation fault during configure

Control: tags -1 important On 20/11/16 13:58, Andrey Rahmatullin wrote: > Control: tags -1 + unreproducible > > On Sun, Sep 04, 2016 at 01:56:41PM +0200, Emilio Pozuelo Monfort wrote: >> Source: lightspark >> Version: 0.7.2+git20150512-2.1 >> Severity: serious >> >> Your package fails to build

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

20.11.2016 в 20:01:25 +0100 Jan Niehusmann написал: > On Sun, Nov 20, 2016 at 07:40:22PM +0400, Stepan Golosunov wrote: > > If SONAME change is needed it is needed when linking libcurl with > > libssl1.0.2 too. (But when linking libcurl with libssl1.0.2 more > > applications are affected due to

Bug#844638: marked as done (lua-sec needs Breaks: prosody (<< 0.9.11~))

Your message dated Sun, 20 Nov 2016 22:03:09 +0200 with message-id <20161120200309.hkszvaaxj5yrk...@bunk.spdns.de> and subject line This was fixed in lua-sec 0.6-2 has caused the Debian Bug report #844638, regarding lua-sec needs Breaks: prosody (<< 0.9.11~) to be marked as done. This means that

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

20.11.2016 в 23:38:48 +0400 Stepan Golosunov написал: > 20.11.2016 в 20:01:25 +0100 Jan Niehusmann написал: > > Still, for 1.1 the SONAME change is definitely necessary. > > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and > compiled with OpenSSL 1.0 will probably suffice in that

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

20.11.2016 в 20:48:44 +0100 Jan Niehusmann написал: > On Sun, Nov 20, 2016 at 11:38:49PM +0400, Stepan Golosunov wrote: > > > Still, for 1.1 the SONAME change is definitely necessary. > > > > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and > > compiled with OpenSSL 1.0 will

  1   2   3   >