Bug#859660: Bug#859660: artemis running issue

Hi Java developers, is there any known issue with running JARs via symlink to /usr/bin? I suspect this is the problem with this bug but I wonder what might be the recommended way from Java team about this way to start Java programs that used to work but is not always relieable. Kind regards

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

On 04/21/2017 08:04 AM, Salvatore Bonaccorso wrote: Hi Lars, On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote: Hi, I lost internet connectivity where I am right now, so probably unable to get this done until Monday. Could maybe use the previous debdiff for Jessie if you're ok wi

Processed: notfound 860303 in 2.6.3-3.1, notfound 860303 in 2.4.9-1.1, notfound 860303 in 2.6.3-3 ...

Processing commands for cont...@bugs.debian.org: > notfound 860303 2.6.3-3.1 Bug #860303 {Done: Moritz Mühlenhoff } [src:freetype] freetype: CVE-2016-10328: heap-buffer-overflow in cff_parser_run() No longer marked as found in versions freetype/2.6.3-3.1. > notfound 860303 2.4.9-1.1 Bug #860303 {

Bug#860303: closed by Moritz Mühlenhoff (Re: Bug#860303: freetype: CVE-2016-10328: heap-buffer-overflow in cff_parser_run())

On Sun, Apr 23, 2017 at 09:00:10PM +, Debian Bug Tracking System wrote: > Actually, further investigation showed that this only affected git head > for a day or so (also confirmed by upstream). I've updated the > security tracker with the necessary information. > > Salvatore, please cancel you

Bug#860465: marked as done (slim: Missing handling of plymouth (#782456))

Your message dated Mon, 24 Apr 2017 03:19:26 + with message-id and subject line Bug#860465: fixed in slim 1.3.6-5 has caused the Debian Bug report #860465, regarding slim: Missing handling of plymouth (#782456) to be marked as done. This means that you claim that the problem has been dealt wi

Processed: user debian...@lists.debian.org, usertagging 861021, affects 858958, affects 861030 ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 861021 piuparts There were no usertags set. Usertags are now: piuparts. > affects 858958 + science-robotics Bug #858958 [morse-simulator-d

Bug#857360: gitlab_8.13.11+dfsg-4 no longer available, unable to install

Got it working. Based on the unicorn logs, I turned off listening for port 1443 (depend on only socket listen) for it to work. A kludge, but it is something quick and dirty I can investigate later.

Bug#833114: marked as done ("RuntimeError: OrderedDict mutated during iteration" on some feeds)

Your message dated Sun, 23 Apr 2017 23:04:38 + with message-id and subject line Bug#833114: fixed in rss2email 1:3.9-2.1 has caused the Debian Bug report #833114, regarding "RuntimeError: OrderedDict mutated during iteration" on some feeds to be marked as done. This means that you claim that

Bug#861040: camping: broken symlink: /usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf -> ../../../../fonts/truetype/lato/Lato-RegularItalic.ttf

Package: camping Version: 2.1.580-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m47.8s ERROR: FAIL: Broken symlinks: /usr/sh

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

Source: gpsshogi Version: 0.7.0-1.1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=gpsshogi&arch=i386&ver=0.7.0-1.1&stamp=1492885164&raw=0 ... No patches applied rm -rf ./.pc rm -f debian/stamp-patch* for dir in lib/gui sample/viewer ; do \ [ ! -f $dir/Makefile ] || /usr/bin/m

Bug#861032: emacs24 frequently FTBFs on ppc64el

Source: emacs24 Version: 24.5+1-9 Severity: serious https://buildd.debian.org/status/logs.php?pkg=emacs24&arch=ppc64el 3 build failures out of the latest 4 build attempts, failing in different places - something is going wrong here. Could this be related to #854799, or what is going wrong here?

Bug#861001: marked as done (libcoarrays0d: broken symlink: /usr/lib/x86_64-linux-gnu/libcaf_mpi.so.0d -> libcaf_mpi.so.1.8.6)

Your message dated Sun, 23 Apr 2017 21:20:00 + with message-id and subject line Bug#861001: fixed in open-coarrays 1.8.6-2 has caused the Debian Bug report #861001, regarding libcoarrays0d: broken symlink: /usr/lib/x86_64-linux-gnu/libcaf_mpi.so.0d -> libcaf_mpi.so.1.8.6 to be marked as done.

Bug#860853: marked as done (open-coarrays FTBFS on armel/armhf: Can't rename module file '../../mod/opencoarrays.mod0' to '../../mod/opencoarrays.mod': No such file or directory)

Your message dated Sun, 23 Apr 2017 21:20:00 + with message-id and subject line Bug#860853: fixed in open-coarrays 1.8.6-2 has caused the Debian Bug report #860853, regarding open-coarrays FTBFS on armel/armhf: Can't rename module file '../../mod/opencoarrays.mod0' to '../../mod/opencoarrays.

Bug#861030: gfsview: broken symlink: /usr/share/gfsview/fonts/Garuda.ttf -> ../../fonts/opentype/tlwg/Garuda.otf

Package: gfsview Version: 20121130+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m28.0s ERROR: FAIL: Broken symlinks: /

Bug#860303: marked as done (freetype: CVE-2016-10328: heap-buffer-overflow in cff_parser_run())

Your message dated Sun, 23 Apr 2017 22:57:42 +0200 with message-id <20170423205742.f3j6bqbyusigmgrg@pisco.westfalen.local> and subject line Re: Bug#860303: freetype: CVE-2016-10328: heap-buffer-overflow in cff_parser_run() has caused the Debian Bug report #860303, regarding freetype: CVE-2016-1032

Bug#861029: AttributeError: When using gi.repository you must not import static modules like "gobject"

Package: aptdaemon Version: 1.1.1-4+deb8u1 Severity: grave Justification: renders package unusable $ aptdcon Traceback (most recent call last): File "/usr/bin/aptdcon", line 25, in import aptdaemon.console File "/usr/lib/python3/dist-packages/aptdaemon/console.py", line 49, in from

Bug#858380: marked as done (llvm-toolchain-3.7: FTBFS in stretch (failing tests))

Your message dated Sun, 23 Apr 2017 22:47:15 +0200 with message-id <11480037-fede-ab34-e669-14f896f12...@debian.org> and subject line fixed has caused the Debian Bug report #858380, regarding llvm-toolchain-3.7: FTBFS in stretch (failing tests) to be marked as done. This means that you claim that

Processed: fixed

Processing commands for cont...@bugs.debian.org: > fixed 858380 1:3.7.1-4~exp1 Bug #858380 [src:llvm-toolchain-3.7] llvm-toolchain-3.7: FTBFS in stretch (failing tests) Marked as fixed in versions llvm-toolchain-3.7/1:3.7.1-4~exp1. > thanks Stopping processing here. Please contact me if you need

Processed: tagging 858366

Processing commands for cont...@bugs.debian.org: > tags 858366 + pending Bug #858366 [libwhy-coq] libwhy-coq: sourceful upload needed to update coq dependency Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 858366: http://bugs.debian.org/cgi

Bug#861027: gprolog: Trivial code fails on amd64

Package: gprolog Version: 1.4.5-4.1+b1 Severity: grave Justification: renders package unusable Hi, Something seems to be very wrong with gprolog on amd64. Consider this trivial Prolog code: parent(david, john). parent(jim, david). grandparent(A, B) :- parent(A, X), parent(X, B). When I try to u

Bug#861028: morse-simulator: abuses Conflicts to circument Policy 10.1 on /usr/bin/morse collision with morse

Package: morse-simulator Version: 0.5.2-1 Severity: serious Hi, both morse and morse-simulator ship /usr/bin/morse Package: morse Description-en: training program about morse-code for aspiring radio hams Package: morse-simulator Description-en: Multi-OpenRobot Simulation Engine Confli

Bug#860700: bitz-server: FTBFS on i386: dh_makeshlibs: failing due to earlier errors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/23/2017 02:51 PM, Jörg Frings-Fürst wrote: > I have strip the symbols files from the buildlogs for all architectures now. > Should I add them into the RC-Bugfix or later into the next upload? I fear that the symbols file generated from the la

Bug#861024: gerris: broken symlinks: /usr/lib/gerris/(m4.awk|gfs2tex.py) -> ../../share/gerris/lib/$1

Package: gerris Version: 20131206+dfsg-13 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m52.3s ERROR: FAIL: Broken symlinks: /

Processed: Re: [Pkg-fonts-devel] Bug#860654: fonts-ocr-b: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

Processing control commands: > severity -1 normal Bug #860654 [src:fonts-ocr-b] fonts-ocr-b: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity Severity set to 'normal' from 'serious' > block -1 by 831425 Bug #860654 [src:fonts-ocr-b] fonts-ocr-b: FTBFS on i386: E: Bu

Bug#860654: [Pkg-fonts-devel] Bug#860654: fonts-ocr-b: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

Control: severity -1 normal Control: block -1 by 831425 Am Mittwoch, den 19.04.2017, 09:15 +0200 schrieb Lucas Nussbaum: > E: Build killed with signal TERM after 150 minutes of inactivity I fail to reproduce this on amd64, so I am sure this is due to the known issue of fontforge exporting malform

Bug#859672: marked as done ([software-properties-gtk] Completely unusable and buggy in stretch, fix it or remove it)

Your message dated Sun, 23 Apr 2017 19:49:52 + with message-id and subject line Bug#859672: fixed in python-apt 1.4.0~beta3 has caused the Debian Bug report #859672, regarding [software-properties-gtk] Completely unusable and buggy in stretch, fix it or remove it to be marked as done. This m

Processed (with 1 error): forcibly merging 859672 692542

Processing commands for cont...@bugs.debian.org: > forcemerge 859672 692542 Bug #859672 [python-apt] [software-properties-gtk] Completely unusable and buggy in stretch, fix it or remove it Unable to merge bugs because: package of #692542 is 'src:python-apt' not 'python-apt' Failed to forcibly mer

Processed: unarchiving 826684, cloning 826684, reopening -1 ..., reassign -1 to spin

Processing commands for cont...@bugs.debian.org: > unarchive 826684 Bug #826684 {Done: Andreas Tille } [staden] staden,spin: error when trying to install together Unarchived Bug 826684 > clone 826684 -1 Bug #826684 {Done: Andreas Tille } [staden] staden,spin: error when trying to install togethe

Processed: Bug#859672 in python-apt marked as pending

Processing control commands: > tag 859672 pending Bug #859672 [python-apt] [software-properties-gtk] Completely unusable and buggy in stretch, fix it or remove it Added tag(s) pending. -- 859672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859672 Debian Bug Tracking System Contact ow...@bu

Bug#859672: in python-apt marked as pending

Control: tag 859672 pending Hello, Bug #859672 in python-apt reported by you has been fixed in the Git repository. You can see the commit message below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/apt/python-apt.git/diff/?id=4fd09c2 (this message was generated

Bug#861006: marked as done (imms FTBFS: undefined reference to ___data_svm_similarity)

Your message dated Sun, 23 Apr 2017 19:19:11 + with message-id and subject line Bug#861006: fixed in imms 3.1.0~svn301-5 has caused the Debian Bug report #861006, regarding imms FTBFS: undefined reference to ___data_svm_similarity to be marked as done. This means that you claim that the probl

Processed: tagging 744753, tagging 854727

Processing commands for cont...@bugs.debian.org: > # propagate stretch-ignore to jessie-ignore > tags 744753 + jessie-ignore Bug #744753 [anacron] anacron: Anacron not triggered when system resumes under systemd Bug #767092 [anacron] anacron fails to run when laptop goes out of sleep Added tag(s)

Processed: tagging 858037

Processing commands for cont...@bugs.debian.org: > # works fine in jessie > tags 858037 + sid Bug #858037 [src:ikarus] ikarus FTBFS on i386: recipe for target 'ikarus.boot' failed (Segmentation fault) Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: tagging 860691

Processing commands for cont...@bugs.debian.org: > tags 860691 + confirmed Bug #860691 [src:jnr-posix] 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.home=/

Processed: reassign 859672 to python-apt

Processing commands for cont...@bugs.debian.org: > reassign 859672 python-apt Bug #859672 [software-properties-gtk] [software-properties-gtk] Completely unusable and buggy in stretch, fix it or remove it Bug reassigned from package 'software-properties-gtk' to 'python-apt'. No longer marked as fo

Bug#861006: imms FTBFS: undefined reference to ___data_svm_similarity

On 2017-04-23 17:30, Adrian Bunk wrote: > g++ immsd.o socketserver.o libimmscore.a libmodel.a `pkg-config glib-2.0 > --libs` -L. -lXss -lXext -lX11 -lsqlite3 -lz -lpcre -ltorch -ltag > -L/usr/X11R6/lib -Wl,-z,relro -L/usr/X11R6/lib -o immsd > libmodel.a(model.o): In function `SVMSimilarityMode

Bug#766397: marked as done (emacs/gnus: Uses s_client to for SSL.)

Your message dated Sun, 23 Apr 2017 18:49:08 + with message-id and subject line Bug#766397: fixed in emacs25 25.1+1-4 has caused the Debian Bug report #766397, regarding emacs/gnus: Uses s_client to for SSL. to be marked as done. This means that you claim that the problem has been dealt with.

Bug#860303: freetype: diff for NMU version 2.6.3-3.2

Control: tags 860303 + pending Dear maintainer, I've prepared an NMU for freetype (versioned as 2.6.3-3.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Salvatore diff -u freetype-2.6.3/debian/changelog freetype-2.6.3/debian/changelog --- freetyp

Processed: freetype: diff for NMU version 2.6.3-3.2

Processing control commands: > tags 860303 + pending Bug #860303 [src:freetype] freetype: CVE-2016-10328: heap-buffer-overflow in cff_parser_run() Added tag(s) pending. -- 860303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860303 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Processed: Re: Bug#860303: freetype: CVE-2016-10328: heap-buffer-overflow in cff_parser_run()

Processing control commands: > severity -1 serious Bug #860303 [src:freetype] freetype: CVE-2016-10328: heap-buffer-overflow in cff_parser_run() Severity set to 'serious' from 'important' -- 860303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860303 Debian Bug Tracking System Contact ow...

Bug#860630: marked as done (python-pyelftools: FTBFS on i386: Test failures)

Your message dated Sun, 23 Apr 2017 18:03:45 + with message-id and subject line Bug#860630: fixed in python-pyelftools 0.24-2 has caused the Debian Bug report #860630, regarding python-pyelftools: FTBFS on i386: Test failures to be marked as done. This means that you claim that the problem ha

Bug#859262: Re: freezes Orca screen reader

Hi Joanmarie, On 23-04-17 15:32, Joanmarie Diggs wrote: > That segfault is an AT-SPI2 bug. And apparently an elusive one. > https://bugzilla.gnome.org/show_bug.cgi?id=767074 Just to get things straight, do you mean here that you do or that you don't believe this segfault has anything to do with t

Bug#858794: gmime: Tests contain a MIME message with a (presumably non-free) Playboy/Hustler/something photo

On Sat 2017-04-22 18:48:00 +, Niels Thykier wrote: > On Sun, 26 Mar 2017 23:06:51 +0300 Sami Liedes wrote: >> $ apt-get source gmime-bin >> $ cd gmime-2.6.22/tests/ >> $ mkdir attachments >> $ cd attachments >> $ cat ../message-partial.* ../*.eml |ripmime -i - >> $ ls -l *.jpg >> -rw--- 1

Processed (with 1 error): Re: gravit segmentation violation

Processing commands for cont...@bugs.debian.org: > tags 860446 + reproducible Unknown tag/s: reproducible. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixe

Bug#860446: gravit segmentation violation

tags 860446 + reproducible severity 860446 normal thanks On 21/04/17 01:16, Tim Retout wrote: > retitle 860446 gravit: Segmentation violation on start (on i386?) > tags 860446 moreinfo > thanks > > For what it's worth, gravit starts for me on amd64, with intel graphics. > > The last call in the lt

Bug#858633: closed by Innocent De Marchi (Bug#858633: fixed in dmaths 4.3.0.0+dfsg1-1)

Hi Adrian, > This fixed the bug for unstable, but the new upstream version won't be > acceptable for fixing the bug in stretch. > > Please make an additional upload to stretch only fixing #858633 > on top of 3.7.0.0+dfsg1-1 > > It is not possible: the error is only solved by updating the sources

Bug#861006: imms FTBFS: undefined reference to ___data_svm_similarity

Source: imms Version: 3.1.0~svn301-4 Severity: serious https://buildd.debian.org/status/package.php?p=imms&suite=sid ... g++ immsd.o socketserver.o libimmscore.a libmodel.a `pkg-config glib-2.0 --libs` -L. -lXss -lXext -lX11 -lsqlite3 -lz -lpcre -ltorch -ltag -L/usr/X11R6/lib -Wl,-z,relro -L/

Bug#860662: mlucas: FTBFS on i386: dh_auto_test: make -j64 check VERBOSE=1 returned exit code 2

Bug #860664: signature.asc Description: PGP signature

Bug#860662: mlucas: FTBFS on i386: dh_auto_test: make -j64 check VERBOSE=1 returned exit code 2

Alex Vong writes: > Upon inspection, it seems the problem is caused by some serious memory > leaks: >>> executipthread_create:: Cannot allocate memory >>> FAIL self_test.test (exit status: 139) > > Building with '-fsanitize=leak' seems to confirm it: [...] After further testing, I think the abov

Bug#856720: diaspora{, -installer}: fails to install: Errno::EEXIST: File exists @ dir_s_mkdir - /usr/share/diaspora/tmp

On Fri, 31 Mar 2017 00:37:12 +0200 Andreas Beckmann wrote: > Followup-For: Bug #856720 > Control: found -1 0.6.3.0+debian4 > > Hi, > > and there we go again ... Can you confirm if you test system has systemd? That would explain why it is not reproduceable in my local system. signature.asc De

Processed: bug 860986 is forwarded to https://github.com/ldx/python-iptables/issues/182

Processing commands for cont...@bugs.debian.org: > forwarded 860986 https://github.com/ldx/python-iptables/issues/182 Bug #860986 [python-iptables] python-iptables library did not work Set Bug forwarded-to-address to 'https://github.com/ldx/python-iptables/issues/182'. > thanks Stopping processin

Bug#859926: [Tts-project] Bug#859926: speechd-up: fails to install

Le 23/04/2017 à 15:14, Paul Gevers a écrit : > Hi Jean-Philippe, > > On 23-04-17 13:47, MENGUAL Jean-Philippe wrote: >> Given delays, and to avoid autoremoval, maybe we could remove the >> initscript so that the package to be iostallable? And documenting how to >> run it manually? > > I propose

Bug#860992: marked as done (Uninstallable: wrong dependency to kdeinit instead of kinit)

Your message dated Sun, 23 Apr 2017 13:49:06 + with message-id and subject line Bug#860992: fixed in gwenview 4:16.08.3-3 has caused the Debian Bug report #860992, regarding Uninstallable: wrong dependency to kdeinit instead of kinit to be marked as done. This means that you claim that the pr

Processed: tagging 666847, found 857522 in 1:9.10.3.dfsg.P4-12.2, affects 861001

Processing commands for cont...@bugs.debian.org: > tags 666847 - patch Bug #666847 [libapache2-mod-spamhaus] mod-spamhaus: sourceful transition towards Apache 2.4 Removed tag(s) patch. > found 857522 1:9.10.3.dfsg.P4-12.2 Bug #857522 [libbind-export-dev] libbind-export-dev: broken symlinks: /usr

Bug#859262: Re: freezes Orca screen reader

That segfault is an AT-SPI2 bug. And apparently an elusive one. https://bugzilla.gnome.org/show_bug.cgi?id=767074 On 04/23/2017 04:46 AM, Paul Gevers wrote: > Hi Joanmarie, > > Yesterday, I send you a log while Synaptic had not much to do, because I > ran it earlier the same day (so maybe the ori

Bug#859926: [Tts-project] Bug#859926: speechd-up: fails to install

Hi Jean-Philippe, On 23-04-17 13:47, MENGUAL Jean-Philippe wrote: > Given delays, and to avoid autoremoval, maybe we could remove the > initscript so that the package to be iostallable? And documenting how to > run it manually? I proposed that already in this bug, but cobra convinced me to not do

Bug#782456: Bug#860463: nodm: Missing handling of plymouth (#782456)

On Mon, 17 Apr 2017 at 12:05:41 +0200, Niels Thykier wrote: > For init scripts that can be done by the following shell snippet (just > before starting the DM): > > """ > if [ -x /bin/plymouth ] ; then >/bin/plymouth quit > fi > """ Should this say "/bin/plymouth quit --wait"? https://bugs.lau

Bug#860939: node-diffie-hellman: Please clarify security concerns

control: forwarded -1 https://github.com/crypto-browserify/diffie-hellman/issues/22 On Sat, Apr 22, 2017 at 10:32 AM, Chris Lamb wrote: > Source: node-diffie-hellman > Version: 5.0.2-1 > Severity: serious > X-Debbugs-CC: Bastien Roucariès > > Hi, > > I just ACCEPTed node-diffie-hellman from NEW

Bug#861001: libcoarrays0d: broken symlink: /usr/lib/x86_64-linux-gnu/libcaf_mpi.so.0d -> libcaf_mpi.so.1.8.6

Package: libcoarrays0d Version: 1.8.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libcoarrays-dev Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. There is no libcaf_mpi.so.1.8.6 in any package. ldconfig

Processed: libcoarrays0d: broken symlink: /usr/lib/x86_64-linux-gnu/libcaf_mpi.so.0d -> libcaf_mpi.so.1.8.6

Processing control commands: > affects -1 + libcoarrays-dev Bug #861001 [libcoarrays0d] libcoarrays0d: broken symlink: /usr/lib/x86_64-linux-gnu/libcaf_mpi.so.0d -> libcaf_mpi.so.1.8.6 Added indication that 861001 affects libcoarrays-dev -- 861001: http://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#860700: bitz-server: FTBFS on i386: dh_makeshlibs: failing due to earlier errors

Hello Adrian, Am Samstag, den 22.04.2017, 21:45 +0200 schrieb John Paul Adrian Glaubitz: > Hi Joerg! > > While your updated package version fixes the FTBFS, you are still only > providing > the symbols files for i386 and amd64, for the remaining architectures the > symbols > files are missing a

Bug#837360: marked as done (cuneiform: FTBFS with GCC 6: error: narrowing conversion of '196' from 'int' to 'char' inside { })

Your message dated Sun, 23 Apr 2017 12:33:51 + with message-id and subject line Bug#837360: fixed in cuneiform 1.1.0+dfsg-6 has caused the Debian Bug report #837360, regarding cuneiform: FTBFS with GCC 6: error: narrowing conversion of '196' from 'int' to 'char' inside { } to be marked as don

Bug#781354: marked as done ([cuneiform] Buffer overflow triggered by user supplied image)

Your message dated Sun, 23 Apr 2017 12:33:51 + with message-id and subject line Bug#781354: fixed in cuneiform 1.1.0+dfsg-6 has caused the Debian Bug report #781354, regarding [cuneiform] Buffer overflow triggered by user supplied image to be marked as done. This means that you claim that the

Bug#860739: libghc-xcb-types-dev: cannot parse xcb-proto 1.12

Hi, On 22/04/17 20:48, Niels Thykier wrote: > On Sat, 22 Apr 2017 18:13:50 +0100 James Cowgill >> On Wed, 19 Apr 2017 16:05:12 +0100 James Cowgill wrote: >>> Package: libghc-xcb-types-dev >>> Version: 0.7.1-4 >>> Severity: grave >>> Tags: sid stretch >>> Control: block 839314 by -1 >>> >>> Hi, >

Bug#859926: speechd-up: fails to install

Hi, Given delays, and to avoid autoremoval, maybe we could remove the initscript so that the package to be iostallable? And documenting how to run it manually? Regards, Le 23/04/2017 à 11:04, Paul Gevers a écrit : > Control: reassign -1 speech-dispatcher > Control: retitle -1 breaks with pul

Bug#856720: Patch

On Mon, 17 Apr 2017 14:07:45 + shana...@disroot.org wrote: > Package: diaspora-common > Followup-For: Bug #856720 > Tags: patch > > attaching patch > Shanavas M This is supposed to be created by debian/tmpfiles.d/diaspora.conf and works well with systemd. Hence I could not reproduce locally (

Bug#859262: Re: freezes Orca screen reader

Hi Joanmarie, Yesterday, I send you a log while Synaptic had not much to do, because I ran it earlier the same day (so maybe the original issue wasn't there). Today I tried again, hoping that there were updates to apply, which there were. orca segfaulted on me. Please see the attached stack trace.

Bug#859926: speechd-up: fails to install

Control: reassign -1 speech-dispatcher Control: retitle -1 breaks with pulse-audio as output when spawned by speechd-up from init system Control: affects -1 speechd-up On 22-04-17 22:01, Paul Gevers wrote: > On 22-04-17 21:26, Cobra wrote: >> I was thinking of reassigning to the current speech-di

Processed: Re: Bug#859926: speechd-up: fails to install

Processing control commands: > reassign -1 speech-dispatcher Bug #859926 [speechd-up] speechd-up: fails to install Bug reassigned from package 'speechd-up' to 'speech-dispatcher'. No longer marked as found in versions speechd-up/0.5~20110719-6. Ignoring request to alter fixed versions of bug #8599

Bug#817685: marked as done (tamil-gtk2im: Removal of debhelper compat 4)

Your message dated Sun, 23 Apr 2017 11:04:23 + with message-id and subject line Bug#817685: fixed in tamil-gtk2im 2.2-5 has caused the Debian Bug report #817685, regarding tamil-gtk2im: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been dea

Bug#860992: Uninstallable: wrong dependency to kdeinit instead of kinit

Package: gwenview Version: 4:16.08.3-1 Severity: grave Justification: renders package unusable Hi, the newly added dependency to kdeinit renders the package uninstallable. Only kinit is available in unstable. Regards Michael -- System Information: Debian Release: 9.0 APT prefers mike APT p

Processed (with 5 errors): Re: [Pkg-rust-maintainers] Processed: bugs

Processing commands for cont...@bugs.debian.org: > retitle 860989 cargo: embeds a copy of libgit2 affected by CVE-2016-8568 > CVE-2016-8569 Bug #860989 [cargo] libgit2: CVE-2016-8568 CVE-2016-8569 Changed Bug title to 'cargo: embeds a copy of libgit2 affected by CVE-2016-8568 CVE-2016-8569' from

Processed: bugs

Processing commands for cont...@bugs.debian.org: > clone 840227 -2 Bug #840227 [src:libgit2] libgit2: CVE-2016-8568 CVE-2016-8569 Bug 840227 cloned as bug 860989 > clone 851406 -3 Bug #851406 [src:libgit2] libgit2: CVE-2016-10128 CVE-2016-10129 CVE-2016-10130 Bug 851406 cloned as bug 860990 > reas

Bug#859472: marked as done (khal FTBFS: tests/event_test.py:307: AssertionError)

Your message dated Sun, 23 Apr 2017 09:00:10 + with message-id and subject line Bug#859472: fixed in khal 0.9.5-1 has caused the Debian Bug report #859472, regarding khal FTBFS: tests/event_test.py:307: AssertionError to be marked as done. This means that you claim that the problem has been d

Bug#860046: marked as done (wolfssl: Incomplete debian/copyright?)

Your message dated Sun, 23 Apr 2017 08:52:34 + with message-id and subject line Bug#860046: fixed in wolfssl 3.10.2+dfsg-2 has caused the Debian Bug report #860046, regarding wolfssl: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt

Bug#860986: python-iptables library did not work

Package: python-iptables Version: 0.11.0-2 Severity: serious Justification: required Dear Maintainer: The python-iptables library did not work on my Debian 9. The problem occured likes the following transcript: -- Terminal Output -- <0> [anthon

Bug#860984: khal: Please reference debian/patches/0002-Reference-license-from-copyright-file.patch in debian/copyright

Source: khal Version: 0.9.5-1 Severity: serious X-Debbugs-CC: Filip Pytloun Hi, I just ACCEPTed khal from NEW but noticed it wasn't 100% obvious from debian/copyright that the 0002-Reference-license-from-copyright-file.patch patch existed. Please update your debian/copyright file, at least to p

Bug#860046: wolfssl: Incomplete debian/copyright?

Hi Felix, > Sorry about the oversight. Please find a new upload > on Mentors, closing two bugs. Uploaded :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-