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

Bug#1110077: marked as done (unblock: node-d3-force/2.1.1+~2.1.4-2)



Your message dated Wed, 30 Jul 2025 13:45:05 +0000
with message-id <E1uh77B-003GX4-2d@respighi.debian.org>
and subject line unblock node-d3-force
has caused the Debian Bug report #1110077,
regarding unblock: node-d3-force/2.1.1+~2.1.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.)


-- 
1110077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110077
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: node-d3-force@packages.debian.org, sanvila@debian.org, paultag@debian.org
Control: affects -1 + src:node-d3-force
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package node-d3-force

[ Reason ]
This upload fixes Bug #1110054. The *.dsc file had an invalid priority
in the Package-List field.

[ Impact ]
We don't really know the impact of not fixing this, and that's a problem.
However, only one package in the archive has this anomaly, and it's
trivial to fix it, so fixing it seems a better and simpler course
of action than evaluating the risks of not fixing it.

[ Tests ]
A diff between the old and the new *.dsc file shows that the priority has
been fixed:

 Package-List:
- node-d3-force deb javascript unknown arch=all
+ node-d3-force deb javascript optional arch=all

The package has passed the autopkgtests.

[ Risks ]
The new package is otherwise identical to the old one. The only changes
are the changelog, and also the Standards-Version, but that was a
pending/unreleased commit in salsa which I decided not to revert
to keep the history clean, as it's harmless.

The real risk here is in not fixing it.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]
The current dpkg in trixie now handles the case where there
is no priority in debian/control but the previous package
was apparently built with a dpkg version which did not.

The package is not currently blocked, because it has
autopkgtests and they passed, but the full freeze is tomorrow
so in two days it will need an unblock.

unblock node-d3-force/2.1.1+~2.1.4-2
diff -Nru node-d3-force-2.1.1+~2.1.4/debian/changelog node-d3-force-2.1.1+~2.1.4/debian/changelog
--- node-d3-force-2.1.1+~2.1.4/debian/changelog	2023-09-09 15:42:39.000000000 +0200
+++ node-d3-force-2.1.1+~2.1.4/debian/changelog	2025-07-29 02:05:00.000000000 +0200
@@ -1,3 +1,11 @@
+node-d3-force (2.1.1+~2.1.4-2) unstable; urgency=medium
+
+  * Team upload.
+  * Fix invalid priority in *.dsc file. Closes: #1110054.
+    Thanks to Paul Tagliamonte for the report.
+
+ -- Santiago Vila <sanvila@debian.org>  Tue, 29 Jul 2025 02:05:00 +0200
+
 node-d3-force (2.1.1+~2.1.4-1) unstable; urgency=medium
 
   * Team upload
diff -Nru node-d3-force-2.1.1+~2.1.4/debian/control node-d3-force-2.1.1+~2.1.4/debian/control
--- node-d3-force-2.1.1+~2.1.4/debian/control	2023-09-09 15:39:11.000000000 +0200
+++ node-d3-force-2.1.1+~2.1.4/debian/control	2025-07-29 02:02:03.000000000 +0200
@@ -11,7 +11,7 @@
  , node-rollup-plugin-terser
  , rollup
  , terser
-Standards-Version: 4.6.2
+Standards-Version: 4.7.0
 Vcs-Browser: https://salsa.debian.org/js-team/node-d3-force
 Vcs-Git: https://salsa.debian.org/js-team/node-d3-force.git
 Homepage: https://d3js.org/d3-force/

--- End Message ---
--- Begin Message ---
Unblocked node-d3-force.

--- End Message ---

Reply to: