Marking #919951 as resolved

diff --git a/919951_dune/draft b/919951_dune/draft
deleted file mode 100644 (file)
index 665ff21..0000000
--- a/919951_dune/draft
+++ /dev/null
@@ -1,27 +0,0 @@
-Bug report #916468 on the ownership of the /usr/bin/dune command was
-opened after a quite short discussion in debian-devel¹.
-
-¹ https://lists.debian.org/debian-devel/2018/12/msg00190.html
-
-The Technical Committee has evaluated the situation that led to the
-opening of said bug as well as this one (#919951), and in accordance
-with the Procedure for the Technical Committee, 6.3.6 of the Debian
-Constitution:
-
-   The Technical Committee does not make a technical decision until
-   efforts to resolve it via consensus have been tried and failed,
-   unless it has been asked to make a decision by the person or body
-   who would normally be responsible for it.
-
-Together with a review of the resolution of #916468 and the last
-messages in #919951, the Technical Committee recognizes the situation
-as happily solved thanks to the direct interactions and good will of
-both the maintainers and upstream authors of the affected packages.
-
-Thus, not having a controversy to decide upon anymore, we have decided
-to mark this bug as Closed. Furthermore, the Technical Committee
-considers that, given the very short discussion the involved parties
-had before raising this issue to the Committee, we should remind our
-fellow Developers that any decision reached by the Technical Committee
-can be seen to some as an imposition. We urge everybody to always seek
-a decision by a serious, calm discussion before escalating issues.

diff --git a/resolved_issues/919951_dune/draft b/resolved_issues/919951_dune/draft
new file mode 100644 (file)
index 0000000..665ff21
--- /dev/null
+++ b/resolved_issues/919951_dune/draft
@@ -0,0 +1,27 @@
+Bug report #916468 on the ownership of the /usr/bin/dune command was
+opened after a quite short discussion in debian-devel¹.
+
+¹ https://lists.debian.org/debian-devel/2018/12/msg00190.html
+
+The Technical Committee has evaluated the situation that led to the
+opening of said bug as well as this one (#919951), and in accordance
+with the Procedure for the Technical Committee, 6.3.6 of the Debian
+Constitution:
+
+   The Technical Committee does not make a technical decision until
+   efforts to resolve it via consensus have been tried and failed,
+   unless it has been asked to make a decision by the person or body
+   who would normally be responsible for it.
+
+Together with a review of the resolution of #916468 and the last
+messages in #919951, the Technical Committee recognizes the situation
+as happily solved thanks to the direct interactions and good will of
+both the maintainers and upstream authors of the affected packages.
+
+Thus, not having a controversy to decide upon anymore, we have decided
+to mark this bug as Closed. Furthermore, the Technical Committee
+considers that, given the very short discussion the involved parties
+had before raising this issue to the Committee, we should remind our
+fellow Developers that any decision reached by the Technical Committee
+can be seen to some as an imposition. We urge everybody to always seek
+a decision by a serious, calm discussion before escalating issues.