Bug#879816: marked as done (eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0)

2019-09-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Sep 2019 11:20:48 + with message-id and subject line Bug#879816: fixed in eclipse-titan 6.6.0-1 has caused the Debian Bug report #879816, regarding eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0 to be marked as done. This means that you claim that th

Bug#879816: marked as done (eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0)

2018-12-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Dec 2018 15:19:53 + with message-id and subject line Bug#879816: fixed in eclipse-titan 6.5.0-1 has caused the Debian Bug report #879816, regarding eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0 to be marked as done. This means that you claim that th

Bug#879816: marked as done (eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 16:24:28 + with message-id and subject line Bug#879816: fixed in eclipse-titan 6.3.1-1 has caused the Debian Bug report #879816, regarding eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0 to be marked as done. This means that you claim that th

Bug#879816: marked as done (eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0)

2017-11-28 Thread Debian Bug Tracking System
Your message dated Tue, 28 Nov 2017 10:19:56 + with message-id and subject line Bug#879816: fixed in eclipse-titan 6.3.0-1 has caused the Debian Bug report #879816, regarding eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0 to be marked as done. This means that you claim that th