Processed: tagging 822016

Processing commands for cont...@bugs.debian.org: > tags 822016 + pending Bug #822016 [postfix] postfix: Build arch:all+arch:any but is missing build-{arch,indep} targets Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 822016:

Processed: Re: onboard: FTBFS with GCC 6: needed for in-class initialization

Processing commands for cont...@bugs.debian.org: > tags 812033 + pending Bug #812033 [onboard] onboard: FTBFS with GCC 6: needed for in-class initialization Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 812033:

Bug#829701: mediawiki: nōn-DFSG-free files in package

severity 829701 minor block 829701 by 760306 thanks On 07/08/2016 02:34 AM, Thorsten Glaser wrote: > On Fri, 8 Jul 2016, Faidon Liambotis wrote: >> On Wed, Jul 06, 2016 at 12:21:36PM +0200, Thorsten Glaser wrote: >>> Let me quote: >>>You are authorized to use our trademarks subject to this

Processed: Re: Bug#829701: mediawiki: nōn-DFSG-free files in package

Processing commands for cont...@bugs.debian.org: > severity 829701 minor Bug #829701 [mediawiki] mediawiki: nōn-DFSG-free files in package Severity set to 'minor' from 'serious' > block 829701 by 760306 Bug #829701 [mediawiki] mediawiki: nōn-DFSG-free files in package 829701 was not blocked by

Bug#831058: (no subject)

support for 32bit was removed see #816848 as mentioned in the changelog -- victory no need to CC me :-)

Bug#831058: Package 'pepperflashplugin-nonfree' has no installation candidate for 32-bit Debian 8 Jessie

Package: pepperflashplugin-nonfree Version: 1.8.1+deb8u1 Severity: Grave Greetings Bart, Today (7-13-2016) I am just getting a message that the package 'pepperflashplugin-nonfree' has no installation candidate, and it won't install. That only happens on 32-bit OS computers (with Debian 8 fully

Bug#827905: Character U+2028 can yield file corruption when edited in xterm

On 2016-07-13 20:15:49 -0400, Thomas Dickey wrote: > I don't see the behavior which is described, and haven't seen any > suitable justification for marking this as a "grave" issue, rather > than "normal". Keep in mind that this is a rarely used line-break > character. This is not common, but

Bug#811805: gfan: FTBFS with GCC 6: error: reference is ambiguous

Control: tags -1 pending On Tue, 19 Jan 2016 18:08:29 -0800 Martin Michlmayr wrote: > This package fails to build with GCC 6. GCC 6 has not been released > yet, but it's expected that GCC 6 will become the default compiler for > stretch. This was fixed in Gentoo [1]. I have

Processed: Re: gfan: FTBFS with GCC 6: error: reference is ambiguous

Processing control commands: > tags -1 pending Bug #811805 [gfan] gfan: FTBFS with GCC 6: error: reference is ambiguous Added tag(s) pending. -- 811805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#827905: Character U+2028 can yield file corruption when edited in xterm

On Wed, Jul 13, 2016 at 08:23:34PM +0200, Sven Joachim wrote: > On 2016-06-22 13:46 +0200, Vincent Lefevre wrote: > > > Control: reassign -1 xterm 325-1 > > This problem seems to stem from the attempt to fix bug #738794, at least > it is not present in xterm 324 and earlier. > > > Control:

Bug#817446: marked as done (eep24c: Removal of debhelper compat 4)

Your message dated Thu, 14 Jul 2016 00:03:01 + with message-id and subject line Bug#831037: Removed package(s) from unstable has caused the Debian Bug report #817446, regarding eep24c: Removal of debhelper compat 4 to be marked as done. This means that

Bug#729161: marked as done (scilab-scimax: FTBFS on i386, armel, armhf)

Your message dated Thu, 14 Jul 2016 01:58:51 +0200 with message-id and subject line scilab-scimax was removed from Debian in 2014 has caused the Debian Bug report #729161, regarding scilab-scimax: FTBFS on i386, armel, armhf to be marked as done.

Bug#727132: marked as done (scilab-overload: FTBFS on i386, armel and armhf (regression))

Your message dated Thu, 14 Jul 2016 02:00:55 +0200 with message-id <3f8f07e9-7b52-a700-ace5-5f6916c49...@debian.org> and subject line scilab-overload was removed from Debian in 2014 has caused the Debian Bug report #727132, regarding scilab-overload: FTBFS on i386, armel and armhf (regression) to

Bug#604323: marked as done (Preparations for the removal of the KDE3 and Qt3 libraries)

Your message dated Thu, 14 Jul 2016 01:55:52 +0200 with message-id <8391ea70-567d-9071-9681-ce3b21dfe...@debian.org> and subject line score-reading-trainer was removed from Debian in 2011 has caused the Debian Bug report #604323, regarding Preparations for the removal of the KDE3 and Qt3 libraries

Bug#829488: IRC log discussing the issue

On Thu, Jul 14, 2016 at 12:09:47AM +0200, Thomas Goirand wrote: > We just had a discussion about this bug in the #debian-systemd channel, > and I think it may be helpful. Here's the IRC log: [...] To provide a summary of final conclusions these are the changes we'd like to see: For openrc

Bug#811867: marked as done (goldencheetah: FTBFS with GCC 6: no matching function for call to)

Your message dated Wed, 13 Jul 2016 22:53:34 + with message-id and subject line Bug#811867: fixed in goldencheetah 4.0.0~DEV1607-1 has caused the Debian Bug report #811867, regarding goldencheetah: FTBFS with GCC 6: no matching function for call to to be

Bug#827938: marked as done (pandas: FTBFS in testing (test_plot fails))

Your message dated Wed, 13 Jul 2016 22:27:53 + with message-id and subject line Bug#827938: fixed in pandas 0.18.1-1 has caused the Debian Bug report #827938, regarding pandas: FTBFS in testing (test_plot fails) to be marked as done. This means that you

Bug#829488: IRC log discussing the issue

We just had a discussion about this bug in the #debian-systemd channel, and I think it may be helpful. Here's the IRC log: mbiebl_: The bug I was reffering to you during Debconf was: #829488 [zwiebelbot] Debian#829488: dist-upgrading while switching from openrc to file-rc is broken -

Bug#828883: (no subject)

This actually turns out to be a bug in pybuild (dh-python). In zope.interface's d/control file we have: Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), libpython-all-dbg, libpython-all-dev,

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 828883 dh-python Bug #828883 [src:zope.interface] zope.interface: FTBFS: E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) for details Bug reassigned from package 'src:zope.interface' to 'dh-python'. No

Bug#831040: marked as done (mpv: symbol lookup error: mpv: undefined symbol: ass_set_check_readorder)

Your message dated Wed, 13 Jul 2016 22:36:18 +0200 with message-id <20160713203618.ga27...@ramacher.at> and subject line Re: Bug#831040: mpv: symbol lookup error: mpv: undefined symbol: ass_set_check_readorder has caused the Debian Bug report #831040, regarding mpv: symbol lookup error: mpv:

Bug#831040: mpv: symbol lookup error: mpv: undefined symbol: ass_set_check_readorder

Package: mpv Version: 0.18.0-1 Severity: grave Justification: renders package unusable Not sure what happened, but mpv no longer works on my system: servo:~ 0$ mpv mpv: symbol lookup error: mpv: undefined symbol: ass_set_check_readorder servo:~ 127$ I'm assuming some recent update broke this?

Bug#831039: totem crash on startup, can't start it

Package: totem Version: 3.20.1-3 Severity: grave Justification: renders package unusable Dear Maintainer, When I try to open totem, i've got this error in syslog : org.gnome.Shell.desktop[2942]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for

Bug#829410: marked as done (fassets: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

Your message dated Wed, 13 Jul 2016 15:11:07 -0500 with message-id <22406.41051.381714.911...@max.nulle.part> and subject line Manually closing has caused the Debian Bug report #829410, regarding fassets: FTBFS: dh_clean: Please specify the compatibility level in debian/compat to be marked as

Bug#829548: marked as done (fasianoptions: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

Your message dated Wed, 13 Jul 2016 15:02:10 -0500 with message-id <22406.40514.300663.385...@max.nulle.part> and subject line Manually closing has caused the Debian Bug report #829548, regarding fasianoptions: FTBFS: dh_clean: Please specify the compatibility level in debian/compat to be marked

Bug#831036: nomad: FTBFS: client/fingerprint/cpu.go:25: undefined: cpu.CPUInfo

Source: nomad Version: 0.3.2+dfsg-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, nomad fails to build from source in unstable/amd64: [..]

Processed: found 831034 in 8:6.8.9.9-5

Processing commands for cont...@bugs.debian.org: > found 831034 8:6.8.9.9-5 Bug #831034 [src:imagemagick] imagemagick: CVE-2016-5841 CVE-2016-5842 Marked as found in versions imagemagick/8:6.8.9.9-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 831034:

Bug#831034: imagemagick: CVE-2016-5841 CVE-2016-5842

Source: imagemagick Version: 8:6.8.9.9-7.2 Severity: grave Tags: security upstream Justification: user security hole the following vulnerabilities were published for imagemagick. CVE-2016-5841[0] and CVE-2016-5842[1]. If you fix the vulnerabilities please also make sure to include the CVE

Bug#831028: cfengine3: FTBFS: FAIL: rlist_test [..] Segmentation fault

Source: cfengine3 Version: 3.6.2-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, cfengine3 fails to build from source in unstable/amd64:

Bug#831019: gnucash-docs: accesses the internet during build

Source: gnucash-docs Version: 2.6.13-1 Severity: serious Justification: Policy 4.9 User: la...@debian.org Usertags: network-access Dear Maintainer, Whilst gnucash-docs builds successfully on unstable/amd64, according to Debian Policy 4.9 packages may not attempt network access during a build.

Bug#827905: Character U+2028 can yield file corruption when edited in xterm

On 2016-06-22 13:46 +0200, Vincent Lefevre wrote: > Control: reassign -1 xterm 325-1 This problem seems to stem from the attempt to fix bug #738794, at least it is not present in xterm 324 and earlier. > Control: retitle -1 Character U+2028 can yield file corruption when edited in > xterm > >

Bug#831013: lua-cqueues: FTBFS on powerpc/ppc64: sys/event.h: No such file or directory

Source: lua-cqueues Version: 20160316-3 Severity: serious Justification: fails to build from source The powerpc and ppc64 builds of lua-cqueues have been failing: libtool --silent --tag=CC --mode=compile cc -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic

Processed: Re: Bug#831004: procps: FTBFS on hurd-i386: mv: cannot stat 'kill'

Processing control commands: > severity -1 important Bug #831004 [src:procps] procps: FTBFS on hurd-i386: mv: cannot stat 'kill' Severity set to 'important' from 'serious' -- 831004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831004 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#831004: procps: FTBFS on hurd-i386: mv: cannot stat 'kill'

Control: severity -1 important On 2016-07-13 13:12 -0400, Aaron M. Ucko wrote: > Source: procps > Version: 2:3.3.12-2 > Severity: serious > Justification: fails to build from source (but built successfully in the past) Build failures on non-release architectures are not RC, as you should know.

Bug#822048: linux86: Build arch:all+arch:any but is missing build-{arch,indep} targets

Control: tags -1 + patch On 2016-04-20 22:58 +0200, ni...@thykier.net wrote: > Package: linux86 > Severity: normal > Usertags: arch-all-and-any-missing-targets > > Hi, > > The package linux86 builds an architecture independent *and* an > architecture dependent package, but does not have the (now

Processed: Re: Bug#822048: linux86: Build arch:all+arch:any but is missing build-{arch,indep} targets

Processing control commands: > tags -1 + patch Bug #822048 [linux86] linux86: Build arch:all+arch:any but is missing build-{arch,indep} targets Added tag(s) patch. -- 822048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822048 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#831004: procps: FTBFS on hurd-i386: mv: cannot stat 'kill'

Source: procps Version: 2:3.3.12-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Me again. ;-) The hurd-i386 build of procps gets farther now (thanks!) but still fails: mv /«PKGBUILDDIR»/debian/tmp/bin/kill /«PKGBUILDDIR»/debian/tmp/bbin/

Bug#829150: marked as done (minetest-data: fails to upgrade from 'jessie' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/minetest.svg)

Your message dated Wed, 13 Jul 2016 17:00:04 + with message-id and subject line Bug#829150: fixed in minetest 0.4.14+repack-5 has caused the Debian Bug report #829150, regarding minetest-data: fails to upgrade from 'jessie' - trying to overwrite

Bug#829668: marked as done (libparse-debianchangelog-perl: FTBFS: Failed test 'Output of dpkg_str equal to output of dpkg-parsechangelog')

Your message dated Wed, 13 Jul 2016 16:59:50 + with message-id and subject line Bug#829668: fixed in libparse-debianchangelog-perl 1.2.0-10 has caused the Debian Bug report #829668, regarding libparse-debianchangelog-perl: FTBFS: Failed test 'Output of

Bug#812026: marked as done (zoneminder: FTBFS with GCC 6: flexible array member...)

Your message dated Wed, 13 Jul 2016 17:02:16 + with message-id and subject line Bug#812026: fixed in zoneminder 1.30.0~rc2+dfsg-1 has caused the Debian Bug report #812026, regarding zoneminder: FTBFS with GCC 6: flexible array member... to be marked as

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Am 13.07.2016 um 18:28 schrieb Michael Biebl: > Am 13.07.2016 um 18:24 schrieb Michael Biebl: >> Turns out the problem is in init-system-helpers. >> In 1.35, invoke-rc.d was changed to use systemctl is-enabled. >> This doesn't work for sysv init scripts with v215. >> As init-system-helpers is

Bug#812139: marked as done (libcrypto++: FTBFS with GCC 6: narrowing conversion)

Your message dated Wed, 13 Jul 2016 18:32:45 +0200 with message-id

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Am 13.07.2016 um 18:24 schrieb Michael Biebl: > Turns out the problem is in init-system-helpers. > In 1.35, invoke-rc.d was changed to use systemctl is-enabled. > This doesn't work for sysv init scripts with v215. > As init-system-helpers is unpacked before systemd has been updated (and >

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Control: reassign -1 init-system-helpers Control: found -1 1.35 On Wed, 13 Jul 2016 16:15:56 +0200 Michael Biebl wrote: > Package: rpcbind > Version: 0.2.3-0.5 > Severity: serious > > During a dist-upgrade from jessie to stretch, the rpcbind package failed > to upgrade

Processed: Re: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Processing control commands: > reassign -1 init-system-helpers Bug #830982 [rpcbind] dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start Bug reassigned from package 'rpcbind' to 'init-system-helpers'. No longer marked as found in versions rpcbind/0.2.3-0.5. Ignoring request

Bug#830995: python-apt: FTBFS: Test failures

Source: python-apt Version: 1.1.0~beta3 Severity: serious >From my pbuilder build log: ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/python-apt-1.1.0~beta3' set -e; for python in python2.7 python3.5 ; do \ $python tests/test_all.py -q || [ "linux" = "hurd" ];

Bug#829442: marked as done (libconfig-model-itself-perl: FTBFS: Failed 1/12 test programs. 0/108 subtests failed.)

Your message dated Wed, 13 Jul 2016 15:59:24 + with message-id and subject line Bug#829442: fixed in libconfig-model-lcdproc-perl 2.048-1 has caused the Debian Bug report #829442, regarding libconfig-model-itself-perl: FTBFS: Failed 1/12 test programs.

Bug#830712: marked as done (python-enum34: add Breaks: python-enum)

Your message dated Wed, 13 Jul 2016 15:50:08 + with message-id and subject line Bug#830712: fixed in enum34 1.1.6-1 has caused the Debian Bug report #830712, regarding python-enum34: add Breaks: python-enum to be marked as done. This means that you claim

Bug#830990: baloo: Build-Depends on cruft package libakonadi-dev

¡Hola Daniel! El 2016-07-13 a las 08:10 -0700, Daniel Schepler escribió: Source: baloo Version: 4:4.14.2-2 Severity: serious The baloo source package Build-Depends on libakonadi-dev, which is only available in sid from older versions of src:akonadi than the latest one. Ups, I forgot to

Processed (with 3 errors): gcc-6 FTBFS bugs are serious

Processing commands for cont...@bugs.debian.org: > severity 823419 serious Bug #823419 [src:openjade] openjade: Broken if rebuilt using g++-6 and glibc 2.23 Severity set to 'serious' from 'important' > severity 823447 serious Bug #823447 [src:gtest] gtest: FTBFS with g++-6 and glibc 2.23: Test

Processed (with 1 error): forcibly merging 830793 830944

Processing commands for cont...@bugs.debian.org: > forcemerge 830793 830944 Bug #830793 [ruby-validate-email] en.yml should be installed in /usr/share Unable to merge bugs because: package of #830944 is 'ruby-validate-url' not 'ruby-validate-email' Failed to forcibly merge 830793: Did not alter

Bug#830994: kdepimlibs: Build-Depends on cruft package libakonadi-dev

Source: kdepimlibs Version: 4:4.14.10-4 Severity: serious The kdepimlibs source package Build-Depends on libakonadi-dev, which is only available in sid from versions of src:akonadi older than the latest one. -- Daniel Schepler

Bug#830993: gpsd: FTBFS with gcc-6

Source: gpsd Version: 3.16-2 Severity: serious >From my pbuilder build log, using a chroot preferring gcc-defaults from experimental: ... g++ -o qt-clock_gettime.os -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wextra -Wall -Wno-uninitialized

Bug#827938: About to create an NMU

Cheers Ole, sorry for a delay, I will look into updating package for 0.18.1 release and will take care about this issue On Wed, 13 Jul 2016, Ole Streicher wrote: > Hi Yaroslav, > since that bug will cause several removals from testing in a few days, I > will upload an NMU by the end of the

Processed: Re: Bug#821995: ispell-czech: Build arch:all+arch:any but is missing build-{arch,indep} targets

Processing control commands: > tag -1 + pending Bug #821995 [ispell-czech] ispell-czech: Build arch:all+arch:any but is missing build-{arch,indep} targets Added tag(s) pending. -- 821995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821995 Debian Bug Tracking System Contact

Bug#821995: ispell-czech: Build arch:all+arch:any but is missing build-{arch,indep} targets

Control: tag -1 + pending On Mon, Jul 11, 2016 at 04:11:43PM +0200, Agustin Martin wrote: > > On Wed, Apr 20, 2016 at 10:54:45PM +0200, ni...@thykier.net wrote: > > Package: ispell-czech > > Severity: normal > > Usertags: arch-all-and-any-missing-targets > Proposed patch attached. It is

Bug#830990: baloo: Build-Depends on cruft package libakonadi-dev

Source: baloo Version: 4:4.14.2-2 Severity: serious The baloo source package Build-Depends on libakonadi-dev, which is only available in sid from older versions of src:akonadi than the latest one. -- Daniel Schepler

Bug#830988: Fails to reinstall grub in efi system

package: grub2-common severity: grave Version: 2.02~beta2-22+deb8u1 After installing debian 8.5 jessie, I installed Windows. It removed grub from mbr, so booted into rescue mode using the same cd 1 image, but grub-install failed with this error. grub-install: error

Processed: libjs-handlebars: missing source

Processing control commands: > clone -1 -2 Bug #830986 [src:libjs-handlebars] libjs-handlebars: missing source Bug 830986 cloned as bug 830987 > reassign -2 ruby-handlebars-assets Bug #830987 [src:libjs-handlebars] libjs-handlebars: missing source Bug reassigned from package

Bug#830986: libjs-handlebars: missing source

Source: libjs-handlebars Version: 1.3.0-1 Severity: serious Control: clone -1 -2 Control: reassign -2 ruby-handlebars-assets Control: found -2 2:0.23.0-2 Control: block -2 by -1 Hi, I briefly looked into the package due to the discussion on -devel@ and the ctte bug.  The source for the

Bug#830984: ball: FTBFS: test suite errors

Source: ball Version: 1.4.3~beta1-1 Severity: serious Your package failed to build on most architectures with test suite errors. Build logs at https://buildd.debian.org/status/package.php?p=ball Emilio

Bug#828945: [Pkg-swan-devel] Bug#828945: strongswan: FTBFS in testing (configure fails)

Hi. Version 5.4.0-3 has just reached testing, my autobuilder has tried to build it, and it failed again. May I know why is this marked as "unreproducible" and "moreinfo"? In case it helps, here is a short summary: This package relies on systemd being present in the system to be built. systemd

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Package: rpcbind Version: 0.2.3-0.5 Severity: serious During a dist-upgrade from jessie to stretch, the rpcbind package failed to upgrade cleanly: dpkg: error processing package rpcbind (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency

Processed: Bug#830712 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 830712 pending Bug #830712 [python-enum34] python-enum34: add Breaks: python-enum Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 830712:

Bug#830712: marked as pending

tag 830712 pending thanks Hello, Bug #830712 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/enum34.git;a=commitdiff;h=f290d36 --- commit

Bug#829237: marked as done (systemd-docker: FTBFS: main.go:19:2: cannot find package "github.com/docker/docker/pkg/mflag")

Your message dated Wed, 13 Jul 2016 13:51:38 + with message-id and subject line Bug#829237: fixed in systemd-docker 0.2.1+dfsg-2 has caused the Debian Bug report #829237, regarding systemd-docker: FTBFS: main.go:19:2: cannot find package

Bug#829488: openrc: upgrade jessie -> stretch fails: util-linux.postinst: update-rc.d: not found

Control: reassign -1 openrc Control: retitle -1 dist-upgrading while switching from openrc to file-rc is broken Hello Adam Borowski. Please remember to (B)CC the receiving package when reassigning bug reports to notify the receiver. On Sun, Jul 03, 2016 at 11:19:40PM +0200, Adam Borowski

Processed: Re: Bug#829488: openrc: upgrade jessie -> stretch fails: util-linux.postinst: update-rc.d: not found

Processing control commands: > reassign -1 openrc Bug #829488 [util-linux] util-linux should depend on init-system-helpers Bug reassigned from package 'util-linux' to 'openrc'. Ignoring request to alter found versions of bug #829488 to the same values previously set Ignoring request to alter

Bug#830762: kmail: empty folders list

On Wed, 13 Jul 2016, Maximiliano Curia wrote: > You haven't upgraded kmail, so it seems that you haven't a fully upgraded > kdepim. Make sure that you have the version 4:16.04.2-2 installed. Ah okay… … … damn: Dependency installability problem for [159]kdepim on x32:

Bug#830511: marked as done (kdepim4: kdepim4 build-depends on NBS libkgapi-dev)

Your message dated Wed, 13 Jul 2016 12:34:32 + with message-id and subject line Bug#830511: fixed in kdepim4 4:4.14.10-6 has caused the Debian Bug report #830511, regarding kdepim4: kdepim4 build-depends on NBS libkgapi-dev to be marked as done. This

Bug#811606: FTBFS with GCC 6: multiple errors

Hi László, Thanks for the response. On 09:13 Wed 13 Jul , László Böszörményi wrote: > Hi Apollon, > > On Thu, Jun 30, 2016 at 6:11 PM, Apollon Oikonomopoulos > wrote: > > I think MongoDB 2.4 in unstable is already dead enough[1] that we should > > drop it before it gets

Bug#817651: marked as done (regionset: Removal of debhelper compat 4)

Your message dated Wed, 13 Jul 2016 12:22:23 + with message-id and subject line Bug#817651: fixed in regionset 0.1-3.1 has caused the Debian Bug report #817651, regarding regionset: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#830763: akonadiconsole: crashes hard

¡Hola Thorsten! El 2016-07-11 a las 10:46 +0200, Thorsten Glaser escribió: Package: akonadiconsole Version: 4:4.14.10-2 Severity: serious Justification: makes the package unusable While trying to debug #830762 (to see if the new messages are in fact downloaded) I tried to start

Bug#830762: kmail: empty folders list

¡Hola Thorsten! El 2016-07-11 a las 10:43 +0200, Thorsten Glaser escribió: Package: kmail Version: 4:4.14.10-2 Severity: serious Justification: makes the package unusable After the recent KDEPIM-related updates (including involving a wallet migration, which seems to have worked, and a

Bug#817651: regionset: Removal of debhelper compat 4

Control: tags -1 pending Hi, On Wed, 09 Mar 2016 21:55:31 +0100 ni...@thykier.net wrote: > Source: regionset > Severity: important > Usertags: compat-4-removal >  > Hi, >  > The package regionset uses debhelper with a compat level of 4, > which is deprecated and scheduled for removal. I have

Processed: Bug#817651: regionset: Removal of debhelper compat 4

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

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

Your message dated Wed, 13 Jul 2016 11:48:34 + with message-id and subject line Bug#796585: fixed in aoetools 36-1.1 has caused the Debian Bug report #796585, regarding aoetools: Has init script in runlevel S but no matching service file to be marked as

Bug#830733: marked as done (procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000)

Your message dated Wed, 13 Jul 2016 11:37:11 + with message-id and subject line Bug#830733: fixed in procps 2:3.3.12-2 has caused the Debian Bug report #830733, regarding procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.00 to be marked as

Bug#830772: marked as done (procps: FTBFS on i386: strtod_nol_or_err("123") != 123.000000)

Your message dated Wed, 13 Jul 2016 11:37:11 + with message-id and subject line Bug#830733: fixed in procps 2:3.3.12-2 has caused the Debian Bug report #830733, regarding procps: FTBFS on i386: strtod_nol_or_err("123") != 123.00 to be marked as done.

Bug#796638: marked as done (ocfs2-tools: Has init script in runlevel S but no matching service file)

Your message dated Wed, 13 Jul 2016 10:27:06 + with message-id and subject line Bug#796638: fixed in ocfs2-tools 1.8.4-2 has caused the Debian Bug report #796638, regarding ocfs2-tools: Has init script in runlevel S but no matching service file to be

Bug#830500: marked as done (redis: FTBFS: Test failure)

Your message dated Wed, 13 Jul 2016 10:28:24 + with message-id and subject line Bug#830500: fixed in redis 2:3.2.1-2 has caused the Debian Bug report #830500, regarding redis: FTBFS: Test failure to be marked as done. This means that you claim that the

Bug#827938: About to create an NMU

Hi Yaroslav, since that bug will cause several removals from testing in a few days, I will upload an NMU by the end of the week. Please respond of you have another proposal. Best regards Ole

Bug#825618: marked as done (gnustep-dl2-postgresql-adaptor: fails to upgrade from wheezy to jessie to stretch: cannot switch directory to symlink)

Your message dated Wed, 13 Jul 2016 10:20:27 + with message-id and subject line Bug#825618: fixed in gnustep-dl2 0.12.0-15 has caused the Debian Bug report #825618, regarding gnustep-dl2-postgresql-adaptor: fails to upgrade from wheezy to jessie to

Bug#830959: marked as done (jersey1: FTBFS: Could not resolve dependencies for project com.sun.jersey.contribs:jersey-guice:jar:1.19.1)

Your message dated Wed, 13 Jul 2016 10:20:45 + with message-id and subject line Bug#830959: fixed in jersey1 1.19.1-2 has caused the Debian Bug report #830959, regarding jersey1: FTBFS: Could not resolve dependencies for project

Bug#830960: marked as done (python-cryptography: unmet dependencies)

Your message dated Wed, 13 Jul 2016 10:18:07 + with message-id and subject line Re: Bug#830960: python-cryptography: unmet dependencies has caused the Debian Bug report #830960, regarding python-cryptography: unmet

Bug#830960: python-cryptography: unmet dependencies

Package: python-cryptography Version: 1.1.1-1~bpo8+1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64

Bug#830959: jersey1: FTBFS: Could not resolve dependencies for project com.sun.jersey.contribs:jersey-guice:jar:1.19.1

Source: jersey1 Version: 1.19.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, jersey1 fails to build from source in unstable/amd64: [..]

Bug#830955: keepalived: Segfault - keepalived doesn't work without CONFIG_IP_VS

Package: keepalived Version: 1.2.20-1 Severity: critical Justification: causes serious data loss Dear Maintainer, Could you please update the keepalived to fix this issue? https://github.com/acassen/keepalived/issues/313 -- System Information: Debian Release: stretch/sid APT prefers

Bug#828819: [Ticket#990115419] Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1

Hi Together, we updated the microcode that comes with the BIOS. Here you can download the updated BIOS: [1]http://www.linux-onlineshop.de/forum/index.php?page=Thread=321 -- Mit freundlichen Grüßen / Kind regards Tobias Fischer TUXEDO Computers.com -- TUXEDO Computers GmbH ~ Zeppelinstr. 3 ~

Bug#815363: ola: build-depends on libslp-dev

Package: ola Version: 0.9.8-1 Followup-For: Bug #815363 According to OLA's NEWS file the dependency on SLP was removed in version 0.9.4: "Remove the SLP code since it's no longer required for E1.33.". I tried building the ola package after removing the depency on libslp-dev and it seems to build

Processed: reassign 828712 to alljoyn-services-1509, fixed 828712 in 15.09-2

Processing commands for cont...@bugs.debian.org: > reassign 828712 alljoyn-services-1509 15.09-1 Bug #828712 {Done: Thorsten Alteholz } [alljoyn-services-1504,alljoyn-services-1509] alljoyn-services-1509 and alljoyn-services-1504: error when trying to install together Bug

Processed: Re: redis: FTBFS: Test failure

Processing commands for cont...@bugs.debian.org: > forwarded 830500 https://github.com/antirez/redis/issues/2789 Bug #830500 [src:redis] redis: FTBFS: Test failure Set Bug forwarded-to-address to 'https://github.com/antirez/redis/issues/2789'. > tags 830500 + pending Bug #830500 [src:redis]

Bug#830500: redis: FTBFS: Test failure

forwarded 830500 https://github.com/antirez/redis/issues/2789 tags 830500 + pending thanks Ah, this was filed upstream :) https://github.com/antirez/redis/issues/2789 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#830939: marked as done (knot-resolver: FTBFS: missing files: usr/lib/knot-resolver/tinyweb/*)

Your message dated Wed, 13 Jul 2016 07:48:31 + with message-id and subject line Bug#830939: fixed in knot-resolver 1.1.0~git2016070600-2 has caused the Debian Bug report #830939, regarding knot-resolver: FTBFS: missing files:

Bug#811606: FTBFS with GCC 6: multiple errors

Hi Apollon, On Thu, Jun 30, 2016 at 6:11 PM, Apollon Oikonomopoulos wrote: > I think MongoDB 2.4 in unstable is already dead enough[1] that we should > drop it before it gets a chance to build against GCC 6 in a couple of > months. The attached patch fixes the FTBFS for the

Bug#830500: redis: FTBFS: Test failure

> Hmm, I wonder if this might be a failure that only occurs randomly, > based on timing or something like that. Could you try the attached patch? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git

Processed: severity of 830944 is serious

Processing commands for cont...@bugs.debian.org: > severity 830944 serious Bug #830944 [ruby-validate-url] ruby-validate-url: /usr/lib/ruby/vendor_ruby/locale/en.yml also in ruby-validate-email Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you

Bug#830948: plasma-discover-private and plasma-discover-common: error when trying to install together

Package: plasma-discover-common,plasma-discover-private Version: plasma-discover-common'5.7.0-2@all, plasma-discover-common/5.6.5-1 Version: plasma-discover-private/5.6.5-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2016-07-13 Architecture: amd64 Distribution:

Processed: Re: sensors-applet: FTBFS with gnome-common 3.18: cannot open gnome-doc-utils.make

Processing commands for cont...@bugs.debian.org: > severity 803059 serious Bug #803059 [src:sensors-applet] sensors-applet: FTBFS with gnome-common 3.18: cannot open gnome-doc-utils.make Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need