Your message dated Sat, 12 Aug 2023 12:36:54 +0000
with message-id <e1qunrs-00d8sx...@fasolo.debian.org>
and subject line Bug#1043519: fixed in node-json-stable-stringify 
1.0.2+repack1+~cs1.0.34-1
has caused the Debian Bug report #1043519,
regarding node-json-stable-stringify,node-fast-json-stable-stringify: same 
files packaged twice?
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.)


-- 
1043519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-json-stable-stringify,node-fast-json-stable-stringify
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.0.2+~cs5.2.34-1
Control: found -1 2.1.0-1

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

In case of shared library packages where the conflicting files do not
contain the SOVERSION in their name or path, please also consider
alternative solutions for solving the conflict and avoiding
Breaks+Replaces for easier upgrades in the future. Ideally shared
libraries of different SOVERSIONs should only contain non-conflicting
files and thus be co-installable for smooth upgrades.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package node-fast-json-stable-stringify.
  Preparing to unpack .../node-fast-json-stable-stringify_2.1.0-1_all.deb ...
  Unpacking node-fast-json-stable-stringify (2.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-fast-json-stable-stringify_2.1.0-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/node-fast-json-stable-stringify/README.md', which is also in 
package node-json-stable-stringify 1.0.2+~cs5.2.34-1
  Errors were encountered while processing:
   /var/cache/apt/archives/node-fast-json-stable-stringify_2.1.0-1_all.deb

The following files are part of both packages:

usr/share/doc/node-fast-json-stable-stringify/README.md
usr/share/doc/node-fast-json-stable-stringify/copyright
usr/share/nodejs/fast-json-stable-stringify/index.d.ts
usr/share/nodejs/fast-json-stable-stringify/index.js
usr/share/nodejs/fast-json-stable-stringify/package.json

Is that same software packaged twice under different names?

Why does node-json-stable-stringify (w/o fast) ship
/usr/share/doc/node-fast-json-stable-stringify/copyright
(with fast) ?

cheers,

andreas

--- End Message ---
--- Begin Message ---
Source: node-json-stable-stringify
Source-Version: 1.0.2+repack1+~cs1.0.34-1
Done: Yadd <y...@debian.org>

We believe that the bug you reported is fixed in the latest version of
node-json-stable-stringify, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1043...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yadd <y...@debian.org> (supplier of updated node-json-stable-stringify package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 12 Aug 2023 16:05:34 +0400
Source: node-json-stable-stringify
Architecture: source
Version: 1.0.2+repack1+~cs1.0.34-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Yadd <y...@debian.org>
Closes: 1043519
Changes:
 node-json-stable-stringify (1.0.2+repack1+~cs1.0.34-1) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.2
   * Drop component fast-json-stable-stringify and repack (Closes: #1043519)
Checksums-Sha1: 
 680bf5ff3b2a1a9466480ad0a98ae634b98c6e23 2835 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34-1.dsc
 c0fb25e4d957e0ee2e497c1f553d7f8bb668fd75 1933 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34.orig-types-json-stable-stringify.tar.gz
 d14dc87ad7759b85b5d9e132289eebd886a15696 8946 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34.orig.tar.gz
 29a718eea08e6855c8e9c504286688d1eaa4ab70 3160 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34-1.debian.tar.xz
Checksums-Sha256: 
 3964294d00d52596786204dd973a744669c5af607c6f644cb44e0698780b3b9d 2835 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34-1.dsc
 97957e4ca64da7951874e9b495b4190fe20db19b32bbb04d4a5efaa681253156 1933 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34.orig-types-json-stable-stringify.tar.gz
 0b2e38dafef8c58024c0ef63791442f1b4cbaf5616ab6f19296d33b99a1e733d 8946 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34.orig.tar.gz
 40b31360980dc3e9d5af650a9c9ba39b50e3d11e1a31839b98e4f0c5632ab2a0 3160 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34-1.debian.tar.xz
Files: 
 a98d477f4f7914fe24bd20991763ab62 2835 javascript optional 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34-1.dsc
 520af6e37f09fa80924c364abed1b5cf 1933 javascript optional 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34.orig-types-json-stable-stringify.tar.gz
 39ee7deacd3c6e0190ba63338d23ddb1 8946 javascript optional 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34.orig.tar.gz
 adf20f63ad12584c7cce5d7f5165189f 3160 javascript optional 
node-json-stable-stringify_1.0.2+repack1+~cs1.0.34-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmTXdmEACgkQ9tdMp8mZ
7ulwRg/+K7OZu/+69o1MYvCZOKOQu0dfBTa3fsN10uQc4UkhFA9BPQVUu0vnQpCu
lHacKhHwdiKphHNNW7NbLloifbr3D0WZYS/SlWhvhNtn9/ST8vGRiDdmN38Dlt3f
CjIXM0yooGh7vCyYUSNmD45Xmq9aiqUT7ZdFuAsL9hh3ccWtvjQI76rCIbNyenuU
+DMF8lHo58c9JtVJioYMVzDeTQOiv6DfsNCX9Qv9HeIGAG75dzPv7UsFB14yWEsJ
083UjTMhjj/hJD/hnXtM29fVwWETtKnA5n/IfkwPdjWbOyNKXmNw/9OpF2Y0hPi5
+K1G8gw8FWgL83Z2lPjIcEYR7/mJEMt9Jz7mzdEs5gWzh4FmlyCQb04a0uMVvltU
rhUjrF10ENS7bZRoO1gu0lKvoXYFZyu5lqq5fgEkN7iCHmdYl3Dofd312Mcfrncs
DTrQcmo9v/438YB0MPSqaRYmPZb5SYMgF81VeT6hndsDMb9dbGNmTDrXFBqU69Nd
3c5eFwWdl6RzSXUiLb/Mh3nHkJKnpzY3eVBo9OtrKRgf3x7OHg1lY8pGn+kfQdBU
8jTHVkDApyU7iShMSXaGhpXUt2G9zhpSAF+rU0PzmmY13Ov4vILbQfzOncPgbE81
AiweStTTW0FtpBOuyL6ehqawH0+Qf4ue7GuDxcFuC1s0U72yx6s=
=jHB+
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to