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

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

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

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

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

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#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

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

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#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:

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]

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#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 >

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

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: >

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

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:

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.

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

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: 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

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

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

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:

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#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

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

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'),

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#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

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)

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

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,

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

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

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

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#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#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#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

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:

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=sid /«BUILDDIR»/choreonoid-1.5.0+dfsg/src/Base/ImageWidget.cpp: In member function 'void cnoid::ImageWidget::zoom(double)':

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

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

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#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: […]

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:

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

Bug#842248: marked as pending

tag 842248 pending thanks Hello, Bug #842248 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/urlgrabber.git;a=commitdiff;h=a65262e --- commit

Bug#839138: Ceph maintainership status

On Monday, 17 October 2016 8:53:30 PM AEDT László Böszörményi (GCS) wrote: > I'd a discussion with Dmitry and if I understood correctly, he no > longer wants to be a close contributor - but I let him speak about his > intentions. I confirm that. I had terrible experience with Ceph and I do not

Bug#828139: marked as done (cyrus-sasl2: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 09:21:47 +0100 with message-id <1477902107.1789783.772328257.7e0ef...@webmail.messagingengine.com> and subject line OpenSSL 1.1.0 has caused the Debian Bug report #828139, regarding cyrus-sasl2: FTBFS with openssl 1.1.0 to be marked as done. This means that

Bug#841631: marked as done (bandit: FTBFS: Tests failures)

Your message dated Mon, 31 Oct 2016 09:48:32 + with message-id and subject line Bug#841631: fixed in bandit 1.1.0-3 has caused the Debian Bug report #841631, regarding bandit: FTBFS: Tests failures to be marked as done. This means that you claim that the

Bug#841471: marked as done (fim: FTBFS on several architectures: default_font_byte_array.h:349:1: error: narrowing conversion of '905969664' from 'int' to 'unsigned char' inside { } [-Wnarrowing])

Your message dated Mon, 31 Oct 2016 09:48:40 + with message-id and subject line Bug#841471: fixed in fim 0.5~rc2-2 has caused the Debian Bug report #841471, regarding fim: FTBFS on several architectures: default_font_byte_array.h:349:1: error: narrowing

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

On 10/31/2016 05:13 AM, Anders Kaseorg wrote: > On Sun, 30 Oct 2016, Bas Couwenberg wrote: >> The recent git upload FTBFS on mips64el due to OOM, the missing build on >> mips64el is preventing the qgis rebuild as part of the ongoing gdal >> transition (#842288). >> >> The build was performed on

Bug#817523: libarray-refelem-perl: Removal of debhelper compat 4

Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/compat: Bump to 10. * debian/control: - Build-depend on debhelper (>= 10). - Depend on ${misc:Depends}. * debian/rules: - Switch to dh sequencer. *

Processed: Re: libarray-refelem-perl: Removal of debhelper compat 4

Processing control commands: > tags -1 patch Bug #817523 [src:libarray-refelem-perl] libarray-refelem-perl: Removal of debhelper compat 4 Bug #827681 [src:libarray-refelem-perl] libarray-refelem-perl: FTBFS: dh_clean: Compatibility levels before 5 are no longer supported (level 4 requested)

Processed: reassign 841343 to moarvm

Processing commands for cont...@bugs.debian.org: > reassign 841343 moarvm Bug #841343 [src:rakudo] rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite errors Bug reassigned from package 'src:rakudo' to 'moarvm'. No longer marked as found in versions rakudo/2016.09-2. Ignoring request to alter

Bug#828516: marked as done (pure-ftpd: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 09:50:31 + with message-id and subject line Bug#828516: fixed in pure-ftpd 1.0.43-2 has caused the Debian Bug report #828516, regarding pure-ftpd: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim

Bug#841516: marked as done (python-dogpile.cache: FTBFS randomly (AssertionError: 1 != 0))

Your message dated Mon, 31 Oct 2016 09:50:42 + with message-id and subject line Bug#841516: fixed in python-dogpile.cache 0.6.2-4 has caused the Debian Bug report #841516, regarding python-dogpile.cache: FTBFS randomly (AssertionError: 1 != 0) to be marked

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

On Mon, 31 Oct 2016 07:39:48 +0100 Sebastiaan Couwenberg wrote: > On 10/31/2016 05:13 AM, Anders Kaseorg wrote: > > On Sun, 30 Oct 2016, Bas Couwenberg wrote: > >> The recent git upload FTBFS on mips64el due to OOM, the missing build on > >> mips64el is preventing the qgis

Bug#839138: Ceph maintainership status

On Monday, 17 October 2016 9:34:35 PM AEDT Adrian Bunk wrote: > It would also be OK if you would state that there is noone left active > among the Ceph Maintainers, and that I can orphan the package for > finding new maintainers. I'm not going to maintain Ceph any more. I'm utterly disappointed

Processed: Bug#842248 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 842248 pending Bug #842248 [src:urlgrabber] urlgrabber: FTBFS randomly (build hangs) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 842248:

Bug#827811: marked as done (signond: FTBFS: dh_makeshlibs: failing due to earlier errors)

Your message dated Mon, 31 Oct 2016 10:02:18 +0100 with message-id <20161031090158.oiltodajxjtji...@gnuservers.com.ar> and subject line Re: Bug#827811: signond: FTBFS: dh_makeshlibs: failing due to earlier errors has caused the Debian Bug report #827811, regarding signond: FTBFS: dh_makeshlibs:

Bug#828396: marked as done (libisds: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 09:18:47 + with message-id and subject line Bug#828396: fixed in libisds 0.10.6-1 has caused the Debian Bug report #828396, regarding libisds: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim

Processed: bug 828607 is forwarded to https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html

Processing commands for cont...@bugs.debian.org: > forwarded 828607 > https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html Bug #828607 [src:xml-security-c] xml-security-c: FTBFS with openssl 1.1.0 Set Bug forwarded-to-address to

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

On Mon, 31 Oct 2016, Sebastiaan Couwenberg wrote: > Disabling the tests on mips64el is reasonable. > > You can also do a build on the mips64el porterbox if that succeeds > without changes you can just upload that. Alright. I am still a DM in the process of applying to be a DD, but I’ve now

Processed: fixed 835752 in 4:16.08.2-1

Processing commands for cont...@bugs.debian.org: > fixed 835752 4:16.08.2-1 Bug #835752 {Done: Maximiliano Curia } [src:dolphin] dolphin: FTBFS: dh_install: missing files, aborting Marked as fixed in versions dolphin/4:16.08.2-1. > thanks Stopping processing here. Please

Bug#842668: node-extend-shallow: FTBFS (Cannot find module 'is-extendable')

Package: src:node-extend-shallow Version: 2.0.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#842669: node-map-visit: FTBFS (Cannot find module 'should')

Package: src:node-map-visit Version: 0.1.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#842667: node-collection-visit: FTBFS (Cannot find module 'should')

Package: src:node-collection-visit Version: 0.2.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#828552: spamassassin: FTBFS with openssl 1.1.0

On 2016-10-29 14:15:30 [-0700], Noah Meyerhans wrote: > Control: tags -1 - patch + upstream > Control: forwarded -1 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7361 > > Unfortunately, this patch breaks compatibility with OpenSSL < 1.1.0, as > the CRYPTO_zalloc function does not exist

Bug#841748: esniper: needs update for recent eBay changes

On 29/10/16 15:52, Dmitry Smirnov wrote: Hi Dima, I've prepared esniper updates for to upload: https://anonscm.debian.org/cgit/collab-maint/esniper.git I intend to upload soon... Please review. Thanks. Hi Dmitry, Thanks for your help, I'm going to apply your changes to the newly

Bug#842248: marked as done (urlgrabber: FTBFS randomly (build hangs))

Your message dated Mon, 31 Oct 2016 09:08:05 + with message-id and subject line Bug#842248: fixed in urlgrabber 3.10.1-2 has caused the Debian Bug report #842248, regarding urlgrabber: FTBFS randomly (build hangs) to be marked as done. This means that you

Bug#835786: marked as done (lua-openssl: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 09:05:49 + with message-id and subject line Bug#835786: fixed in lua-openssl 20161029-1-g8caed30-1 has caused the Debian Bug report #835786, regarding lua-openssl: FTBFS with openssl 1.1.0 to be marked as done. This

Bug#835785: marked as done (lua-cqueues: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 09:05:43 + with message-id and subject line Bug#835785: fixed in lua-cqueues 20161018-1 has caused the Debian Bug report #835785, regarding lua-cqueues: FTBFS with openssl 1.1.0 to be marked as done. This means that you

Bug#828377: marked as done (ldns: FTBFS with openssl 1.1.0)

Your message dated Mon, 31 Oct 2016 09:05:37 + with message-id and subject line Bug#828377: fixed in ldns 1.6.17-10 has caused the Debian Bug report #828377, regarding ldns: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the

Bug#842669: marked as done (node-map-visit: FTBFS (Cannot find module 'should'))

Your message dated Mon, 31 Oct 2016 10:49:59 + with message-id and subject line Bug#842669: fixed in node-map-visit 0.1.5-2 has caused the Debian Bug report #842669, regarding node-map-visit: FTBFS (Cannot find module 'should') to be marked as done. This

Bug#841772: marked as done (grub-common: grub-mkconfig generates root= with empty UUID, making system unbootable)

Your message dated Mon, 31 Oct 2016 10:48:58 + with message-id and subject line Bug#841741: fixed in grub2 2.02~beta3-2 has caused the Debian Bug report #841741, regarding grub-common: grub-mkconfig generates root= with empty UUID, making system

Bug#842693: npgsql: FTBFS: CSC: error CS0518: The predefined type `System.Object' is not defined or imported

Source: npgsql Version: 2.2.7+dfsg3-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, npgsql fails to build from source in unstable/amd64:

Bug#841622: marked as done (tiledarray: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create')

Your message dated Mon, 31 Oct 2016 13:29:31 +0200 with message-id and subject line Re: tiledarray: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create' has caused the Debian Bug report

Bug#842339: marked as done (tar: CVE-2016-6321: Bypassing the extract path name)

Your message dated Mon, 31 Oct 2016 13:06:42 + with message-id and subject line Bug#842339: fixed in tar 1.29b-1.1 has caused the Debian Bug report #842339, regarding tar: CVE-2016-6321: Bypassing the extract path name to be marked as done. This means

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

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

Processing control commands: > reassign -1 python-keyring 10.0.2-1 Bug #842500 [src:python-launchpadlib] python-launchpadlib: FTBFS: error: Could not find suitable distribution for Requirement.parse('secretstorage') Bug reassigned from package 'src:python-launchpadlib' to 'python-keyring'. No

Bug#837228: marked as done (chef: FTBFS: ERROR: Test "ruby2.3" failed.)

Your message dated Mon, 31 Oct 2016 13:03:39 + with message-id and subject line Bug#837228: fixed in chef 12.14.60-1 has caused the Debian Bug report #837228, regarding chef: FTBFS: ERROR: Test "ruby2.3" failed. to be marked as done. This means that you

Processed: fixed 840806 in 2.1.0-5+deb8u7

Processing commands for cont...@bugs.debian.org: > fixed 840806 2.1.0-5+deb8u7 Bug #840806 [src:libgd2] libgd2: CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr() Marked as fixed in versions libgd2/2.1.0-5+deb8u7. > thanks Stopping processing here. Please contact me if you need

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

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

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

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

On Mon, 31 Oct 2016 13:06:09 +0100 (CET) Santiago Vila wrote: what's wrong while trying. > > Stupid question: Should this really be [^.].+\. or maybe [^.]+\. ? I'm not good with ruby either, ccing Balu. Also asking upstream for help https://github.com/stympy/faker/issues/737

Bug#841748: esniper: needs update for recent eBay changes

On Monday, 31 October 2016 8:48:30 AM AEDT Dima Barsky wrote: > Thanks for your help, I'm going to apply your changes to the newly > released esniper 2.32.0. I'll upload it a couple of days. Fantastic. :) Thank you. Upstream most likely incorporated authentication patch into new release but I

Bug#842702: Remote Code Execution on Zabbix 2.2 < 3.0.3

Package: zabbix-frontend-php Version: 1:2.2.7+dfsg-2+deb8u1 Severity: grave Zabbix on Jessie is vulnerable to remote code execution through exploit available in [1] (valid zabbix user/password is needed). I do not find any CVE related to this bug. [1] https://www.exploit-db.com/exploits/39937/

Processed: Bug #842679 affects haskell-debian

Processing commands for cont...@bugs.debian.org: > affects 842679 + haskell-debian Bug #842679 [ghc] haskell-debian: FTBFS: ghc: panic! (the 'impossible' happened) Added indication that 842679 affects haskell-debian > thanks Stopping processing here. Please contact me if you need assistance. --

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

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--

Bug#840806: closed by Ondřej Surý <ond...@debian.org> (Bug#840806: fixed in libgd2 2.2.3-87-gd0fec80-1)

Control: reopen -1 Hi Ondřej, While updating the security-tracker information I noticed: On Mon, Oct 31, 2016 at 10:21:15AM +, Debian Bug Tracking System wrote: [...] > + [CVE-2016-6911]: invalid read in gdImageCreateFromTiffPtr() [...] For the recently uploaded Version

Processed: squeezelite: NMU ongoing

Processing control commands: > tags -1 patch pending Bug #842330 [squeezelite] [PATCH] [RC] Fix syslog.h conflict with upcoming lirc-0.9.4 Added tag(s) pending. -- 842330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842330 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: Bug#840806 closed by Ondřej Surý <ond...@debian.org> (Bug#840806: fixed in libgd2 2.2.3-87-gd0fec80-1)

Processing control commands: > reopen -1 Bug #840806 {Done: Ondřej Surý } [src:libgd2] libgd2: CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr() 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may

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

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 autoremove" that did nothing). I > still had

  1   2   >