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

Hi, looking at http://matrix.cpantesters.org/?dist=Lemonldap-NG-Handler+1.9.7 the bug seems to be specific to Debian. I've disabled the heavy handler tests for now in 1.9.7-2. Note that autopkgtest fails since FastCGI server depends on Nginx which can not be installed in autopkgtest environment.

Bug#814030: Security flaw fixed in version 6.2.0

Hi David, On Sun, Mar 27, 2016 at 01:33:01PM +0200, Moritz Mühlenhoff wrote: > On Sun, Feb 07, 2016 at 02:28:04PM -0400, David Prévot wrote: > > Package: php-tcpdf > > Version: 6.0.093+dfsg-1 > > Severity: serious > > Tags: security upstream > > > > According to their changelog [1], upstream fixe

Bug#734688: Call for testers: logrotate 3.11.0-0.1~exp1

Matthias Klose wrote... > fyi, I NMUed logrotate yesterday to fix #849743, currently in delayed. Please > add this fix to your upload. Thanks for the heads-up, included in ~exp2 I had to do for other reasons as well. Christoph signature.asc Description: Digital signature

Bug#850196: marked as done (unblock: dgit/2.14)

Your message dated Thu, 05 Jan 2017 07:15:00 + with message-id <88bed8ec-ea5e-68e9-4c1e-e65c36328...@thykier.net> and subject line Re: Bug#850196: unblock: dgit/2.14 has caused the Debian Bug report #850196, regarding unblock: dgit/2.14 to be marked as done. This means that you claim that the

Bug#850160: Incomplete fix (was: Re: Bug#850160 closed by Reiner Herrmann (Bug#850160: fixed in firejail 0.9.44.2-2))

Hi Reiner, On Wed, Jan 04, 2017 at 11:21:05PM +, Debian Bug Tracking System wrote: >* Add upstream fix for CVE-2017-5180 (Closes: #850160). Thanks. The fix had a followup which does not seem to be applied, cf. https://github.com/netblue30/firejail/issues/1020#issuecomment-270514760 Regar

Bug#850007: closing 850007, closing 850008

close 850007 0.9.11+dfsg-1 close 850008 0.9.11+dfsg-1 thanks

Processed: closing 850007, closing 850008

Processing commands for cont...@bugs.debian.org: > close 850007 0.9.11+dfsg-1 Bug #850007 [src:libvncserver] libvncserver: CVE-2016-9941 Marked as fixed in versions libvncserver/0.9.11+dfsg-1. Bug #850007 [src:libvncserver] libvncserver: CVE-2016-9941 Marked Bug as done > close 850008 0.9.11+dfsg-

Bug#833335: marked as done (namazu2-index-tools and namazu2: error when trying to install together)

Your message dated Thu, 5 Jan 2017 15:30:57 +0900 with message-id and subject line Re: namazu2-index-tools and namazu2: error when trying to install together has caused the Debian Bug report #85, regarding namazu2-index-tools and namazu2: error when trying to install together to be marked as

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

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: /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- privat

Bug#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

Source: mysql-5.6 Version: 5.6.30-1 Severity: grave Tags: security Justification: user security hole Hi When installing myssql-server-5.6 in stretch and sid, then mysqld is started and listend not binding on localhost only, but listen on *. tcpLISTEN 0 80 :::mysql

Bug#850215: zendframework: CVE-2016-10034

Source: zendframework Version: 1.12.9+dfsg-1 Severity: grave Tags: upstream security Justification: user security hole Hi, the following vulnerability was published for zendframework. CVE-2016-10034[0]: | The setFrom function in the Sendmail adapter in the zend-mail | component before 2.4.11, 2.

Processed: retitle 850160 to firejail: CVE-2017-5180: local root exploit

Processing commands for cont...@bugs.debian.org: > retitle 850160 firejail: CVE-2017-5180: local root exploit Bug #850160 {Done: Reiner Herrmann } [firejail] firejail: Firejail local root exploit Changed Bug title to 'firejail: CVE-2017-5180: local root exploit' from 'firejail: Firejail local ro

Bug#818926: perl6-panda: panda doesn't start up / find needed libraries

On Wed, 04 Jan 2017 08:22:46 +0100, Dominique Dumont wrote: > > I'm just reading > > http://blogs.perl.org/users/steve_mynott/2017/01/rakudo-star-past-present-and-future.html > > which mentions that Rakudo Star is moving from panda to zef. > Thanks for the link. I'm currently trying to figure out

Processed: unblock 738897 with 672390, block 738897 with 850210

Processing commands for cont...@bugs.debian.org: > unblock 738897 with 672390 Bug #738897 [ftp.debian.org] RM: libsigc++-1.2 -- RoQA; orphaned, obsolete version Bug #850185 [ftp.debian.org] RM: libsigc++-1.2 -- RoQA, RC buggy, unmaintained 738897 was blocked by: 672390 738897 was not blocking any

Bug#833037: marked as done (python-factory-boy: missing depends on ipaddress)

Your message dated Thu, 05 Jan 2017 01:48:30 + with message-id and subject line Bug#833037: fixed in factory-boy 2.8.1-1 has caused the Debian Bug report #833037, regarding python-factory-boy: missing depends on ipaddress to be marked as done. This means that you claim that the problem has be

Bug#833037: [PKG-Openstack-devel] Bug#833037: Bug#833037: python-factory-boy: missing depends on ipaddress

Brian May writes: > Not sure if I can git push to the openstack git repository, so I haven't > done so (and I might have to redo it anyway). If I can get this working, > I might move it to DPMT. Ok, just building and uploading. Note that this isn't going to really help, there are 2 RC bugs agai

Processed: Bug#833037 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 833037 pending Bug #833037 [python-factory-boy] python-factory-boy: missing depends on ipaddress Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 833037: http://bugs.debian.org/cgi-bin/bu

Bug#849649: marked as done (commons-daemon: FTBFS on arm: fatal error: jni_md.h: No such file or directory)

Your message dated Thu, 05 Jan 2017 00:18:43 + with message-id and subject line Bug#849649: fixed in commons-daemon 1.0.15-7 has caused the Debian Bug report #849649, regarding commons-daemon: FTBFS on arm: fatal error: jni_md.h: No such file or directory to be marked as done. This means tha

Bug#833037: [PKG-Openstack-devel] Bug#833037: Bug#833037: python-factory-boy: missing depends on ipaddress

Ondrej Novy writes: > Maybe orphan it first? Is this package used in Debian? I tried to fix this issue, but the package has a FTBFS error: ImportError: The ``fake-factory`` package is now called ``Faker``. So I updated it to the latest version of python-factory-boy from Pypi (referenced from

Processed: Pending fixes for bugs in the commons-daemon package

Processing commands for cont...@bugs.debian.org: > tag 849649 + pending Bug #849649 [src:commons-daemon] commons-daemon: FTBFS on arm: fatal error: jni_md.h: No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 849649: h

Bug#849649: Pending fixes for bugs in the commons-daemon package

tag 849649 + pending thanks Some bugs in the commons-daemon package are closed in revision ccb7f63f4fb6388f671e8d4a354095319b698247 in branch 'master' by Markus Koschany The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/commons-daemon.git/commit/?id=ccb7f63 Commit message:

Bug#849041: marked as done (dgit: psuedomerge commits have no author.)

Your message dated Wed, 04 Jan 2017 23:18:27 + with message-id and subject line Bug#849041: fixed in dgit 2.14 has caused the Debian Bug report #849041, regarding dgit: psuedomerge commits have no author. to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#850160: marked as done (firejail: Firejail local root exploit)

Your message dated Wed, 04 Jan 2017 23:18:32 + with message-id and subject line Bug#850160: fixed in firejail 0.9.44.2-2 has caused the Debian Bug report #850160, regarding firejail: Firejail local root exploit to be marked as done. This means that you claim that the problem has been dealt wi

Bug#850196: unblock: dgit/2.14

Package: release.debian.org Severity: grave User: release.debian@packages.debian.org Usertags: unblock Please unblock package dgit dgit 2.13 has a HIDEOUS bug which causes it to generate malformed git commits. (#849041) To my surprise, extreme disappointment, and soon everyone's annoyance, n

Bug#849041: dgit: psuedomerge commits have no author.

peter green writes ("Bug#849041: dgit: psuedomerge commits have no author."): > I have a script that can be used to fix the commits but of course the only > way to fix them is to change history and that has obvious downsides. Thanks. I'm going to write a better script. I think the history-rewri

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > forcemerge 738897 850185 Bug #738897 [ftp.debian.org] RM: libsigc++-1.2 -- RoQA; orphaned, obsolete version Bug #850185 [ftp.debian.org] RM: libsigc++-1.2 -- RoQA, RC buggy, unmaintained 850185 was not blocked by any bugs. 850185 was not blocking

Bug#849845: got hit as well

Hi all, Got hit on one of my machines which upgraded before the serious bug was invoked - └─[$] apt-cache policy gnupg dirmngr gnupg: Installed: 2.1.17-2 Candidate: 2.1.17-2 Version table: *** 2.1.17-2 600 600 http://httpredir.debian.org/debian stretch/main amd64 Packages

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 849119 important Bug #849119 [playonlinux] playonlinux: Buttons fail to appear in most or all pop up dialog boxes Severity set to 'important' from 'grave' > forwarded 849119 https://www.playonlinux.com/fr/issue-5438.html Bug #849119 [pla

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 844146 + help Bug #844146 [src:libmicrohttpd] libmicrohttpd: FTBFS: Test failures Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 844146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84

Bug#849041: dgit: psuedomerge commits have no author.

On 04/01/17 22:03, Ian Jackson wrote: Control: severity -1 critical peter green writes ("Bug#849041: dgit: psuedomerge commits have no author."): Unfortunately I ran into a problem. It seems that the psuedomerge commits generated by dgit have no author: field and this makes it impossible to pus

Bug#849119: playonlinux: Buttons fail to appear in most or all pop up dialog boxes

Dear Ray, Thank you for taking the time to investigate. I forwarded the issue upstream, and hopefully they will come up with a solution soon enough. In the meantime, I will downgrade the severity of this bug, as playonlinux is still usable by most people. Best regards, Bertrand PS Could you p

Bug#833037: [PKG-Openstack-devel] Bug#833037: Bug#833037: python-factory-boy: missing depends on ipaddress

Hi, 2017-01-04 16:31 GMT+01:00 Thomas Goirand : > Please file a bug against ftp.debian.org to get the package removed. > Maybe orphan it first? -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B

Processed: Re: affects 834522

Processing commands for cont...@bugs.debian.org: > unarchive 834281 Bug #834281 {Done: intrigeri } [libgnupg-interface-perl] libgnupg-interface-perl: FTBFS, test failures, probably gpg2 Unarchived Bug 834281 > affects 834281 src:gnupg2 Bug #834281 {Done: intrigeri } [libgnupg-interface-perl] lib

Processed (with 2 errors): Re: affects 834522

Processing commands for cont...@bugs.debian.org: > affects 834522 = src:gnupg2 Bug #834522 {Done: Florian Schlichting } [libgnupg-perl] libgnupg-perl: FTBFS, test failures, probably gpg2 Removed indication that 834522 affects 835075, 834281, and + Added indication that 834522 affects src:gnupg2 >

Processed: Proper version tracking

Processing commands for cont...@bugs.debian.org: > notfound 828524 0.5.12-1.1 Bug #828524 {Done: Boyuan Yang <073p...@gmail.com>} [src:qterm] qterm: FTBFS with openssl 1.1.0 The source 'qterm' and version '0.5.12-1.1' do not appear to match any binary packages No longer marked as found in versio

Bug#849602: not a bug

On Wed, Jan 04, 2017 at 10:24:06PM +0530, shirish शिरीष wrote: > at bottom :- > > On 04/01/2017, Patrick Mutwiri wrote: > > thats how fonts are installed. > > > > > > this is not a bug. > > > > > > > > > > *Kind Regards,* > > > > > > Patrick Mutwiri / _dev > > > > +254 727 542 899 > > > > Nairobi

Processed: Re: Bug#849041: dgit: psuedomerge commits have no author.

Processing control commands: > severity -1 critical Bug #849041 [dgit] dgit: psuedomerge commits have no author. Severity set to 'critical' from 'serious' -- 849041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#849041: dgit: psuedomerge commits have no author.

Control: severity -1 critical peter green writes ("Bug#849041: dgit: psuedomerge commits have no author."): > Unfortunately I ran into a problem. It seems that the psuedomerge > commits generated by dgit have no author: field and this makes it > impossible to push them to github. I have discove

Processed: Re: node-sprintf-js: FTBFS randomly (AssertionError)

Processing commands for cont...@bugs.debian.org: > severity 849971 important Bug #849971 [src:node-sprintf-js] node-sprintf-js: FTBFS randomly (AssertionError) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 849971: http

Bug#849971: node-sprintf-js: FTBFS randomly (AssertionError)

severity 849971 important thanks Hello. I'm setting the severity of this bug to "important" not because I don't think it is not RC (as Release Policy still says that packages must autobuild *without* failure), but because the Release Managers are considering to decide about RC-ness of this kind o

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

Control: clone -1 -2 Control: reassign -2 dbconfig-common Control: retitle -2 dbc: db-dump must use root credentials when needed Hi all, I think I found the issue. Since commit 95571e6¹ the postinst script of dbconfig properly executes install code with user privileges as it has always said it wo

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

Processing control commands: > clone -1 -2 Bug #848137 [tango-db] tango-db: fails to upgrade from 'jessie': mysqldump: tango has insufficent privileges to SHOW CREATE PROCEDURE `class_att_prop`! Bug 848137 cloned as bug 850190 > reassign -2 dbconfig-common Bug #850190 [tango-db] tango-db: fails t

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 818265 important Bug #818265 [src:pyzmq] pyzmq: FTBFS with newest zeromq3 Bug #818278 [src:pyzmq] pyzmq: binNMUs using zeromq3 4.1.x are timing out in the tests Bug #846673 [src:pyzmq] pyzmq: FTBFS: timer_createQCzujp.c:(.text+0x15): un

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

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 tango-db just never tested before? Have you seen other dbconfig-common dependent packages fail since MariaDB became def

Bug#828457: nodejs: FTBFS with openssl 1.1.0

Package: nodejs Version: 4.6.1~dfsg-1 Followup-For: Bug #828457 Control: reopen -1 This bug has been fixed in nodejs 6.9.2~dfsg-1, which is in experimental, node in testing. Reopening, then. Jérémy

Processed: Re: nodejs: FTBFS with openssl 1.1.0

Processing control commands: > reopen -1 Bug #828457 {Done: Jérémy Lal } [src:nodejs] nodejs: FTBFS with openssl 1.1.0 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fix

Bug#817551: libsigc++-1.2: Removal of debhelper compat 4

Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: severity -2 normal Control: retitle -2 RM: libsigc++-1.2 -- RoQA, RC buggy, unmaintained On Wed, 09 Mar 2016 21:30:45 +0100 ni...@thykier.net wrote: > Source: libsigc++-1.2 > Severity: important > Usertags: compat-4-removal > > Hi,

Processed: Re: libsigc++-1.2: Removal of debhelper compat 4

Processing control commands: > clone -1 -2 Bug #817551 [src:libsigc++-1.2] libsigc++-1.2: Removal of debhelper compat 4 Bug 817551 cloned as bug 850185 > reassign -2 ftp.debian.org Bug #850185 [src:libsigc++-1.2] libsigc++-1.2: Removal of debhelper compat 4 Bug reassigned from package 'src:libsigc

Processed (with 5 errors): Re: Bug#850077: duplicity: Backup fail since upgrade of python-crypto from 2.6-4+deb7u3 to 2.6-4+deb7u4

Processing commands for cont...@bugs.debian.org: > reassign 850077 python-paramiko Bug #850077 [duplicity] duplicity: Backup fail since upgrade of python-crypto from 2.6-4+deb7u3 to 2.6-4+deb7u4 Bug reassigned from package 'duplicity' to 'python-paramiko'. No longer marked as found in versions du

Bug#850077: duplicity: Backup fail since upgrade of python-crypto from 2.6-4+deb7u3 to 2.6-4+deb7u4

reassign 850077 python-paramiko retitle 850077 python-paramiko doesn't work with python-crypto 2.6-4 thanks, On Tue, 03 Jan 2017 21:49:21 +0100, Patrick Valsecchi writes: >Since yesterday's update, backup to a SSH target is broken and leads to this st >acktrace: > >ssh: Unknown exception: CTR mode

Processed: Re: Request for help - scilab segfaults with TSX

Processing control commands: > severity 844134 normal Bug #844134 [scilab] scilab segfaults with TSX Bug #844135 [scilab] scilab segfaults with TSX Bug #844138 [scilab] scilab segfaults with TSX Severity set to 'normal' from 'serious' Severity set to 'normal' from 'serious' Severity set to 'normal

Bug#844134: Request for help - scilab segfaults with TSX

Control: severity 844134 normal Samuel Thibault writes ("Re: Request for help - scilab segfaults with TSX"): > Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote: > > On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote: > > > This looks like a threading bug in Scilab exposed by TSX. > >

Bug#849651: efibootmgr: FTBFS on armhf: collect2: error: ld returned 1 exit status; 2-byte wchar_t

On Thu, Dec 29, 2016 at 03:22:02PM +, Chris West (Faux) wrote: >Source: efibootmgr >Version: 14-1 >Severity: serious >Justification: fails to build from source >Tags: sid stretch >User: reproducible-bui...@lists.alioth.debian.org >Usertags: ftbfs >X-Debbugs-CC: reproducible-bui...@lists.alioth.

Bug#844134: Request for help - scilab segfaults with TSX

Gilles Filippini writes ("Request for help - scilab segfaults with TSX"): > Control: tag -1 + help ... > I've just noticed this RC bug [1] against scilab. After reading through > the recent thread on this subject [2] I must admit I have no clue what > to do. > > [1] https://bugs.debian.org/cgi-bin

Bug#844134: Request for help - scilab segfaults with TSX

Hello, Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote: > On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote: > > This looks like a threading bug in Scilab exposed by TSX. > > I've just noticed this RC bug [1] against scilab. FYI, glibc is about to just disable TSX entirely in vers

Processed: Proper version tracking

Processing commands for cont...@bugs.debian.org: > fixed 828524 1:0.7.1-1 Bug #828524 {Done: Boyuan Yang <073p...@gmail.com>} [src:qterm] qterm: FTBFS with openssl 1.1.0 Ignoring request to alter fixed versions of bug #828524 to the same values previously set > thanks Stopping processing here.

Bug#850035: marked as done (libqbscore1.7: ships libqbscore.so.1)

Your message dated Wed, 04 Jan 2017 18:48:32 + with message-id and subject line Bug#850035: fixed in qbs 1.7.0+dfsg-2 has caused the Debian Bug report #850035, regarding libqbscore1.7: ships libqbscore.so.1 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Request for help - scilab segfaults with TSX

Processing control commands: > tag -1 + help Bug #844134 [scilab] scilab segfaults with TSX Bug #844135 [scilab] scilab segfaults with TSX Bug #844138 [scilab] scilab segfaults with TSX Added tag(s) help. Added tag(s) help. Added tag(s) help. -- 844134: http://bugs.debian.org/cgi-bin/bugreport.c

Bug#844134: Request for help - scilab segfaults with TSX

Control: tag -1 + help Hi, On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote: > This looks like a threading bug in Scilab exposed by TSX. I've just noticed this RC bug [1] against scilab. After reading through the recent thread on this subject [2] I must admit I have no clue what to do. [1]

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

On Wed 2017-01-04 09:27:16 -0500, intrigeri wrote: > Daniel Kahn Gillmor: >> I've been able to replicate the problems described by intrigeri in >> https://bugs.debian.org/849845; i'm preparing an update to gpg with >> cherry-picked patches that resolves most of them for me. > > I'd be happy to test

Bug#844568: jack: diff for NMU version 3.1.1+cvs20050801-29.2

On Wed, 4 Jan 2017 14:55:26 +0100 Mattia Rizzolo wrote: [...] > I've prepared an NMU for jack (versioned as 3.1.1+cvs20050801-29.2) [...] Thanks a lot Mattia, that's really appreciated! Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ...

Bug#848137: [Dbconfig-common-devel] Bug#848137: RE:Bug#848137: Info received (problem with the upgrade of tango-db)

Hello, > I am suspecting that this commit may be related to the current behavior: > https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git/commit/?id=acdb99d61abfff54630c4cfba6e4452357a83fb9 > I believe I implemented there that the drop of the database is performed > with the user privi

Bug#835542: marked as done (flex: comparison between signed and unsigned integer expressions)

Your message dated Wed, 04 Jan 2017 17:33:47 + with message-id and subject line Bug#835542: fixed in flex 2.6.1-1.2 has caused the Debian Bug report #835542, regarding flex: comparison between signed and unsigned integer expressions to be marked as done. This means that you claim that the pro

Bug#846459: marked as done (pam: add libfl-dev to Build-Depends)

Your message dated Wed, 04 Jan 2017 17:34:08 + with message-id and subject line Bug#846459: fixed in pam 1.1.8-3.5 has caused the Debian Bug report #846459, regarding pam: add libfl-dev to Build-Depends to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: Re: python-crypto: regression: 2.6-4+deb7u4 breaks python-paramiko

Processing commands for cont...@bugs.debian.org: > tags 850025 + pending Bug #850025 [python-crypto] python-crypto: regression: 2.6-4+deb7u4 breaks python-paramiko Added tag(s) pending. > tags 850077 + pending Bug #850077 [duplicity] duplicity: Backup fail since upgrade of python-crypto from 2.6

Bug#850077: python-crypto: regression: 2.6-4+deb7u4 breaks python-paramiko

tags 850025 + pending tags 850077 + pending thanks Just uploaded. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#849626: marked as done (libphp-swiftmailer: CVE-2016-10074)

Your message dated Wed, 04 Jan 2017 17:04:02 + with message-id and subject line Bug#849626: fixed in libphp-swiftmailer 5.4.2-1.1 has caused the Debian Bug report #849626, regarding libphp-swiftmailer: CVE-2016-10074 to be marked as done. This means that you claim that the problem has been de

Bug#849602: not a bug

at bottom :- On 04/01/2017, Patrick Mutwiri wrote: > thats how fonts are installed. > > > this is not a bug. > > > > > *Kind Regards,* > > > Patrick Mutwiri / _dev > > +254 727 542 899 > > Nairobi, Kenya > > http://patric.xyz > > [image: Twitter] [image: Faceb

Bug#849626: Patch for 5.4.2-1.1 NMU

Hi, I've taken the liberty to fix this security issue in an NMU to sid. Attached is the debdiff. Cheers, Thijs diff -Nru libphp-swiftmailer-5.4.2/debian/changelog libphp-swiftmailer-5.4.2/debian/changelog --- libphp-swiftmailer-5.4.2/debian/changelog 2016-06-10 14:26:56.0 + +++ libph

Bug#828524: marked as done (qterm: FTBFS with openssl 1.1.0)

Your message dated Wed, 04 Jan 2017 16:34:05 + with message-id and subject line Bug#828524: fixed in qterm 1:0.7.1-1 has caused the Debian Bug report #828524, regarding qterm: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Processed: Re: Bug#850013: vim-youcompleteme: Please provide a newer version, the current one doesn't work any more

Processing control commands: > tags -1 pending Bug #850013 [vim-youcompleteme] vim-youcompleteme: Please provide a newer version, the current one doesn't work any more Added tag(s) pending. -- 850013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850013 Debian Bug Tracking System Contact ow.

Bug#850013: vim-youcompleteme: Please provide a newer version, the current one doesn't work any more

Control: tags -1 pending Thanks for reporting. This package is actually updated and a working version is available in git repository. I just need to solve a problem before upload. On 2017-01-03, Philipp Marek wrote: > Package: vim-youcompleteme > Version: 0+20160327+git1b76af4-2 > Severity: norm

Processed: Unfound the bug

Processing commands for cont...@bugs.debian.org: > notfound 847970 0.7.4-1 Bug #847970 {Done: Ole Streicher } [src:sunpy] sunpy FTBFS in stretch due to missing skimage No longer marked as found in versions sunpy/0.7.4-1. > End of message, stopping processing here. Please contact me if you need a

Bug#833037: [PKG-Openstack-devel] Bug#833037: python-factory-boy: missing depends on ipaddress

On 12/30/2016 04:17 PM, Christopher Baines wrote: > On 29/12/16 09:04, Thomas Goirand wrote: >> On 12/28/2016 01:39 AM, Brian May wrote: >>> Thomas Goirand writes: >>> If you're supposed to maintain this package, the least you can do is subscribe to the package bug reports. You cannot ex

Processed: bug 849082 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=119690

Processing commands for cont...@bugs.debian.org: > forwarded 849082 https://rt.cpan.org/Public/Bug/Display.html?id=119690 Bug #849082 {Done: Niko Tyni } [libapache2-mod-perl2] libapache2-mod-perl2: FTBFS: test failures with Apache 2.4.25 Set Bug forwarded-to-address to 'https://rt.cpan.org/Publi

Processed: bug 850160 is forwarded to https://github.com/netblue30/firejail/issues/1020

Processing commands for cont...@bugs.debian.org: > forwarded 850160 https://github.com/netblue30/firejail/issues/1020 Bug #850160 [firejail] firejail: Firejail local root exploit Set Bug forwarded-to-address to 'https://github.com/netblue30/firejail/issues/1020'. > thanks Stopping processing here

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

Daniel Kahn Gillmor: > I've been able to replicate the problems described by intrigeri in > https://bugs.debian.org/849845; i'm preparing an update to gpg with > cherry-picked patches that resolves most of them for me. I'd be happy to test these changes before you upload. If you wish, push them to

Processed: found 850160 in 0.9.44.2-1

Processing commands for cont...@bugs.debian.org: > found 850160 0.9.44.2-1 Bug #850160 [firejail] firejail: Firejail local root exploit Marked as found in versions firejail/0.9.44.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 850160: http://bugs.debian.org/

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

On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote: > On 29/12/16 20:56, Gaudenz Steinlin wrote: > > > > Hi Emilio > > > > Emilio Pozuelo Monfort writes: > > > >> Source: ceph > >> Version: 10.2.5-2 > >> Severity: serious > >> > >> Your package failed to build on mips/el: > >> > >> g++ -DHAVE_CO

Bug#809997: emscripten: neither in stable nor testing

Le 04/01/2017 à 15:21, Xavier Bestel a écrit : > Le mercredi 04 janvier 2017 à 15:15 +0100, Sylvestre Ledru a écrit : >> yes, emscripten is, afaik, still using a forked version of llvm... >> see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775147#10 >> Since it didn't move for the last 2 year

Bug#809997: emscripten: neither in stable nor testing

Le mercredi 04 janvier 2017 à 15:15 +0100, Sylvestre Ledru a écrit : > yes, emscripten is, afaik, still using a forked version of llvm... > see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775147#10 > Since it didn't move for the last 2 years, maybe we should just ship > emscripten with the f

Bug#809997: emscripten: neither in stable nor testing

Le 04/01/2017 à 15:04, Xavier Bestel a écrit : > Package: emscripten > Version: 1.22.1-1 > Followup-For: Bug #809997 > > Dear Maintainer, > > I can't seem to be able to install emscripten in jessie, nor in testing. yes, emscripten is, afaik, still using a forked version of llvm... see: https://bu

Processed: notfixed 847970 in 0.7.4-1

Processing commands for cont...@bugs.debian.org: > # unconfuse the bts > notfixed 847970 0.7.4-1 Bug #847970 {Done: Ole Streicher } [src:sunpy] sunpy FTBFS in stretch due to missing skimage No longer marked as fixed in versions 0.7.4-1. > thanks Stopping processing here. Please contact me if you

Bug#850160: firejail: Firejail local root exploit

Package: firejail Severity: grave Tags: security Justification: user security hole Please see http://www.openwall.com/lists/oss-security/2017/01/04/1 Cheers, Moritz

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

Processing control commands: > severity 849845 grave Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore Severity set to 'grave' from 'important' -- 849845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849845 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#809997: emscripten: neither in stable nor testing

Package: emscripten Version: 1.22.1-1 Followup-For: Bug #809997 Dear Maintainer, I can't seem to be able to install emscripten in jessie, nor in testing. Regards, Xav -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (900, 'stable')

Bug#844568: jack: diff for NMU version 3.1.1+cvs20050801-29.2

Control: tags 844568 + pending Dear maintainer, I've prepared an NMU for jack (versioned as 3.1.1+cvs20050801-29.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. BTW, I did this NMU using dgit, and it's the first time I use it, I hope nothing went wrong.

Processed: jack: diff for NMU version 3.1.1+cvs20050801-29.2

Processing control commands: > tags 844568 + pending Bug #844568 [jack] jack: complains about missing dependency and dies Added tag(s) pending. -- 844568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: vim-youcompleteme: Please provide a newer version, the current one doesn't work any more

Processing control commands: > severity -1 grave Bug #850013 [vim-youcompleteme] vim-youcompleteme: Please provide a newer version, the current one doesn't work any more Severity set to 'grave' from 'normal' -- 850013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850013 Debian Bug Tracking

Processed: Re: vim-youcompleteme: 'KeyError's on every key press flooding vim

Processing control commands: > severity -1 grave Bug #850113 [vim-youcompleteme] vim-youcompleteme: 'KeyError's on every key press flooding vim Severity set to 'grave' from 'important' -- 850113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850113 Debian Bug Tracking System Contact ow...@bu

Bug#831081: marked as done (repsnapper: FTBFS with GCC 6: ./libraries/amf/amftools-code/include/STL_File.h:92:104: error: call of overloaded 'abs(double)' is ambiguous)

Your message dated Wed, 04 Jan 2017 12:33:37 + with message-id and subject line Bug#831081: fixed in repsnapper 2.4a0-2 has caused the Debian Bug report #831081, regarding repsnapper: FTBFS with GCC 6: ./libraries/amf/amftools-code/include/STL_File.h:92:104: error: call of overloaded 'abs(do

Bug#810907: marked as done (repsnapper: FTBFS on ppc64el: termios problems)

Your message dated Wed, 04 Jan 2017 12:33:36 + with message-id and subject line Bug#810907: fixed in repsnapper 2.4a0-2 has caused the Debian Bug report #810907, regarding repsnapper: FTBFS on ppc64el: termios problems to be marked as done. This means that you claim that the problem has been

Bug#814331: marked as done (repsnapper: nothing displayed in 3d window)

Your message dated Wed, 04 Jan 2017 12:33:37 + with message-id and subject line Bug#814331: fixed in repsnapper 2.4a0-2 has caused the Debian Bug report #814331, regarding repsnapper: nothing displayed in 3d window to be marked as done. This means that you claim that the problem has been deal

Bug#792205: fusioninventory-agent: modifies conffiles (policy 10.7.3): /etc/fusioninventory/agent.cfg

Hi Andreas, from my point of view, this is not a bug. fusioninventory-agent package uses ucf to handle such case and between v2.2.3 (wheezy version) & v2.3.10 (jessie version), the default installed agent.cfg configuration has been changed a little (mostly commented new config value and few minor

Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

Hi Adrian, On 01/04/2017 08:50 AM, John Paul Adrian Glaubitz wrote: > Hi! > > The current version 7.4.4-3 of libatomic-ops builds fine on all architectures > [1]. > Can we close this or am I missing something? I understand that they are building because the tests are being bypassed as an workar

Bug#850147: mariadb-10.0: stretch should be released with mariadb-10.1 only

Source: mariadb-10.0 Version: 10.0.28-2 Severity: serious Hi, the remaining bits needed for the transition from mariadb-10.0 to mariadb-10.1 are updates to the dependencies in mysql-defaults (and this RC bug to get 10.0 removed at some point). Andreas

Bug#849602: not a bug

thats how fonts are installed. this is not a bug. *Kind Regards,* Patrick Mutwiri / _dev +254 727 542 899 Nairobi, Kenya http://patric.xyz [image: Twitter] [image: Facebook] [image: Google +]

Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

Hi! The current version 7.4.4-3 of libatomic-ops builds fine on all architectures [1]. Can we close this or am I missing something? Adrian > [1] https://buildd.debian.org/status/package.php?p=libatomic-ops -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `.

Bug#849991: marked as done (breathe: FTBFS with new doxygen?)

Your message dated Wed, 04 Jan 2017 10:18:31 + with message-id and subject line Bug#849991: fixed in doxygen 1.8.13-4 has caused the Debian Bug report #849991, regarding breathe: FTBFS with new doxygen? to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#790352: marked as done (pyro: remove version 3 in stretch?)

Your message dated Wed, 04 Jan 2017 10:03:32 + with message-id and subject line Bug#790352: fixed in pyro 1:3.14-5 has caused the Debian Bug report #790352, regarding pyro: remove version 3 in stretch? to be marked as done. This means that you claim that the problem has been dealt with. If th

  1   2   >