Bug#800289: marked as done (ipcheck: Please migrate a supported debhelper compat level)

Your message dated Sat, 15 Oct 2016 05:21:56 + with message-id and subject line Bug#800289: fixed in ipcheck 0.233-2 has caused the Debian Bug report #800289, regarding ipcheck: Please migrate a supported debhelper compat level to be marked as done. This

Bug#840806: libgd2: invalid read in gdImageCreateFromTiffPtr()

Source: libgd2 Version: 2.1.0-5 Severity: grave Tags: security upstream patch Control: fixed -1 2.1.0-5+deb8u7 For tracking the isssue. DSA-3693-1 included the patch 0020-Fix-invalid-read-in-gdImageCreateFromTiffPtr.patch to fix: > Subject: Fix invalid read in gdImageCreateFromTiffPtr() with

Processed: libgd2: invalid read in gdImageCreateFromTiffPtr()

Processing control commands: > fixed -1 2.1.0-5+deb8u7 Bug #840806 [src:libgd2] libgd2: invalid read in gdImageCreateFromTiffPtr() Marked as fixed in versions libgd2/2.1.0-5+deb8u7. -- 840806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840806 Debian Bug Tracking System Contact

Processed: libgd2: Stack Buffer Overflow in GD dynamicGetbuf

Processing control commands: > fixed -1 2.1.0-5+deb8u7 Bug #840805 [src:libgd2] libgd2: Stack Buffer Overflow in GD dynamicGetbuf Marked as fixed in versions libgd2/2.1.0-5+deb8u7. -- 840805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840805 Debian Bug Tracking System Contact

Bug#840805: libgd2: Stack Buffer Overflow in GD dynamicGetbuf

Source: libgd2 Version: 2.1.0-5 Severity: grave Tags: security upstream Control: fixed -1 2.1.0-5+deb8u7 For tracking this issue. DSA-3693-1 included the 0019-Patch-for-security-bug-https-bugs.php.net-bug.php-id.patch patch fixing a stack buffer overflow in dynamicGetbuf as per upstream commit

Processed: found 839659 in 2.1.0-5, fixed 839659 in 2.1.0-5+deb8u7

Processing commands for cont...@bugs.debian.org: > found 839659 2.1.0-5 Bug #839659 [src:libgd2] libgd2: CVE-2016-7568: Integer overflow in gdImageWebpCtx Ignoring request to alter found versions of bug #839659 to the same values previously set > # fixed in DSA-3693-1 > fixed 839659

Bug#840546: CVE-2016-7966 kdepimlibs jessie

Hi Sandro, On Fri, Oct 14, 2016 at 10:56:00PM +0200, Sandro Knauß wrote: > Hi, > > now I'm fully confused - you said on IRC, I should better create a deb8u2 > ontop. Well I created now the debdiff for a deb8u2. > > So you can decide what is the best way for the sec team and what version >

Bug#840481: marked as done (Singular4: readline migration: piping error)

Your message dated Sat, 15 Oct 2016 04:32:06 + with message-id and subject line Bug#840481: fixed in singular 4.0.3-p3+ds-2 has caused the Debian Bug report #840481, regarding Singular4: readline migration: piping error to be marked as done. This means

Bug#817514: kterm: diff for NMU version 6.2.0-46.2

Control: tags 817514 + patch Control: tags 817514 + pending Dear maintainer, I've prepared an NMU for kterm (versioned as 6.2.0-46.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u kterm-6.2.0/debian/changelog

Processed: kterm: diff for NMU version 6.2.0-46.2

Processing control commands: > tags 817514 + patch Bug #817514 [src:kterm] kterm: Removal of debhelper compat 4 Added tag(s) patch. > tags 817514 + pending Bug #817514 [src:kterm] kterm: Removal of debhelper compat 4 Added tag(s) pending. -- 817514:

Bug#835360: rkt: FTBFS on several architectures

On Friday, 14 October 2016 5:24:53 PM AEDT Andreas Henriksson wrote: > (Despite this debdiff, asking for removal could possibly be a better > idea as there's obviously not enough backing to properly support ppc64le > right now and thus probably not for the lifetime of stretch.) Andreas, thank you

Bug#840761: marked as done (python-opcua: FTBFS (ImportError: No module named setuptools))

Your message dated Fri, 14 Oct 2016 22:47:09 + with message-id and subject line Bug#840761: fixed in python-opcua 0.10.17-2 has caused the Debian Bug report #840761, regarding python-opcua: FTBFS (ImportError: No module named setuptools) to be marked as

Bug#840382: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31

Confirmed fixed as of 2:4.4.6+dfsg-2. If there is any release after which, I have not teted. On 10/14/2016 12:08 PM, Mathieu Parent wrote: To the recipients: Do you still have the problem when using latest packages from sid? I cant' reproduce the problem anymore. Thanks Mathieu Parent

Bug#840789: ruby-gettext: FTBFS: Error: test_relative(TestToolsXGetText::TestReference): NoMethodError: undefined method `stub' for #

Source: ruby-gettext Version: 3.2.2-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, ruby-gettext fails to build from source in

Bug#840761: marked as pending

tag 840761 pending thanks Hello, Bug #840761 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/python-opcua.git;a=commitdiff;h=9c4f3eb --- commit

Processed: Bug#840761 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 840761 pending Bug #840761 [src:python-opcua] python-opcua: FTBFS (ImportError: No module named setuptools) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 840761:

Bug#805004: marked as done (clang-modernize-3.8: uninstallable in sid)

Your message dated Fri, 14 Oct 2016 23:59:34 +0300 with message-id <20161014205934.b77udo5fuoh36...@bunk.spdns.de> and subject line clang-modernize-3.8 has been removed from unstable has caused the Debian Bug report #805004, regarding clang-modernize-3.8: uninstallable in sid to be marked as done.

Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie

On Fri, 14 Oct 2016 06:47:47 +0200 Salvatore Bonaccorso wrote: [...] > Hi Francesco, Hello Salvatore, thanks for your fast reply! > > On Thu, Oct 13, 2016 at 11:56:22PM +0200, Francesco Poli (wintermute) wrote: [...] > > After the security update: [...] > > I was unable to use zathura or

Bug#840546: CVE-2016-7966 kdepimlibs jessie

Hi, now I'm fully confused - you said on IRC, I should better create a deb8u2 ontop. Well I created now the debdiff for a deb8u2. So you can decide what is the best way for the sec team and what version should be uploaded where. Best Regards, sandro -- Am Freitag, 14. Oktober 2016,

Bug#840685: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

Control: severity -1 normal Control: found -1 8.0.14-1 Hi Paul, On Sat, Oct 15, 2016 at 07:25:59AM +1100, paul.sz...@sydney.edu.au wrote: > Dear Salvatore, > > > You are operating here outside of /tmp (sticky world-writable > > directory) which the above issue for the init scripts relies on, >

Processed: Re: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

Processing control commands: > severity -1 normal Bug #840685 [tomcat8] TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory Severity set to 'normal' from 'critical' > found -1 8.0.14-1 Bug #840685 [tomcat8] TOCTOU race condition in initscript on chown'ing JVM_TMP

Bug#840685: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

Dear Salvatore, > You are operating here outside of /tmp (sticky world-writable > directory) which the above issue for the init scripts relies on, > right? fs.protected_(hardlinks|symlinks) is exactly a hardening for > those issues: > https://www.kernel.org/doc/Documentation/sysctl/fs.txt I

Bug#840298: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31

It seems to be fixed, thanks. On 10/14/2016 09:08 PM, Mathieu Parent wrote: To the recipients: Do you still have the problem when using latest packages from sid? I cant' reproduce the problem anymore. Thanks Mathieu Parent -- Ivan Sergio Borgonovo http://www.webthatworks.it

Bug#839827: marked as done (freeimage: CVE-2016-5684)

Your message dated Fri, 14 Oct 2016 20:10:20 + with message-id and subject line Bug#839827: fixed in freeimage 3.15.4-4.2+deb8u1 has caused the Debian Bug report #839827, regarding freeimage: CVE-2016-5684 to be marked as done. This means that you claim

Bug#840685: tomcat8: DSA-3670 incomplete

Dear Markus, Sorry to reply again. > ... But there is another rm -rf "$JVM_TMP" command in the stop target > that would remove your symlink again. I now see what you mean. There is an rm when you "stop" tomcat, and another in the "start"; so maybe there are two in restart. No matter: I watch

Bug#840546: CVE-2016-7966 kdepimlibs jessie

Hi, Just an additional comment on the debdiff: On Fri, Oct 14, 2016 at 08:23:04PM +0200, Sandro Knauß wrote: > Hey, > > I now back ported the second part of the fix of the CVE. I updated the > version > deb8u1 from Scott. Should I create a deb8u2 for the additional patch? Please note, to

Bug#840685: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

Hi Paul, Markus followed already up, I just want to give some additional comments on the below: On Fri, Oct 14, 2016 at 07:07:52PM +1100, paul.sz...@sydney.edu.au wrote: > Dear Salvatore, > > > ... if the attacher created a symlink between the rm and the mkdir > > then mkdir will still fail

Bug#840546: CVE-2016-7966 kdepimlibs jessie

On Fri, Oct 14, 2016 at 08:23:04PM +0200, Sandro Knauß wrote: > Hey, > > I now back ported the second part of the fix of the CVE. I updated the > version > deb8u1 from Scott. Should I create a deb8u2 for the additional patch? > > I attached the uptodate debdiff. Thanks, please upload.

Bug#840298: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31

To the recipients: Do you still have the problem when using latest packages from sid? I cant' reproduce the problem anymore. Thanks Mathieu Parent

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

Hello Graham, Graham Inggs wrote on 2016-10-14 16:35: > > PIE by default is happening for Stretch. > Release Team have given the go-ahead, see message #21 of #835148 [1], > and the changes have already been committed to SVN [2] and should be > included in the next GCC6 upload. Thank you for

Bug#840685: tomcat8: DSA-3670 incomplete

Dear Markus, > First of all you can only gain write permissions as the tomcat8 user if > you exploit an yet unknown security vulnerability in a web application > or Tomcat itself. Debian's tomcat8 user has no shell access by default. Yes, this is a privilege escalation issue: exactly as in

Processed: your mail

Processing commands for cont...@bugs.debian.org: > submitter 840067 la...@debian.org Bug #840067 {Done: Maximiliano Curia } [src:kscreen] kscreen: FTBFS: debug.h:24:25: fatal error: kscreen/log.h: No such file or directory Changed Bug submitter to 'la...@debian.org' from 'Chris

Bug#840546: CVE-2016-7966 kdepimlibs jessie

Hey, I now back ported the second part of the fix of the CVE. I updated the version deb8u1 from Scott. Should I create a deb8u2 for the additional patch? I attached the uptodate debdiff. Regards, sandro Am Donnerstag, 13. Oktober 2016, 18:19:35 CEST schrieb Moritz Mühlenhoff: > On Thu, Oct

Processed: retitle 840685 to TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory

Processing commands for cont...@bugs.debian.org: > retitle 840685 TOCTOU race condition in initscript on chown'ing JVM_TMP > temporary directory Bug #840685 [tomcat8] tomcat8: DSA-3670 incomplete Changed Bug title to 'TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory'

Bug#833741: Workaround

Hello, There is no big problem for existing installations, but if you make a new installation then flash does not work. This is what I do as root as a workaround: apt-get install pepperflashplugin-nonfree cd /usr/lib/ mv pepperflashplugin-nonfree pepperflashplugin-nonfree-backup mkdir

Bug#838440: marked as done (nodejs: can't migrate to testing because of lack of armel binaries)

Your message dated Fri, 14 Oct 2016 19:07:16 +0200 with message-id <26466882-f042-8eec-f353-9f81c01dd...@xs4all.nl> and subject line Re: [Pkg-javascript-devel] Bug#838440: Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries has caused the Debian Bug report #838440,

Bug#840581: marked as done (vim-conque: ConqueTerm doesn't appear to load into vim)

Your message dated Fri, 14 Oct 2016 18:49:40 +0200 with message-id <20161014164940.l3qbz6ks7xxfl...@jwilk.net> and subject line Re: Bug#840581: vim-conque: ConqueTerm doesn't appear to load into vim has caused the Debian Bug report #840581, regarding vim-conque: ConqueTerm doesn't appear to load

Bug#840733: e2fsprogs contains non-free file

On Fri, Oct 14, 2016 at 12:18:31PM +0300, Adrian Bunk wrote: > Source: e2fsprogs > Version: 1.43.3-1 > Severity: serious > > lib/et/test_cases/imap_err.et: > > The "for non-commercial purposes only" is a clear violation > of clause 6 of the DFSG. Thanks for pointing that out. Please note that

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

On വെള്ളി 14 ഒക്ടോബര്‍ 2016 07:29 വൈകു, Aaron M. Ucko wrote: > depending on the architecture. For whatever reason, the problem was with > jison@0.4.x on arm64, armhf, mips, powerpc, ppc64el, s390x, and the > non-release architecture kfreebsd-amd64, and test@* on i386, mips64el, > mipsel, and the

Bug#835360: rkt: FTBFS on several architectures

Hello all. On Thu, Oct 13, 2016 at 01:29:31PM +, Luca BRUNO wrote: > On Thursday, 13 October 2016 13:59:27 UTC Andreas Henriksson wrote: > > > Fwiw, there's a chain of {build-,}dependencies that would need to be > > removed on ppc64el > > Ah, when I wrote my previous answer I didn't

Bug#840770: openvswitch: FTBFS on almost all big-endian architectures: 954: ofproto-dpif - in place modification (vlan) FAILED (ofproto-dpif.at:7237)

Source: openvswitch Version: 2.5.1~pre+git20160626-2 Severity: serious Hi, openvswitch failed to build on almost all of our big-endian architectures: https://buildd.debian.org/status/package.php?p=openvswitch As you can see it failed on mips, powerpc, s390x, m68k, ppc64 and sparc64, all of

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

Hi, On Sun, 13 Dec 2015 22:12:24 +0100 gregor herrmann wrote: > Control: tag -1 - pending > > On Mon, 14 Dec 2015 08:05:22 +1100, Ian Wienand wrote: > > > The patch has not been applied because it is not clear it is correct > > > > There is a thread that starts at [1] and

Bug#806000: brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

On Fri, 14 Oct 2016, Petter Reinholdtsen wrote: > Control: tags -1 + patch > > I had a look, and while I do not quite understand the build system and why it > fail to create the directory it need to install, I applied this patch and got > the 'dpkg-buildpackage -A' build working: > > diff -ur

Processed: golang-github-naoina-toml: Source package is not fully buildable within Debian main

Processing control commands: > block -1 by 840766 Bug #840767 [src:golang-github-naoina-toml] golang-github-naoina-toml: Source package is not fully buildable within Debian main 840767 was not blocked by any bugs. 840767 was not blocking any bugs. Added blocking bug(s) of 840767: 840766 --

Bug#840767: golang-github-naoina-toml: Source package is not fully buildable within Debian main

Source: golang-github-naoina-toml Source-Version: 0.1.0-1 Severity: serious Control: block -1 by 840766 Hi! This package contains a «parse.peg» which is the source for «parse.peg.go». But the required program to build that (golang-github-pointlander-peg) is not currently present in Debian, which

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

Hi Joachim On 14 October 2016 at 15:23, Joachim Wiedorn wrote: > for now motif should be compiled without buildflag 'pie'. I think it is > not needed for the next release - it is disabled by default, because not > all packages can be compiled with this flag. PIE by default

Bug#840761: python-opcua: FTBFS (ImportError: No module named setuptools)

Package: src:python-opcua Version: 0.10.17-1 Severity: serious Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Bug#840760: node-livescript: FTBFS (npm: Command not found)

Package: src:node-livescript Version: 1.5.0+dfsg-1 Severity: serious Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

Source: node-lex-parser Version: 0.1.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automatic builds of node-lex-parser all failed with either npm ERR! Error: Attempt to unlock jison@0.4.x, which hasn't been locked npm ERR! at unlock

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

Hello, for now motif should be compiled without buildflag 'pie'. I think it is not needed for the next release - it is disabled by default, because not all packages can be compiled with this flag. --- Have a nice day. Joachim (Germany) pgp0i55wnVLkQ.pgp Description: Digitale Signatur von

Bug#840685: tomcat8: DSA-3670 incomplete

On 14.10.2016 10:07, paul.sz...@sydney.edu.au wrote: [...] >> So while I think it should be fixed, this would not warrant a DSA, >> since mitigated by default in Debian. > > No mitigation: fix and DSA, please! I agree with Salvatore. I have tested the following: First of all you can only gain

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

Hello, for now motif should be compiled without hardening buildflag 'pie' (see patch). --- d01/debian/rules2016-09-28 22:22:07.0 +0200 +++ d02/debian/rules2016-10-14 01:04:31.0 +0200 @@ -2,7 +2,7 @@ export DEB_CFLAGS_MAINT_APPEND=-D_FILE_OFFSET_BITS=64 export

Bug#834126: marked as done (open-gram: FTBFS: make[1]: *** [lm_sc.t3g] Aborted (core dumped))

Your message dated Fri, 14 Oct 2016 13:35:44 + with message-id and subject line Bug#834126: fixed in open-gram 0.1.22+20131212-2 has caused the Debian Bug report #834126, regarding open-gram: FTBFS: make[1]: *** [lm_sc.t3g] Aborted (core dumped) to be

Bug#840477: marked as done (cryptsetup: initramfs hook cryptroot fails if root is lvm and spans multiple devices/nodes)

Your message dated Fri, 14 Oct 2016 13:03:44 + with message-id and subject line Bug#840480: fixed in cryptsetup 2:1.7.2-4 has caused the Debian Bug report #840480, regarding cryptsetup: initramfs hook cryptroot fails if root is lvm and spans multiple

Bug#840480: marked as done (cryptsetup initramfs hook warning with multiple encrypted physical volumes)

Your message dated Fri, 14 Oct 2016 13:03:44 + with message-id and subject line Bug#840480: fixed in cryptsetup 2:1.7.2-4 has caused the Debian Bug report #840480, regarding cryptsetup initramfs hook warning with multiple encrypted physical volumes to be

Processed: valac: Regression in DBus gio-2.0.vapi binding

Processing control commands: > affects -1 mdbus2 Bug #840746 [valac] valac: Regression in DBus gio-2.0.vapi binding Added indication that 840746 affects mdbus2 -- 840746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840746 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#840746: valac: Regression in DBus gio-2.0.vapi binding

Package: valac Version: 0.34.0-1 Severity: serious Tags: patch upstream Justification: renders mdbus package completly useless Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=772902 Control: affects -1 mdbus2 Hi, vala 0.34 has updated gio-2.0.vapi file, which removed "array_null_terminated

Bug#839364: marked as done (golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt)

Your message dated Fri, 14 Oct 2016 12:03:36 + with message-id and subject line Bug#839690: Removed package(s) from unstable has caused the Debian Bug report #839364, regarding golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt to be

Bug#624025: marked as done (dsyslog: Uses deprecated _set_priority GnuTLS functions / broken with GnuTLS 3.4.0)

Your message dated Fri, 14 Oct 2016 11:50:41 + with message-id and subject line Bug#835369: Removed package(s) from unstable has caused the Debian Bug report #624025, regarding dsyslog: Uses deprecated _set_priority GnuTLS functions / broken with GnuTLS

Bug#706493: marked as done (python-abiword: missing python-gtk2 dependency)

Your message dated Fri, 14 Oct 2016 11:49:45 + with message-id and subject line Bug#826400: Removed package(s) from unstable has caused the Debian Bug report #706298, regarding python-abiword: missing python-gtk2 dependency to be marked as done. This

Bug#831179: marked as done (pjproject: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors)

Your message dated Fri, 14 Oct 2016 11:49:06 + with message-id and subject line Bug#831179: fixed in pjproject 2.5.1~dfsg-3 has caused the Debian Bug report #831179, regarding pjproject: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors to be

Bug#706298: marked as done (python-abiword: missing python-gobject-2 dependency)

Your message dated Fri, 14 Oct 2016 11:49:45 + with message-id and subject line Bug#826400: Removed package(s) from unstable has caused the Debian Bug report #706298, regarding python-abiword: missing python-gobject-2 dependency to be marked as done. This

Bug#706017: marked as done (segmentation fault on import)

Your message dated Fri, 14 Oct 2016 11:49:45 + with message-id and subject line Bug#826400: Removed package(s) from unstable has caused the Debian Bug report #706017, regarding segmentation fault on import to be marked as done. This means that you claim

Bug#727084: marked as done (src:python-abiword: libabiword-3.0 mini-transition)

Your message dated Fri, 14 Oct 2016 11:49:45 + with message-id and subject line Bug#826400: Removed package(s) from unstable has caused the Debian Bug report #727084, regarding src:python-abiword: libabiword-3.0 mini-transition to be marked as done. This

Bug#736598: marked as done ([src:hotot] Sourceless file)

Your message dated Fri, 14 Oct 2016 11:46:25 + with message-id and subject line Bug#743767: Removed package(s) from unstable has caused the Debian Bug report #736598, regarding [src:hotot] Sourceless file to be marked as done. This means that you claim

Bug#810133: marked as done (proll: FTBFS: Build-Depends-Indep: sparc-utils which is in nothing newer than oldstable)

Your message dated Fri, 14 Oct 2016 11:45:20 + with message-id and subject line Bug#658886: Removed package(s) from unstable has caused the Debian Bug report #810133, regarding proll: FTBFS: Build-Depends-Indep: sparc-utils which is in nothing newer than

Bug#728578: marked as done (hotot: segfaults on startup)

Your message dated Fri, 14 Oct 2016 11:46:25 + with message-id and subject line Bug#743767: Removed package(s) from unstable has caused the Debian Bug report #728578, regarding hotot: segfaults on startup to be marked as done. This means that you claim

Bug#749253: marked as done (hotot-gtk: depends on python-webkit which is deprecated)

Your message dated Fri, 14 Oct 2016 11:46:25 + with message-id and subject line Bug#743767: Removed package(s) from unstable has caused the Debian Bug report #749253, regarding hotot-gtk: depends on python-webkit which is deprecated to be marked as done.

Bug#729975: marked as done (hotot: Wheezy version no longer usable with Twitter, uses retired 1.0 API)

Your message dated Fri, 14 Oct 2016 11:46:25 + with message-id and subject line Bug#743767: Removed package(s) from unstable has caused the Debian Bug report #729975, regarding hotot: Wheezy version no longer usable with Twitter, uses retired 1.0 API to

Bug#760623: marked as done (hotot: Hotot fails to start with import error)

Your message dated Fri, 14 Oct 2016 11:46:25 + with message-id and subject line Bug#743767: Removed package(s) from unstable has caused the Debian Bug report #760623, regarding hotot: Hotot fails to start with import error to be marked as done. This means

Bug#840736: gnome-maps: always offline cant browse any map

On Fri, 14 Oct 2016 20:58:34 +1100 Fulano Diego Perez wrote: Hi, > > cannot browse any maps > > always reports offline with active internet comms > > ignore missing pkgs below - report bug has confusion with this > I cannot reproduce this. Are you using

Bug#840736: gnome-maps: always offline cant browse any map

Package: gnome-maps Version: 3.22.0-1 Severity: grave Justification: renders package unusable cannot browse any maps always reports offline with active internet comms ignore missing pkgs below - report bug has confusion with this -- System Information: Debian Release: stretch/sid APT

Bug#840573: unicon: DFSG-incompatible license

On Thu, Oct 13, 2016 at 11:58:00AM +0200, Santiago Vila wrote: > On Wed, 12 Oct 2016, Joao Eriberto Mota Filho wrote: > > > Source: unicon > > Severity: serious > > Tags: upstream > > Justification: Policy 2.2.1 > > > > Dear Maintainer, > > > > The file unicon/ImmModules/cxterm/utils/HZtable.h

Bug#840692: [pkg-cinnamon] Bug#840692: nemo-python: plugin is not recognized or loaded by Nemo

Control: tag -1 + unreproducible Control: severity -1 normal ¡Hola Nathan! El 2016-10-13 a las 15:25 -0700, Nathan Osman escribió: Package: nemo-python Version: 3.0.0-3 Severity: grave Justification: renders package unusable The nemo-python extension is not displayed in the "Extensions"

Processed: Re: [pkg-cinnamon] Bug#840692: nemo-python: plugin is not recognized or loaded by Nemo

Processing control commands: > tag -1 + unreproducible Bug #840692 [nemo-python] nemo-python: plugin is not recognized or loaded by Nemo Added tag(s) unreproducible. > severity -1 normal Bug #840692 [nemo-python] nemo-python: plugin is not recognized or loaded by Nemo Severity set to 'normal'

Bug#840733: e2fsprogs contains non-free file

Source: e2fsprogs Version: 1.43.3-1 Severity: serious lib/et/test_cases/imap_err.et: # Copyright 1998 Carnegie Mellon University # # No warranties, either expressed or implied, are made regarding the # operation, use, or results of the software. # # Permission to use, copy, modify and

Bug#840732: qbrew: FTBFS: install: cannot create regular file '/usr/bin/qbrew': Permission denied

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

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

Hi, 2016-10-14 7:36 GMT+02:00 Johannes Schauer : > don't know if our current sbuild backporter Luca (in CC) would be willing to > write such a patch, especially considering that > > - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page >accordingly) to

Bug#840728: libp11: FTBFS: openssl-1.0.2/engines: No such file or directory

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

Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere

Hi Emilio, this is a known issue which would be fixed if khronos-opencl-clhpp would be accepted by ftpmaster in new queue. I've given a hint to frpmaster about this hoping that this can be solved quickly but unfortunately with no success so far. :-( Kind regards Andreas. On Fri, Oct 14,

Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere

Source: libhmsbeagle Version: 2.1.2+20160525-1 Severity: serious Hi, Your package failed to build on i386 with: /«BUILDDIR»/libhmsbeagle-2.1.2+20160525/libhmsbeagle/GPU/GPUInterface.h: In member function 'void opencl_device::GPUInterface::PrintfDeviceVector(GPUPtr, int, double, int*, Real)':

Bug#840685: tomcat8: DSA-3670 incomplete

Dear Salvatore, > ... if the attacher created a symlink between the rm and the mkdir > then mkdir will still fail with -p on a symlink. (Or do I miss > something?). ... Yes, you missed a simple test: $ mkdir mydir $ ln -s mydir mylink $ ls -ld my* drwx-- 2 psz amstaff 4096 Oct 14 18:46

Bug#806000: brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Control: tags -1 + patch I had a look, and while I do not quite understand the build system and why it fail to create the directory it need to install, I applied this patch and got the 'dpkg-buildpackage -A' build working: diff -ur brickos-0.9.0.dfsg/debian/rules

Processed: Re: brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Processing control commands: > tags -1 + patch Bug #806000 [src:brickos] brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory) Added tag(s) patch. -- 806000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806000 Debian Bug Tracking System Contact

Bug#840689: libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures

Control: tags -1 + confirmed Hi, On Thu, Oct 13, 2016 at 11:03:15PM +0200, Emilio Pozuelo Monfort wrote: > Package: libterm-readline-gnu-perl > Version: 1.34-1 > Severity: serious > > Hi, > > On a rebuild against libreadline7, your package failed to build on > big-endian, 64-bit architectures:

Processed: Re: Bug#840689: libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures

Processing control commands: > tags -1 + confirmed Bug #840689 [libterm-readline-gnu-perl] libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures Added tag(s) confirmed. -- 840689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840689 Debian Bug Tracking System Contact

Processed: Re: [Debian-med-packaging] Bug#834856: python-pysam fails to build on mips64el arch.: failed test

Processing control commands: > severity -1 serious Bug #834856 [python-pysam] python-pysam fails to build on mips64el arch.: failed test Severity set to 'serious' from 'important' -- 834856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834856 Debian Bug Tracking System Contact

Bug#840685: tomcat8: DSA-3670 incomplete

Hi Paul, hi Markus, On Fri, Oct 14, 2016 at 08:42:11AM +1100, paul.sz...@sydney.edu.au wrote: > Dear Markus, > > >> [ I contacted t...@security.debian.org about this, but no response ... ] > > ... Please send them to the security team > > first and not to a public mailing list. > > I did. They

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

On Fri 2016-10-14 01:36:56 -0400, Johannes Schauer wrote: > - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page >accordingly) to *not* require signing of the internal dummy repository (and >thus you don't need to run sbuild-update --keygen anymore) and that

Bug#840097: sysprof ppc binaries removed

Control: severity -1 important Hello! The old powerpc binaries has now been removed from unstable. Porter assistance with identifying if this is a real issue or a testcase problem would be welcome. Regards, Andreas Henriksson

Processed: sysprof ppc binaries removed

Processing control commands: > severity -1 important Bug #840097 [sysprof] sysprof: FTBFS on powerpc: ERROR:test-capture.c:68:test_reader_basic: assertion failed: (map != NULL) Severity set to 'important' from 'serious' -- 840097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840097 Debian