[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#854953: marked as done (unblock: dustmite/0~20170126.e95dff8-2)



Your message dated Sun, 19 Feb 2017 23:22:08 +0100
with message-id <20170219222206.GA3054@ugent.be>
and subject line Re: unblock: dustmite/0~20170126.e95dff8-2
has caused the Debian Bug report #854953,
regarding unblock: dustmite/0~20170126.e95dff8-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.)


-- 
854953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854953
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: unblock
Severity: minor

Please unblock dustmite 0~20170126.e95dff8-2.
This is a new package for testing which unfortunately didn't make the
deadline due to being stuck in NEW for almost 2 months. It has no
reverse-dependencies and does not interfere with any other package in
Debian, so including it in the release is very save (it also has no
known bugs affecting Debian at time).

The main reason why I want this in Debian Stretch is to debug D
compiler issues. Dustmite is an invaluable tool for finding minimal
testcases for compiler bugs or to create minimal testcases for any
other issues affecting D code. It's very useful for bug reporters to
have this tool available if they find an issue in another D-based
software in the Debian archive.
So, having it directly available from the archive would help a lot
with debugging these issues.

Usually I would go with backports for something like this, but since
it's very early in the freeze and the dustmite package does not affect
any other software (only depends on gdc for building, even), I think
asking for an unblock is justified.

It is also worth noting that this package is not affected by RC issue
#850958, which affects most D packages in Debian, since dustmite is
built with the GDC compiler instead of LDC.
(we are confident though to resolve that issue in-time for the release
and have the remaining packages built on ppc64el and migrate)

Kind regards,
    Matthias

unblock dustmite/0~20170126.e95dff8-2

--- End Message ---
--- Begin Message ---
Hi,

On Sun, Feb 12, 2017 at 02:36:25PM +0100, Matthias Klumpp wrote:
> Please unblock dustmite 0~20170126.e95dff8-2.
> This is a new package for testing which unfortunately didn't make the
> deadline due to being stuck in NEW for almost 2 months.

Sorry, but we're not accepting new packages in stretch.

Cheers,

Ivo

--- End Message ---

Reply to: