Your message dated Tue, 14 Mar 2023 21:50:49 +0000
with message-id <e1pccxh-00daa2...@respighi.debian.org>
and subject line unblock node-regexpu-core
has caused the Debian Bug report #1032962,
regarding unblock: node-regexpu-core/5.2.2-3
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 ow...@bugs.debian.org
immediately.)
--
1032962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-regexpu-c...@packages.debian.org
Control: affects -1 + src:node-regexpu-core
Please unblock package node-regexpu-core
[ Reason ]
This ensure required node-unicode-match-property-ecmascript is used
during upgrades
from bullseye.
This minimum version requirement is already mentioned in package.json
by upstream
but missed when preparing the package.
[ Impact ]
This was noticed when testing gitlab upgrade from bullseye-fasttrack to
bookworm-fasttrack
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/192#note_9747
If this is not accepted, either gitlab will have to add this version
constraint
or the user will have to update this package manually. Gitlab being
very brittle
about its large dependency chains, directly running a dist-upgrade may
not be the
best method of upgrade. So it is recommended to upgrade gitlab first
and then do
the dist-upgrade.
[ Tests ]
No change in upstream code only and implicit dependency made explicit.
[ Risks ]
This only changes minimum version of a dependency which is already
satisfied in
bookworm but not in bullseye.
[ 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 ]
unblock node-regexpu-core/5.2.2-3
diff -Nru node-regexpu-core-5.2.2/debian/changelog node-regexpu-core-5.2.2/debian/changelog
--- node-regexpu-core-5.2.2/debian/changelog 2022-11-30 22:02:03.000000000 +0530
+++ node-regexpu-core-5.2.2/debian/changelog 2023-03-14 15:01:43.000000000 +0530
@@ -1,3 +1,12 @@
+node-regexpu-core (5.2.2-3) unstable; urgency=medium
+
+ * Team upload
+ * Update node-unicode-match-property-ecmascript minimum version to (>= 2.0~)
+ (This is required to fix breakage in babel-loader when upgrading from
+ bullseye)
+
+ -- Pirate Praveen <prav...@debian.org> Tue, 14 Mar 2023 15:01:43 +0530
+
node-regexpu-core (5.2.2-2) unstable; urgency=medium
[ Debian Janitor ]
diff -Nru node-regexpu-core-5.2.2/debian/control node-regexpu-core-5.2.2/debian/control
--- node-regexpu-core-5.2.2/debian/control 2022-11-30 22:02:03.000000000 +0530
+++ node-regexpu-core-5.2.2/debian/control 2023-03-14 15:01:43.000000000 +0530
@@ -13,7 +13,7 @@
node-regjsgen,
node-regjsparser (>= 0.6.4~),
node-unicode-15.0.0,
- node-unicode-match-property-ecmascript,
+ node-unicode-match-property-ecmascript (>= 2.0~),
node-unicode-match-property-value-ecmascript (>= 2.1~),
dh-sequence-nodejs
Standards-Version: 4.6.1
@@ -28,7 +28,7 @@
node-regenerate-unicode-properties (>= 10.1~),
node-regjsgen,
node-regjsparser (>= 0.6.4~),
- node-unicode-match-property-ecmascript,
+ node-unicode-match-property-ecmascript (>= 2.0~),
node-unicode-match-property-value-ecmascript (>= 2.1~),
${misc:Depends}
Multi-Arch: foreign
--- End Message ---
--- Begin Message ---
Unblocked.
--- End Message ---
