Bug#917807: libcaca: CVE-2018-20544 CVE-2018-20545 CVE-2018-20546 CVE-2018-20547 CVE-2018-20548 CVE-2018-20549

Hi nicoo, On Mon, Mar 11, 2019 at 12:34:56AM +0100, Nicolas Braud-Santoni wrote: > clone 917807 -1 > retitle -1 Orphan libcaca > severity -1 normal > thanks > > > Hi Sam, > > I'm planning on fixing those security issues for Buster. > > Given that you last touched the package in 2014, and

Bug#924291: netrek-client-cow: build can loop indefinitely on failure

Source: netrek-client-cow Version: 3.3.1-1 Severity: serious Justification: breaks build infrastructure When mkkey fails to run, netrek-client-cow has a very bad failure mode. It loops until mkkey succeeds: | until ./mkkey key.cow.linux "Client Of Win" "automatic packaged key"

Bug#861027: marked as done (gprolog: Trivial code fails on amd64)

Your message dated Mon, 11 Mar 2019 03:21:28 + with message-id and subject line Bug#861027: fixed in gprolog 1.4.5.0-1 has caused the Debian Bug report #861027, regarding gprolog: Trivial code fails on amd64 to be marked as done. This means that you claim that the problem has been dealt

Bug#921788: marked as done (libdc1394-22: FTBFS (LaTeX error))

Your message dated Mon, 11 Mar 2019 01:11:36 +0100 with message-id <20190311001136.GA10914@nicolasthinkpad> and subject line bug fixed in texlive-latex has caused the Debian Bug report #921788, regarding libdc1394-22: FTBFS (LaTeX error) to be marked as done. This means that you claim that the

Bug#920442: marked as done (libcaca FTBFS in unstable)

Your message dated Mon, 11 Mar 2019 01:11:36 +0100 with message-id <20190311001136.GA10914@nicolasthinkpad> and subject line bug fixed in texlive-latex has caused the Debian Bug report #920442, regarding libcaca FTBFS in unstable to be marked as done. This means that you claim that the problem

Bug#861027: gprolog bug still there despite easy fixes

Hi, the problem with Debian gprolog is that it's based on an experimental branch (modules), which is incomplete and is the cause of the bug. The fix may be as simple as getting the regular upstream and recompiling it. I'm a bit confused with the git-based packaging tools, so maybe I should

Processed: Re: Bug#917807: libcaca: CVE-2018-20544 CVE-2018-20545 CVE-2018-20546 CVE-2018-20547 CVE-2018-20548 CVE-2018-20549

Processing commands for cont...@bugs.debian.org: > clone 917807 -1 Bug #917807 [src:libcaca] libcaca: CVE-2018-20544 CVE-2018-20545 CVE-2018-20546 CVE-2018-20547 CVE-2018-20548 CVE-2018-20549 Bug 917807 cloned as bug 924281 > retitle -1 Orphan libcaca Bug #924281 [src:libcaca] libcaca:

Bug#917807: libcaca: CVE-2018-20544 CVE-2018-20545 CVE-2018-20546 CVE-2018-20547 CVE-2018-20548 CVE-2018-20549

clone 917807 -1 retitle -1 Orphan libcaca severity -1 normal thanks Hi Sam, I'm planning on fixing those security issues for Buster. Given that you last touched the package in 2014, and didn't address this critical bug within 3 months, may I go ahead and orphan the package while I'm at it? I

Bug#924224: marked as done (uima-utils: broken symlink: /usr/share/uima/lib/uima-adapter-soap.jar -> ../../java/uimaj-adapter-soap.jar)

Your message dated Sun, 10 Mar 2019 23:25:05 + with message-id and subject line Bug#924224: fixed in uimaj 2.10.2-3 has caused the Debian Bug report #924224, regarding uima-utils: broken symlink: /usr/share/uima/lib/uima-adapter-soap.jar -> ../../java/uimaj-adapter-soap.jar to be marked as

Bug#861027: gprolog bug still there despite easy fixes

Hello Tony, tony mancill (Sunday 2019-03-10): > I had a try at this. I pulled the latest upstream release 1.4.5 from > gprolog.org [1], which is dated February of 2019 and it exhibits the > same problem reported in this bug report. Are you sure? The official 1.4.5 works for me when

Bug#920442: #920442: libcaca FTBFS in unstable

I also was able to build in unstable, but building in buster still FTBFS, so at one of the build-dependencies is still broken in buster. live well, vagrant

Bug#767827: marked as done (nfdump: fails to remove: /usr/bin/deb-systemd-helper: error: unable to link /etc/systemd/system/nfdump.service to /dev/null: File exists)

Your message dated Mon, 11 Mar 2019 00:21:54 +0100 with message-id and subject line Closing has caused the Debian Bug report #767827, regarding nfdump: fails to remove: /usr/bin/deb-systemd-helper: error: unable to link /etc/systemd/system/nfdump.service to /dev/null: File exists to be marked as

Bug#917738: marked as done (openhft-chronicle-threads: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32] cannot find symbol)

Your message dated Sun, 10 Mar 2019 23:20:26 + with message-id and subject line Bug#917738: fixed in openhft-chronicle-threads 1.1.6-2 has caused the Debian Bug report #917738, regarding openhft-chronicle-threads: FTBFS: [ERROR]

Processed: Re: Bug#921266: Could this simple typo be the reason: "ream" <-> "realm"?

Processing control commands: > severity -1 important Bug #921266 [linphone] linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry Severity set to 'important' from 'serious' > tags -1 moreinfo Bug #921266 [linphone] linphone: Segfault and crash with "error 4 in

Bug#921266: Could this simple typo be the reason: "ream" <-> "realm"?

Control: severity -1 important Control: tags -1 moreinfo Hi Alf, > I now tried to collect debug info with the cli-version - it crashes the > same way with segfault: > > linphonec -d 5 -l linphone-debug > > the last lines in the debug output after password enty and before crash are: > >

Processed: Re: Bug#913119: Bug#913138: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Processing control commands: > tag 913138 pending Bug #913138 [src:linux] linux: I/O on md RAID 6 hangs completely Added tag(s) pending. > tag 913119 pending Bug #913119 [src:linux] linux-image-4.18.0-2-amd64: Hangs on lvm raid1 Added tag(s) pending. -- 913119:

Bug#913119: Bug#913138: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Control: tag 913138 pending Control: tag 913119 pending On 2019-02-26, martin wrote: > On 2019-02-26 21:11, Cesare Leonardi wrote: >> On 13/02/19 18:21, Dragan Milenkovic wrote: >>> This patch is already on its way to stable branches. I have tested it >>> and confirmed that it resolves the

Processed: Re: Bug#913119: Bug#913138: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Processing control commands: > tag 913138 pending Bug #913138 [src:linux] linux: I/O on md RAID 6 hangs completely Ignoring request to alter tags of bug #913138 to the same tags previously set > tag 913119 pending Bug #913119 [src:linux] linux-image-4.18.0-2-amd64: Hangs on lvm raid1 Ignoring

Processed: Bug #924224 in uimaj marked as pending

Processing control commands: > tag -1 pending Bug #924224 [uima-utils] uima-utils: broken symlink: /usr/share/uima/lib/uima-adapter-soap.jar -> ../../java/uimaj-adapter-soap.jar Added tag(s) pending. -- 924224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924224 Debian Bug Tracking System

Bug#924224: Bug #924224 in uimaj marked as pending

Control: tag -1 pending Hello, Bug #924224 in uimaj reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#884463: passenger: CVE-2017-16355: arbitrary file read

Hey, It looks like version 5.0.30 is not impacted by the CVE[1], and to the best of my abilities, I couldn't reproduce the insecure behavior. I didn't try to read through the source to see if a fix patch *might* still do something useful. Commit 4043718264095cde6623c2cbe8c644541036d7bf[2] does

Bug#908595: krb5-subdomain and ms-subdomain update policy rules ineffective

Control: severity -1 important Control: tags -1 + wontfix Control: tags -1 - patch Hi Dominik, > I discovered the following security bug in bind9 a few weeks ago, and > responsibly disclosed it to the ISC security officer. Unfortunately, until > today they did not acknowledge it is a security

Processed: Re: Bug#908595: krb5-subdomain and ms-subdomain update policy rules ineffective

Processing control commands: > severity -1 important Bug #908595 [src:bind9] krb5-subdomain and ms-subdomain update policy rules ineffective Severity set to 'important' from 'grave' > tags -1 + wontfix Bug #908595 [src:bind9] krb5-subdomain and ms-subdomain update policy rules ineffective Added

Bug#882015: marked as done (ldns: CVE-2017-1000231: Memory corruption in ldns_rr_new_frm_fp_l (double free))

Your message dated Sun, 10 Mar 2019 22:34:40 + with message-id and subject line Bug#882015: fixed in ldns 1.7.0-4 has caused the Debian Bug report #882015, regarding ldns: CVE-2017-1000231: Memory corruption in ldns_rr_new_frm_fp_l (double free) to be marked as done. This means that you

Bug#861027: gprolog bug still there despite easy fixes

On Wed, Jul 04, 2018 at 06:55:11PM +0300, Cedric Ware wrote: > > Hello, > > I don't think anything changed with this bug, which still prevents > gprolog's inclusion in any stable release, and affects Ubuntu as well. > > I believe just pulling the latest upstream source would fix it. > >

Processed: Re: Bug#923839: shim-signed: setup of shim-signed failed with 'Could not delete variable: No space left on device'

Processing control commands: > reassign 891434 src:grub2 Bug #891434 [grub-efi] grub-efi: System fails to boot after "No space left on device" on EFI variable storage Bug reassigned from package 'grub-efi' to 'src:grub2'. No longer marked as found in versions grub2/2.02+dfsg1-1 and

Processed: Re: Bug#923839: shim-signed: setup of shim-signed failed with 'Could not delete variable: No space left on device'

Processing control commands: > reassign 891434 src:grub2 Bug #891434 [src:grub2] grub-efi: System fails to boot after "No space left on device" on EFI variable storage Bug #923839 [src:grub2] efibootmgr should only be called if changes are needed Ignoring request to reassign bug #891434 to the

Bug#891434: Bug#923839: shim-signed: setup of shim-signed failed with 'Could not delete variable: No space left on device'

Control: reassign 891434 src:grub2 Control: forcemerge 891434 923839 On Tue, Mar 05, 2019 at 03:43:31PM -0800, Steve Langasek wrote: > But I'm reassigning this bug to grub2, because I think the right answer for > nearly all efibootmgr write failures on update of the bootloader packages is > that

Processed: tagging 921542

Processing commands for cont...@bugs.debian.org: > tags 921542 + pending Bug #921542 [src:linux] tc qdisc kernel crash Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 921542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 Debian

Processed: fixed 890075 in 3.3.0-2

Processing commands for cont...@bugs.debian.org: > fixed 890075 3.3.0-2 Bug #890075 [src:ruby-http] ruby-http ftbfs (test failures with 2.5) Marked as fixed in versions ruby-http/3.3.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 890075:

Bug#909413: marked as done (cffi broke pyopencl ?)

Your message dated Sun, 10 Mar 2019 14:40:01 -0700 with message-id <20190310214000.pfiunmg5q2ngc...@elgar.kardiogramm.net> and subject line Re: Bug#909413: segfault when leaving the python3-dbg interpreter has caused the Debian Bug report #909413, regarding cffi broke pyopencl ? to be marked as

Bug#923465: fixed in freecad 0.18~pre1+dfsg1-5

Hi Salman, On 3/10/19 9:05 AM, Salman Mohammadi wrote: > Dear Maintainer, > > > I could install this package (0.18~pre1+dfsg1-4) with no problem and > this bug seems to be resolved. But on the tracker page, this package has > been marked for autoremoval on 29 March, with this message: > >

Bug#915291: java3ds-fileloader FTBFS: error: package com.sun.j3d.utils.applet does not exist

On Sun, Dec 02, 2018 at 04:36:37PM +0200, Adrian Bunk wrote: > Source: java3ds-fileloader > Version: 1.2+dfsg-3 > Severity: serious > Tags: ftbfs > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/java3ds-fileloader.html > > ... > build: > [mkdir] Created dir: >

Processed: forcibly merging 924061 923715

Processing commands for cont...@bugs.debian.org: > forcemerge 924061 923715 Bug #924061 [ceph-osd] ceph-osd: ceph-volume@.service missing Bug #923715 [ceph-osd] ceph-osd: missing systemd service in package: ceph-volume@.service Severity set to 'grave' from 'normal' Merged 923715 924061 > thanks

Bug#866898: Fwd: Re: Bug #866898 - Xorg issues

Forwarded Message Subject:Re: Bug #866898 - Xorg issues Date: Sun, 10 Mar 2019 20:44:24 + From: Matthew Vernon To: Andrew M.A. Cater Hi, On 10/03/2019 14:06, Andrew M.A. Cater wrote: Lurking in Debian BSP in Cambridge: does the above bug still

Bug#895320: Prototype fix

A prototype patch is attached. This splits up the offending .dot file into two separate .dot files, each with a single graph. The package then builds. Please double-check this. You'd need to ship this as a patch in debian/patches. Let me know if you'd like me to finish this as an nmu. >From

Bug#924271: marked as done (openarena: crashes at launch with "Couldn't compile shader" message.)

Your message dated Sun, 10 Mar 2019 20:11:12 + with message-id <20190310201112.ga16...@espresso.pseudorandom.co.uk> and subject line Re: Bug#924271: openarena: crashes at launch with "Couldn't compile shader" message. has caused the Debian Bug report #924271, regarding openarena: crashes at

Bug#924271: openarena: crashes at launch with "Couldn't compile shader" message.

Yes, that fixes the problem. Thanks! On Sun, 10 Mar 2019, 19:57 Simon McVittie, wrote: > Control: reassign -1 ioquake3 1.36+u20181222.e5da13f~dfsg-1 > Control: tags -1 + moreinfo > Control: affects -1 openarena quake3 > Control: affects 923226 + openarena quake3 > > On Sun, 10 Mar 2019 at

Bug#924271: openarena: crashes at launch with "Couldn't compile shader" message.

Control: reassign -1 ioquake3 1.36+u20181222.e5da13f~dfsg-1 Control: tags -1 + moreinfo Control: affects -1 openarena quake3 Control: affects 923226 + openarena quake3 On Sun, 10 Mar 2019 at 19:42:20 +, Matthew Hoare wrote: >    Program failed to launch with a lengthy error message

Processed: Re: Bug#924271: openarena: crashes at launch with "Couldn't compile shader" message.

Processing control commands: > reassign -1 ioquake3 1.36+u20181222.e5da13f~dfsg-1 Bug #924271 [openarena] openarena: crashes at launch with "Couldn't compile shader" message. Bug reassigned from package 'openarena' to 'ioquake3'. No longer marked as found in versions openarena/0.8.8+dfsg-2.

Bug#924272: decopy: FTBFS (mv: cannot stat 'README.1': No such file or directory)

Package: src:decopy Version: 0.2.4.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python3

Bug#895320: (no subject)

reassign -1 mk-configure thanks Hi. I looked into this, and the conclusions are: - This is not an FTBFS for graphviz, but rather for mk-configure. The graphviz package builds just fine, but ... - The "dot" executable it produces has a bug: graphs spanning multiple pages contain incorrect

Processed: reassign 895320 to mk-configure

Processing commands for cont...@bugs.debian.org: > reassign 895320 mk-configure Bug #895320 [graphviz] mk-configure FTBFS: Error: /undefined in setupLatin1 Bug reassigned from package 'graphviz' to 'mk-configure'. No longer marked as found in versions graphviz/2.40.1-3. Ignoring request to alter

Processed: affects 924256

Processing commands for cont...@bugs.debian.org: > affects 924256 + openjpeg2 Bug #924256 {Done: Andrej Shadura } [javahelper] javahelper: javadoc: error - The code being documented uses packages in the unnamed module Bug #923748 {Done: Andrej Shadura } [javahelper] javahelper: javadoc: error

Bug#924271: openarena: crashes at launch with "Couldn't compile shader" message.

Package: openarena Version: 0.8.8+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I attempted to launch the program. * What exactly did you do (or not do) that was effective (or ineffective)? Ran `openarena` from a

Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop

Control: severity -1 important Control: tags -1 + unreproducible On Mon, 03 Sep 2018 at 20:32:14 -0500, william l-k wrote: > Could this be what we were looking for: > > Aug 28 09:30:54 user gnome-shell[3348]: JS ERROR: TypeError: > this._currentWindow is null I don't think so: it doesn't look

Processed: Re: Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop

Processing control commands: > severity -1 important Bug #907490 [gnome-shell] gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop Severity set to 'important' from 'grave' > tags -1 + unreproducible Bug #907490 [gnome-shell] gnome-shell: Unrecoverable failure in

Bug#921558: lsb-base: killproc does not pass name parameter to start-stop-daemon

control: tags -1 +moreinfo [2019-02-06 20:20] Andreas Metzler > Package: lsb-base > Version: 10.2018112800 > Severity: serious > > Hello, > > there is a logic error in /lib/lsb/init-functions's killproc: > > base=${1##*/} > if [ ! $pidfile ]; then > name_param="--name $base

Processed: Re: lsb-base: killproc does not pass name parameter to start-stop-daemon

Processing control commands: > tags -1 +moreinfo Bug #921558 [lsb-base] lsb-base: killproc does not pass name parameter to start-stop-daemon Added tag(s) moreinfo. -- 921558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921558 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#923609: proposed solution

[2019-03-08 22:40] Niko Tyni > On Fri, Mar 08, 2019 at 02:39:53PM +, Dmitry Bogatov wrote: > > > I believe this patch would somewhat solve issue. Dear submitter, can you > > please apply this patch, build package and check, that `gdbm_load-nolfs' > > binary from created bin:gdbmtool does

Bug#917203: FTBFS on at least two architectures: test failure in the enigma algorithm

On Mon, Dec 24, 2018 at 12:20:05AM +, Steve McIntyre wrote: >Package: src:libmcrypt >Version: 2.5.8-3.3 >Severity: serious >Tags: ftbfs >Justification: fails to build from source (but built successfully in the past) > >Hi! > >I've been doing a full rebuild of the Debian archive, building all

Bug#924191: marked as done (libg810-led-dev: missing Depends: libg810-led0 (= ${binary:Version}))

Your message dated Sun, 10 Mar 2019 18:49:17 + with message-id and subject line Bug#924191: fixed in g810-led 0.3.3-2 has caused the Debian Bug report #924191, regarding libg810-led-dev: missing Depends: libg810-led0 (= ${binary:Version}) to be marked as done. This means that you claim that

Bug#899662: *prod* Please fix pykerberos bug #899662?

On Sun, Mar 10, 2019 at 07:34:46PM +0100, Guido Günther wrote: >Hi, >On Sun, Mar 10, 2019 at 02:11:38PM +, Steve McIntyre wrote: >> Hi guys, >> >> I don't know if you've even seen this RC bug. Could you please update >> the maintainer address to point to something that works? > >I wasn't. I

Bug#923756: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923755: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#924256: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923758: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923757: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923754: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923748: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923753: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923751: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:35:11 + with message-id and subject line Bug#923756: fixed in javatools 0.72.5 has caused the Debian Bug report #923756, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#899662: *prod* Please fix pykerberos bug #899662?

Hi, On Sun, Mar 10, 2019 at 02:11:38PM +, Steve McIntyre wrote: > Hi guys, > > I don't know if you've even seen this RC bug. Could you please update > the maintainer address to point to something that works? I wasn't. I can do so next week. -- Guido

Bug#923748: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

On Sun, 10 Mar 2019 at 18:14, Markus Koschany wrote: > > Control: reopen -1 > > Hello Andrej, > > bug 923748 is about a different issue and unrelated to your recent upload. > We need to fix it too and I proposed a patch here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923756#30 Sorry

Processed: Bug #923756 in javatools marked as pending

Processing control commands: > tag -1 pending Bug #923756 [javahelper] javahelper: javadoc: error - The code being documented uses packages in the unnamed module Bug #923748 [javahelper] javahelper: javadoc: error - The code being documented uses packages in the unnamed module Bug #923751

Bug#923756: Bug #923756 in javatools marked as pending

Control: tag -1 pending Hello, Bug #923756 in javatools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys

> > On Mon, Jan 7, 2019, 16:58 Chris Wilson > >>> Hi Reinhard, >>> >>> If I make the workaround suggested on this thread >>> (change >>> SECLEVEL to 1 in /etc/ssl/openssl.cnf) then test/basicserver passes again. >>> This is at least a good

Processed: Re: Bug#923748: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Processing control commands: > reopen -1 Bug #923748 {Done: Andrej Shadura } [javahelper] javahelper: javadoc: error - The code being documented uses packages in the unnamed module Bug #923751 {Done: Andrej Shadura } [javahelper] javahelper: javadoc: error - The code being documented uses

Bug#923748: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Control: reopen -1 Hello Andrej, bug 923748 is about a different issue and unrelated to your recent upload. We need to fix it too and I proposed a patch here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923756#30 Markus signature.asc Description: OpenPGP digital signature

Bug#923757: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923751: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#924256: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923756: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923753: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923755: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923754: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923758: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#923748: marked as done (javahelper: javadoc: error - The code being documented uses packages in the unnamed module)

Your message dated Sun, 10 Mar 2019 18:04:53 + with message-id and subject line Bug#923748: fixed in javatools 0.72.4 has caused the Debian Bug report #923748, regarding javahelper: javadoc: error - The code being documented uses packages in the unnamed module to be marked as done. This

Bug#924256: openjpeg2: FTBFS: Can't exec "jh_build": No such file or directory at /usr/bin/dh line 908.

Hi Andreas, On Sun, Mar 10, 2019 at 06:15:50PM +0100, Andreas Metzler wrote: > Control: reassign -1 javahelper 0.72.3 > Control: forcemerge 923748 924256 > Control: retitle -1 shebang line in jh_build "#!/use/bin/perl" > > On 2019-03-10 Salvatore Bonaccorso wrote: > > Source: openjpeg2 > >

Processed: Bug #923748 in javatools marked as pending

Processing control commands: > tag -1 pending Bug #923748 [javahelper] javahelper: javadoc: error - The code being documented uses packages in the unnamed module Bug #923751 [javahelper] javahelper: javadoc: error - The code being documented uses packages in the unnamed module Bug #923753

Processed: severity of 924191 is serious

Processing commands for cont...@bugs.debian.org: > severity 924191 serious Bug #924191 [libg810-led-dev] libg810-led-dev: missing Depends: libg810-led0 (= ${binary:Version}) Ignoring request to change severity of Bug 924191 to the same value. > thanks Stopping processing here. Please contact me

Bug#888533: marked as done (openjpeg2: CVE-2018-5785: integer overflow in opj_j2k_setup_encoder function in openjp2/j2k.c)

Your message dated Sun, 10 Mar 2019 17:50:19 + with message-id and subject line Bug#888533: fixed in openjpeg2 2.3.0-2 has caused the Debian Bug report #888533, regarding openjpeg2: CVE-2018-5785: integer overflow in opj_j2k_setup_encoder function in openjp2/j2k.c to be marked as done. This

Bug#910763: marked as done (openjpeg2: CVE-2018-18088)

Your message dated Sun, 10 Mar 2019 17:50:19 + with message-id and subject line Bug#910763: fixed in openjpeg2 2.3.0-2 has caused the Debian Bug report #910763, regarding openjpeg2: CVE-2018-18088 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#889683: marked as done (openjpeg2: CVE-2018-6616: Excessive Iteration in opj_t1_encode_cblks)

Your message dated Sun, 10 Mar 2019 17:50:19 + with message-id and subject line Bug#889683: fixed in openjpeg2 2.3.0-2 has caused the Debian Bug report #889683, regarding openjpeg2: CVE-2018-6616: Excessive Iteration in opj_t1_encode_cblks to be marked as done. This means that you claim that

Bug#884738: marked as done (openjpeg2: CVE-2017-17480: stack-based buffer overflow in pgxtovolume function in jp3d/convert.c)

Your message dated Sun, 10 Mar 2019 17:50:19 + with message-id and subject line Bug#884738: fixed in openjpeg2 2.3.0-2 has caused the Debian Bug report #884738, regarding openjpeg2: CVE-2017-17480: stack-based buffer overflow in pgxtovolume function in jp3d/convert.c to be marked as done.

Bug#923748: Bug #923748 in javatools marked as pending

Control: tag -1 pending Hello, Bug #923748 in javatools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: user debian...@lists.debian.org, found 905052 in 4.20.0-1, found 856939 in 0.78.1-1 ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > found 905052 4.20.0-1 Bug #905052 [xfslibs-dev] xfslibs-dev: broken symlink: /lib/libhandle.a -> /usr/lib/libhandle.a Marked as found in versions

Processed: your mail

Processing commands for cont...@bugs.debian.org: > block 922031 by 924261 Bug #922031 [certbot] certbot: Debian 9 systemd timer inactive after upgrade to 0.28.0-1~deb9u1 922031 was not blocked by any bugs. 922031 was not blocking any bugs. Added blocking bug(s) of 922031: 924261 > thanks

Bug#924256: openjpeg2: FTBFS: Can't exec "jh_build": No such file or directory at /usr/bin/dh line 908.

Control: retitle -1 javahelper: javadoc: error - The code being documented uses packages in the unnamed module Hi, Am 10.03.19 um 18:15 schrieb Andreas Metzler: > Control: reassign -1 javahelper 0.72.3 > Control: forcemerge 923748 924256 > Control: retitle -1 shebang line in jh_build

Processed: Re: Bug#924256: openjpeg2: FTBFS: Can't exec "jh_build": No such file or directory at /usr/bin/dh line 908.

Processing control commands: > retitle -1 javahelper: javadoc: error - The code being documented uses > packages in the unnamed module Bug #924256 [javahelper] shebang line in jh_build "#!/use/bin/perl" Bug #923748 [javahelper] shebang line in jh_build "#!/use/bin/perl" Bug #923751 [javahelper]

Bug#922031: Timer Disabling on Package Update? (is: #922031)

Am 10.03.19 um 18:23 schrieb Harlan Lieberman-Berg: > On Sun, Mar 10, 2019 at 1:19 PM Michael Biebl wrote: >> Let's bump this to serious. I think you should consider making another >> stable upload for this. >> As users have pointed out, systems which aren't rebooted regularly are >> otherwise up

Bug#908815: libdmtx: diff for NMU version 0.7.5-2.1

Control: tags 908815 + patch Control: tags 908815 + pending Dear maintainer, I've prepared an NMU for libdmtx (versioned as 0.7.5-2.1), and uploaded it to experimental so that it can go through NEW. I've done this without delay since there's no other version in experimental. Regards, smcv

Processed: libdmtx: diff for NMU version 0.7.5-2.1

Processing control commands: > tags 908815 + patch Bug #908815 [libdmtx0a] [libdmtx0a] Structs in dmtx.h have changed without new ABI number Added tag(s) patch. > tags 908815 + pending Bug #908815 [libdmtx0a] [libdmtx0a] Structs in dmtx.h have changed without new ABI number Added tag(s)

Bug#918309: [PKG-Openstack-devel] Bug#918309: sphinxcontrib-programoutput: Please update to v0.13 that is compatible with Sphinx 1.8

On 3/9/19 11:32 PM, Chris Lamb wrote: > tags 918309 + pending patch > thanks > > I've uploaded sphinxcontrib-programoutput 0.11-3.1 to DELAYED/5: > > sphinxcontrib-programoutput (0.11-3.1) unstable; urgency=medium > > * Non-maintainer upload. > * Fix FTBFS with Sphinx 1.8 by

Processed: Re: Bug#872635: Info received (util-linux: FTBFS on armel: test failure)

Processing control commands: > severity -1 important Bug #872635 [src:util-linux] util-linux: FTBFS on armel: test failure Severity set to 'important' from 'serious' -- 872635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872635 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#872635: Info received (util-linux: FTBFS on armel: test failure)

control: severity -1 important Downgrading to important this is not RC I should have done this on previous email. /Andy

Bug#922031: Timer Disabling on Package Update? (is: #922031)

On Sun, Mar 10, 2019 at 1:19 PM Michael Biebl wrote: > Let's bump this to serious. I think you should consider making another > stable upload for this. > As users have pointed out, systems which aren't rebooted regularly are > otherwise up for a nasty experience. > You might consider asking the

Bug#924254: dmtx-utils: diff for NMU version 0.7.6-1.1

Control: tags 924254 + pending Dear maintainer, To unblock #908815, I've prepared an NMU for dmtx-utils (versioned as 0.7.6-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay or cancel it, or alternatively if I should reschedule it to go into unstable without delay.

Processed: dmtx-utils: diff for NMU version 0.7.6-1.1

Processing control commands: > tags 924254 + pending Bug #924254 [dmtx-utils] dmtx-utils: hard-codes dependency on libdmtx0a Added tag(s) pending. -- 924254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Timer Disabling on Package Update? (is: #922031)

Processing control commands: > severity -1 serious Bug #922031 [certbot] certbot: Debian 9 systemd timer inactive after upgrade to 0.28.0-1~deb9u1 Severity set to 'serious' from 'important' -- 922031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922031 Debian Bug Tracking System Contact

  1   2   3   >