Bug#893112: marked as done (nmu: eclipse-titan_6.3.1-1)
Your message dated Wed, 28 Mar 2018 19:01:45 +0200
with message-id <aa52ba6f-3ab9-03ef-d105-1746f91db112@debian.org>
and subject line Re: nmu: eclipse-titan_6.3.1-1
has caused the Debian Bug report #893112,
regarding nmu: eclipse-titan_6.3.1-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
893112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893112
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: eclipse-titan depends on gcc < 7.2.0, but unstable has gcc-7.3.0
- From: Harald Welte <laforge@gnumonks.org>
- Date: Fri, 16 Mar 2018 16:22:49 +0100
- Message-id: <152121376910.18601.16187592091958682970.reportbug@localhost.localdomain>
Package: eclipse-titan
Severity: grave
This is history repeating itself, see debian bug 879816
I would hope this can be solved in a generic way, without breaking the eclipse-titan
package every few months when debian updates the gcc version.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages eclipse-titan depends on:
ii default-jdk 2:1.9-61
ii expect 5.45.4-1
ii gcc 4:7.3.0-1
ii libc6 2.27-2
ii libgcc1 1:8-20180312-2
ii libncurses5 6.1-1
ii libpcap-dev 1.8.1-6
ii libpcre3-dev 2:8.39-9
ii libsctp-dev 1.0.17+dfsg-2
ii libssl-dev 1.1.0g-2
ii libssl1.1 1.1.0g-2
ii libstdc++6 8-20180312-2
ii libtinfo5 6.1-1
ii libxml2 2.9.4+dfsg1-6.1
ii libxml2-dev 2.9.4+dfsg1-6.1
ii make 4.2.1-1
ii perl 5.26.1-5
ii python 2.7.14-4
eclipse-titan recommends no packages.
eclipse-titan suggests no packages.
--- End Message ---
--- Begin Message ---
On 18/03/18 02:58, Andreas Beckmann wrote:
> severity 893112 normal
> reassign 893112 release.debian.org
> retitle 893112 nmu: eclipse-titan_6.3.1-1
> user release.debian.org@packages.debian.org
> usertag 893112 binnmu
> thanks
>
> On Fri, 16 Mar 2018 16:22:49 +0100 Harald Welte <laforge@gnumonks.org> wrote:
>> Package: eclipse-titan
>> Severity: grave
>>
>> This is history repeating itself, see debian bug 879816
>>
>> I would hope this can be solved in a generic way, without breaking the eclipse-titan
>> package every few months when debian updates the gcc version.
>
> This just needs a binNMU.
>
> nmu eclipse-titan_6.3.1-1 . ANY . unstable . -m "Rebuild against gcc 7.3.0."
Scheduled now.
Cheers,
Emilio
--- End Message ---
Reply to: