Processed: severity of 816101 is serious, tagging 816101

Processing commands for cont...@bugs.debian.org: > severity 816101 serious Bug #816101 [src:petsc] FTBFS on mipsel - broken openmpi breaks petsc build Severity set to 'serious' from 'important' > tags 816101 + sid stretch Bug #816101 [src:petsc] FTBFS on mipsel - broken openmpi breaks petsc build

Bug#740111: Fixed in unstable

On Tue, 25 Feb 2014 23:26:48 +0100 Yann Dirson wrote: > fixed 740111 1.4.2-1 > thanks >  >  Can the bug be closed then? (marking it fixed won't do that) If so, just reply to 740111-d...@bugs.debian.org ;-) -- tobi

Bug#821910: marked as done (gnupg1: fails to upgrade from 'sid' - trying to overwrite /usr/share/info/gnupg1.info.gz)

Your message dated Fri, 22 Apr 2016 04:24:05 + with message-id and subject line Bug#821910: fixed in gnupg 1.4.20-6+exp2 has caused the Debian Bug report #821910, regarding gnupg1: fails to upgrade from 'sid' - trying to overwrite

Bug#821910: marked as pending

tag 821910 pending thanks Hello, Bug #821910 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-gnupg/gnupg.git;a=commitdiff;h=165850d --- commit

Processed: Bug#821910 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 821910 pending Bug #821910 [gnupg1] gnupg1: fails to upgrade from 'sid' - trying to overwrite /usr/share/info/gnupg1.info.gz Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 821910:

Bug#821942: marked as done (libnet-dns-sec-perl: Errors were encountered while processing: libnet-dns-sec-perl)

Your message dated Fri, 22 Apr 2016 00:19:05 + with message-id and subject line Bug#820332: fixed in libnet-dns-perl 1.05-2 has caused the Debian Bug report #820332, regarding libnet-dns-sec-perl: Errors were encountered while processing:

Bug#820332: marked as done (libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts)

Your message dated Fri, 22 Apr 2016 00:19:05 + with message-id and subject line Bug#820332: fixed in libnet-dns-perl 1.05-2 has caused the Debian Bug report #820332, regarding libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts to be

Processed: reassign 821942 to libnet-dns-perl,libnet-dns-sec-perl, forcibly merging 820332 821942

Processing commands for cont...@bugs.debian.org: > reassign 821942 libnet-dns-perl,libnet-dns-sec-perl Bug #821942 [libnet-dns-sec-perl] libnet-dns-sec-perl: Errors were encountered while processing: libnet-dns-sec-perl Bug reassigned from package 'libnet-dns-sec-perl' to

Bug#822201: ca-certificates-java: postinst and trigger should fail if no known jvm is found

Package: ca-certificates-java Version: 20160321 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, the setup_path routine in ca-certificates-java.postinst does not take into account that it might not find a known jre. In that case $jvm and $JAVA_HOME will be invalid. This

Processed: Pending fixes for bugs in the libnet-dns-perl package

Processing commands for cont...@bugs.debian.org: > tag 820332 + pending Bug #820332 [libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts Ignoring request to alter tags of bug #820332 to the same tags previously set > thanks Stopping

Bug#820332: Pending fixes for bugs in the libnet-dns-perl package

tag 820332 + pending thanks Some bugs in the libnet-dns-perl package are closed in revision e99ccedccbc29784b9fdd4096c039373cb5c4dbd in branch 'master' by Axel Beckert The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-dns-perl.git/commit/?id=e99cced Commit

Processed: tagging 820332

Processing commands for cont...@bugs.debian.org: > tags 820332 + pending Bug #820332 [libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#822194: libdebug: FTBFS: No rule to make target 'libdebug.so.0', needed by 'with-depends'

Source: libdebug Version: 0.5.1-1 Severity: serious Justification: fails to build from source libdebug FTBFS when built in parallel: | make with-depends | make[3]: Entering directory '/«PKGBUILDDIR»/src' | gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wall -W

Processed: Re: eagle: cannot be rebuilt against libssl1.0.2

Processing control commands: > found -1 7.5.0-1 Bug #804531 {Done: Scott Howard } [eagle] eagle: cannot be rebuilt against libssl1.0.2 Marked as found in versions eagle/7.5.0-1; no longer marked as fixed in versions eagle/7.5.0-1 and reopened. -- 804531:

Bug#804531: eagle: cannot be rebuilt against libssl1.0.2

Followup-For: Bug #804531 Control: found -1 7.5.0-1 eagle still (Build-)Depends: libssl1.0.0 and the binary is still linked against libssl.so.1.0.0 Since the only API/ABI difference between libssl1.0.0 and libssl1.0.2 is the removal of some symbols, you could try the following: * switch

Processed: Re: Bug#783876: Seriously, these binaries should be stripped by default

Processing control commands: > severity -1 important Bug #783876 [gcc-5] gcc-5: consider stripping lto1 / cc1 / cc1plus Severity set to 'important' from 'serious' -- 783876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783876 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#783876: Seriously, these binaries should be stripped by default

Control: severity -1 important On 21.04.2016 19:28, Steve McIntyre wrote: Control: severity -1 serious Justification: wasting many megabytes of space and download sorry, I don't see this as a justification. We're shipping broken toolchain packages please stop trolling. Nothing is broken.

Bug#822182: dvbtune: FTBFS: error: unknown type name 'uint16_t'

Package: dvbtune Version: 0.5.ds-1 Severity: serious This package fails to build in unstable: > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux ... > gcc -Wall -I /usr/include/libxml2 -I ../DVB/include -DVERSION=\"0.5\" > -DNEWSTRUCTdvbtune.c tune.o -o dvbtune > In file

Bug#783876: Seriously, these binaries should be stripped by default

On 21.04.2016 20:08, Ondřej Surý wrote: From reading the bug comments I can see both sides of the argument, so why we don't ship just two versions that would be exchangeable - one with symbols and one (default) stripped? The stripped one would be installed by default and if you need to produce

Bug#822178: cargo: FTBFS: error: Cannot declare a non-inline module inside a block unless it has a path attribute

Package: cargo Version: 0.8.0-2 Severity: serious This package fails to build in unstable: > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux ... > /libgit2-0_3_3.rlib --extern toml=/<>/deps/libtoml-0_1_25.rlib > --extern curl=/<>/deps/libcurl-0_2_14.rlib --extern >

Processed: same issue, merge

Processing commands for cont...@bugs.debian.org: > reassign 818331 src:aac-tactics Bug #818331 [aac-tactics] aac-tactics: FTBFS: constructor vcons (in type vT) expects 2 arguments Bug reassigned from package 'aac-tactics' to 'src:aac-tactics'. No longer marked as found in versions 0.4-5.

Processed (with 1 error): same issue, merge

Processing commands for cont...@bugs.debian.org: > forcemerge 813459 818331 Bug #813459 [src:aac-tactics] aac-tactics: FTBFS: Error: The constructor vcons (in type vT) expects 2 arguments. Unable to merge bugs because: package of #818331 is 'aac-tactics' not 'src:aac-tactics' Failed to forcibly

Bug#821233: perlbal: FTBFS: Unable to start socket: Address already in use

Control: reopen -1 Control: severity -1 important On Sun, Apr 17, 2016 at 12:41:15AM +0200, gregor herrmann wrote: > Control: tag -1 + unreproducible > > On Sat, 16 Apr 2016 23:23:50 +0100, Chris Lamb wrote: > > > perlbal fails to build from source in unstable/amd64: > > > Didn't get 200 OK:

Processed: Re: Bug#821233: perlbal: FTBFS: Unable to start socket: Address already in use

Processing control commands: > reopen -1 Bug #821233 {Done: Chris Lamb } [src:perlbal] perlbal: FTBFS: Unable to start socket: Address already in use Bug reopened Ignoring request to alter fixed versions of bug #821233 to the same values previously set > severity -1 important

Bug#820845: marked as done (openstack-dashboard-apache: modifies conffiles (policy 10.7.3): /etc/apache2/sites-available/openstack-dashboard{, -ssl}.conf)

Your message dated Thu, 21 Apr 2016 19:34:54 + with message-id and subject line Bug#820845: fixed in horizon 2:9.0.0-2 has caused the Debian Bug report #820845, regarding openstack-dashboard-apache: modifies conffiles (policy 10.7.3):

Bug#821868: marked as done (openstack-dashboard: causes trigger loop)

Your message dated Thu, 21 Apr 2016 19:34:54 + with message-id and subject line Bug#821868: fixed in horizon 2:9.0.0-2 has caused the Debian Bug report #821868, regarding openstack-dashboard: causes trigger loop to be marked as done. This means that you

Processed: untag #754838

Processing commands for cont...@bugs.debian.org: > tags 754838 - pending Bug #754838 [grr.app] grr.app: Cannot add new feeds Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 754838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754838

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

On Thu, Apr 21, 2016 at 9:13 PM, Tobias Frost wrote: > Thanks Muammar, > :) > I have filed the RM. > > Kudos for maintaining smc.. Thanks for having filled the RM. Have a nice day. -- Muammar El Khatib. Linux user: 403107. GPG Key = 71246E4A. http://muammar.me |

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

Thanks Muammar, I have filed the RM. Kudos for maintaining smc.. --  tobi

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

Hi Tobias, On Thu, Apr 21, 2016 at 7:58 AM, Tobias Frost wrote: > Sorry, I overread the "Yes."... Don't worry. > As the rest of it confuses me: Does that mean you are OK with filing an > RM at this point of time? Yes, I am ok with filling an RM for SMC. Upstream is not

Bug#819782: marked as done (libdatabase-dump-perl: FTBFS: t/dumptruck.t failure)

Your message dated Thu, 21 Apr 2016 21:47:38 +0300 with message-id <20160421184738.GA11716@estella.local.invalid> and subject line Re: Bug#819782: libdatabase-dump-perl: FTBFS: t/dumptruck.t failure has caused the Debian Bug report #819782, regarding libdatabase-dump-perl: FTBFS: t/dumptruck.t

Bug#822118: RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages

Hi As I said to Andreas a few weeks ago, the FW4SPL team is currently working on a new version of the framework using VTK6, ITK4, and the new Boost version. We should be able to remove the dependences to the old versions of these packages over the next week. About libpng, I'm not sure to

Bug#783876: Seriously, these binaries should be stripped by default

>From reading the bug comments I can see both sides of the argument, so why we don't ship just two versions that would be exchangeable - one with symbols and one (default) stripped? The stripped one would be installed by default and if you need to produce trace, you would install the second

Bug#821894: marked as done (cluster-glue: copyright file missing after upgrade (policy 12.5))

Your message dated Thu, 21 Apr 2016 17:49:05 + with message-id and subject line Bug#821894: fixed in cluster-glue 1.0.12-5 has caused the Debian Bug report #821894, regarding cluster-glue: copyright file missing after upgrade (policy 12.5) to be marked as

Bug#821154: chromium: crashes on video

Control: tags -1 + patch On 2016-04-20 21:49:23, Gedalya wrote: > On 04/20/2016 08:13 PM, Gedalya wrote: > > Going to try this patch now. > > Built with pbuilder against sid. /usr/lib/chromium/chromium is now ~2MB > smaller. > New packages pulled in from sid: libavcodec57 libavformat57

Processed: Re: Bug#821154: chromium: crashes on video

Processing control commands: > tags -1 + patch Bug #821154 [chromium] chromium: crashes on video Added tag(s) patch. -- 821154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Seriously, these binaries should be stripped by default

Processing control commands: > severity -1 serious Bug #783876 [gcc-5] gcc-5: consider stripping lto1 / cc1 / cc1plus Severity set to 'serious' from 'wishlist' -- 783876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783876 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU

Hi Lars, On Wed, Apr 20, 2016 at 08:20:56AM +0200, Salvatore Bonaccorso wrote: > Hi Lars, > > On Tue, Apr 19, 2016 at 12:27:51PM -0700, Lars Tangvald wrote: > > We've prepared MySQL 5.5.49 packages for Debian Wheezy and Jessie > > with fixes for the CVEs listed in Oracle's April CPU. > > The

Bug#820939: marked as done (Non-free file test/srgb.icm)

Your message dated Thu, 21 Apr 2016 16:52:46 + with message-id and subject line Bug#820939: fixed in ruby-rmagick 2.15.4+dfsg-1 has caused the Debian Bug report #820939, regarding Non-free file test/srgb.icm to be marked as done. This means that you claim

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016 13:34:33 +0200 Alexander Wirt wrote: > > OK. I sent a github PR with both commits to ease your work. You could > > have just asked for them... > I already integrated them, but thanks. And sorry for being grumpy, but I > really dislike those 0-day nmus.

Processed: python-future hides and breaks python-configparser

Processing control commands: > forwarded -1 https://github.com/PythonCharmers/python-future/issues/118 Bug #822157 [src:python-future] python-future hides and breaks python-configparser Set Bug forwarded-to-address to 'https://github.com/PythonCharmers/python-future/issues/118'. > affects -1

Bug#822157: python-future hides and breaks python-configparser

Source: python-future Version: 0.15.2-1 Severity: serious Tags: upstream User: de...@kali.org Usertags: origin-kali Control: forwarded -1 https://github.com/PythonCharmers/python-future/issues/118 Control: affects -1 python-configparser python-future provides the "configparser" module and so does

Processed: tag #820707 and #618456

Processing commands for cont...@bugs.debian.org: > tags 820707 + pending Bug #820707 [src:camera.app] camera.app: FTBFS: DigitalCamera.m:15:21: fatal error: gphoto2.h: No such file or directory Added tag(s) pending. > tags 618456 + pending Bug #618456 [camera.app] Typo in a .desktop entry Added

Bug#822115: xarchiver: X server crashes when cancelling file extraction

Am 21.04.2016 um 16:19 schrieb g66...@tfwno.gf: [...] > Apologies, I didn't realize there was significant difference between > running Xarchiver and extracting, versus using the Extract Here/To > option in Thunar. But apparently the latter pops up a progress box and > that's the one that crashes,

Bug#822115: xarchiver: X server crashes when cancelling file extraction

On 2016-04-21 21:37, Markus Koschany wrote: Am 21.04.2016 um 13:07 schrieb mai: Package: xarchiver Version: 1:0.5.4-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Pretty much as per the description: If I select an archive and "extract here" then attempt to

Processed: tagging 733693, tagging 817504

Processing commands for cont...@bugs.debian.org: > # NMU in DELAYED/5 > tags 733693 + pending Bug #733693 [ipkungfu] please do not depend on module-init-tools Added tag(s) pending. > tags 817504 + pending Bug #817504 [src:ipkungfu] ipkungfu: Removal of debhelper compat 4 Added tag(s) pending. >

Processed: Re: Bug#822120: Boost 1.55 to be removed; your attention required

Processing control commands: > tag -1 pending Bug #822120 [feel++] Boost 1.55 to be removed; your attention required Added tag(s) pending. > severity -1 serious Bug #822120 [feel++] Boost 1.55 to be removed; your attention required Severity set to 'serious' from 'normal' -- 822120:

Bug#821785: marked as done (sipwitch: FTBFS: service.cpp:256:28: error: invalid conversion from 'const sockaddr*' to 'sockaddr*' [-fpermissive])

Your message dated Thu, 21 Apr 2016 13:21:06 + with message-id and subject line Bug#821785: fixed in sipwitch 1.9.15-1 has caused the Debian Bug report #821785, regarding sipwitch: FTBFS: service.cpp:256:28: error: invalid conversion from 'const

Bug#822116: marked as done (bzr: FTBFS in testing (test fail))

Your message dated Thu, 21 Apr 2016 13:19:39 + with message-id and subject line Bug#822116: fixed in bzr 2.7.0-5 has caused the Debian Bug report #822116, regarding bzr: FTBFS in testing (test fail) to be marked as done. This means that you claim that the

Bug#822070: marked as done (courier-mta: Transition from "daemon" user to "courier" user is handled terribly)

Your message dated Thu, 21 Apr 2016 13:19:50 + with message-id and subject line Bug#822070: fixed in courier 0.75.0-19 has caused the Debian Bug report #822070, regarding courier-mta: Transition from "daemon" user to "courier" user is handled terribly to

Bug#822071: marked as done (maildrop: Upgrade from courier-maildrop: Default delivery location changed from Maildirs $/HOME/Maildir to /var/mail/$USER)

Your message dated Thu, 21 Apr 2016 13:19:50 + with message-id and subject line Bug#822071: fixed in courier 0.75.0-19 has caused the Debian Bug report #822071, regarding maildrop: Upgrade from courier-maildrop: Default delivery location changed from

Processed: severity of 822076 is important

Processing commands for cont...@bugs.debian.org: > severity 822076 important Bug #822076 [src:linux] linux-image-4.4.0-1-amd64: Monitor becomes blank during boot on built-in Intel i915 chip Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you

Bug#822118: RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages

Package: fw4spl Severity: serious Justification: blocks-transitions Dear maintainer / ftp-masters, fw4spl is RC buggy with 5 bugs: #797475 fw4spl: does not support parallel build #797481 fw4spl: FTBFS - Doesn't support boost 1.58 #809935 fw4spl: FTBFS with libpng16 #820632 fw4spl: depends on

Bug#822091: libxmlbeans-java: Embeds classes without source

Le 21/04/2016 09:29, Markus Koschany a écrit : > While I was working on #820839, I discovered that the source package > ships external jar and zip files in external/. > > I tried to repack the tarball but then the package failed to build > from source. Apparently the build system requires the

Processed: Re: aptitude: artificial report to prevent migrating the package to testing

Processing commands for cont...@bugs.debian.org: > found 802958 aptitude/0.8-1 Bug #802958 [aptitude] aptitude: artificial report to prevent migrating the package to testing Marked as found in versions aptitude/0.8-1. > stop Stopping processing here. Please contact me if you need assistance. --

Bug#822115: xarchiver: X server crashes when cancelling file extraction

Am 21.04.2016 um 13:07 schrieb mai: > Package: xarchiver > Version: 1:0.5.4-1 > Severity: grave > Justification: causes non-serious data loss > > Dear Maintainer, > > Pretty much as per the description: If I select an archive and "extract here" > then attempt to cancel the extraction, the

Bug#822116: bzr: FTBFS in testing (test fail)

On Thu, Apr 21, 2016 at 01:12:02PM +0200, Santiago Vila wrote: > Package: src:bzr > Version: 2.7.0-4 > Severity: serious > > Dear maintainer: > > This package currently fails to build from source in stretch. > > -- > Traceback (most

Bug#778599: Vulnerabilities in nanohttp

On Thu, 21 Apr 2016 02:58:18 PM Salvatore Bonaccorso wrote: > Given the package looks unmaintained (last update by maintainer back > in 20 Jun 2010, I think it is the best option to remove the package as > well from unstable). It is already gone in testing, so will not be > included in stretch and

Bug#822115: xarchiver: X server crashes when cancelling file extraction

Package: xarchiver Version: 1:0.5.4-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Pretty much as per the description: If I select an archive and "extract here" then attempt to cancel the extraction, the desktop crashes and drops me back to text console. I'm not

Bug#822116: bzr: FTBFS in testing (test fail)

Package: src:bzr Version: 2.7.0-4 Severity: serious Dear maintainer: This package currently fails to build from source in stretch. -- Traceback (most recent call last): File

Bug#821868: marked as pending

tag 821868 pending thanks Hello, Bug #821868 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=openstack/horizon.git;a=commitdiff;h=7de3eba --- commit

Processed: Bug#821868 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 821868 pending Bug #821868 [openstack-dashboard] openstack-dashboard: causes trigger loop Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 821868:

Bug#822103: light-locker: Cannot unlock screen

Screen cannot be unlocked after 'light-locker-command -l' as neither keyboard nor mouse action brings up the unlocking dialog, screen just stays dark. SSH access still working though. smime.p7s Description: S/MIME Cryptographic Signature

Bug#822104: guessnet: FTBFS: *** libiw not found. Check 'config.log' for more details.

Source: guessnet Version: 0.56 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, guessnet fails to build from source in unstable/amd64: [..]

Bug#822103: light-locker: Cannot unlock screen

Package: light-locker Version: 1.7.0-3 Severity: grave Justification: renders package unusable -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) Locale:

Bug#822085: RM: root-system: RoQA unmaintained, RC-buggy, FTBFS, blocks removal of old packages

On Thu, Apr 21, 2016 at 08:14:31AM +0200, Tobias Frost wrote: > As it is now blocking other packages, I raise the question if it should be > removed from Debian. It is indeed in a very bad state. I tried to revive it some time back, and also committed something to git for it, but really, it's a

Bug#822099: python-odf: depends on python3.4

Source: python-odf Version: 1.3.2+dfsg1-1 Severity: serious python-odf-tools depends on python3.4 which is going away. It needs to be rebuilt to lose that dependency. Cheers, Julien

Bug#822097: python3-future: depends on python3.4 which is going away

Package: python3-future Version: 0.15.2-1 Severity: serious python3-future depends on python3.4, which is being removed (replaced with 3.5), so the package needs to be rebuilt to drop that dependency. Cheers, Julien

Bug#822098: python3-gear: depends on python3.4

Package: python3-gear Version: 0.5.8-2 Severity: serious python3-gear depends on python3.4 which is replaced by python3.5. Your package needs to be rebuilt to lose that dependency. Cheers, Julien

Processed: closing 820098

Processing commands for cont...@bugs.debian.org: > close 820098 Bug #820098 [src:pcl] FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 820098:

Bug#820098: closing 820098

close 820098 thanks This should be fixed with vtk6 (6.2.0+dfsg1-11.1).

Bug#821785: sipwitch: FTBFS: service.cpp:256:28: error: invalid conversion from 'const sockaddr*' to 'sockaddr*' [-fpermissive]

Quoting peter green (2016-04-21 05:14:40) >> service.cpp: In static member function 'static void >> sipwitch::service::publish(const char*)': >>service.cpp:256:28: error: invalid conversion from 'const sockaddr*' to >> 'sockaddr*' [-fpermissive] >> host = resolver.getAddr(); > This

Bug#821350: marked as done (dh-golang: generates rubbish in Built-Using; errors on invocation)

Your message dated Thu, 21 Apr 2016 07:49:11 + with message-id and subject line Bug#821350: fixed in dh-golang 1.16 has caused the Debian Bug report #821350, regarding dh-golang: generates rubbish in Built-Using; errors on invocation to be marked as done.

Processed: severity of 822065 is important, severity of 822066 is important

Processing commands for cont...@bugs.debian.org: > severity 822065 important Bug #822065 [courier-mta] courier-mta: init script references the wrong configuration file; completely broken. Severity set to 'important' from 'grave' > severity 822066 important Bug #822066 [courier-mta]

Processed: reassign 822067 to src:courier, reassign 822068 to src:courier, forcibly merging 822067 822068

Processing commands for cont...@bugs.debian.org: > reassign 822067 src:courier Bug #822067 [courier-mta] courier-mta: init scripts completely broken Bug reassigned from package 'courier-mta' to 'src:courier'. No longer marked as found in versions courier/0.75.0-18. Ignoring request to alter fixed

Processed: Re: Bug#822067: courier-mta: init scripts completely broken

Processing control commands: > tags -1 +moreinfo Bug #822067 [courier-mta] courier-mta: init scripts completely broken Added tag(s) moreinfo. > severity -1 important Bug #822067 [courier-mta] courier-mta: init scripts completely broken Severity set to 'important' from 'grave' -- 822067:

Bug#822091: libxmlbeans-java: Embeds classes without source

Package: libxmlbeans-java Version: 2.6.0-4 Severity: serious While I was working on #820839, I discovered that the source package ships external jar and zip files in external/. I tried to repack the tarball but then the package failed to build from source. Apparently the build system requires

Bug#822067: courier-mta: init scripts completely broken

Control: tags -1 +moreinfo Control: severity -1 important J, you probably should not fill bugs when you are pissed. This bug report is not a bug report, but a complaint. If you have anything you want to fix, you should say it. You are also more then welcome to send patches or join the effort to

Bug#821350: dh-golang: generates rubbish in Built-Using; errors on invocation

I unfortunately don’t have time to test this package before uploading. If anyone has the time to either contribute a working and comprehensive test suite for the package and/or take over maintenance, that’d be much appreciated. I’m merely uploading these patches as-is to avoid blocking progress

Bug#821933: marked as done (golang-github-azure-azure-sdk-for-go: package FTBFS due to fail of testsuite)

Your message dated Thu, 21 Apr 2016 07:19:03 + with message-id and subject line Bug#821933: fixed in golang-github-azure-azure-sdk-for-go 2.1.1~beta-1 has caused the Debian Bug report #821933, regarding golang-github-azure-azure-sdk-for-go: package FTBFS

Bug#778599: Vulnerabilities in nanohttp

B0;115;0cOn Thu, Apr 21, 2016 at 06:58:18AM +0200, Salvatore Bonaccorso wrote: > Hi, > > On Wed, Apr 20, 2016 at 11:01:29PM +0200, Sebastian Andrzej Siewior wrote: > > On 2015-03-15 06:42:08 [+0100], Salvatore Bonaccorso wrote: > > > On Tue, Feb 17, 2015 at 10:07:06AM +, Patrick Coleman

Bug#822085: RM: root-system: RoQA unmaintained, RC-buggy, FTBFS, blocks removal of old packages

Source: root-system Severity: serious Justification: libpng1.2-removal Dear maintainer / ftp-master, root-system is RC-Buggy with 2 RC-Bugs: #778108 root-system: ftbfs with GCC-5 #809874 root-system: FTBFS with libpng16 Both bugs do not have any maintainer response or action, the gcc bug is

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

On Sun, 17 Apr 2016 15:24:28 +0200 Muammar El Khatib wrote: > Hi Tobias, >  > On Sun, Apr 17, 2016 at 3:18 PM, Tobias Frost wrote: > > Maybe we should let it go? >  > Yes. There is other option, because some people has forked SMC. The > project is