Bug#883017: marked as done (nmu: rebar_2.6.4-2)
Your message dated Wed, 3 Jan 2018 10:56:54 +0100
with message-id <bfc8d1dd-b7fc-6666-5fc7-2d9517a757dd@debian.org>
and subject line Re: Bug#883017: nmu: rebar_2.6.4-2
has caused the Debian Bug report #883017,
regarding nmu: rebar_2.6.4-2
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.)
--
883017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883017
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nmu: rebar_2.6.4-2
- From: Philipp Huebner <debalance@debian.org>
- Date: Tue, 28 Nov 2017 21:34:44 +0100
- Message-id: <151190128458.7199.14286582903499824029.reportbug@dex.debalance.de>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
Hi,
I have run into strange problems while packaging the new ejabberd
release, they went away when I rebuilt rebar with the current Erlang/OTP
release, so please do a binNMU for unstable!
Thanks!
nmu rebar_2.6.4-2 . ANY . unstable . -m "Rebuild against the new Erlang/OTP release"
--- End Message ---
--- Begin Message ---
- To: Philipp Huebner <debalance@debian.org>, 883017-done@bugs.debian.org
- Subject: Re: Bug#883017: nmu: rebar_2.6.4-2
- From: Emilio Pozuelo Monfort <pochu@debian.org>
- Date: Wed, 3 Jan 2018 10:56:54 +0100
- Message-id: <bfc8d1dd-b7fc-6666-5fc7-2d9517a757dd@debian.org>
- In-reply-to: <9dc6fd14-23c5-cd04-282c-e74455473b5a@debian.org>
- References: <151190128458.7199.14286582903499824029.reportbug@dex.debalance.de> <9dc6fd14-23c5-cd04-282c-e74455473b5a@debian.org>
On 30/12/17 16:55, Philipp Huebner wrote:
> It seems the problems have gone away,
> maybe due to one of the Erlang bugfix releases that have been uploaded
> since reporting this bug.
>
> However, a binNMU is still a good idea IMO.
If the problem is gone, let's close this. We don't like to schedule binNMUs for
mysterious problems. (If there's been some sort of ABI break, it should be found
and properly dealt with.)
Cheers,
Emilio
--- End Message ---
Reply to: