Bug#850023: ImportError when importing ruamel.yaml

❦ 6 janvier 2017 22:51 GMT, Chris Lamb  : > So, the binary package is missing a Depends on `python-typing`. > > However, it looks like this "should" work: > >install_requires=dict( >[…] >py27=["ruamel.ordereddict", "typing"], >[…] >) This seems

Bug#850491: marked as done (slurm-llnl: CVE-2016-10030)

Your message dated Sat, 7 Jan 2017 07:41:18 +0100 with message-id <20170107064118.zjhqzuvysb3444xj@eldamar.local> and subject line Re: Bug#850491: slurm-llnl: CVE-2016-10030 has caused the Debian Bug report #850491, regarding slurm-llnl: CVE-2016-10030 to be marked as done. This means that you

Bug#850491: slurm-llnl: CVE-2016-10030

Source: slurm-llnl Version: 14.03.9-5 Severity: grave Tags: upstream patch security fixed-upstream Justification: user security hole Hi, the following vulnerability was published for slurm-llnl. CVE-2016-10030[0]: | The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, | 16.x

Bug#839050: marked as done (js24 crashes on ARM64)

Your message dated Sat, 07 Jan 2017 03:05:31 + with message-id and subject line Bug#839050: fixed in mozjs24 24.2.0-5.1 has caused the Debian Bug report #839050, regarding js24 crashes on ARM64 to be marked as done. This means that you claim that the

Bug#849794: qtwebengine-opensource-src: FTBFS on buildd machines

On Saturday, January 07, 2017 12:10:58 AM Santiago Vila wrote: > On Sat, 31 Dec 2016, Scott Kitterman wrote: > > FTBFS bugs are only RC when there is an existing binary for the > > architecture. > That's not really accurate, because the binary could have been created > by "cheating" (for example,

Processed: Re: gcr: FTBFS: Test failures

Processing control commands: > tags -1 moreinfo unreproducible Bug #846728 [src:gcr] gcr: FTBFS: FAIL: test-gnupg-collection 3 /gcr/gnupg-collection/reload Added tag(s) moreinfo and unreproducible. -- 846728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846728 Debian Bug Tracking System

Bug#846728: gcr: FTBFS: Test failures

Control: tags -1 moreinfo unreproducible Hi Lucas On Sat, 3 Dec 2016 08:41:49 +0100 Lucas Nussbaum wrote: > Source: gcr > Version: 3.20.0-3 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20161202 qa-ftbfs > Justification: FTBFS

Processed: Bug#828506 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 828506 pending Bug #828506 {Done: Eric Dorland } [src:pkcs11-helper] pkcs11-helper: FTBFS with openssl 1.1.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 828506:

Bug#828506: marked as pending

tag 828506 pending thanks Hello, Bug #828506 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=pkg-opensc/pkcs11-helper.git;a=commitdiff;h=6f55e4d --- commit

Bug#614374: marked as done (pg_upgradecluster fails when datdba is a role without login privilege)

Your message dated Fri, 06 Jan 2017 23:32:12 + with message-id and subject line Bug#838812: fixed in postgresql-common 165+deb8u2 has caused the Debian Bug report #838812, regarding pg_upgradecluster fails when datdba is a role without login privilege to

Bug#838812: marked as done (pg_upgradecluster skips databases owned by a role who is not a user)

Your message dated Fri, 06 Jan 2017 23:32:12 + with message-id and subject line Bug#838812: fixed in postgresql-common 165+deb8u2 has caused the Debian Bug report #838812, regarding pg_upgradecluster skips databases owned by a role who is not a user to be

Bug#849495: marked as done (python-crypto: CVE-2013-7459)

Your message dated Fri, 06 Jan 2017 23:32:13 + with message-id and subject line Bug#849495: fixed in python-crypto 2.6.1-5+deb8u1 has caused the Debian Bug report #849495, regarding python-crypto: CVE-2013-7459 to be marked as done. This means that you

Bug#614374: marked as done (pg_upgradecluster fails when datdba is a role without login privilege)

Your message dated Fri, 06 Jan 2017 23:32:12 + with message-id and subject line Bug#614374: fixed in postgresql-common 165+deb8u2 has caused the Debian Bug report #614374, regarding pg_upgradecluster fails when datdba is a role without login privilege to

Bug#838812: marked as done (pg_upgradecluster skips databases owned by a role who is not a user)

Your message dated Fri, 06 Jan 2017 23:32:12 + with message-id and subject line Bug#614374: fixed in postgresql-common 165+deb8u2 has caused the Debian Bug report #614374, regarding pg_upgradecluster skips databases owned by a role who is not a user to be

Bug#849794: qtwebengine-opensource-src: FTBFS on buildd machines

On Sat, 31 Dec 2016, Scott Kitterman wrote: > FTBFS bugs are only RC when there is an existing binary for the architecture. That's not really accurate, because the binary could have been created by "cheating" (for example, the package may have missing build-dependencies but the uploaded packages

Bug#828506: marked as done (pkcs11-helper: FTBFS with openssl 1.1.0)

Your message dated Fri, 06 Jan 2017 23:05:30 + with message-id and subject line Bug#828506: fixed in pkcs11-helper 1.21-1 has caused the Debian Bug report #828506, regarding pkcs11-helper: FTBFS with openssl 1.1.0 to be marked as done. This means that you

Processed: Re: qtwebengine-opensource-src: FTBFS on buildd machines

Processing commands for cont...@bugs.debian.org: > severity 849794 serious Bug #849794 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS on buildd machines Severity set to 'serious' from 'important' > retitle 849794 qtwebengine-opensource-src: FTBFS in every arch (including >

Bug#850023: ImportError when importing ruamel.yaml

Hi, > ImportError when importing ruamel.yaml So, the binary package is missing a Depends on `python-typing`. However, it looks like this "should" work: install_requires=dict( […] py27=["ruamel.ordereddict", "typing"], […] ) Regards, -- ,''`. : :' :

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

Hi all, I was able to get the new version - ─[$] sudo aptitude install gnupg=2.1.17-3 dirmngr=2.1.17-3 gpgv=2.1.17-3 gnupg-agent=2.1.17-3 gpgsm=2.1.17-3 scdaemon=2.1.17-3 -y Installed it perfectly ─[$] apt-cache policy gnupg [4:19:09] gnupg: Installed: 2.1.17-3 Candidate: 2.1.17-3

Bug#850458: marked as done (s3ql: FTBFS (No such file or directory: 'ps'))

Your message dated Fri, 06 Jan 2017 22:34:26 + with message-id and subject line Bug#850458: fixed in s3ql 2.21+dfsg-2 has caused the Debian Bug report #850458, regarding s3ql: FTBFS (No such file or directory: 'ps') to be marked as done. This means that

Bug#850469: dgit: Can't push: corrupted object

Nikolaus Rath writes ("Re: Bug#850469: dgit: Can't push: corrupted object"): > On Jan 06 2017, Ian Jackson wrote: > > 2. If the faulty merge commit 1bc3c1e2d353 is at the top of your > > history and not buried in it, you can perhaps strip it off and try > >

Bug#850469: dgit: Can't push: corrupted object

Ian Jackson writes ("Re: Bug#850469: dgit: Can't push: corrupted object"): > Oh, in that case you win. I think if you install 2.14 or 2.16 and run > `dgit quilt-fixup' it will generate a fresh uncorrupted merge, then. Actually, I think this may be wrong wrong - maybe the merge is only generated

Bug#850336: rmpi: FTBFS (Cannot find mpi.h header file)

Thanks for fixing this so quickly! On Thu, Jan 05, 2017 at 08:13:37PM -0600, Dirk Eddelbuettel wrote: > > On 6 January 2017 at 02:53, Santiago Vila wrote: > | Hi. > | > | I've triggered rebuilds in reproducible builds > > Why? That wasn't what I asked you to do. > > | and it also fails there:

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

> gbp:info: Tarballs 'texlive-bin_2016.20160513.41080.orig.tar.xz' not found at > '../tarballs' I cannot reproduce your problem. I was able to successfully checkout texlive-bin_2016.20160513.41080.orig.tar.xz from the textlive-bin repository using pristine-tar manually: pristine-tar

Bug#850469: dgit: Can't push: corrupted object

On Jan 06 2017, Ian Jackson wrote: > Control: forcemerge 849041 -1 > > Nikolaus Rath writes ("Bug#850469: dgit: Can't push: corrupted object"): >> remote: dgit-repos-server: reject: corrupted object >> 1bc3c1e2d353386487d7d8e7740ebd21f369b107 (missing metadata) >

Bug#850007: marked as done (libvncserver: CVE-2016-9941)

Your message dated Fri, 06 Jan 2017 21:17:30 + with message-id and subject line Bug#850007: fixed in libvncserver 0.9.9+dfsg2-6.1+deb8u2 has caused the Debian Bug report #850007, regarding libvncserver: CVE-2016-9941 to be marked as done. This means that

Bug#845639: marked as done (Compatibility with xserver 1.19 / xorg-video-abi-23)

Your message dated Fri, 06 Jan 2017 21:17:39 + with message-id and subject line Bug#845639: fixed in nvidia-graphics-drivers-legacy-304xx 304.134-0~deb8u1 has caused the Debian Bug report #845639, regarding Compatibility with xserver 1.19 /

Bug#846331: marked as done (nvidia-graphics-drivers: CVE-2016-7382, CVE-2016-7389: missing permissions check and improper validation vulnerability)

Your message dated Fri, 06 Jan 2017 21:17:38 + with message-id and subject line Bug#846331: fixed in nvidia-graphics-drivers 340.101-1 has caused the Debian Bug report #846331, regarding nvidia-graphics-drivers: CVE-2016-7382, CVE-2016-7389: missing

Bug#846331: marked as done (nvidia-graphics-drivers: CVE-2016-7382, CVE-2016-7389: missing permissions check and improper validation vulnerability)

Your message dated Fri, 06 Jan 2017 21:17:39 + with message-id and subject line Bug#846331: fixed in nvidia-graphics-drivers-legacy-304xx 304.134-0~deb8u1 has caused the Debian Bug report #846331, regarding nvidia-graphics-drivers: CVE-2016-7382,

Bug#848195: marked as done (nvidia-graphics-drivers: CVE-2016-8826)

Your message dated Fri, 06 Jan 2017 21:17:39 + with message-id and subject line Bug#848195: fixed in nvidia-graphics-drivers-legacy-304xx 304.134-0~deb8u1 has caused the Debian Bug report #848195, regarding nvidia-graphics-drivers: CVE-2016-8826 to be

Bug#850008: marked as done (libvncserver: CVE-2016-9942)

Your message dated Fri, 06 Jan 2017 21:17:30 + with message-id and subject line Bug#850008: fixed in libvncserver 0.9.9+dfsg2-6.1+deb8u2 has caused the Debian Bug report #850008, regarding libvncserver: CVE-2016-9942 to be marked as done. This means that

Bug#848195: marked as done (nvidia-graphics-drivers: CVE-2016-8826)

Your message dated Fri, 06 Jan 2017 21:17:38 + with message-id and subject line Bug#848195: fixed in nvidia-graphics-drivers 340.101-1 has caused the Debian Bug report #848195, regarding nvidia-graphics-drivers: CVE-2016-8826 to be marked as done. This

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

On 06/01/17 11:48, Norbert Preining wrote: > Package: pristine-tar > Version: 1.37 > Severity: grave > Justification: renders package unusable > > HI all, > > pristine-tar is somehow broken, to put it friendly: > $ gbp buildpackage -us -uc -rfakeroot > gbp:info: Tarballs

Bug#849777: marked as done (shutter: CVE-2016-10081: Insecure use of perl exec())

Your message dated Fri, 06 Jan 2017 21:04:56 + with message-id and subject line Bug#849777: fixed in shutter 0.93.1-1.3 has caused the Debian Bug report #849777, regarding shutter: CVE-2016-10081: Insecure use of perl exec() to be marked as done. This

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

Hi Tomasz, Thanks for coming back. I'm away from my computer due to a long weekend here, but " Yes it is texlive-bin * I guess I haven't done an upload since September " I cannot run with -d etc now, but will do when I'm back All the best Norbert On January 7, 2017 5:59:39 AM

Bug#847580: marked as done (Embeds dietlibc (GPL) but does not have a Built-Using field)

Your message dated Fri, 06 Jan 2017 21:05:35 + with message-id and subject line Bug#847580: fixed in util-vserver 0.30.216-pre3120-1.3 has caused the Debian Bug report #847580, regarding Embeds dietlibc (GPL) but does not have a Built-Using field to be

Bug#849777: shutter: CVE-2016-10081: Insecure use of perl exec()

Hi Dominique, On Fri, Jan 06, 2017 at 07:33:07PM +0100, Dominique Dumont wrote: > On Sat, 31 Dec 2016 12:39:57 +0100 Christoph Biedl ulm.de> wrote: > > Christoph Biedl wrote... > > > > > The patch attached > > Thanks. > > I've tested the patch and it's fine. > >

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

On Fri 2017-01-06 14:47:46 -0500, shirish शिरीष wrote: > I can confirm Jaden's findings. Perhaps the content hasn't reached his > mirror yet. It's same thing at my end. I just updated to see if the > new version has come up at my end. (not even in sid/unstable) > > [$] apt-cache policy gpgv >

Bug#828556: sslscan: FTBFS with openssl 1.1.0

On 2017-01-05 23:33:59 [+0100], Christoph Berg wrote: > > why on libssl-dev (<< 1.1.0~)? > > The | libssl-dev (<< 1.1.0~) part is there to enable backporting to > jessie without having to revert libssl1.0-dev back to libssl-dev. and I though that this is one of the changes you do when you intend

Processed: Re: Bug#850469: dgit: Can't push: corrupted object

Processing control commands: > forcemerge 849041 -1 Bug #849041 {Done: Ian Jackson } [dgit] dgit: psuedomerge commits have no author. Bug #850469 [dgit] dgit: Can't push: corrupted object Severity set to 'critical' from 'normal' Marked Bug as done Marked as fixed

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

at bottom :- On 07/01/2017, Daniel Kahn Gillmor wrote: > On Fri 2017-01-06 12:49:32 -0500, Jaden Peterson wrote: >> I have no place in the topic of this bug, but I installed the patches >> you provided on January 5th onto my Debian Testing system. I would like >> to

Bug#850456: [Debichem-devel] Bug#850456: elpa: FTBFS (not enough slots available)

Hi On 6 January 2017 at 20:00, Santiago Vila wrote: > -- > There are not enough slots available in the system to satisfy the 2 slots > that were requested by the application: >

Bug#850464: nfs-blkmap.service fails to start at boot

package: nfs-kernel-server version: 1:1.3.4-2 severity: serious The blkmapd process looks for /run/rpc_pipefs/nfs/blocklayout It fails to find it and the system boot doesn't complete, it asks for an emergency login on the text console. I don't see anything under /run/rpc_pipefs/nfs Other NFS

Bug#849593: marked as done (libfftw3-single3: dependencies in shlibs file not tight enough)

Your message dated Fri, 06 Jan 2017 19:03:41 + with message-id and subject line Bug#849593: fixed in fftw3 3.3.5-2 has caused the Debian Bug report #849593, regarding libfftw3-single3: dependencies in shlibs file not tight enough to be marked as done.

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

On Fri 2017-01-06 12:49:32 -0500, Jaden Peterson wrote: > I have no place in the topic of this bug, but I installed the patches > you provided on January 5th onto my Debian Testing system. I would like > to notify you that gpgv2 depends on gpgv version 2.1.17-3 or greater, > which is not

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

Your message dated Fri, 06 Jan 2017 18:48:27 + with message-id and subject line Bug#849651: fixed in efibootmgr 14-2 has caused the Debian Bug report #849651, regarding efibootmgr: FTBFS on armhf: collect2: error: ld returned 1 exit status; 2-byte wchar_t

Bug#849220: marked as done (ipykernel: FTBFS (failing tests))

Your message dated Fri, 6 Jan 2017 22:45:31 +0400 with message-id and subject line ipykernel: FTBFS (failing tests) has caused the Debian Bug report #849220, regarding ipykernel: FTBFS (failing tests) to be marked as done. This means that you

Bug#850456: [Debichem-devel] Bug#850456: elpa: FTBFS (not enough slots available)

> How many CPU cores do you have? I said that in the bug report: > The bug should be reproducible with sbuild on a single CPU virtual machine. Thanks.

Processed: closing 849216

Processing commands for cont...@bugs.debian.org: > close 849216 1.4.9-2 Bug #849216 [python-sphinx] Packages which FTBFS with AssertionError about len(context) Marked as fixed in versions sphinx/1.4.9-2. Bug #849216 [python-sphinx] Packages which FTBFS with AssertionError about len(context)

Bug#849216: closing 849216

close 849216 1.4.9-2 thanks

Bug#850456: [Debichem-devel] Bug#850456: elpa: FTBFS (not enough slots available)

Hi, On Fri, Jan 06, 2017 at 06:00:17PM +, Santiago Vila wrote: > I tried to build this package in stretch with "dpkg-buildpackage -A" > but it failed: > > > [...] > debian/rules build-arch > dh build-arch >

Bug#849777: shutter: CVE-2016-10081: Insecure use of perl exec()

On Sat, 31 Dec 2016 12:39:57 +0100 Christoph Biedl wrote: > Christoph Biedl wrote... > > > The patch attached Thanks. I've tested the patch and it's fine. I've also created a patch to replace all system("big string") calls to system(@big_list) in all plugins

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

Control: tag -1 +pending On Wed, Jan 04, 2017 at 07:04:59PM +, Steve McIntyre wrote: >On Thu, Dec 29, 2016 at 03:22:02PM +, Chris West (Faux) wrote: >> >>The package fails to build on armhf: ... >Confirmed - just seen the same build failure on a porter box. Looks >like YA issue found

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

Processing control commands: > tag -1 +pending Bug #849651 [src:efibootmgr] efibootmgr: FTBFS on armhf: collect2: error: ld returned 1 exit status; 2-byte wchar_t Added tag(s) pending. -- 849651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849651 Debian Bug Tracking System Contact

Bug#850458: s3ql: FTBFS (No such file or directory: 'ps')

Package: src:s3ql Version: 2.21+dfsg-1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-arch dh build-arch --with

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

Package: src:elpa Version: 2016.05.001-2 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-arch dh build-arch

Bug#849216: Packages which FTBFS with AssertionError about len(context)

Control: reassign -1 python-sphinx 1.4.9-1 Control: affects -1 checkbox-ng dhcpcanon ipywidgets nbsphinx pylibmc Control: close -1 python-sphinx 1.4.9-2 On Tue, 03 Jan 2017 22:09:00 + ju wrote: > Niko Tyni: > > > > Seems to be

Processed (with 1 error): Re: Bug#849216: Packages which FTBFS with AssertionError about len(context)

Processing control commands: > reassign -1 python-sphinx 1.4.9-1 Bug #849216 [checkbox-ng,dhcpcanon,ipywidgets,nbsphinx,pylibmc] Packages which FTBFS with AssertionError about len(context) Bug reassigned from package 'checkbox-ng,dhcpcanon,ipywidgets,nbsphinx,pylibmc' to 'python-sphinx'.

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

On Thu, 05 Jan 2017 16:56:40 -0500 Daniel Kahn Gillmor wrote: > Control: fowarded 849845 https://bugs.gnupg.org/gnupg/issue2902 > > On Thu 2017-01-05 08:15:06 -0500, intrigeri wrote: > > Daniel Kahn Gillmor: > >> The remaining problem for me ws that when i use tor, if i

Processed: Re: [pkg-go] Bug#849663: golang-github-boltdb-bolt: FTBFS on 32-bit: db_test.go:534: constant 2147483648 overflows int

Processing commands for cont...@bugs.debian.org: > forwarded 849663 https://github.com/boltdb/bolt/issues/645 Bug #849663 [src:golang-github-boltdb-bolt] golang-github-boltdb-bolt: FTBFS on 32-bit: db_test.go:534: constant 2147483648 overflows int Set Bug forwarded-to-address to

Bug#849663: [pkg-go] Bug#849663: golang-github-boltdb-bolt: FTBFS on 32-bit: db_test.go:534: constant 2147483648 overflows int

forwarded 849663 https://github.com/boltdb/bolt/issues/645 thanks Hi, Thanks for the report. I have forwarded the bug upstream, and will try to produce a fix meanwhile. On 29/12/16 13:24, Chris West (Faux) wrote: > Source: golang-github-boltdb-bolt > Version: 1.2.1-2 > Severity: serious >

Bug#850453: Non-fatal harmful errors upgrading from pre-0.82 to 0.82 under cow-shell

Package: cowdancer Version: 0.82 Severity: serious Running cowbuilder --update gives a load of the following errors: > ERROR: ld.so: object '/usr/lib/cowdancer/libcowdancer.so' from LD_PRELOAD > cannot be preloaded (cannot open shared object file): ignored. The entire update process runs under

Bug#850430: marked as done (postfix 3.1.4-1 breaks on lmtp interface)

Your message dated Fri, 06 Jan 2017 16:49:17 + with message-id and subject line Bug#850430: fixed in postfix 3.1.4-2 has caused the Debian Bug report #850430, regarding postfix 3.1.4-1 breaks on lmtp interface to be marked as done. This means that you

Bug#850400: marked as done (postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail)

Your message dated Fri, 06 Jan 2017 16:49:17 + with message-id and subject line Bug#850400: fixed in postfix 3.1.4-2 has caused the Debian Bug report #850400, regarding postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving

Bug#818616: What should I do?

On Mon, Dec 26, 2016 at 02:01:34PM +0100, Enrico Tassi wrote: > Hum, I'm a bit lost here. 2.0.4 is fine, but does not work on arm64. > What about 2.1-beta2 + fix allocator (as in message #35) ? Was it > tested? Does it work? Should I upload it? Hi Enrico, Yes - I verified it, it does work on

Bug#850430: postfix 3.1.4-1 breaks on lmtp interface

* LaMont Jones 2017.01.06 16:58: > On Fri, Jan 06, 2017 at 03:22:34PM +0100, Thomas Leuxner wrote: > > $ grep lmtp /etc/postfix/master.cf > > lmtp unix - - y - - lmtp > > Is there by any chance any trailing whitespace on that line? > >

Bug#850419: [Pkg-javascript-devel] Bug#850419: Local installation seems needed

Control: severity -1 important On വെള്ളി 06 ജനുവരി 2017 04:07 വൈകു, Bastien ROUCARIES wrote: > Using grunt for node-sprintf-js I get > > Fatal error: Unable to find local grunt. > > If you're seeing this message, grunt hasn't been installed locally to > your project. For more information about

Processed: Re: [Pkg-javascript-devel] Bug#850419: Local installation seems needed

Processing control commands: > severity -1 important Bug #850419 [node-grunt-cli] Local installation seems needed Severity set to 'important' from 'serious' -- 850419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 850430

Processing commands for cont...@bugs.debian.org: > tags 850430 + pending Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface Ignoring request to alter tags of bug #850430 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#850430: postfix 3.1.4-1 breaks on lmtp interface

On Fri, Jan 06, 2017 at 03:22:34PM +0100, Thomas Leuxner wrote: > $ grep lmtp /etc/postfix/master.cf > lmtp unix - - y - - lmtp Is there by any chance any trailing whitespace on that line? lamont

Processed: tagging 850400

Processing commands for cont...@bugs.debian.org: > tags 850400 + pending Bug #850400 [postfix-mysql] postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail Ignoring request to alter tags of bug #850400 to the same tags previously set > thanks Stopping processing

Processed: tagging 850430

Processing commands for cont...@bugs.debian.org: > tags 850430 + pending Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface Ignoring request to alter tags of bug #850430 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 850400

Processing commands for cont...@bugs.debian.org: > tags 850400 + pending Bug #850400 [postfix-mysql] postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail Ignoring request to alter tags of bug #850400 to the same tags previously set > thanks Stopping processing

Bug#850317: [Reportbug-maint] Bug#850317: reportbug: crashes when attaching a .tar.gz

control: severity -1 normal On Thu, Jan 5, 2017 at 3:56 PM, Dominik George wrote: > Package: reportbug > Version: 7.1.2 > Severity: grave > Justification: causes non-serious data loss severity greatly overstated: you're not losing any data > > -BEGIN PGP SIGNED

Processed: bug 850438 is forwarded to https://github.com/silnrsi/teckit/issues/1

Processing commands for cont...@bugs.debian.org: > forwarded 850438 https://github.com/silnrsi/teckit/issues/1 Bug #850438 [teckit] teckit: license problem with SFconv/ConvertUTF.[ch] Set Bug forwarded-to-address to 'https://github.com/silnrsi/teckit/issues/1'. > thanks Stopping processing here.

Processed: Re: [Reportbug-maint] Bug#850317: reportbug: crashes when attaching a .tar.gz

Processing control commands: > severity -1 normal Bug #850317 [reportbug] reportbug: crashes when attaching a .tar.gz Severity set to 'normal' from 'grave' -- 850317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: severity of 849683 is normal

Processing commands for cont...@bugs.debian.org: > severity 849683 normal Bug #849683 [calibre] calibre: reproducible crash when pressing any button Severity set to 'normal' from 'grave' > tag 849683 +moreinfo Bug #849683 [calibre] calibre: reproducible crash when pressing any button Added tag(s)

Processed: tagging 850430

Processing commands for cont...@bugs.debian.org: > tags 850430 + pending Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface Ignoring request to alter tags of bug #850430 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#844568: marked as done (jack: complains about missing dependency and dies)

Your message dated Fri, 06 Jan 2017 15:07:48 + with message-id and subject line Bug#844568: fixed in jack 3.1.1+cvs20050801-29.2 has caused the Debian Bug report #844568, regarding jack: complains about missing dependency and dies to be marked as done.

Processed: tagging 850430

Processing commands for cont...@bugs.debian.org: > tags 850430 + pending Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface Ignoring request to alter tags of bug #850430 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 850400

Processing commands for cont...@bugs.debian.org: > tags 850400 + pending Bug #850400 [postfix-mysql] postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail Ignoring request to alter tags of bug #850400 to the same tags previously set > thanks Stopping processing

Processed: tagging 850400

Processing commands for cont...@bugs.debian.org: > tags 850400 + pending Bug #850400 [postfix-mysql] postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail Ignoring request to alter tags of bug #850400 to the same tags previously set > thanks Stopping processing

Processed: tagging 850400

Processing commands for cont...@bugs.debian.org: > tags 850400 + pending Bug #850400 [postfix-mysql] postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 850430

Processing commands for cont...@bugs.debian.org: > tags 850430 + pending Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface Ignoring request to alter tags of bug #850430 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 850400

Processing commands for cont...@bugs.debian.org: > tags 850400 + pending Bug #850400 [postfix-mysql] postfix-mysql 3.1.4-1 regression with postfix-mysql.so stops sending and receiving mail Ignoring request to alter tags of bug #850400 to the same tags previously set > thanks Stopping processing

Bug#787956: raising the severity, prevents usage of the multilib packages

On Fri, Jan 06, 2017 at 08:48:06AM +0100, Matthias Klose wrote: > On 05.12.2016 18:50, Mark Brown wrote: > > As we have been discussing it is still not clear to me if I should fix > > or remove the multilib packages since it is still not clear to me that > > there is a sensible use case for them.

Processed: tagging 850430

Processing commands for cont...@bugs.debian.org: > tags 850430 + pending Bug #850430 [postfix] postfix 3.1.4-1 breaks on lmtp interface Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 850430:

Bug#850438: teckit: license problem with SFconv/ConvertUTF.[ch]

Package: teckit Version: 2.5.4~svn140+ds2-1 Severity: serious Tags: upstream Hello, According to Lintian, there is a problem with this file, which is licensed by Unicode: Tag: license-problem-convert-utf-code Severity: serious Certainty: possible Info: The following file source files include

Bug#850430: postfix 3.1.4-1 breaks on lmtp interface

* Thomas Leuxner 2017.01.06 13:45: > Jan 6 13:27:03 nihlus postfix/qmgr[10795]: 3tw3Qk5C62z2B: > from=, size=2366, nrcpt=1 (queue active) > Jan 6 13:27:03 nihlus postfix/smtp[10817]: fatal: unknown service: > private/dovecot-lmtp/tcp > Jan 6

Processed: bug 849845 is forwarded to https://bugs.gnupg.org/gnupg/issue2902

Processing commands for cont...@bugs.debian.org: > forwarded 849845 https://bugs.gnupg.org/gnupg/issue2902 Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore Set Bug forwarded-to-address to 'https://bugs.gnupg.org/gnupg/issue2902'. > thanks Stopping processing here. Please

Bug#849683: calibre: reproducible crash when pressing any button

Package: calibre Severity: normal Followup-For: Bug #849683 I have the same version and I just added a book to test your scenario. I have not run into any crash, hence +moreinfo and lowering the severity. Also, can you generate a better backtrace ? -- System Information: Debian Release:

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

Hi Tzafrir, On Fri, Jan 06, 2017 at 12:25:07AM +0100, Tzafrir Cohen wrote: > The version in Jessie-backports seems to be the only one affected by it. will you upload a fixed version to jessie-bpo or should I? (I'd be happy if you did, but I was the person introducing mock to bpo, so I'd take

Bug#850160: marked as done (firejail: CVE-2017-5180: local root exploit)

Your message dated Fri, 06 Jan 2017 13:03:25 + with message-id and subject line Bug#850160: fixed in firejail 0.9.44.2-3 has caused the Debian Bug report #850160, regarding firejail: CVE-2017-5180: local root exploit to be marked as done. This means that

Bug#850160: Incomplete fix (was: Re: Bug#850160 closed by Reiner Herrmann <rei...@reiner-h.de> (Bug#850160: fixed in firejail 0.9.44.2-2))

Hi Reiner, On Fri, Jan 06, 2017 at 12:37:23PM +0100, Reiner Herrmann wrote: > Hi Moritz, > > On Fri, Jan 06, 2017 at 10:53:17AM +0100, Moritz Muehlenhoff wrote: > > there have been new CVE assignments for firejail. Most of them are fixed in > > stretch, but two of those have not made it into a

Bug#850430: postfix 3.1.4-1 breaks on lmtp interface

Package: postfix Version: 3.1.4-1 Severity: grave After upgrading and having the symlink and 'master.cf' changes applied by the installation scripts, local LMTP delivery fails. Notice the _tcp_ string being added to the UNIX socket: Jan 6 13:27:03 nihlus postfix/qmgr[10795]: 3tw3Qk5C62z2B:

Processed: Re: Bug#850417: dpkg: error: dpkg status database is locked by another process

Processing control commands: > severity -1 normal Bug #850417 [dpkg] dpkg: error: dpkg status database is locked by another process Severity set to 'normal' from 'grave' -- 850417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850417 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#850417: dpkg: error: dpkg status database is locked by another process

Control: severity -1 normal On 2017-01-06 13:15:18 +0100, Guillem Jover wrote: > Hi! > > On Fri, 2017-01-06 at 11:33:08 +0100, Vincent Lefevre wrote: > > Package: dpkg > > Version: 1.18.18 > > Severity: grave > > Justification: renders package unusable > > I don't think this severity is right

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

Control: fowarded 849845 https://bugs.gnupg.org/gnupg/issue2902 On Thu 2017-01-05 08:15:06 -0500, intrigeri wrote: > Daniel Kahn Gillmor: >> The remaining problem for me ws that when i use tor, if i get back >> records, the connections fail, but the IPv6 records are not marked as >> dead, so

Bug#850417: dpkg: error: dpkg status database is locked by another process

Hi! On Fri, 2017-01-06 at 11:33:08 +0100, Vincent Lefevre wrote: > Package: dpkg > Version: 1.18.18 > Severity: grave > Justification: renders package unusable I don't think this severity is right here, at least for dpkg, but let's see. > When I tried to upgrade from aptitude: > > Performing

Bug#845851: marked as done (gnustep-sqlclient: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Fri, 06 Jan 2017 11:50:20 + with message-id and subject line Bug#845851: fixed in gnustep-sqlclient 1.7.3-2.1 has caused the Debian Bug report #845851, regarding gnustep-sqlclient: switch to build depend on the metapackage

  1   2   >