Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

Control: tags -1 + fixed I believe this bug has been fixed in . But I'm not the maintainer behind this package so I'll leave the rest for its maintainers. I found this bug during a rebuild of al

Processed: Re: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

Processing control commands: > tags -1 + fixed Bug #842721 [src:jayway-jsonpath] jayway-jsonpath: FTBFS (Could not resolve all dependencies) Added tag(s) fixed. -- 842721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842721 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#828302: Request for sponsorship for fqterm 0.9.8.3.r4+git20161029-1

Hi Aron, I have prepared a new release (snapshot) of fqterm which contains the fix for FTBFS with OpenSSL 1.1.0 from upstream git HEAD snapshot. Looking forward to your review and sponsorship. Changes since last upload: fqterm (0.9.8.3.r4+git20161029-1) unstable; urgency=medium * New upstre

Processed: Tag as forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 821481 https://jira.z-hub.io/projects/ZP/issues/ZP-804 Bug #821481 [d-push] d-push: PHP 7.0 Transition Set Bug forwarded-to-address to 'https://jira.z-hub.io/projects/ZP/issues/ZP-804'. > thanks Stopping processing here. Please contact

Processed: severity of 818280 is normal, tagging 818280

Processing commands for cont...@bugs.debian.org: > severity 818280 normal Bug #818280 [lvm2] upgrade-reports: System is unusable after "aptitute safe-upgrade" Severity set to 'normal' from 'critical' > tags 818280 + moreinfo Bug #818280 [lvm2] upgrade-reports: System is unusable after "aptitute

Bug#839435: marked as done (nsscache must build-depend on tzdata)

Your message dated Tue, 01 Nov 2016 04:18:57 + with message-id and subject line Bug#839435: fixed in nsscache 0.32-2 has caused the Debian Bug report #839435, regarding nsscache must build-depend on tzdata to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: Re: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd

Processing control commands: > tag -1 moreinfo Bug #841883 [src:linux] linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd Added tag(s) moreinfo. -- 841883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841883 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#841883: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd

Control: tag -1 moreinfo I think this may be the same as bug #841850 which is fixed in version 4.8.5-1.  Please let us know whether that works for you. Ben. -- Ben Hutchings Horngren's Observation:    Among economists, the real world is often a special case. signature.asc Desc

Processed: Fix for the clipper FTBFS

Processing control commands: > tags -1 patch Bug #811763 [clipper] clipper: FTBFS with GCC 6: narrowing conversion Added tag(s) patch. -- 811763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#811763: Fix for the clipper FTBFS

Control: tags -1 patch What broke the build is that gcc 6 changed the default C++ standard from C++98 to C++14. Not all valid C++98 code is also valid C++11 and C++14 code. Note that this just changed the default, when told to process C++98 code gcc 6 does not differ in any significant way from

Bug#842763: choreonoid FTBFS on armel and armhf: no matching function for call to 'QTransform::map(int, int, double*, double*)'

Source: choreonoid Version: 1.5.0+dfsg-0.1 Severity: serious https://buildd.debian.org/status/package.php?p=choreonoid&suite=sid /«BUILDDIR»/choreonoid-1.5.0+dfsg/src/Base/ImageWidget.cpp: In member function 'void cnoid::ImageWidget::zoom(double)': /«BUILDDIR»/choreonoid-1.5.0+dfsg/src/Base/Ima

Bug#834718: choreonoid: maintainer address bounces

On Thu, Aug 18, 2016 at 11:21:27AM +0200, Jakub Wilk wrote: > Source: choreonoid > Version: 1.5.0+dfsg-0.1 > Severity: serious > Justification: Policy §3.3 > > I tried to report a bug against this package, and I got: > > > Your mail to 'Ubuntu-devel-discuss' with the subject > > > >Bug#83471

Processed: This one also looks pretty RC

Processing commands for cont...@bugs.debian.org: > severity 760660 serious Bug #760660 [bindgraph] bindgraph, don't startup. Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 760660: http://bugs.debian.org/cgi-bin/bugreport

Bug#837420: marked as done (dietlibc: FTBFS with bindnow and PIE enabled)

Your message dated Tue, 01 Nov 2016 03:05:07 + with message-id and subject line Bug#837420: fixed in dietlibc 0.34~cvs20160606-3 has caused the Debian Bug report #837420, regarding dietlibc: FTBFS with bindnow and PIE enabled to be marked as done. This means that you claim that the problem ha

Processed: Re: Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

Processing control commands: > notfound -1 git/1:2.10.2-1 Bug #842586 [src:git] git: FTBFS on mips64el (fatal: Out of memory, getdelim failed) No longer marked as found in versions git/1:2.10.2-1. > close -1 Bug #842586 [src:git] git: FTBFS on mips64el (fatal: Out of memory, getdelim failed) Mar

Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

Control: notfound -1 git/1:2.10.2-1 Control: close -1 On Mon, 31 Oct 2016, Sebastiaan Couwenberg wrote: > I think we can close this issue as notfound in git/1:2.10.2-1, since the > most reliable mips64el buildd was able to build it successfully. Thanks, doing so. Anders

Bug#842753: FTBFS: test failures

Package: libnet-sip-perl Version: 0.690-1 Severity: serious Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 0.690-1 fails to build all over the place with more or less failing tests: https://buildd.debian.org/status/f

Bug#841511: python-bitbucket-api, python-bitbucket: error when trying to install together

On Mon, Oct 24, 2016 at 12:56:08PM +, David Villa wrote: > I think python-bitbucket can be removed. Its functionality is quite limited. Hi David, In that case, could you help to send a removal request? -- ChangZhuo Chen (陳昌倬) Debian Developer (https://nm.debian.org/public/person/czchen) K

Bug#836885: [Pkg-openldap-devel] Bug#836885: please stop building against Heimdal

On Tue, Nov 01, 2016 at 01:12:08AM +0100, Emilio Pozuelo Monfort wrote: This is blocking the removal of heimdal, thus bumping to serious. Yes, sorry about that. I am actively working on this, but it's not quite ready to upload yet.

Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

On 31 October 2016 at 17:12, Michael Hudson-Doyle wrote: > The question is, do we backport the fixes for golang-1.6, or just remove it > from the archive? Looks like removal would be fairly straightforward; the only package currently affected is "golang-github-docker-go", which could just as well

Bug#773205: libatomic-ops-dev: FTBFS on mips64el

I'm sorry about this. I must have misread the history of that branch My preference is to be in sync with upstream, so I have asked if we can get this in a 7.4.5 release [1] If no response, or not possible, I'll add these back in Thanks, -i [1] https://github.com/ivmai/libatomic_ops/issues/20

Bug#837485: [pkg-golang-devel] Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

I fixed this problem a while ago upstream for Go 1.7 ( https://github.com/golang/go/issues/15443, https://github.com/golang/go/issues/15887). The question is, do we backport the fixes for golang-1.6, or just remove it from the archive? I'd lean towards the latter. On 1 November 2016 at 08:18, Niel

Processed: Re: please stop building against Heimdal

Processing control commands: > severity -1 serious Bug #836885 [src:openldap] please stop building against Heimdal Severity set to 'serious' from 'important' -- 836885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Removal of Heimdal from testing

Processing control commands: > severity -1 serious Bug #837628 [libheimdal-kadm5-perl] Removal of Heimdal from testing Severity set to 'serious' from 'normal' -- 837628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#818561: Useless in Debian

Hi Axel, haskell-hoogle maintainers, Le 31/10/2016 à 13:25, Axel Beckert a écrit : > David Prévot wrote: >> Package: libjs-chosen >> Version: 0.9.11-2 >> Severity: serious >> Tags: sid stretch >> >> [ Filled as an RC-bug by the maintainer to see the package auto-removed >> from testing. ] >> >>

Bug#842752: postgresql-9.6: FTBFS: test failures on i386/armel/armhf

Source: postgresql-9.6 Version: 9.6.1-1 Severity: serious Your package failed to build on i386, armel and armhf with test errors. See the logs at https://buildd.debian.org/status/package.php?p=postgresql-9.6 Emilio -- System Information: Debian Release: stretch/sid APT prefers unstable APT

Bug#842751: fim: FTBFS on several architectures

Package: fim Version: 0.5~rc2-2 Severity: serious Your package still fails to build on several architectures. See the logs at https://buildd.debian.org/status/package.php?p=fim Emilio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (700,

Bug#830423: marked as done (connect-proxy: FTBFS: dpkg-buildpackage: error: dpkg-genchanges gave error exit status 25)

Your message dated Mon, 31 Oct 2016 23:48:40 + with message-id and subject line Bug#830423: fixed in connect-proxy 1.105-1 has caused the Debian Bug report #830423, regarding connect-proxy: FTBFS: dpkg-buildpackage: error: dpkg-genchanges gave error exit status 25 to be marked as done. This

Bug#841597: blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

Thanks your report. But in my environment that I made with pbuilder and cowbuilder, the problem does not reappear. Please tell me your environmental how to make because I want to test it in the same environment. Best regards, -- Kouhei Maeda KeyID 4096R/7E37CE41 2016-10-21 22:38 GMT+09:00 Luca

Bug#818561: Useless in Debian

Hi, David Prévot wrote: > Package: libjs-chosen > Version: 0.9.11-2 > Severity: serious > Tags: sid stretch > > [ Filled as an RC-bug by the maintainer to see the package auto-removed > from testing. ] > > I packaged libjs-chosen as used by owncloud, but owncloud is going away, > see #816376.

Bug#829477: marked as done (courier-mta: fails to install: Invalid command 'gendh')

Your message dated Mon, 31 Oct 2016 23:19:05 + with message-id and subject line Bug#829477: fixed in courier 0.76.3-1 has caused the Debian Bug report #829477, regarding courier-mta: fails to install: Invalid command 'gendh' to be marked as done. This means that you claim that the problem has

Bug#828272: marked as done (courier: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 23:19:05 + with message-id and subject line Bug#828272: fixed in courier 0.76.3-1 has caused the Debian Bug report #828272, regarding courier: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#818280: upgrade-reports: System is unusable after "aptitute safe-upgrade" [SOLVED]

Control: reassign -1 lvm2 On Wed, 16 Mar 2016 17:51:32 +0100 Gilles Sadowski wrote: > Hi. > > It turned out that the problem was related to LVM partitions not being > "available" while "systemd" was trying to run "fsck" on them. > > In maintenance mode, I just ran > > # vgchange -a y theVolum

Processed: Re: Bug#818280: upgrade-reports: System is unusable after "aptitute safe-upgrade" [SOLVED]

Processing control commands: > reassign -1 lvm2 Bug #818280 [systemd] upgrade-reports: System is unusable after "aptitute safe-upgrade" Bug reassigned from package 'systemd' to 'lvm2'. Ignoring request to alter found versions of bug #818280 to the same values previously set Ignoring request to a

Processed: Re: Bug#828579: trousers: FTBFS with openssl 1.1.0

Processing control commands: > tags -1 patch Bug #828579 [src:trousers] trousers: FTBFS with openssl 1.1.0 Added tag(s) patch. -- 828579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#828579: trousers: FTBFS with openssl 1.1.0

control: tags -1 patch On 2016-06-26 12:24:29 [+0200], Kurt Roeckx wrote: > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build can be found at: > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/trous

Bug#829477: courier-mta: fails to install: Invalid command 'gendh'

Yes, I already had a fix in repo (use dhparam -2 instead) and I have just uploaded that. Ondřej On 31 October 2016 11:24:13 PM Andreas Beckmann wrote: On 2016-10-31 16:32, Stefan Hornburg (Racke) wrote: On 07/03/2016 07:07 PM, Andreas Beckmann wrote: Package: courier-mta Version: 0.76.1-3

Processed: Re: pkcs11-helper: FTBFS with openssl 1.1.0

Processing control commands: > forwarded -1 https://github.com/OpenSC/pkcs11-helper/pull/7 Bug #828506 [src:pkcs11-helper] pkcs11-helper: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to 'https://github.com/OpenSC/pkcs11-helper/pull/7'. > tags -1 patch Bug #828506 [src:pkcs11-helper] pkcs

Bug#828506: pkcs11-helper: FTBFS with openssl 1.1.0

control: forwarded -1 https://github.com/OpenSC/pkcs11-helper/pull/7 control: tags -1 patch On 2016-06-26 12:23:44 [+0200], Kurt Roeckx wrote: > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build can be found at: >

Bug#828259: cargo: FTBFS with openssl 1.1.0

On 2016-06-26 12:21:14 [+0200], Kurt Roeckx wrote: > Source: cargo > Version: 0.9.0-1 > Severity: important > Control: block 827061 by -1 > > Hi, > > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build can be found

Bug#841420: Breaks Nvidia driver install from .run

I can confirm that the new version of GCC breaks the module's compilation when i try to install the Nvidia driver for my graphic card from the .run file. The only solution that i found was to launch "export CC=/usr/bin/gcc-5" before to launch the driver's installation Cheers, Maxime

Bug#842748: incremental: FTBFS (failing tests)

Package: src:incremental Version: 16.10.1-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#829477: courier-mta: fails to install: Invalid command 'gendh'

On 2016-10-31 16:32, Stefan Hornburg (Racke) wrote: > On 07/03/2016 07:07 PM, Andreas Beckmann wrote: >> Package: courier-mta >> Version: 0.76.1-3+exp1 > I believe this line in the script /usr/lib/courier/mkesmtpdcert > causes the error: > > /usr/bin/openssl gendh -rand "$PEMFILE".rand 512

Processed: Move to systemd

Processing commands for cont...@bugs.debian.org: > reassign 818280 systemd Bug #818280 [upgrade-reports] upgrade-reports: System is unusable after "aptitute safe-upgrade" Bug reassigned from package 'upgrade-reports' to 'systemd'. Ignoring request to alter found versions of bug #818280 to the sam

Processed: Kernel issue?

Processing commands for cont...@bugs.debian.org: > reassign 842458 src:linux Bug #842458 [upgrade-reports] upgrade-reports: After dist-upgrade from jessie to testing, kernel doesn't load, not a single message on screen Bug reassigned from package 'upgrade-reports' to 'src:linux'. Ignoring request

Processed: libghc-lambdabot-haskell-plugins-dev: inane memory usage during profiling build

Processing control commands: > forwarded -1 https://ghc.haskell.org/trac/ghc/ticket/12790 Bug #842740 [libghc-lambdabot-haskell-plugins-dev] libghc-lambdabot-haskell-plugins-dev: inane memory usage during profiling build Set Bug forwarded-to-address to 'https://ghc.haskell.org/trac/ghc/ticket/127

Bug#842740: libghc-lambdabot-haskell-plugins-dev: inane memory usage during profiling build

Package: libghc-lambdabot-haskell-plugins-dev Version: 5.1-2 Severity: serious Control: forwarded -1 https://ghc.haskell.org/trac/ghc/ticket/12790 Number of terms skyrockets during Simplify, probable GHC bug.

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

On Mon, Oct 31, 2016 at 12:31 AM, Konstantin Demin wrote: > I have tested several scenarios and "KCPPFLAGS=-fno-PIE" does that > trick much better :-) > > -- > SY, > Konstantin Demin uname -a Linux cohuatlicue 4.7.10.tezcatlipoca #1 SMP PREEMPT Mon Oct 31 09:47:07 PDT 2016 x86_64 GNU/Linux i.e.,

Bug#842710: [gcc-6] Fails to compile OpenWrt/LEDE prereq-build

Control: reassign -1 release.debian.org Control: severity -1 normal Control: retitle -1 nmu: zlib_1:1.2.8.dfsg-2 Control: affects -1 src:zlib On Mon, Oct 31, 2016 at 03:27:11PM +0100, Charlemagne Lasse wrote: > Package: gcc-6 > Version: 6.2.0-10 > Severity: serious > X-Debbugs-CC: lede-...@lists.i

Processed: Re: [gcc-6] Fails to compile OpenWrt/LEDE prereq-build

Processing control commands: > reassign -1 release.debian.org Bug #842710 [gcc-6] [gcc-6] Fails to compile OpenWrt/LEDE prereq-build Bug reassigned from package 'gcc-6' to 'release.debian.org'. No longer marked as found in versions gcc-6/6.2.0-10. Ignoring request to alter fixed versions of bug #8

Processed: fixed upstream

Processing commands for cont...@bugs.debian.org: > tags 828469 fixed-upstream Bug #828469 [src:openipmi] openipmi: FTBFS with openssl 1.1.0 Added tag(s) fixed-upstream. > forwarded 828469 > https://sourceforge.net/p/openipmi/code/ci/eeacbf0c675b61881fc00539cb365de084950ceb/ Bug #828469 [src:openi

Processed: tag security

Processing commands for cont...@bugs.debian.org: > tags 842702 security Bug #842702 [zabbix-frontend-php] Remote Code Execution on Zabbix 2.2 < 3.0.3 Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 842702: http://bugs.debian.org/cgi-bin/bugr

Bug#842737: ohai: FTBFS: Could not find 'addressable' (>= 0) among 31 total gem(s) (Gem::LoadError)

Source: ohai Version: 8.21.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ohai fails to build from source in unstable/amd64: […] ┌──

Bug#837359: ocaml: FTBFS on -fPIE binNMU on armhf - test failure

On Mon, Oct 31, 2016 at 06:46:00PM +, Niels Thykier wrote: > Control: retitle -1 ocaml: FTBFS on -fPIE binNMU on armhf - test failure > > Dear maintainer, > > We have tried to binNMU ocaml in unstable now that PIE is on by default. > This worked fine on all release architectures except armhf

Bug#838812: pg_upgradecluster skips databases owned by a role who is not a user

Package: postgresql-common Version: 177.pgdg80+1 Followup-For: Bug #838812 Dear Maintainer, I can confirm the problem; the attached patch fixes it. A brief explanation: In the query to select databases which need upgrading, pg_database is joined onto pg_user, which is a view of pg_shadow, which

Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

On Mon, 12 Sep 2016 00:55:37 +0200 Balint Reczey wrote: > Source: golang-1.6 > Version: 1.6.3-1 > Severity: important > User: bal...@balintreczey.hu > Usertags: pie-bindnow-20160906 > Justification: FTBFS on amd64 with extra hardening > Tags: patch > > Hi, > > During a rebuild of all packages in

Bug#774082: What is the solution/workaround ?

Le 31/10/2016 à 18:22, Benoit Plessis a écrit : > > Hi, > > I am also affected by this issue, where the initramfs only activate the > root/usr lv's > > what is the recommended jessie workaround, disabling lvmetad ? The workaround I gave in my comment #74 [1] allows me to use lvmetad on all my j

Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

On Mon, 31 Oct 2016 15:30:52 + James Cowgill wrote: > I've had a bit of a look at this bug. I've now tried to build git on two > different machines running different hardware (octeon and loongson) and > it built fine both times so I'm not too sure what's going on here. > > All 3 builds which f

Bug#837569: marked as done (psicode needs PIE binNMU)

Your message dated Mon, 31 Oct 2016 18:53:00 + with message-id and subject line Re: mpqc3: FTBFS with bindnow and PIE enabled has caused the Debian Bug report #837569, regarding psicode needs PIE binNMU to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#837359: ocaml: FTBFS on -fPIE binNMU on armhf - test failure

Control: retitle -1 ocaml: FTBFS on -fPIE binNMU on armhf - test failure Dear maintainer, We have tried to binNMU ocaml in unstable now that PIE is on by default. This worked fine on all release architectures except armhf, where 4 tests failed: """ Summary: 468 test(s) passed 4 test(s) fa

Processed: Re: Bug#837359: ocaml: FTBFS on -fPIE binNMU on armhf - test failure

Processing control commands: > retitle -1 ocaml: FTBFS on -fPIE binNMU on armhf - test failure Bug #837359 [src:ocaml] ocaml needs PIE binNMU Changed Bug title to 'ocaml: FTBFS on -fPIE binNMU on armhf - test failure' from 'ocaml needs PIE binNMU'. -- 837359: http://bugs.debian.org/cgi-bin/bugr

Bug#841683: marked as done (lp-solve needs PIE binNMU)

Your message dated Mon, 31 Oct 2016 18:49:00 + with message-id and subject line Re: liblpsolve55-dev: Please build liblpsolve55.a with -fPIC has caused the Debian Bug report #841683, regarding lp-solve needs PIE binNMU to be marked as done. This means that you claim that the problem has been

Bug#806118: marked as done (tiff: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

Your message dated Mon, 31 Oct 2016 18:37:29 + with message-id and subject line Bug#806118: fixed in tiff 4.0.6-3 has caused the Debian Bug report #806118, regarding tiff: FTBFS when built with dpkg-buildpackage -A (No such file or directory) to be marked as done. This means that you claim t

Bug#841343: marked as done (rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite errors)

Your message dated Mon, 31 Oct 2016 18:04:37 + with message-id and subject line Bug#841343: fixed in moarvm 2016.10+dfsg-1 has caused the Debian Bug report #841343, regarding rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite errors to be marked as done. This means that you claim that the

Bug#842722: marked as done (kgb-bot: FTBFS (failing tests))

Your message dated Mon, 31 Oct 2016 18:04:00 + with message-id and subject line Bug#842722: fixed in kgb-bot 1.34-2 has caused the Debian Bug report #842722, regarding kgb-bot: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#841420: Patch to allow build

> -Original Message- > From: Arthur Gautier [mailto:ba...@gandi.net] > On Sun, Oct 30, 2016 at 01:32:14AM -0300, Raymond Burkholder wrote: > > Step 1: > > > > scripts/config --disable CC_STACKPROTECTOR_STRONG > > This is a step forward security, we can not just disable it on production >

Processed: [bts-link] source package src:pen

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pen > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.o

Bug#840664: marked as done (ruby-faker: FTBFS randomly (failing tests))

Your message dated Mon, 31 Oct 2016 17:49:30 + with message-id and subject line Bug#840664: fixed in ruby-faker 1.6.6-1 has caused the Debian Bug report #840664, regarding ruby-faker: FTBFS randomly (failing tests) to be marked as done. This means that you claim that the problem has been deal

Processed: [bts-link] source package esniper

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package esniper > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.o

Bug#841614: node-es6-promise: FTBFS: compile-modules shows help

Hi, On 31/10/2016 08:01, Lucas Nussbaum wrote: On 29/10/16 at 11:14 +0200, Julien Puydt wrote: Hi, I tried to "pbuilder create" a new base.tgz, but it still had tzdata and lsb-base, so I had to "pbuilder login --save-after-login" and remove them by hand using "dpkg --purge" (then "apt-get auto

Processed: [bts-link] source package src:pythonmagick

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pythonmagick > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth

Processed: [bts-link] source package src:ettercap

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ettercap > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.deb

Bug#774082: What is the solution/workaround ?

Hi, I am also affected by this issue, where the initramfs only activate the root/usr lv's what is the recommended jessie workaround, disabling lvmetad ? -- Benoit Plessis +33 6 77 42 78 32 4096R/44E6FA9A 486D 2804 3EAB 3D74 5D05 826D 997F 26D9 44E6 FA9A

Bug#842722: [kgb-maintainers] Bug#842722: kgb-bot: FTBFS (failing tests)

Control: tag -1 + confirmed On Mon, 31 Oct 2016 16:42:43 +, Santiago Vila wrote: > Package: src:kgb-bot > Version: 1.34-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 t

Processed: Re: [kgb-maintainers] Bug#842722: kgb-bot: FTBFS (failing tests)

Processing control commands: > tag -1 + confirmed Bug #842722 [src:kgb-bot] kgb-bot: FTBFS (failing tests) Added tag(s) confirmed. -- 842722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#842722: kgb-bot: FTBFS (failing tests)

Package: src:kgb-bot Version: 1.34-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#842723: python-pytils: FTBFS (failing tests)

Package: src:python-pytils Version: 0.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#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

Package: src:jayway-jsonpath Version: 2.0.0-2 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#841420: Patch to allow build

On Sun, Oct 30, 2016 at 01:32:14AM -0300, Raymond Burkholder wrote: > Step 1: > > scripts/config --disable CC_STACKPROTECTOR_STRONG This cannot be a serious step. The original commit message and message on LKML: http://lkml.iu.edu/hypermail/linux/kernel/1312.2/03960.html This is a step forward

Bug#828298: marked as done (ettercap: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 16:33:38 + with message-id and subject line Bug#828298: fixed in ettercap 1:0.8.2-3 has caused the Debian Bug report #828298, regarding ettercap: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#828584: marked as done (unbound: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 16:01:04 + with message-id and subject line Bug#828584: fixed in unbound 1.5.10-1 has caused the Debian Bug report #828584, regarding unbound: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#811988: marked as done (libcgicc: FTBFS with GCC 6: call overloaded is ambiguous)

Your message dated Mon, 31 Oct 2016 16:00:24 + with message-id and subject line Bug#811988: fixed in libcgicc 3.2.16-0.1 has caused the Debian Bug report #811988, regarding libcgicc: FTBFS with GCC 6: call overloaded is ambiguous to be marked as done. This means that you claim that the proble

Bug#842591: debootstrap-udeb: fails to validate InRelease (BADSIG)

On Mon, Oct 31, 2016 at 04:18:55PM +0100, Cyril Brulebois wrote: > No, the “certainly did” and “worked fine” bits are wrong. > > And that's not just me, we've had users report it, Philip Hands saw it > as well. So no it did *NOT* work (in the specific case where it actually > matters). Yes, turns

Processed: limit source to dacs, tagging 737641, tagging 828277, tagging 729475

Processing commands for cont...@bugs.debian.org: > limit source dacs Limiting to bugs with field 'source' containing at least one of 'dacs' Limit currently set to 'source':'dacs' > tags 737641 + pending Bug #737641 [dacs] dacs: [PATCH] Enable build on newer arches Added tag(s) pending. > tags 828

Bug#829477: courier-mta: fails to install: Invalid command 'gendh'

On 07/03/2016 07:07 PM, Andreas Beckmann wrote: > Package: courier-mta > Version: 0.76.1-3+exp1 > 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 thi

Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

Hi, I've had a bit of a look at this bug. I've now tried to build git on two different machines running different hardware (octeon and loongson) and it built fine both times so I'm not too sure what's going on here. All 3 builds which failed were Loongson machines running 3.16 kernels. While I kn

Bug#842500: marked as done (python-launchpadlib: FTBFS: error: Could not find suitable distribution for Requirement.parse('secretstorage'))

Your message dated Mon, 31 Oct 2016 15:25:16 + with message-id and subject line Bug#842500: fixed in python-keyring 10.0.2-2 has caused the Debian Bug report #842500, regarding python-launchpadlib: FTBFS: error: Could not find suitable distribution for Requirement.parse('secretstorage') to be

Bug#842591: debootstrap-udeb: fails to validate InRelease (BADSIG)

Lennart Sorensen (2016-10-31): > On Sun, Oct 30, 2016 at 05:28:57PM +0100, Cyril Brulebois wrote: > > The (re)addition of InRelease support broke debootstrap(-udeb) in a d-i > > context. The sed|tr|sed dance doesn't kill the final newline, which > > leads to a BAD signature. > > The one I propose

Processed: closing 838216

Processing commands for cont...@bugs.debian.org: > close 838216 12.14.60-1 Bug #838216 [chef] Could not find 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError) Marked as fixed in versions chef/12.14.60-1. Bug #838216 [chef] Could not find 'chef-zero' (~> 4.5) - did find: [chef-z

Processed: reassign 834126 open-gram

Processing commands for cont...@bugs.debian.org: > reassign 834126 open-gram Bug #834126 {Done: Liang Guo } [sunpinyin-utils] open-gram: FTBFS: make[1]: *** [lm_sc.t3g] Aborted (core dumped) Bug reassigned from package 'sunpinyin-utils' to 'open-gram'. Ignoring request to alter found versions of

Processed: Re: src:librsync: FTBFS on big-endian architectures

Processing commands for cont...@bugs.debian.org: > retitle 780507 src:librsync: FTBFS on big-endian architectures Bug #780507 [src:librsync] src:librsync: FTBFS on BE Changed Bug title to 'src:librsync: FTBFS on big-endian architectures' from 'src:librsync: FTBFS on BE'. > thanks Stopping process

Bug#780507: src:librsync: FTBFS on big-endian architectures

retitle 780507 src:librsync: FTBFS on big-endian architectures thanks Renaming for clarity. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#842713: ocamlbuild: FTBFS: E: Error: unit Ocamlbuild exported in ocamlbuild but already exported by ocaml-nox/ocaml-base-nox v4.02.3-7+b1

Source: ocamlbuild Version: 0.9.3-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ocamlbuild fails to build from source in experimental/amd64:

Bug#842591: debootstrap-udeb: fails to validate InRelease (BADSIG)

On Sun, Oct 30, 2016 at 05:28:57PM +0100, Cyril Brulebois wrote: > Package: debootstrap-udeb > Version: 1.0.85 > Severity: grave > Justification: renders package unusable > > The (re)addition of InRelease support broke debootstrap(-udeb) in a d-i > context. The sed|tr|sed dance doesn't kill the fi

Bug#842710: [gcc-6] Fails to compile OpenWrt/LEDE prereq-build

Package: gcc-6 Version: 6.2.0-10 Severity: serious X-Debbugs-CC: lede-...@lists.infradead.org There is a regression after gcc-6 6.2.0-6. I get following output when trying to compile LEDE/OpenWrt "Please install a static zlib" This is wrong $ ls -ltr /usr/lib/x86_64-linux-gnu/libz.a -rw-r--r-- 1

Processed: Bug#842500 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 842500 pending Bug #842500 [python-keyring] python-launchpadlib: FTBFS: error: Could not find suitable distribution for Requirement.parse('secretstorage') Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#842500: marked as pending

tag 842500 pending thanks Hello, Bug #842500 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/python-keyring.git;a=commitdiff;h=4577db6 --- commit 4577db603ddfb5

Processed: forwarded upstream

Processing commands for cont...@bugs.debian.org: > forwarded 840664 https://github.com/stympy/faker/issues/737 Bug #840664 [src:ruby-faker] ruby-faker: FTBFS randomly (failing tests) Set Bug forwarded-to-address to 'https://github.com/stympy/faker/issues/737'. > End of message, stopping processing

Processed: ncmpc: NMU uploaded in deferred/queue

Processing control commands: > tags -1 patch pending Bug #842326 [ncmpc] [PATCH] [RC] Fix FTBS for when building against upcoming lirc-0.9.4 Added tag(s) pending. -- 842326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842326 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#842500: python-launchpadlib: FTBFS: error: Could not find suitable distribution for Requirement.parse('secretstorage')

Control: reassign -1 python-keyring 10.0.2-1 Control: affects -1 src:python-launchpadlib Hi Chris, On Sat, Oct 29, 2016 at 07:15:19PM +0100, Chris Lamb wrote: > Dear Maintainer, > > python-launchpadlib fails to build from source in unstable/amd64: > > […] > error: Could not find suitable dist

  1   2   >