Processed: found 860544 in 5.5.23-2

Processing commands for cont...@bugs.debian.org: > # for the BTS version tracking > found 860544 5.5.23-2 Bug #860544 [src:mysql-5.5] Security fixes from the April 2017 CPU Marked as found in versions mysql-5.5/5.5.23-2. > thanks Stopping processing here. Please contact me if you need

Bug#861218: libgssapi-krb5-2: soname-independent files in shared library package (policy 8.2)

Package: libgssapi-krb5-2 Version: 1.15-1 Severity: serious Justification: violates policy section 8.2 libgssapi-krb5-2 is a shared library package and contains /etc/gss/mech.d/README. The latter filename does not depend on the soname of the library and thus does not change when the soname

Bug#861021: marked as done (spin: missing Breaks+Replaces: staden (<< 2.0.0+b11))

Your message dated Wed, 26 Apr 2017 04:04:59 + with message-id and subject line Bug#861021: fixed in spin 6.4.5+dfsg-3 has caused the Debian Bug report #861021, regarding spin: missing Breaks+Replaces: staden (<< 2.0.0+b11) to be marked as done. This

Processed: reopening 861021

Processing commands for cont...@bugs.debian.org: > # reopening to provide version with Replaces > reopen 861021 Bug #861021 {Done: tony mancill } [spin] spin: missing Breaks+Replaces: staden (<< 2.0.0+b11) 'reopen' may be inappropriate when a bug has been closed with a

Bug#790796: sensord: RRD data loss

On Tue, 2017-04-25 at 17:22 +0200, Aurelien Jarno wrote: > What's your use case for sensord without RRD? Logging values and alarms > into syslog? Yes, when a machine powers off overnight, having that info in syslog helps diagnose what happened. > In that case we might just want to

Bug#861189: marked as done (keystone: CVE-2017-2673: federated user gets wrong role)

Your message dated Wed, 26 Apr 2017 00:34:06 + with message-id and subject line Bug#861189: fixed in keystone 2:10.0.0-9 has caused the Debian Bug report #861189, regarding keystone: CVE-2017-2673: federated user gets wrong role to be marked as done. This

Bug#861033: marked as done (gpsshogi FTBFS with libosl 0.8.0-1.2: /usr/share/libosl-dev/makefile.conf: No such file or directory)

Your message dated Tue, 25 Apr 2017 23:04:15 + with message-id and subject line Bug#861033: fixed in libosl 0.8.0-1.3 has caused the Debian Bug report #861033, regarding gpsshogi FTBFS with libosl 0.8.0-1.2: /usr/share/libosl-dev/makefile.conf: No such

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

Am 26.04.2017 um 00:23 schrieb Bernd Zeimetz: > Hi, > >> Does this break existing services/packages in stretch? If so, which ones? >> I'm trying to evaluate if this RC or can be fixed for buster. > > yes. As mentioned, #856429 - run-vmblock\x2dfuse.mount from > open-vm-tools-desktop. Hm, but

Bug#861033: gpsshogi FTBFS with libosl 0.8.0-1.2: /usr/share/libosl-dev/makefile.conf: No such file or directory

Control: reassign -1 libosl-dev 0.8.0-1.2 On 2017-04-24 00:02, Adrian Bunk wrote: > make[1]: Entering directory '/«PKGBUILDDIR»/lib' > ../makefile.conf:5: /usr/share/libosl-dev/makefile.conf: No such file or > directory OK, adding back makefile.conf Andreas

Processed: Re: Bug#861033: gpsshogi FTBFS with libosl 0.8.0-1.2: /usr/share/libosl-dev/makefile.conf: No such file or directory

Processing control commands: > reassign -1 libosl-dev 0.8.0-1.2 Bug #861033 [src:gpsshogi] gpsshogi FTBFS with libosl 0.8.0-1.2: /usr/share/libosl-dev/makefile.conf: No such file or directory Bug reassigned from package 'src:gpsshogi' to 'libosl-dev'. No longer marked as found in versions

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

Hi, > Does this break existing services/packages in stretch? If so, which ones? > I'm trying to evaluate if this RC or can be fixed for buster. yes. As mentioned, #856429 - run-vmblock\x2dfuse.mount from open-vm-tools-desktop. Please upload it for stretch. Thanks, Bernd -- Bernd Zeimetz

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

Hi Am 25.04.2017 um 22:09 schrieb Bernd Zeimetz: > Package: init-system-helpers > Version: 1.47 > Severity: serious > Tags: patch > > Hi, > > to fix #856429 I need to handle a unit with an escaped character > correctly in the maintainer scripts generated by dh_systemd*. > > Unfortunately

Bug#861172: marked as done (node-jsonstream FTBFS in stretch: Build dependency node-tape is not available)

Your message dated Tue, 25 Apr 2017 21:52:14 + with message-id and subject line Bug#861172: fixed in node-jsonstream 1.0.3-4 has caused the Debian Bug report #861172, regarding node-jsonstream FTBFS in stretch: Build dependency node-tape is not available

Processed: tagging 861028

Processing commands for cont...@bugs.debian.org: > tags 861028 + jessie-ignore Bug #861028 [morse-simulator] morse-simulator: abuses Conflicts to circument Policy 10.1 on /usr/bin/morse collision with morse Added tag(s) jessie-ignore. > thanks Stopping processing here. Please contact me if you

Processed: user release.debian....@packages.debian.org, usertagging 861028, tagging 861028

Processing commands for cont...@bugs.debian.org: > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was ni...@thykier.net). > usertags 861028 stretch-can-defer There were no usertags set. Usertags are now: stretch-can-defer. > tags 861028 +

Bug#849098: marked as done (llvm-toolchain-3.9: Please add ELF symbols versions to the libraries)

Your message dated Tue, 25 Apr 2017 21:09:49 + with message-id and subject line Bug#849098: fixed in llvm-toolchain-3.9 1:3.9.1-8 has caused the Debian Bug report #849098, regarding llvm-toolchain-3.9: Please add ELF symbols versions to the libraries to be

Bug#840318: marked as done (susv4: download url has changed)

Your message dated Tue, 25 Apr 2017 21:02:12 + with message-id and subject line Bug#840318: fixed in sus 7.20161013~deb8u1 has caused the Debian Bug report #840318, regarding susv4: download url has changed to be marked as done. This means that you claim

Processed: block 860861 with 861204

Processing commands for cont...@bugs.debian.org: > block 860861 with 861204 Bug #860861 [open-vm-tools-desktop] run-vmblock\x2dfuse.mount present but not enabled Bug #860875 [open-vm-tools-desktop] open-vm-tools-desktop: run-vmblock\x2dfuse.mount fails to start during boot 860861 was not

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

Package: init-system-helpers Version: 1.47 Severity: serious Tags: patch Hi, to fix #856429 I need to handle a unit with an escaped character correctly in the maintainer scripts generated by dh_systemd*. Unfortunately deb-systemd-invoke does not quote the unit name properly in a systemctl call,

Bug#861112: xsane: always crashes on start

Hi, Seems to happen also with scanimage: $ scanimage -L scanimage: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed. Aborted A.

Processed: severity of 860861 is serious

Processing commands for cont...@bugs.debian.org: > severity 860861 serious Bug #860861 [open-vm-tools-desktop] run-vmblock\x2dfuse.mount present but not enabled Bug #860875 [open-vm-tools-desktop] open-vm-tools-desktop: run-vmblock\x2dfuse.mount fails to start during boot Severity set to

Bug#860691: jnr-posix: FTBFS on i386: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.ho

forwarded 860691 https://github.com/jnr/jnr-posix/issues/99 thanks I have forwarded this bug report upstream. I can confirm that two tests fail on i386 but succeed on amd64. The version in experimental is also affected. Four tests are failing here. If we can't come up with a better solution, we

Processed: Re: jnr-posix: FTBFS on i386: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven

Processing commands for cont...@bugs.debian.org: > forwarded 860691 https://github.com/jnr/jnr-posix/issues/99 Bug #860691 [src:jnr-posix] jnr-posix: FTBFS on i386: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp

Bug#860940: marked as done (minicom: CVE-2017-7467: Out of bounds write in vt100.c)

Your message dated Tue, 25 Apr 2017 19:47:15 + with message-id and subject line Bug#860940: fixed in minicom 2.7-1+deb8u1 has caused the Debian Bug report #860940, regarding minicom: CVE-2017-7467: Out of bounds write in vt100.c to be marked as done. This

Bug#858546: marked as done (CVE-2017-5029: Integer overflow in xsltAddTextString)

Your message dated Tue, 25 Apr 2017 19:47:14 + with message-id and subject line Bug#858546: fixed in libxslt 1.1.28-2+deb8u3 has caused the Debian Bug report #858546, regarding CVE-2017-5029: Integer overflow in xsltAddTextString to be marked as done.

Bug#859143: marked as done (kup: please update to v0.3.6 due changes on k.o)

Your message dated Tue, 25 Apr 2017 19:47:14 + with message-id and subject line Bug#859143: fixed in kup 0.3.2-2 has caused the Debian Bug report #859143, regarding kup: please update to v0.3.6 due changes on k.o to be marked as done. This means that you

Bug#857343: marked as done (logback: CVE-2017-5929: serialization vulnerability affecting the SocketServer and ServerSocketReceiver components)

Your message dated Tue, 25 Apr 2017 19:47:15 + with message-id and subject line Bug#857343: fixed in logback 1:1.1.2-1+deb8u1 has caused the Debian Bug report #857343, regarding logback: CVE-2017-5929: serialization vulnerability affecting the

Bug#858914: marked as done (CVE-2017-5929: serialization vulnerability in SocketServer and ServerSocketReceiver)

Your message dated Tue, 25 Apr 2017 19:47:15 + with message-id and subject line Bug#857343: fixed in logback 1:1.1.2-1+deb8u1 has caused the Debian Bug report #857343, regarding CVE-2017-5929: serialization vulnerability in SocketServer and

Bug#849098: marked as done (llvm-toolchain-3.9: Please add ELF symbols versions to the libraries)

Your message dated Tue, 25 Apr 2017 16:35:51 + with message-id and subject line Bug#849098: fixed in llvm-toolchain-3.8 1:3.8.1-22 has caused the Debian Bug report #849098, regarding llvm-toolchain-3.9: Please add ELF symbols versions to the libraries to

Bug#861180: shc: infinite loop does not work properly

Thanks Eriberto for the offer. I don't know how fast Francisco can response. Javier, could you see if you can do anything? Thanks. On Tue, Apr 25, 2017 at 12:24 PM, Eriberto wrote: > 2017-04-25 13:09 GMT-03:00 Tong Sun : > > Thanks for

Bug#861180: shc: infinite loop does not work properly

2017-04-25 13:09 GMT-03:00 Tong Sun : > Thanks for the detailed steps Eriberto, forwarding to the upstream author. > > Francisco, could you take a look at it please? > > Thanks This bug could be solved soon to avoid shc be excluded from next Debian Stable. I can

Bug#861189: keystone: CVE-2017-2673: federated user gets wrong role

Source: keystone Version: 2:10.0.0-8 Severity: grave Tags: patch security upstream Hi, the following vulnerability was published for keystone. CVE-2017-2673[0]: federated user gets wrong role If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities &

Bug#861180: shc: infinite loop does not work properly

Thanks for the detailed steps Eriberto, forwarding to the upstream author. Francisco, could you take a look at it please? Thanks On Tue, Apr 25, 2017 at 10:20 AM, Eriberto Mota wrote: > 2017-04-25 10:42 GMT-03:00 Tong Sun : > > Hi

Bug#858803: [Pkg-leofs-devel] Bug#858803: erlang-cowboy: Cowboy 2.0 != Cowboy 1.0

Top posting because I'm mobile. In short, you're confusing API changes with ABI changes. ABI is irrelevant for Erlang since it's interpreted. I'll reply more in depth later the exact API changes that break existing code. But frankly anything written for Cowboy 1.0 will NOT work for Cowboy 2.0

Bug#861173: marked as done (python-dogpile.cache: Non-determistically FTBFS due to unreliable timing in tests)

Your message dated Tue, 25 Apr 2017 16:04:05 + with message-id and subject line Bug#861173: fixed in python-dogpile.cache 0.6.2-5 has caused the Debian Bug report #861173, regarding python-dogpile.cache: Non-determistically FTBFS due to unreliable timing

Bug#823170: [Request received] Bug#823170: Info received ([Request received] Bug#823170: Info received ([Request received] Bug#823170: Info received ([Request received] Bug#82317...

##- Please type your reply above this line -## Your request (133) has been received and is being reviewed by our support staff. To add additional comments, reply to this email. [image: 823170] *823170* Apr 25, 22:57 +07 Thank you for the additional information you have supplied regarding

Bug#823170: [Request received] Bug#823170: Info received ([Request received] Bug#823170: Info received ([Request received] Bug#823170: Info received ([Request received] Bug#82317...

##- Please type your reply above this line -## Your request (132) has been received and is being reviewed by our support staff. To add additional comments, reply to this email. [image: 823170] *823170* Apr 25, 22:54 +07 Thank you for the additional information you have supplied regarding

Bug#823170:

Bug#823170: [Request received] Bug#823170: Info received ([Request received] Bug#823170: Info received ([Request received] Bug#823170: Info received ()))

##- Please type your reply above this line -## Your request (131) has been received and is being reviewed by our support staff. To add additional comments, reply to this email. [image: 823170] *823170* Apr 25, 22:51 +07 Thank you for the additional information you have supplied regarding

Bug#823170: [Request received] Bug#823170: Info received ([Request received] Bug#823170: Info received ())

##- Please type your reply above this line -## Your request (130) has been received and is being reviewed by our support staff. To add additional comments, reply to this email. [image: 823170] *823170* Apr 25, 22:49 +07 Thank you for the additional information you have supplied regarding

Bug#823170: [Request received] Bug#823170: Info received ()

##- Please type your reply above this line -## Your request (129) has been received and is being reviewed by our support staff. To add additional comments, reply to this email. [image: 823170] *823170* Apr 25, 22:45 +07 Thank you for the additional information you have supplied regarding

Bug#823170:

Bug#790796: sensord: RRD data loss

On 2017-04-25 17:22:37 +0200, Aurelien Jarno wrote: > While that might work (provided we keep multiple versions of the file), > I think the data are not really usable as each period will have a > different format. The real way to fix that would be to use one RRD file > per sensor, but it becomes a

Bug#790796: sensord: RRD data loss

On 2017-04-12 12:24, Paul Wise wrote: > This was an unfortunate outcome for those of us who use sensord but do > not use the RRD mode at all. I think it would have been better to just > disable the RRD mode, but that wouldn't have been the right solution. What's your use case for sensord without

Processed: Re: [Pkg-javascript-devel] Bug#861172: node-jsonstream FTBFS in stretch: Build dependency node-tape is not available

Processing control commands: > owner -1 ro...@debian.org Bug #861172 [src:node-jsonstream] node-jsonstream FTBFS in stretch: Build dependency node-tape is not available Owner recorded as ro...@debian.org. -- 861172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861172 Debian Bug Tracking

Processed: Add missing sid tag

Processing commands for cont...@bugs.debian.org: > tags 861180 sid Bug #861180 [shc] shc: infinite loop does not work properly Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 861180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861180 Debian

Bug#861172: [Pkg-javascript-devel] Bug#861172: node-jsonstream FTBFS in stretch: Build dependency node-tape is not available

control: owner -1 ro...@debian.org On Tue, Apr 25, 2017 at 2:10 PM, Adrian Bunk wrote: > Source: node-jsonstream > Version: 1.0.3-3 > Severity: serious > > node-jsonstream build-depends on node-tape, which is not in stretch. > > -- > Pkg-javascript-devel mailing list >

Processed: Version tracking fix

Processing commands for cont...@bugs.debian.org: > notfound 848694 1.7~git20150920 Bug #848694 [libroken18-heimdal] libroken18-heimdal >= 1.7~git20150920 removed two symbols There is no source info for the package 'libroken18-heimdal' at version '1.7~git20150920' with architecture '' Unable to

Bug#858803: [Pkg-leofs-devel] Bug#858803: erlang-cowboy: Cowboy 2.0 != Cowboy 1.0

Control: notfound -1 2.0.0~pre.1+dfsg1-2 Dear Chris, On 03/27/2017 04:49 AM, Chris Pacejo wrote: > Package: erlang-cowboy > Version: 2.0.0~pre.1+dfsg1-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > For some reason, erlang-cowboy source has been updated

Processed: Re: [Pkg-leofs-devel] Bug#858803: erlang-cowboy: Cowboy 2.0 != Cowboy 1.0

Processing control commands: > notfound -1 2.0.0~pre.1+dfsg1-2 Bug #858803 [erlang-cowboy] erlang-cowboy: Cowboy 2.0 != Cowboy 1.0 No longer marked as found in versions erlang-cowboy/2.0.0~pre.1+dfsg1-2. -- 858803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858803 Debian Bug Tracking

Bug#858803: marked as done (erlang-cowboy: Cowboy 2.0 != Cowboy 1.0)

Your message dated Tue, 25 Apr 2017 16:32:54 +0200 with message-id and subject line Re: [Pkg-leofs-devel] Bug#858803: erlang-cowboy: Cowboy 2.0 != Cowboy 1.0 has caused the Debian Bug report #858803, regarding erlang-cowboy: Cowboy 2.0 !=

Bug#860627: The issue looks like not enough RAM

Hi, As much as I can tell, it looks like to me that there's random crashes on i386 because of the lack of RAM. It looks like the test suite needs more than i386 can offer. Indeed, removing the --parallel option when running the tests seem to improve the situation. Though I'm not convince that

Processed: OpenStack i386 FTBFS are of severity important

Processing commands for cont...@bugs.debian.org: > severity 860627 important Bug #860627 [src:nova] nova: FTBFS on i386: Test failures Severity set to 'important' from 'serious' > severity 860642 important Bug #860642 [src:cinder] cinder: FTBFS on i386: Test failures Severity set to 'important'

Bug#861180: shc: infinite loop does not work properly

2017-04-25 10:42 GMT-03:00 Tong Sun : > Hi Eriberto, > > Is your infinite loop problem exactly as described in > https://sfxpt.wordpress.com/2014/02/23/shc-3-8-9-is-not-usable/ ? Hi Tong! Thanks for your quick reply. No, not embedded here. See the following

Bug#861180: shc: infinite loop does not work properly

Hi Eriberto, Is your infinite loop problem exactly as described in https://sfxpt.wordpress.com/2014/02/23/shc-3-8-9-is-not-usable/ ? On Tue, Apr 25, 2017 at 9:24 AM, Joao Eriberto Mota Filho < eribe...@debian.org> wrote: > Package: shc > Version: 3.8.9b-1+b1 > Severity: grave > Tags: upstream

Processed: ufoai 2.5-2 pending

Processing commands for cont...@bugs.debian.org: > tags 860680 pending Bug #860680 [ufoai-tools] ufoai: map compiler ufo2map segfaults Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 860680:

Bug#860680: ufoai: map compiler ufo2map segfaults

On Fri, 21 Apr 2017 18:16:48 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?= wrote: [...] > > I think this crash is caused by this part in LoadMapFile: > > char entityString[MAX_TOKEN_CHARS]; > const char* ump = GetUMPName(filename); > if (ump != nullptr) >

Bug#861180: shc: infinite loop does not work properly

Package: shc Version: 3.8.9b-1+b1 Severity: grave Tags: upstream stretch Justification: renders package unusable Dear Maintainer, The shc command is generating executables which can not be used over Stretch and Sid. After generate the executable, when running, the program.sh.x enter in an

Bug#861178: nodejs-dev: broken/uninstallable backports

Severity: grave Version: 4.7.2~dfsg-2~bpo8+1 Package: nodejs-dev nodejs-dev in jessie-backports depends on libssl1.0-dev, which does not exist. -- Mit freundlichen Grüßen Bernd Zeimetz Systems Engineer Debian Developer conova communications GmbH Web| http://www.conova.com/ E-Mail |

Bug#861175: cairocffi: Please drop Build-Depends and Recommends on xcffib

Source: cairocffi Version: 0.7.2-1 Severity: grave Justification: stretch-is-blocker / Depends on Source that FTBFS Hi, We have unfortunately learned that we cannot compile xcffib (neither in unstable nor in stretch). Fixing it requires changes to more than one package and none of these changes

Bug#861173: python-dogpile.cache: Non-determistically FTBFS due to unreliable timing in tests

Source: python-dogpile.cache Version: 0.6.2-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, python-dogpile.cache's testsuite appears to use

Bug#861172: node-jsonstream FTBFS in stretch: Build dependency node-tape is not available

Source: node-jsonstream Version: 1.0.3-3 Severity: serious node-jsonstream build-depends on node-tape, which is not in stretch.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 857085 861167 Bug #857085 [src:ldc] terminix FTBFS on armhf: Error executing /usr/bin/ldc2: Segmentation fault Bug #861167 [src:ldc] ldc: ftbfs on i386: ldc segfaults Set Bug forwarded-to-address to

Bug#861108: live-build: stretch image produced with default configuration does not boot

I confirm the problem. I have looked into it and in fact i had two problems. First, the initrd was broken. The kernel said "write error" uncompressing initrd. Cause seems to be the intel_microcode package, as disabling it fixes this problem. The broken initrd had just intel files in it.

Bug#860580: marked as done (clang-3.8: broken symlink: /usr/bin/scan-build-py-3.8 -> ../share/clang/scan-build-py-3.8/bin/scan-build)

Your message dated Tue, 25 Apr 2017 12:22:21 +0200 with message-id <20170425102219.ga3...@ugent.be> and subject line Re: clang-3.8: broken symlink: /usr/bin/scan-build-py-3.8 -> ../share/clang/scan-build-py-3.8/bin/scan-build has caused the Debian Bug report #860580, regarding clang-3.8: broken

Bug#861169: opendkim: Systemd service file should not specify a socket

Source: opendkim Version: 2.11.0~alpha-9 Severity: grave Justification: renders package unusable Dear Maintainer, I already opened a ticket on a this issue but there was a misunderstanding and I open it again with new arguments. The problem is with the service file

Bug#848694: libroken18-heimdal >= 1.7~git20150920 removed two symbols

Brian May writes: > In this case I don't think interference with gcrypt is likely, as the > only package in Debian that uses Heimdal is OpenAFS, and neither Heimdal > or OpenAFS depend on heimdal. Might be a problem - at least in theory > for locally built packages however.

Bug#848694: libroken18-heimdal >= 1.7~git20150920 removed two symbols

Sergio Gelato writes: > That's what my suggested Breaks: addition was intended to document and > enforce. > > IIRC the issue came to my attention while backporting openafs 1.8.0~pre1 > to jessie from experimental. One then has a choice between reverting a > patch to

Bug#861167: ldc: ftbfs on i386: ldc segfaults

Source: ldc Version: 1:1.1.1-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, ldc 1:1.1.1-2 and 1:1.1.1-3 ftbfs on i386 buildds with a segfault. Logs at https://buildd.debian.org/status/fetch.php?pkg=ldc=i386=1%3A1.1.1-2=1492986438=0 and

Bug#861121: marked as done (weechat: CVE-2017-8073)

Your message dated Tue, 25 Apr 2017 09:34:14 + with message-id and subject line Bug#861121: fixed in weechat 1.7-3 has caused the Debian Bug report #861121, regarding weechat: CVE-2017-8073 to be marked as done. This means that you claim that the problem

Bug#861165: padre does not start - DBD::SQLite::db do failed ...

Package: padre Version: 1.00+dfsg-3 Severity: grave Justification: renders package unusable padre fails to start with the following info left in the terminal window: DBD::SQLite::db do failed: Safety level may not be changed inside a transaction at (eval 1907) line 37. Perl exited with active

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > forwarded 860952 d...@rarlab.com Bug #860952 [rar] Statically linked to glibc, in breach of policy and copyright Set Bug forwarded-to-address to 'd...@rarlab.com'. > done Unknown command or malformed arguments to command. > End of message,

Bug#861152: nagstamon: InsecureRequestWarning: Unverified HTTPS request is being made.

Control: forwarded -1 https://github.com/HenriWahl/Nagstamon/issues/302 Control: tags -1 + upstream confirmed Hi Paul, On Tue, 25 Apr 2017 11:27:01 +0800 Paul Wise wrote: > Severity: serious > Tags: security > > When I run nagstamon from a terminal against the Debian nagios I

Processed: Re: nagstamon: InsecureRequestWarning: Unverified HTTPS request is being made.

Processing control commands: > forwarded -1 https://github.com/HenriWahl/Nagstamon/issues/302 Bug #861152 [nagstamon] nagstamon: InsecureRequestWarning: Unverified HTTPS request is being made. Set Bug forwarded-to-address to 'https://github.com/HenriWahl/Nagstamon/issues/302'. > tags -1 +

Processed: severity of 848694 is grave

Processing commands for cont...@bugs.debian.org: > # Unhandled ABI breakage > severity 848694 grave Bug #848694 [libroken18-heimdal] libroken18-heimdal >= 1.7~git20150920 removed two symbols Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need

Bug#829255: oss4-dkms: Fails to build for 4.6.0-1-amd64

Package: oss4-dkms Followup-For: Bug #829255 Hello, the patch works for me with linux 4.9 and 4.10. Please uppload fixed package to distributions that use the new kernels. Thanks Michal -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing'), (700,

Bug#857085: [Pkg-d-devel] Bug#857085: terminix FTBFS on armhf: Error executing /usr/bin/ldc2: Segmentation fault

2017-04-25 8:27 GMT+02:00 Iain Buclaw : > [...] > If running in gdb makes the problem go away, have you tried turning on > core dumps in buildd? Yes, without useful results: https://github.com/ldc-developers/ldc/issues/2022#issuecomment-288481397

Bug#857085: [Pkg-d-devel] Bug#857085: terminix FTBFS on armhf: Error executing /usr/bin/ldc2: Segmentation fault

On 24 April 2017 at 20:04, Matthias Klumpp wrote: > Hi! > > Here is a short summary on the bug: > > 1) It only happens on Debian buildds, Fedora and Arch are not > affected. I examined the build logs and the environments are > relatively similar, with a notable difference