Processed: closing 851425

Processing commands for cont...@bugs.debian.org: > # Submitter address is forged and no description was provided > close 851425 Bug #851425 [initramfs-tools] initramfs-tools: multiple bugs in initramfs and the booting experience, preventing use of computer Marked Bug as done > thanks Stopping

Bug#817718: wayv: Removal of debhelper compat 4

Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/rules: - Remove legacy DH_COMPAT export. - Add recommended build-arch and build-indep targets. - Use dh_prep instead of dh_clean -k. - Don't allow distclean to

Processed: Re: wayv: Removal of debhelper compat 4

Processing control commands: > tags -1 patch Bug #817718 [src:wayv] wayv: Removal of debhelper compat 4 Added tag(s) patch. -- 817718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: mendexk: Removal of debhelper compat 4

Processing control commands: > tags -1 patch Bug #817579 [src:mendexk] mendexk: Removal of debhelper compat 4 Added tag(s) patch. -- 817579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#817579: mendexk: Removal of debhelper compat 4

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

Bug#851267: marked as done (hatari FTBFS on mips*, arm64, s390x: error: #error unrecognized CPU type)

Your message dated Sun, 15 Jan 2017 04:04:14 + with message-id and subject line Bug#851267: fixed in hatari 2.0.0+dfsg-2 has caused the Debian Bug report #851267, regarding hatari FTBFS on mips*, arm64, s390x: error: #error unrecognized CPU type to be

Bug#779265: marked as done (qreator: fails to generate QR code image)

Your message dated Sun, 15 Jan 2017 04:07:22 + with message-id and subject line Bug#779265: fixed in qreator 13.05.3-3 has caused the Debian Bug report #779265, regarding qreator: fails to generate QR code image to be marked as done. This means that you

Bug#725827: marked as done (qreator: does not strt in stndard installation (no GeoIP provider))

Your message dated Sun, 15 Jan 2017 04:07:22 + with message-id and subject line Bug#725827: fixed in qreator 13.05.3-3 has caused the Debian Bug report #725827, regarding qreator: does not strt in stndard installation (no GeoIP provider) to be marked as

Bug#810158: ksh fails to install on systems with merged /usr

Control: severity -1 important Marco d'Itri wrote: > Control: severity -1 grave > > Patch attached. > Merged /usr is the default since debootstrap 1.0.85, so the package > is uninstallable on new systems. Merged /usr is no more the default since debootstrap 1.0.87, so the package is installable

Processed: Re: Bug#810158: ksh fails to install on systems with merged /usr

Processing control commands: > severity -1 important Bug #810158 [ksh] ksh fails to install on systems with merged /usr Severity set to 'important' from 'grave' -- 810158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810158 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: summary 851446 58

Processing commands for cont...@bugs.debian.org: > summary 851446 58 Summary recorded from message bug 851446 message 58 > thanks Stopping processing here. Please contact me if you need assistance. -- 851446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851446 Debian Bug Tracking System

Processed: notfound 683103 in 2.88dsf-59

Processing commands for cont...@bugs.debian.org: > notfound 683103 2.88dsf-59 Bug #683103 {Done: Simon McVittie } [initscripts] mkdir: cannot create directory `/run/shm': File exists No longer marked as found in versions sysvinit/2.88dsf-59. > thanks Stopping processing here.

Bug#851446: mkdir: cannot create directory `/run/shm': File exists

On Sat, 24 Sep 2016 at 20:44:49 +0200, Simó Albert i Beltran wrote: > I found the same issue upgrading a VPS from wheezy to jessie with the > version 2.88dsf-59. Please don't reopen old bug reports, even if the symptoms are the same, unless you are absolutely sure the root cause is also the same.

Processed: cloning 683103, closing 683103, found -2 in 2.88dsf-59, notfound -2 in 2.88dsf-29 ..., submitter -2

Processing commands for cont...@bugs.debian.org: > clone 683103 -2 Bug #683103 [initscripts] mkdir: cannot create directory `/run/shm': File exists Bug 683103 cloned as bug 851446 > close 683103 Bug #683103 [initscripts] mkdir: cannot create directory `/run/shm': File exists Marked Bug as done >

Bug#844845: marked as done (tkrat: FTBFS: osdep.c:445:40: error: dereferencing pointer to incomplete type 'X509 {aka struct x509_st}')

Your message dated Sun, 15 Jan 2017 00:36:48 + with message-id and subject line Bug#844845: fixed in tkrat 1:2.2cvs20100105-true-dfsg-6.1 has caused the Debian Bug report #844845, regarding tkrat: FTBFS: osdep.c:445:40: error: dereferencing pointer to

Bug#809290: marked as done (shogun: FTBFS with Eigen 3.3)

Your message dated Sat, 14 Jan 2017 23:49:41 + with message-id and subject line Bug#809290: fixed in shogun 3.2.0-7.4 has caused the Debian Bug report #809290, regarding shogun: FTBFS with Eigen 3.3 to be marked as done. This means that you claim that the

Bug#850973: marked as done (python-shogun: FTBFS: build-dependency not installable: libshogun-dev (>= 3.2.0~))

Your message dated Sat, 14 Jan 2017 23:49:41 + with message-id and subject line Bug#809290: fixed in shogun 3.2.0-7.4 has caused the Debian Bug report #809290, regarding python-shogun: FTBFS: build-dependency not installable: libshogun-dev (>= 3.2.0~) to

Bug#851437: astroplan: FTBFS (requires Internet to build)

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

Bug#850948: needrestart: Hangs in apt hook with a zombie

Re, Jonas Smedegaard writes: >> I think the severity of this bug should be lowered to important since >> there is no policy violation of needrestart at all. > > I think it is quite worrisome if simply installing (not actively using) > needrestart inside a chroot spawns daemons

Processed: Re: Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

Processing control commands: > retitle -1 ffmpeg: ChromaprintContext FTBFS Bug #851026 [src:ffmpeg] ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen' Changed Bug title to 'ffmpeg: ChromaprintContext FTBFS' from 'ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to

Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

Control: retitle -1 ffmpeg: ChromaprintContext FTBFS Control: forwarded -1 https://trac.ffmpeg.org/ticket/5997 Control: tags -1 fixed-upstream On Sat, Jan 14, 2017 at 06:47:02AM +0100, Carl Eugen Hoyos wrote: > The relevant lines in the build log are afaict: > > src/libavformat/chromaprint.c: In

Bug#851433: mydumper: FTBFS: .../man1/mydumper.1: No such file or directory

Source: mydumper Version: 0.9.1-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Thanks for taking care of #850847/#850969. Alas, builds of mydumper covering only only its architecture-dependent binary packages (as on the autobuilders, or with

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > unarchive 835170 Bug #835170 {Done: Emilio Pozuelo Monfort } [release.debian.org] transition: protobuf Unarchived Bug 835170 > forcemerge 809290 850973 Bug #809290 [src:shogun] shogun: FTBFS with Eigen 3.3 Bug #850973

Bug#813718: marked as done (mricron FTBFS because fpc check got more strict)

Your message dated Sat, 14 Jan 2017 22:33:45 + with message-id and subject line Bug#813718: fixed in mricron 0.20140804.1~dfsg.1-2 has caused the Debian Bug report #813718, regarding mricron FTBFS because fpc check got more strict to be marked as done.

Bug#821537: Fix from Ubuntu for netmrg

Control: tag -1 pending On Mon, 21 Nov 2016 22:53:43 +0200 Adrian Bunk wrote: > The fix I found in Ubuntu for these bugs is attached. Thanks. I uploaded a NMU to DELAYED/2 fixing these issues. Please let me know if I should delay it longer. netmrg (0.20-7.1) unstable;

Processed: Re: Fix from Ubuntu for netmrg

Processing control commands: > tag -1 pending Bug #821537 [netmrg] netmrg: PHP 7.0 Transition Added tag(s) pending. -- 821537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Fix from Ubuntu for netmrg

Processing control commands: > tag -1 pending Bug #790454 [netmrg] FTBFS in unstable due to build-depends on libmysqlclient15-dev Added tag(s) pending. -- 790454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

On 13.01.2017 20:28, Adrian Bunk wrote: Hi, > Has there been any feedback regarding whether this might already be fixed? > > Currently this bug would prevent that proftpd-mod-clamav could be in > stretch. > OK, I'm able to reproduce the bug, I'll try to test the fix. Hilmar --

Bug#851022: The most important part of the error message

Control: retitle -1 libpqxx FTBFS: sed: character class syntax is [[:space:]], not [:space:] The most important part of the error message is: ... checking for PQexec in -lpq... yes sed: character class syntax is [[:space:]], not [:space:] checking for correct C++ linkage of basic libpq

Processed: The most important part of the error message

Processing control commands: > retitle -1 libpqxx FTBFS: sed: character class syntax is [[:space:]], not > [:space:] Bug #851022 [src:libpqxx] libpqxx: FTBFS: ./conftest.cpp:43: undefined reference to `PQexec' Changed Bug title to 'libpqxx FTBFS: sed: character class syntax is [[:space:]], not

Processed: Retitle based on the actual error

Processing commands for cont...@bugs.debian.org: > retitle 851046 tcsh FTBFS: 122. lexical.at:551: testing Quoting of expansions > in `...` ... FAILED Bug #851046 [src:tcsh] tcsh: FTBFS: | ./conftest.c:20: undefined reference to `crypt' Changed Bug title to 'tcsh FTBFS: 122. lexical.at:551:

Bug#814030: Security flaw fixed in version 6.2.0

On Mon, Jan 09, 2017 at 09:39:30PM +0100, Raphael Hertzog wrote: > Hi everybody, > > On Thu, 05 Jan 2017, Raphael Hertzog wrote: > > CCing upstream author for confirmation. Nicola we are trying to understand > > what security fix went into tcpdf 6.2.0. The bug is private on > > sourceforge, could

Bug#851413: gertty: Uninstallable in Debian Unstable

[Axel Beckert, 2017-01-14] > gertty is uninstallable in Debian Unstable (but not in Debian Testing) > since it depends on python-sqlalchemy (< 1.1), but Debian Unstable > currently contains python-sqlalchemy at version 1.1.4+ds1-1. I uploaded rebuilt version to DELAYED/2 I don't know why I

Bug#850948: needrestart: Hangs in apt hook with a zombie

Quoting Thomas Liske (2017-01-14 16:09:26) > I've replied to #850948 where I think you wan't to discuss the > piuparts-needrestart-* issue. Thanks for correcting my error (I realized it only after posting) > Jonas Smedegaard writes: > >> Maybe it is just a debconf frontend

Bug#851137: closing 851137

close 851137 2.2.0+really2.1.0-1 thanks Reverted to 2.1.0 that doesn't need scandir Scott K

Processed: closing 851137

Processing commands for cont...@bugs.debian.org: > close 851137 2.2.0+really2.1.0-1 Bug #851137 [python-pathlib2] Requires a dependency on missing 'scandir' module Marked as fixed in versions python-pathlib2/2.2.0+really2.1.0-1. Bug #851137 [python-pathlib2] Requires a dependency on missing

Bug#847820: marked as done (kicad: FTBFS: cannot access .../kicad-common/...)

Your message dated Sat, 14 Jan 2017 21:31:14 + with message-id and subject line Bug#847820: fixed in kicad 4.0.5+dfsg1-1 has caused the Debian Bug report #847820, regarding kicad: FTBFS: cannot access .../kicad-common/... to be marked as done. This means

Bug#851000: marked as done (kicad: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl)

Your message dated Sat, 14 Jan 2017 21:31:14 + with message-id and subject line Bug#851000: fixed in kicad 4.0.5+dfsg1-1 has caused the Debian Bug report #851000, regarding kicad: FTBFS: a2x: ERROR: missing configuration file:

Bug#813718: Patch in the MRIcron FTBFS bug

2017-01-14 16:54 GMT+01:00 Andreas Tille : > Hi Adrian, > > On Fri, Jan 13, 2017 at 05:29:01PM +0200, Adrian Bunk wrote: >> I saw you were just working on the MRIcron package. >> >> Can you take a look at the patch in >>

Processed: Express the blocking relationship explicitly

Processing commands for cont...@bugs.debian.org: > block 847493 by 744741 Bug #847493 [yubikey-piv-manager] pkg_resources.DistributionNotFound: The 'PySide' distribution was not found and is required by yubikey-piv-manager 847493 was not blocked by any bugs. 847493 was not blocking any bugs.

Bug#844886: libalog is waiting for binutils testing migration

libalog is waiting for gcc-6 testing migration, which itself depends on binutils testing migration. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

Bug#838800: rss-glx is waiting for imagemagick testing transition

rss-glx is waiting for the imagemagick testing transition. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S.

Bug#851425: initramfs-tools: multiple bugs in initramfs and the booting experience, preventing use of computer

Package: initramfs-tools Version: 0.120+deb8u2 Severity: critical Justification: breaks the whole system Dear Maintainer, x *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was

Processed: Re: Bug#850885: apache2: Using dwww, fails with internal server error when trying to access /usr/share/doc

Processing commands for cont...@bugs.debian.org: > reassign 850885 dwww Bug #850885 [apache2] apache2: Using dwww, fails with internal server error when trying to access /usr/share/doc Bug reassigned from package 'apache2' to 'dwww'. No longer marked as found in versions apache2/2.4.25-1.

Processed: migrate ace to openssl1.1 in buster

Processing commands for cont...@bugs.debian.org: > user pkg-openssl-de...@lists.alioth.debian.org Setting user to pkg-openssl-de...@lists.alioth.debian.org (was sebast...@breakpoint.cc). > clone 828229 -1 Bug #828229 {Done: Sebastian Andrzej Siewior } [src:ace] ace:

Bug#843491: marked as done (witty: Depends on libmysqlclient18 which is no longer available)

Your message dated Sat, 14 Jan 2017 19:38:31 + with message-id and subject line Bug#843491: fixed in witty 3.3.6+dfsg-1.1 has caused the Debian Bug report #843491, regarding witty: Depends on libmysqlclient18 which is no longer available to be marked as

Bug#847760: marked as done (witty: FTBFS on amd64, -fPIC issues)

Your message dated Sat, 14 Jan 2017 19:38:31 + with message-id and subject line Bug#846772: fixed in witty 3.3.6+dfsg-1.1 has caused the Debian Bug report #846772, regarding witty: FTBFS on amd64, -fPIC issues to be marked as done. This means that you

Bug#846772: marked as done (witty: FTBFS: ld: final link failed: Nonrepresentable section on output)

Your message dated Sat, 14 Jan 2017 19:38:31 + with message-id and subject line Bug#846772: fixed in witty 3.3.6+dfsg-1.1 has caused the Debian Bug report #846772, regarding witty: FTBFS: ld: final link failed: Nonrepresentable section on output to be

Processed: Fix version tracking for not acknowledged xfsprogs NMU

Processing commands for cont...@bugs.debian.org: > unarchive 766811 Bug #766811 {Done: Marco d'Itri } [xfslibs-dev] spurious library links Unarchived Bug 766811 > found 822369 4.3.0 Bug #822369 [xfsprogs] xfsprogs: FTBFS: error: redefinition of 'struct fsxattr' Bug #822470

Bug#828229: marked as done (ace: FTBFS with openssl 1.1.0)

Your message dated Sat, 14 Jan 2017 19:04:20 + with message-id and subject line Bug#828229: fixed in ace 6.3.3+dfsg-1.2 has caused the Debian Bug report #828229, regarding ace: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that

Bug#806602: marked as done (ace: FTBFS when built with dpkg-buildpackage -A (override_dh_install fails))

Your message dated Sat, 14 Jan 2017 19:04:20 + with message-id and subject line Bug#806602: fixed in ace 6.3.3+dfsg-1.2 has caused the Debian Bug report #806602, regarding ace: FTBFS when built with dpkg-buildpackage -A (override_dh_install fails) to be

Bug#800198: marked as done (pretzel: Please migrate a supported debhelper compat level)

Your message dated Sat, 14 Jan 2017 18:59:51 + with message-id and subject line Bug#851364: Removed package(s) from unstable has caused the Debian Bug report #800198, regarding pretzel: Please migrate a supported debhelper compat level to be marked as

Bug#821828: marked as done (pretzel: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2))

Your message dated Sat, 14 Jan 2017 18:59:51 + with message-id and subject line Bug#851364: Removed package(s) from unstable has caused the Debian Bug report #821828, regarding pretzel: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8,

Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

On 13.01.2017 20:28, Adrian Bunk wrote: > On Thu, Sep 22, 2016 at 01:19:07PM +0200, Hilmar Preuße wrote: >> Am 25.07.2014 um 11:43 schrieb Stanislav German-Evtushenko: Hi, >>> mod_clamav.c doesn't work and reports "error: Can not stat file (9): Bad >>> file descriptor" on a new file coming to

Bug#851422: openjpeg2: CVE-2016-9572 CVE-2016-9573

Source: openjpeg2 Version: 2.1.0-2 Severity: grave Tags: security upstream patch Justification: user security hole Forwarded: https://github.com/uclouvain/openjpeg/issues/863 Control: fixed -1 2.1.0-2+deb8u2 Hi, the following vulnerabilities were published for openjpeg2. Filling it as RC

Processed: openjpeg2: CVE-2016-9572 CVE-2016-9573

Processing control commands: > fixed -1 2.1.0-2+deb8u2 Bug #851422 [src:openjpeg2] openjpeg2: CVE-2016-9572 CVE-2016-9573 The source 'openjpeg2' and version '2.1.0-2+deb8u2' do not appear to match any binary packages Marked as fixed in versions openjpeg2/2.1.0-2+deb8u2. -- 851422:

Bug#806602: ace: diff for NMU version 6.3.3+dfsg-1.2

control: Tags: patch pending Dear maintainer, I've prepared an NMU for ace (versioned as 6.3.3+dfsg-1.2). The diff is attached to this message. Regards. diff -Nru ace-6.3.3+dfsg/debian/changelog ace-6.3.3+dfsg/debian/changelog --- ace-6.3.3+dfsg/debian/changelog 2016-07-01 07:43:37.0

Bug#851420: openteacher: Requires no longer provided python-qt4 QtWebKit module

Package: openteacher Version: 3.2-2 Severity: grave Tags: upstream sid stretch Justification: renders package unusable The QtWebKit module for python-qt4 was dropped from stretch due to unresolved security issues with the underlying Qt4 QtWebKit module. This package makes use of the Qt4 version:

Bug#851419: cyclograph-qt4: Requires no longer provided python-qt4 QtWebKit module

Package: cyclograph-qt4 Version: 1.7.1-1 Severity: grave Tags: upstream stretch sid Justification: renders package unusable The QtWebKit module for python-qt4 was dropped from stretch due to unresolved security issues with the underlying Qt4 QtWebKit module. This package makes use of the Qt4

Bug#851182: gdb is broken in current sid: "std::string f (void)" doesn't work

Control: severity -1 normal I don't think gdb is broken because the following works: (gdb) p 'f[abi:cxx11]' $1 = {std::__cxx11::string (void)} 0x8f0 (gdb) Downgrading this bug report to 'normal' because it might still be possible that gdb should be updated to work with the

Processed: Re: gdb is broken in current sid: "std::string f (void)" doesn't work

Processing control commands: > severity -1 normal Bug #851182 [gdb] gdb is broken in current sid: "std::string f (void)" doesn't work Severity set to 'normal' from 'grave' -- 851182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851182 Debian Bug Tracking System Contact

Bug#833741: Patch updated for 1.8.3

Updated Bob's patch, which was against 1.8.1, to 1.8.3. This fixes both RC bugs, uploading a NMU hoping it's not too late... diff --git a/debian/changelog b/debian/changelog index e94d50a..965efd3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,17 @@ +pepperflashplugin-nonfree

Bug#845880: marked as done (mysqmail: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Sat, 14 Jan 2017 17:51:39 + with message-id and subject line Bug#845880: fixed in mysqmail 0.4.9-10.2 has caused the Debian Bug report #845880, regarding mysqmail: switch to build depend on the metapackage default-libmysqlclient-dev to

Bug#805952: marked as done (mysqmail: FTBFS when built with dpkg-buildpackage -A (no binary artifacts))

Your message dated Sat, 14 Jan 2017 17:51:38 + with message-id and subject line Bug#805952: fixed in mysqmail 0.4.9-10.2 has caused the Debian Bug report #805952, regarding mysqmail: FTBFS when built with dpkg-buildpackage -A (no binary artifacts) to be

Bug#822006: marked as done (mysqmail: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Sat, 14 Jan 2017 17:51:38 + with message-id and subject line Bug#822006: fixed in mysqmail 0.4.9-10.2 has caused the Debian Bug report #822006, regarding mysqmail: Build arch:all+arch:any but is missing build-{arch,indep} targets to be

Processed: Re: terminal.app: Provides x-terminal-emulator, but doesn't implement the requirements

Processing control commands: > severity -1 important Bug #848097 [terminal.app] terminal.app: Provides x-terminal-emulator, but doesn't implement the requirements Severity set to 'important' from 'serious' -- 848097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848097 Debian Bug Tracking

Bug#848097: terminal.app: Provides x-terminal-emulator, but doesn't implement the requirements

Control: severity -1 important Hi Ben! > Until (or unless) this is implemented, the `Provides:` header and the > update-alternatives logic must be removed. Do you really think that this justifies the severity 'serious' for this bug report? With this severity, the package will be removed from

Processed: Re: nufw: switch to build depend on the metapackage default-libmysqlclient-dev

Processing control commands: > tag -1 pending Bug #845882 [nufw] nufw: switch to build depend on the metapackage default-libmysqlclient-dev Added tag(s) pending. -- 845882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845882 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#817232: postinst trying to disable /etc/init.d/keyboard-setup

Control: tags -1 +moreinfo Control: tags -1 +unreproducible Hi! I cannot reproduce this issue on a standard Debian sid installation with systemd which has been the default in Debian since Jessie now. Can you provide a few more details on how to reproduce this? > System is running with file-rc

Bug#845882: nufw: switch to build depend on the metapackage default-libmysqlclient-dev

Followup-For: Bug #845882 Control: tag -1 pending Hi, I just uploaded a NMU fixing these issues to DELAYED/2, please let me know if I should delay it longer. nufw (2.4.3-3.4) unstable; urgency=medium . * Non-maintainer upload. * Switch Build-Depends to default-libmysqlclient-dev.

Processed: Re: postinst trying to disable /etc/init.d/keyboard-setup

Processing control commands: > tags -1 +moreinfo Bug #817232 [keyboard-configuration] postinst trying to disable /etc/init.d/keyboard-setup Added tag(s) moreinfo. > tags -1 +unreproducible Bug #817232 [keyboard-configuration] postinst trying to disable /etc/init.d/keyboard-setup Added tag(s)

Bug#826548: marked as done (libdbusmenu: FTBFS: touch: cannot touch 'debian/stamp-makefile-check/gtk2': No such file or directory)

Your message dated Sat, 14 Jan 2017 19:20:10 +0200 with message-id <20170114172010.uchgisvrhf2uc7os@localhost> and subject line This was fixed in 0.4.139 has caused the Debian Bug report #826548, regarding libdbusmenu: FTBFS: touch: cannot touch 'debian/stamp-makefile-check/gtk2': No such file or

Bug#830362: marked as done (libapache-mod-log-sql: FTBFS: build-dependency not installable: libmysqlclient15-dev)

Your message dated Sat, 14 Jan 2017 17:20:45 + with message-id and subject line Bug#830362: fixed in libapache-mod-log-sql 1.100-16.3 has caused the Debian Bug report #830362, regarding libapache-mod-log-sql: FTBFS: build-dependency not installable:

Bug#851413: gertty: Uninstallable in Debian Unstable

Package: gertty Severity: serious Version: 1.4.0-1 Tags: sid Dear Maintainer, gertty is uninstallable in Debian Unstable (but not in Debian Testing) since it depends on python-sqlalchemy (< 1.1), but Debian Unstable currently contains python-sqlalchemy at version 1.1.4+ds1-1. This is probably

Bug#851412: FTBFS on mips*, tests fail with SIGSEGV

Am 14.01.2017 um 18:02 schrieb Michael Biebl: > binutils_2.27.90.20170114-1. Building in stretch chroot though was > successful. So my observation is: > > binutils_2.27.90.20170114-1: fails > binutils_2.27.90.20170113-1: fails > binutils_2.27.51.20161220-1: ok > > So it looks like a mips

Processed: Reassign to where the bug was

Processing commands for cont...@bugs.debian.org: > reassign 826548 cdbs 0.4.137 Bug #826548 [src:libdbusmenu] libdbusmenu: FTBFS: touch: cannot touch 'debian/stamp-makefile-check/gtk2': No such file or directory Bug reassigned from package 'src:libdbusmenu' to 'cdbs'. No longer marked as found

Bug#831932: marked as done (icedtea-web: FTBFS with dpkg-buildpackage -A: dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2)

Your message dated Sat, 14 Jan 2017 17:04:54 + with message-id and subject line Bug#831932: fixed in icedtea-web 1.6.2-3.1 has caused the Debian Bug report #831932, regarding icedtea-web: FTBFS with dpkg-buildpackage -A: dpkg-buildpackage: error:

Bug#845867: marked as done (libpreludedb: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Sat, 14 Jan 2017 17:05:21 + with message-id and subject line Bug#845867: fixed in libpreludedb 1.0.0-2.4 has caused the Debian Bug report #845867, regarding libpreludedb: switch to build depend on the metapackage

Bug#845828: marked as done (cctools: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Sat, 14 Jan 2017 17:04:28 + with message-id and subject line Bug#845828: fixed in cctools 4.0-1.1 has caused the Debian Bug report #845828, regarding cctools: switch to build depend on the metapackage default-libmysqlclient-dev to be

Bug#851412: FTBFS on mips*, tests fail with SIGSEGV

Source: systemd Version: 232-10 Severity: serious User: debian-m...@lists.debian.org Usertags: mips-port Hi mips porters, the latest upload of systemd FTBFS on mips* [1]. Contrary to what the buildd status page shows, mips64el is also affected. The build chroot on mips64el did not have a

Bug#799097: mrtg-rrd: Regression after the fix for bug #787608.

On Friday, 13 January 2017 15:24:54 CET Damyan Ivanov wrote: > Perhaps somebody from the perl group (CC-ed) can take a look? See below... > > > --- a/mrtg-rrd.cgi > > > +++ b/mrtg-rrd.cgi > > > @@ -496,7 +496,7 @@ sub common_args($$$) > > > > > > { > > > > > > my ($name, $target, $q)

Bug#847292: proot: diff for NMU version 5.1.0-1.2 (was: proot misses the "binary loader size" fix)

Control: tags 847292 + patch Control: tags 847292 + pending Dear maintainer, I've prepared an NMU for proot (versioned as 5.1.0-1.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. In addition to fixing the RC bug, I included a workaround for

Processed: proot: diff for NMU version 5.1.0-1.2 (was: proot misses the "binary loader size" fix)

Processing control commands: > tags 847292 + patch Bug #847292 [proot] proot misses the "binary loader size" fix Added tag(s) patch. > tags 847292 + pending Bug #847292 [proot] proot misses the "binary loader size" fix Added tag(s) pending. -- 847292:

Bug#849531: [Logwatch-devel] Bug#849531: Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

Hi, Am 2017-01-14 um 16:48 schrieb Mike Tremaine: > >> 0002-Use-pager-on-stdout-output-to-terminal.patch >> >> Use pager less if output is on terminal. This should address the issues >> associated with escape sequences in logs that may mess with your >> terminal. Less seems to be good at

Processed: found 851408 in 2.4.7-4, found 851408 in 1.8.6-4

Processing commands for cont...@bugs.debian.org: > found 851408 2.4.7-4 Bug #851408 [src:groovy] CVE-2016-6814 Marked as found in versions groovy/2.4.7-4. > found 851408 1.8.6-4 Bug #851408 [src:groovy] CVE-2016-6814 Marked as found in versions groovy/1.8.6-4. > thanks Stopping processing here.

Bug#844285: pidgin: steals (warps) mouse cursor (not just focus) when new message comes in [SEC=UNCLASSIFIED]

Control: tags -1 +moreinfo Control: tags -1 +unreproducible Hi! > Like bugs #399786 and #518339, the mouse is warped to an open > conversation window when a new message comes into that conversation. > Typing a password at the time, and your password gets entered into > that conversation. I have

Bug#849122: [pkg-wpa-devel] Bug#849122: Wifi stop working with wpasupplicant 2.6-2

Hi, On 14 Jan 2017 16:16, "marcelomen...@gmail.com" wrote: Hi, I'm having this issue as well. For weeks now, every time I forget about it and do an aptitude upgrade I have to manually downgrade to 2.5-2+v2.4-3+b1 because my dongle USB stop working. I'm afraid that in

Processed: Re: pidgin: steals (warps) mouse cursor (not just focus) when new message comes in [SEC=UNCLASSIFIED]

Processing control commands: > tags -1 +moreinfo Bug #844285 [pidgin] pidgin: steals (warps) mouse cursor (not just focus) when new message comes in [SEC=UNCLASSIFIED] Added tag(s) moreinfo. > tags -1 +unreproducible Bug #844285 [pidgin] pidgin: steals (warps) mouse cursor (not just focus) when

Bug#851347: marked as done (libjson-validator-perl: uses deprecated Mojo::Util::slurp, makes libswagger2-perl FTBFS)

Your message dated Sat, 14 Jan 2017 16:08:42 + with message-id and subject line Bug#851347: fixed in libjson-validator-perl 0.91+dfsg-1 has caused the Debian Bug report #851347, regarding libjson-validator-perl: uses deprecated Mojo::Util::slurp, makes

Bug#848756: marked as done (ibus-table-createdb fails on non-existing $HOME)

Your message dated Sat, 14 Jan 2017 16:07:51 + with message-id and subject line Bug#848756: fixed in ibus-table 1.9.14-3 has caused the Debian Bug report #848756, regarding ibus-table-createdb fails on non-existing $HOME to be marked as done. This means

Bug#848765: marked as done (ibus-table-createdb fails on non-existing $HOME)

Your message dated Sat, 14 Jan 2017 16:07:51 + with message-id and subject line Bug#848756: fixed in ibus-table 1.9.14-3 has caused the Debian Bug report #848756, regarding ibus-table-createdb fails on non-existing $HOME to be marked as done. This means

Bug#848765: marked as done (ibus-table-createdb fails on non-existing $HOME)

Your message dated Sat, 14 Jan 2017 16:07:51 + with message-id and subject line Bug#848765: fixed in ibus-table 1.9.14-3 has caused the Debian Bug report #848765, regarding ibus-table-createdb fails on non-existing $HOME to be marked as done. This means

Bug#848756: marked as done (ibus-table-createdb fails on non-existing $HOME)

Your message dated Sat, 14 Jan 2017 16:07:51 + with message-id and subject line Bug#848765: fixed in ibus-table 1.9.14-3 has caused the Debian Bug report #848765, regarding ibus-table-createdb fails on non-existing $HOME to be marked as done. This means

Processed: Re: rar t - segmentation fault

Processing control commands: > merge 820381 849546 Bug #820381 [rar] rar crashes. Bug #849546 [rar] rar t - segmentation fault Merged 820381 849546 -- 820381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820381 849546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849546 Debian Bug

Bug#849546: rar t - segmentation fault

Control: merge 820381 849546 Hello! This is a duplicate of #820381 [1], merging. Please check for existing bug reports before filing a new one to avoid noise in the bug tracker. Thanks, Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820381 -- .''`. John Paul Adrian

Bug#851408: CVE-2016-6814

Source: groovy Severity: grave Tags: security Hi, please see http://seclists.org/oss-sec/2017/q1/92 Cheers, Moritz

Bug#784619: Creepy: Still some work to do

Hi, I just found time to test Creepy after the last lot of QString changes. The QString import error is no longer there, although there is no guarantee that my changes were correct. Unfortunately now I get: $ creepy -v Traceback (most recent call last): File "/usr/bin/creepy", line 14, in

Processed: found 851162 in 2.7.0~rc2-1, reassign 851351 to nagios-plugins-contrib, reassign 851277 to gnupg

Processing commands for cont...@bugs.debian.org: > found 851162 2.7.0~rc2-1 Bug #851162 [src:h5py] FTBFS: issues with longdouble precision on ppc Marked as found in versions h5py/2.7.0~rc2-1. > reassign 851351 nagios-plugins-contrib 17.20161211 Bug #851351 [nagios-plugins-contib] check_raid:

Bug#813718: Patch in the MRIcron FTBFS bug

Hi Adrian, On Fri, Jan 13, 2017 at 05:29:01PM +0200, Adrian Bunk wrote: > I saw you were just working on the MRIcron package. > > Can you take a look at the patch in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813718#40 > ? Thanks for the ping. I tried to turn the suggested patch

Bug#777814: ceph: ftbfs with GCC-5

On 01/14/2017 04:50 PM, Don Armstrong wrote: > On January 14, 2017 9:31:11 AM CST, John Paul Adrian Glaubitz > wrote: >> Is there a reason why this bug was reopened? > > Hey; it was just wrongly archived by the BTS so it was unarchived by me, but > not > reopened.

  1   2   >