Your message dated Sun, 11 Feb 2024 18:23:24 +0000
with message-id <e1rzeu8-007fcb...@fasolo.debian.org>
and subject line Bug#1063685: fixed in precious 0.6.0-4
has caused the Debian Bug report #1063685,
regarding precious - upcoming rust-indexmap update.
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.)


-- 
1063685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: precious

Now that rust-ahash 0.8 is in trixie and noble I hope to update
rust-hashbrown and rust-indexmap soon to versions 0.14
and version 2 respectively. The new versions are currently
available in experimental.

precious does not use hashbrown directly, and already uses
indexmap 2 upstream, so the fix is a simple matter of
dropping a patch and updating the build dependency.

Debdiff is attatched.
diff -Nru precious-0.6.0/debian/changelog precious-0.6.0/debian/changelog
--- precious-0.6.0/debian/changelog     2024-01-30 14:43:30.000000000 +0000
+++ precious-0.6.0/debian/changelog     2024-02-11 01:24:39.000000000 +0000
@@ -1,3 +1,10 @@
+precious (0.6.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop 2001_indexnap.patch and update build-depends for indexmap 2.
+
+ -- Peter Michael Green <plugw...@debian.org>  Sun, 11 Feb 2024 01:24:39 +0000
+
 precious (0.6.0-3) unstable; urgency=medium
 
   * update patch 2001_toml;
diff -Nru precious-0.6.0/debian/control precious-0.6.0/debian/control
--- precious-0.6.0/debian/control       2024-01-30 14:34:12.000000000 +0000
+++ precious-0.6.0/debian/control       2024-02-11 01:24:24.000000000 +0000
@@ -21,8 +21,8 @@
  librust-filetime-0.2+default-dev (>= 0.2.18),
  librust-globset-0.4+default-dev (>= 0.4.9),
  librust-ignore-0.4+default-dev (>= 0.4.18),
- librust-indexmap-1+default-dev (>= 1.9.1),
- librust-indexmap-1+serde-dev (>= 1.9.1),
+ librust-indexmap-2+default-dev (>= 2.0.2),
+ librust-indexmap-2+serde-dev (>= 2.0.2),
  librust-itertools+default-dev (<< 0.11),
  librust-log-0.4+default-dev (>= 0.4.17),
  librust-md5-0.7+default-dev,
diff -Nru precious-0.6.0/debian/patches/2001_indexmap.patch 
precious-0.6.0/debian/patches/2001_indexmap.patch
--- precious-0.6.0/debian/patches/2001_indexmap.patch   2023-12-19 
20:58:05.000000000 +0000
+++ precious-0.6.0/debian/patches/2001_indexmap.patch   1970-01-01 
00:00:00.000000000 +0000
@@ -1,18 +0,0 @@
-Description: accept older branch of crate indexmap
-Author: Jonas Smedegaard <d...@jones.dk>
-Bug-Debian: https://bugs.debian.org/1053953
-Forwarded: not-needed
-Last-Update: 2023-12-19
----
-This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
---- a/Cargo.toml
-+++ b/Cargo.toml
-@@ -35,7 +35,7 @@
- filetime = "0.2.22"
- globset = "0.4.13"
- ignore = "0.4.20"
--indexmap = { version = "2.0.2", features = ["serde"] }
-+indexmap = { version = ">= 1.9.3, <= 2.0.2", features = ["serde"] }
- itertools = ">= 0.9.0, < 0.11.0"
- log = "0.4.20"
- md5 = "0.7.0"
diff -Nru precious-0.6.0/debian/patches/series 
precious-0.6.0/debian/patches/series
--- precious-0.6.0/debian/patches/series        2023-11-28 23:56:05.000000000 
+0000
+++ precious-0.6.0/debian/patches/series        2024-02-11 01:23:59.000000000 
+0000
@@ -1,4 +1,3 @@
 2001_comfy-table.patch
-2001_indexmap.patch
 2001_toml.patch
 2002_privacy.patch

--- End Message ---
--- Begin Message ---
Source: precious
Source-Version: 0.6.0-4
Done: Jonas Smedegaard <d...@jones.dk>

We believe that the bug you reported is fixed in the latest version of
precious, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard <d...@jones.dk> (supplier of updated precious 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: Sun, 11 Feb 2024 18:46:17 +0100
Source: precious
Architecture: source
Version: 0.6.0-4
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <d...@jones.dk>
Changed-By: Jonas Smedegaard <d...@jones.dk>
Closes: 1063685
Changes:
 precious (0.6.0-4) unstable; urgency=medium
 .
   * relax build-dependencies for crate indexmap;
     closes: bug#1063685, thanks to Peter Michael Green
Checksums-Sha1:
 d88b19d75d7f83035e1f142fecd7d4162e2dcc01 2993 precious_0.6.0-4.dsc
 294ae9d55b4a1cdde1583f1b68ac87c41ad341f7 29632 precious_0.6.0-4.debian.tar.xz
 10a63d5649a98d4e6da0b47bc109fa439bf5c410 18538 precious_0.6.0-4_amd64.buildinfo
Checksums-Sha256:
 19eafb77c54309c635bc2784c029df4313bf1a030f792d37a55ac91b709808bb 2993 
precious_0.6.0-4.dsc
 5e5ffae0e4a43cd05a41cf39c5110675b3ebf96b144742ac56e1affd6c913e49 29632 
precious_0.6.0-4.debian.tar.xz
 f883255d22df7a2beec9cd7b31f79eef6b102b5d297be01c21ddd4f65cc4bfa4 18538 
precious_0.6.0-4_amd64.buildinfo
Files:
 c007ec7845528b2ed62fd0359b536555 2993 devel optional precious_0.6.0-4.dsc
 b7ba2623de83149c6673a0ae405c05c3 29632 devel optional 
precious_0.6.0-4.debian.tar.xz
 8c00b32f31c8eb7397b69e6bf1b980f0 18538 devel optional 
precious_0.6.0-4_amd64.buildinfo

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

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmXJCZMACgkQLHwxRsGg
ASGFVBAAllJHitdWQENjNJbIf39PQwva4wK41da8CyzWfMZHKnQ8vz4ggBgNmt1e
I6yfV2dwBDOoRcWykR5+CQc1+jEN/XqsYWSneoupYpndsOsFVIPLpXKhSgT18L+i
8sftmD/ccOjs4S51aLXleVJlitn3/xpUWPEwlJVeoHLvFpjl590eQPoUOW/9AiYb
NccdfNEpstyuTtZEqbr10ilQjypmJWmcsuuHMozqYxZsu5bPj932Sk0khNoZsp6V
LxUdqX1EgbBFYrIijxzswE4B20WfB2uym76n3He1nuPzpFmzq12brseiS1ZVf4kh
HQlC0JMvnp2i0PK5WdZM0z68JWY0HeqJ3v9g3OVBj1mCTYxvEfR9MmzK2xVR6qlo
mUsQ7TKcfpp9lMQkzIkVY1Y4wtV6N6Y8A1ys9VctCiRtWNPehCHHb59yAd2+OZb3
ZGQplQWr5AcH8QUqWYIi8/lw7lIRmNHZ8gREtpAgcnLXtCQ/CcQYD7ZdzrfFSoyB
khqs33sLSdSizkhZ2SCpDAlZ92z3rMtwqTP1kmn973wJMrDDQ2jRRnAvEqV/2RCX
j7TeVC5GFJH7857Rux1kyJQ5EDwLgu/15OwaVVaY2609DSHmmcR5ixpbhMf2MyCf
f8hJfXhMQp36E/wEsHxE34FIqSV7SocOdbwlLwWaGznxyVEd3jU=
=Ni0e
-----END PGP SIGNATURE-----

Attachment: pgph25_r5Cmui.pgp
Description: PGP signature


--- End Message ---

Reply via email to