Bug#826042: MICROSOFT OUTLOOK NOTIFICATION

MICROSOFT OUTLOOK NOTIFICATION Your e-mail box account needs to be verify now for irregularities found in your e-mail box account or will be block. Do verify immediately Microsoft Security Outlook Team Thank You. Copyright © 2017 Microsoft Outlook .Inc

Processed: retitle 850017 to icoutils: CVE-2017-5208: exploitable crash in wrestool

Processing commands for cont...@bugs.debian.org: > retitle 850017 icoutils: CVE-2017-5208: exploitable crash in wrestool Bug #850017 {Done: Colin Watson } [icoutils] Exploitable crash in wrestool Changed Bug title to 'icoutils: CVE-2017-5208: exploitable crash in wrestool'

Processed: closing 850017

Processing commands for cont...@bugs.debian.org: > close 850017 0.31.0-2+deb8u1 Bug #850017 {Done: Colin Watson } [icoutils] Exploitable crash in wrestool Marked as fixed in versions icoutils/0.31.0-2+deb8u1. Bug #850017 {Done: Colin Watson } [icoutils]

Bug#850017: closing 850017

close 850017 0.31.0-2+deb8u1 thanks

Bug#796617: marked as done (fsprotect: Has init script in runlevel S but no matching service file)

Your message dated Mon, 09 Jan 2017 04:50:24 + with message-id and subject line Bug#796617: fixed in fsprotect 1.0.7 has caused the Debian Bug report #796617, regarding fsprotect: Has init script in runlevel S but no matching service file to be marked as

Bug#819992: marked as done ([fsprotect] Requires aufs kernel module which is not part of Debian)

Your message dated Mon, 09 Jan 2017 04:50:24 + with message-id and subject line Bug#819992: fixed in fsprotect 1.0.7 has caused the Debian Bug report #819992, regarding [fsprotect] Requires aufs kernel module which is not part of Debian to be marked as

Bug#849628: ufw: FTBFS: Command '--dry-run route allow ssh/udp' exited with '1', but expected '0'

On Sun, 2017-01-08 at 07:39 -0600, Jamie Strandboge wrote: > On Thu, 2016-12-29 at 09:10 +, Chris Lamb wrote: > >   Command '--dry-run allow ssh/udp' exited with '1', but expected '0' > >   ** FAIL ** FYI, this is now fixed in trunk and this will be fixed in 0.35-3 which will be uploaded

Bug#850661: marked as done (Provides line defines versioned virtual packages)

Your message dated Mon, 9 Jan 2017 15:26:47 +1300 with message-id <20170109022647.t3zkcz46rgotb...@fishbowl.rw.madduck.net> and subject line Policy is being updated has caused the Debian Bug report #850661, regarding Provides line defines versioned virtual packages to be marked as done. This

Bug#850661: Provides line defines versioned virtual packages

Hi martin (2017.01.09_02:36:38_+0200) > Provides defines virtual packages, and those do not (and cannot as > it wouldn't make sense) carry version numbers. They have been supported in dpkg since 1.17.11, and other tools since. Pypy is not the only package to use them. And it waited until they

Bug#850663: baresip-ffmpeg,baresip-gstreamer,baresip-x11: Missing Breaks/Replaces on baresip/0.4.20-1

Package: baresip-ffmpeg,baresip-gstreamer,baresip-x11 Version: baresip/0.5.0-1~exp4 Severity: serious Dear Debian Baresip Maintainers, installing baresip-ffmpeg, baresip-gstreamer, or baresip-x11 from experimental while baresip from unstable is already installed, results in the following

Bug#850661: Provides line defines versioned virtual packages

Package: pypy-lib Version: 5.3.1+dfsg-1 Severity: serious aptitude complains about the Provides line for pypy-lib: W: Ignoring Provides line with DepCompareOp for package pypy-cffi W: Ignoring Provides line with DepCompareOp for package pypy-cffi-backend-api-max W: Ignoring Provides line with

Bug#848736: marked as done (freebsd-buildutils: FTBFS: ld: cannot find -ll)

Your message dated Sun, 08 Jan 2017 23:20:23 + with message-id and subject line Bug#848736: fixed in freebsd-buildutils 10.3~svn296373-6 has caused the Debian Bug report #848736, regarding freebsd-buildutils: FTBFS: ld: cannot find -ll to be marked as

Bug#846578: marked as done (freebsd-buildutils: ships libl.a, libfl.a which are also in flex-old)

Your message dated Sun, 08 Jan 2017 23:20:23 + with message-id and subject line Bug#846578: fixed in freebsd-buildutils 10.3~svn296373-6 has caused the Debian Bug report #846578, regarding freebsd-buildutils: ships libl.a, libfl.a which are also in

Bug#846427: marked as done (freebsd-buildutils: add libfl-dev to Build-Depends)

Your message dated Sun, 08 Jan 2017 23:20:23 + with message-id and subject line Bug#846427: fixed in freebsd-buildutils 10.3~svn296373-6 has caused the Debian Bug report #846427, regarding freebsd-buildutils: add libfl-dev to Build-Depends to be marked as

Processed: systemd-shim not fully compatible with systemd 232

Processing control commands: > severity -1 serious Bug #844785 [systemd-shim] systemd-shim not fully compatible with systemd 232 Bug #846230 [systemd-shim] policykit-1-gnome: Fails to start with warning: "Unable to determine the session we are in: No session for pid" Severity set to 'serious'

Bug#848766: reel: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: response = http.request(request)

On Sun, Jan 08, 2017 at 05:50:15PM -0500, micah anderson wrote: > Antonio Terceiro writes: > > >> Relevant part (hopefully): > >> > Failure/Error: response = http.request(request) > >> > > >> > OpenSSL::SSL::SSLError: > >> >SSL_connect returned=1 errno=0

Bug#848766: reel: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: response = http.request(request)

Antonio Terceiro writes: >> Relevant part (hopefully): >> > Failure/Error: response = http.request(request) >> > >> > OpenSSL::SSL::SSLError: >> >SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert >> > unsupported certificate Hmm, I built

Processed: Re: /usr/bin/krb5-config.heimdal: Syntax error: ";;" unexpected

Processing control commands: > severity -1 serious Bug #850653 [heimdal-multidev] /usr/bin/krb5-config.heimdal: Syntax error: ";;" unexpected Severity set to 'serious' from 'important' > affects -1 src:openldap Bug #850653 [heimdal-multidev] /usr/bin/krb5-config.heimdal: Syntax error: ";;"

Bug#838704: NMU: gnustep-dl2-postgresql-adaptor: fails to upgrade on a long grown system

Dear all,  since the hard freeze come closer I've uploaded an NMU with two days delay.  Apart from the already proposed patch I also added overrides for the two lintian warnings because it seems that the files in question are not actually arch dependent. Moving these files into an arch

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

Hi Frederic, On 05-01-17 18:21, PICCA Frederic-Emmanuel wrote: > It is true that for now my package works only if the database name is tango. > > this is a limitation but I do not want to mix this into this bug report. Ack. > so can you help me write the right snipser at the right place in the

Bug#848137: problem with the upgrade of tango-db

Hi Andreas, On 05-01-17 13:49, Andreas Beckmann wrote: > On 2017-01-04 21:55, Paul Gevers wrote: >> Hi Frederic-Emmanuel, Andreas, >> >> @Andreas, am I correct in the assumption that jessie to stretch with >> tango-db was fine until MariaDB became the default? Or was this >> migration with

Bug#849794: marked as done (qtwebengine-opensource-src: FTBFS in every arch (including "all") but amd64)

Your message dated Sun, 08 Jan 2017 21:09:21 + with message-id and subject line Bug#849794: fixed in qtwebengine-opensource-src 5.7.1+dfsg-3 has caused the Debian Bug report #849794, regarding qtwebengine-opensource-src: FTBFS in every arch (including

Bug#832015: marked as done (libblocksruntime: FTBFS with -fdebug-prefix-map)

Your message dated Sun, 08 Jan 2017 21:07:42 + with message-id and subject line Bug#832015: fixed in libblocksruntime 0.4.1-1.1 has caused the Debian Bug report #832015, regarding libblocksruntime: FTBFS with -fdebug-prefix-map to be marked as done. This

Bug#840845: marked as done (python-pygraphviz: FTBFS with /bin/sh as bash)

Your message dated Sun, 08 Jan 2017 21:08:06 + with message-id and subject line Bug#840845: fixed in python-pygraphviz 1.4~rc1-1 has caused the Debian Bug report #840845, regarding python-pygraphviz: FTBFS with /bin/sh as bash to be marked as done. This

Bug#838483: marked as done (gprbuild starts failing with "no native compiler found for language 'ada'")

Your message dated Sun, 08 Jan 2017 21:05:43 + with message-id and subject line Bug#838483: fixed in gprbuild 2015-6 has caused the Debian Bug report #838483, regarding gprbuild starts failing with "no native compiler found for language 'ada'" to be

Bug#849657: marked as done (ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory)

Your message dated Sun, 08 Jan 2017 21:04:00 + with message-id and subject line Bug#849657: fixed in ceph 10.2.5-4 has caused the Debian Bug report #849657, regarding ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory to be

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 850647 serious Bug #850647 [afterstep] afterstep: Afterstep broken, almost unusable. Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 850647:

Processed: Bug#840845 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 840845 pending Bug #840845 {Done: Cyril Brulebois } [src:python-pygraphviz] python-pygraphviz: FTBFS with /bin/sh as bash Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#840845: marked as pending

tag 840845 pending thanks Hello, Bug #840845 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-pygraphviz.git;a=commitdiff;h=182b7ee --- commit

Processed: Bug#840845 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 840845 pending Bug #840845 {Done: Cyril Brulebois } [src:python-pygraphviz] python-pygraphviz: FTBFS with /bin/sh as bash Ignoring request to alter tags of bug #840845 to the same tags previously set > thanks Stopping

Bug#840845: marked as pending

tag 840845 pending thanks Hello, Bug #840845 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-pygraphviz.git;a=commitdiff;h=eee5591 --- commit

Bug#835107: libpthread-workqueue: FTBFS: Testsuite hangs

Control: severity -1 important Control: tags -1 unreproducible moreinfo Hi Daniel, On Mon, 22 Aug 2016 08:18:19 -0700 Daniel Schepler wrote: ... > > From my pbuilder build log (on amd64): > > ... >dh_auto_test > make -j1 check VERBOSE=1 > make[1]: Entering directory

Processed: Re: libpthread-workqueue: FTBFS: Testsuite hangs

Processing control commands: > severity -1 important Bug #835107 [src:libpthread-workqueue] libpthread-workqueue: FTBFS: Testsuite hangs Severity set to 'important' from 'serious' > tags -1 unreproducible moreinfo Bug #835107 [src:libpthread-workqueue] libpthread-workqueue: FTBFS: Testsuite

Processed: Re: Bug#811278: kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling [SA-16:02]

Processing commands for cont...@bugs.debian.org: > # fixed in 10.3 branch since r293897 > fixed 811278 kfreebsd-10/10.3~svn296373-1 Bug #811278 {Done: Steven Chamberlain } [src:kfreebsd-10] kfreebsd-10: CVE-2016-1880: Linux compatibility layer incorrect futex handling

Bug#811954: binutils-msp430: diff for NMU version 2.22~msp20120406-5.1

Control: tags 811954 + patch Control: tags 811954 + pending Dear maintainer, I've prepared an NMU for binutils-msp430 (versioned as 2.22~msp20120406-5.1), upload to DELAYED/5 will follow shortly. Please feel free to tell me if I should delay it longer. Regards, Christoph diff -u

Processed: Re: gprbuild starts failing with "no native compiler found for language 'ada'"

Processing control commands: > severity 838483 serious Bug #838483 [gprbuild] gprbuild starts failing with "no native compiler found for language 'ada'" Severity set to 'serious' from 'normal' -- 838483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838483 Debian Bug Tracking System Contact

Processed: binutils-msp430: diff for NMU version 2.22~msp20120406-5.1

Processing control commands: > tags 811954 + patch Bug #811954 [binutils-msp430] binutils-msp430: FTBFS with GCC 6: left shift of negative value Added tag(s) patch. > tags 811954 + pending Bug #811954 [binutils-msp430] binutils-msp430: FTBFS with GCC 6: left shift of negative value Added tag(s)

Bug#848766: reel: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: response = http.request(request)

On Mon, Dec 19, 2016 at 10:19:26PM +0100, Lucas Nussbaum wrote: > Source: reel > Version: 0.6.1-3 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20161219 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid,

Bug#824907: ruby-reek: Fails to load library from main script

On Thu, Jan 05, 2017 at 02:19:19PM +0800, Andrew Lee wrote: > Package: ruby-reek > Followup-For: Bug #824907 > > Thanks for reporting such issue. After replace require_relative with > relative paths with "require 'reek'" and such in bin/reek. I still > got: >

Processed: closing 830099

Processing commands for cont...@bugs.debian.org: > close 830099 Bug #830099 {Done: Sebastien Badia } [ruby-em-http-request] Could not find 'em-socksify' (>= 0.3) Bug 830099 is already marked as done; not doing anything. > thanks Stopping processing here. Please contact me if

Bug#830099: closing 830099

close 830099 thanks this has been fixed with the upload of ruby-em-socksify (0.3.1-1), but for some reason the automatic closing did not happen.

Bug#850352: pristine-tar: perl errors, badly broken

Control: tag -1 + unreproducible Control: severity -1 normal On Fri, Jan 06, 2017 at 10:26:21PM +0100, Tomasz Buchert wrote: > > gbp:info: Tarballs 'texlive-bin_2016.20160513.41080.orig.tar.xz' not found > > at '../tarballs' > > I cannot reproduce your problem. No point in letting this bug

Processed: Re: Bug#850352: pristine-tar: perl errors, badly broken

Processing control commands: > tag -1 + unreproducible Bug #850352 [pristine-tar] pristine-tar: perl errors, badly broken Added tag(s) unreproducible. > severity -1 normal Bug #850352 [pristine-tar] pristine-tar: perl errors, badly broken Severity set to 'normal' from 'grave' -- 850352:

Bug#847286: closed by Pirate Praveen <prav...@debian.org> (Bug#847286: fixed in diaspora-installer 0.6.0.0+debian5)

On Fri, Dec 30, 2016 at 03:36:05PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the diaspora-installer package: > > #847286: diaspora-installer: installs world-writable files under >

Bug#840823: execnet test failures

(I had never heard of this package before your d-d post: I'm looking at it because of the number of to-be-autoremoved reverse dependencies) I can't reproduce any of these test failures: dpkg-buildpackage -us -uc -A in a sid/amd64 cowbuilder --login chroot (build-deps + ccache eatmydata

Processed (with 1 error): forcibly merging 850430 850426

Processing commands for cont...@bugs.debian.org: > forcemerge 850430 850426 Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface Unable to merge bugs because: package of #850426 is 'postfix-lmdb' not 'postfix' Failed to forcibly merge 850430: Did not alter merged bugs. > thanks

Processed (with 1 error): forcibly merging 850400 849682

Processing commands for cont...@bugs.debian.org: > forcemerge 850400 849682 Bug #850400 {Done: LaMont Jones } [postfix-mysql] postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail Unable to merge bugs because: package of #849682 is

Bug#850632: openuniverse: fails to start "input in flex scanner failed

Package: openuniverse Version: 1.0beta3.1+dfsg-5 Severity: serious Justification: unkown When I try to start openuniverse, I see the message input in flex scanner failed after which nothing happens. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990,

Bug#817726: marked as done (wmxres: Removal of debhelper compat 4)

Your message dated Sun, 08 Jan 2017 17:20:16 + with message-id and subject line Bug#817726: fixed in wmxres 1.2-10.1 has caused the Debian Bug report #817726, regarding wmxres: Removal of debhelper compat 4 to be marked as done. This means that you claim

Bug#829173: marked as done (swiginac: FTBFS: /usr/include/ginac/ptr.h:37:13: error: expected '; ' at end of member declaration)

Your message dated Sun, 08 Jan 2017 17:19:08 + with message-id and subject line Bug#850550: Removed package(s) from unstable has caused the Debian Bug report #829173, regarding swiginac: FTBFS: /usr/include/ginac/ptr.h:37:13: error: expected '; ' at end

Bug#818673: marked as done (Useless in Debian)

Your message dated Sun, 08 Jan 2017 17:20:00 + with message-id and subject line Bug#850582: Removed package(s) from unstable has caused the Debian Bug report #818673, regarding Useless in Debian to be marked as done. This means that you claim that the

Bug#789407: unable to send openpgp messages

On Sat, 20 Jun 2015 21:10:56 +0530 Pirate Praveen wrote: > package: pidgin-openpgp > version: 0.1-2 > severity: grave > > I can only receive openpgp messages, sending does not work. > Hi. I've just tried to reproduce the behavior with two seperate XMPP accounts on two

Bug#843232: marked as done (heat: CVE-2016-9185: template source URL allows network port scan)

Your message dated Sun, 08 Jan 2017 17:03:42 + with message-id and subject line Bug#843232: fixed in heat 1:7.0.0-2 has caused the Debian Bug report #843232, regarding heat: CVE-2016-9185: template source URL allows network port scan to be marked as done.

Bug#850231: marked as done (heat: FTBFS (TypeError: unsupported operand type(s) for +=: 'int' and 'str'))

Your message dated Sun, 08 Jan 2017 17:03:42 + with message-id and subject line Bug#850231: fixed in heat 1:7.0.0-2 has caused the Debian Bug report #850231, regarding heat: FTBFS (TypeError: unsupported operand type(s) for +=: 'int' and 'str') to be

Processed: retitle 839293 to google-cloud-print-connector: FTBFS - go install returned exit code 2

Processing commands for cont...@bugs.debian.org: > retitle 839293 google-cloud-print-connector: FTBFS - go install returned exit > code 2 Bug #839293 [src:google-cloud-print-connector] google-cloud-print-connector: FTBFS: dh_auto_build: go install -v -p 1 github.com/google/cups-connector/cdd

Bug#811582: marked as done (FTBFS with GCC 6: statement indented as if it were guarded by)

Your message dated Sun, 08 Jan 2017 16:18:46 + with message-id and subject line Bug#811582: fixed in ion 3.2.1+dfsg-1.1 has caused the Debian Bug report #811582, regarding FTBFS with GCC 6: statement indented as if it were guarded by to be marked as done.

Bug#811593: FTBFS with GCC 6: statement indented as if it were guarded by

Hi Mike! > The attached patch should fix the issue, although it's not completely > clear to me if these were hidden (until now) mistakes or not. It actually looks like those were mistakes and the proper fix would have been to use braces around the next two statements, so that argv.erase() is

Bug#811576: FTBFS with GCC 6: statement indented as if it were guarded by

I tried the attached patch, the build still fails, this time with a different issue though: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -D_LINUX -DLOCALEDIR=\"/usr/share/locale\" -DTSS_LIB_IS_12 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.

Bug#805988: aboot: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

On Sun, Jan 08, 2017 at 04:38:36PM +0100, John Paul Adrian Glaubitz wrote: > Control: user debian-al...@lists.debian.org > Control: usertags alpha > > > Apparently (see Bug #821332), I would need somebody having an alpha to > > check that "dpkg-buildpackage -A" works. > > I can actually do that,

Bug#805988: aboot: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Control: user debian-al...@lists.debian.org Control: usertags alpha > Apparently (see Bug #821332), I would need somebody having an alpha to > check that "dpkg-buildpackage -A" works. I can actually do that, I have access to an alpha porterbox. However, you can also actually do it yourself by

Bug#848761: marked as done (ovito: FTBFS: Test failures)

Your message dated Sun, 08 Jan 2017 15:18:57 + with message-id and subject line Bug#848761: fixed in ovito 2.8.1+dfsg1-1 has caused the Debian Bug report #848761, regarding ovito: FTBFS: Test failures to be marked as done. This means that you claim that

Bug#849597: marked as done (libguestfs0: Missing multiple dependencies)

Your message dated Sun, 08 Jan 2017 15:07:20 + with message-id and subject line Bug#849597: fixed in libguestfs 1:1.34.3-6 has caused the Debian Bug report #849597, regarding libguestfs0: Missing multiple dependencies to be marked as done. This means that

Processed: already fixed

Processing commands for cont...@bugs.debian.org: > close 817677 Bug #817677 [src:sredird] sredird: Removal of debhelper compat 4 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 817677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817677

Bug#817677: already fixed

close 817677 thanks I fixed this in version 2.2.1-2 but forgot to put a closes: entry in the changelog. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#820921: marked as done (pam-ssh-agent-auth: Ignores return value of seteuid() in two cases)

Your message dated Sun, 08 Jan 2017 13:50:05 + with message-id and subject line Bug#820921: fixed in pam-ssh-agent-auth 0.10.2-2 has caused the Debian Bug report #820921, regarding pam-ssh-agent-auth: Ignores return value of seteuid() in two cases to be

Bug#828488: marked as done (pam-ssh-agent-auth: FTBFS with openssl 1.1.0)

Your message dated Sun, 08 Jan 2017 13:50:05 + with message-id and subject line Bug#828488: fixed in pam-ssh-agent-auth 0.10.2-2 has caused the Debian Bug report #828488, regarding pam-ssh-agent-auth: FTBFS with openssl 1.1.0 to be marked as done. This

Bug#849546: rar a also segmentation fault in Debian Testing

Same happens to me with "rar a": rar 5.30 b2 debian testing kernel 4.8.0 64 bits every time I try to create a rar with "rar a" I receive a segmentation fault, so it is not posible create rar files even with gnome file-roller

Bug#850320: mock: CVE-2016-6299: privilige escalation via mock-scm

Hi Tzafrir, On Sat, Jan 07, 2017 at 10:28:01PM +0100, Tzafrir Cohen wrote: > I prepared a version in the branch jessie-backports in git[1]. > > It seems to work OK here. I don't hae my key in the backports keyring, > so I prefer that you upload it. done, thanks! Also created a git tag and

Processed: retitle 850599 to petsc: Missing depends on libhdf5-mpi-dev in -dev pkg

Processing commands for cont...@bugs.debian.org: > retitle 850599 petsc: Missing depends on libhdf5-mpi-dev in -dev pkg Bug #850599 {Done: Drew Parsons } [petsc] slepc: FTBFS: Unable to link with PETSc Changed Bug title to 'petsc: Missing depends on libhdf5-mpi-dev in -dev

Bug#849657: [Ceph-maintainers] Bug#849657: ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory

Aurelien Jarno writes: > On 2017-01-05 14:00, Gaudenz Steinlin wrote: >> >> Hi >> >> Aurelien Jarno writes: >> >> > On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote: >> >> On 29/12/16 20:56, Gaudenz Steinlin wrote: >> > >> > The problem is indeed

Bug#828616: marked as done (yubico-piv-tool: FTBFS with openssl 1.1.0)

Your message dated Sun, 08 Jan 2017 12:03:53 + with message-id and subject line Bug#828616: fixed in yubico-piv-tool 1.4.2-2 has caused the Debian Bug report #828616, regarding yubico-piv-tool: FTBFS with openssl 1.1.0 to be marked as done. This means

Processed: cloning 802706, notfound 802706 in 3.7.3+dfsg1-3, reassign -1 to petsc, closing -1 ...

Processing commands for cont...@bugs.debian.org: > # splitting into two bugs so the BTS can track what is happening > clone 802706 -1 Bug #802706 {Done: Drew Parsons } [src:slepc] slepc: FTBFS: Unable to link with PETSc Bug 802706 cloned as bug 850599 > notfound 802706

Bug#849657: [Ceph-maintainers] Bug#849657: ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory

Emilio Pozuelo Monfort writes: > On 05/01/17 14:00, Gaudenz Steinlin wrote: >> >> Hi >> >> Aurelien Jarno writes: >> >>> On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote: On 29/12/16 20:56, Gaudenz Steinlin wrote: >>> >>> The problem is indeed a

Bug#850456: marked as done (elpa: FTBFS (not enough slots available))

Your message dated Sun, 08 Jan 2017 11:48:22 + with message-id and subject line Bug#850456: fixed in elpa 2016.05.001-3 has caused the Debian Bug report #850456, regarding elpa: FTBFS (not enough slots available) to be marked as done. This means that you

Bug#850552: marked as done (txfixtures: FTBFS: MismatchError: > returned None)

Your message dated Sun, 08 Jan 2017 11:18:36 + with message-id and subject line Bug#850552: fixed in txfixtures 0.2.5-1 has caused the Debian Bug report #850552, regarding txfixtures: FTBFS: MismatchError: > returned None to be marked as done. This means

Bug#850552: marked as pending

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

Processed: Bug#850552 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 850552 pending Bug #850552 [src:txfixtures] txfixtures: FTBFS: MismatchError: > returned None Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 850552:

Processed: already fixed

Processing commands for cont...@bugs.debian.org: > close 800258 Bug #800258 [src:logtools] logtools: Please migrate a supported debhelper compat level Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 800258:

Bug#800258: already fixed

close 800258 thanks This was fixed in 0.13e but I forgot to list it in the changelog. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Processed: Re: cloning 843861, retitle -1 to potrace: CVE-2016-8686: memory allocation failure ..., reopening -1

Processing control commands: > severity -1 normal Bug #850595 [potrace] potrace: CVE-2016-8686: memory allocation failure Severity set to 'normal' from 'serious' -- 850595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850595 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#850595: cloning 843861, retitle -1 to potrace: CVE-2016-8686: memory allocation failure ..., reopening -1

Control: severity -1 normal Note that this is neither considered an issue upstream. So let's lower severity for this issue. The CVE was sssigned most likely due to the DoS risk, for applications using potrace. AFAICT.

Bug#843861: CVE-2016-8685 and CVE-2016-8686

Hi Salvatore, Sure feel free to do that but I doubt it's going to be fixed. Upstream doesn't think it's a bug... and actually I agree with him on this. potrace will try to handle whatever size of input file is... if it's bigger than available memory then it will fail. But what exactly it

Processed: cloning 843861, retitle -1 to potrace: CVE-2016-8686: memory allocation failure ..., reopening -1

Processing commands for cont...@bugs.debian.org: > clone 843861 -1 Bug #843861 {Done: Bartosz Fenski } [potrace] potrace: CVE-2016-8685 CVE-2016-8686 Bug 843861 cloned as bug 850595 > retitle -1 potrace: CVE-2016-8686: memory allocation failure Bug #850595 {Done: Bartosz Fenski

Bug#843861: CVE-2016-8685 and CVE-2016-8686

Hi Bartosz, On Sun, Jan 08, 2017 at 09:51:04AM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the potrace package: > > #843861: potrace: CVE-2016-8685 CVE-2016-8686 > > It has been closed by Bartosz Fenski

Bug#843861: marked as done (potrace: CVE-2016-8685 CVE-2016-8686)

Your message dated Sun, 08 Jan 2017 09:48:26 + with message-id and subject line Bug#843861: fixed in potrace 1.13-3 has caused the Debian Bug report #843861, regarding potrace: CVE-2016-8685 CVE-2016-8686 to be marked as done. This means that you claim

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

at bottom :- On 08/01/2017, intrigeri wrote: > shirish शिरीष: >> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197 > >> gpg: keyserver receive failed: No keyserver available > >> Tried it multiple times but get the above failure. > > [...] > >> Any ideas what I need to

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

shirish शिरीष: > ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197 > gpg: keyserver receive failed: No keyserver available > Tried it multiple times but get the above failure. [...] > Any ideas what I need to do next ? Add a "debug-all" line in ~/.gnupg/dirmngr.conf, restart

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

at bottom :- On 08/01/2017, intrigeri wrote: > shirish शिरीष: >> in-line :- > >> On 07/01/2017, Daniel Kahn Gillmor wrote: >>> Have you restarted dirmngr since the upgrade? > >> how do I restart it ? > > systemctl --user restart dirmngr.socket > >