Your message dated Tue, 23 Jun 2026 15:33:52 +0000
with message-id <[email protected]>
and subject line Bug#1140594: fixed in ruby-histogram 0.2.4.1-3
has caused the Debian Bug report #1140594,
regarding ruby-histogram has an undeclared file conflict on /usr/bin/histogram
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 [email protected]
immediately.)


-- 
1140594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140594
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ruby-histogram
Version: 0.2.4.1-2
Severity: serious
User: [email protected]
Usertags: fileconflict
Control: affects -1 + outguess

ruby-histogram has an undeclared file conflict.  This may result in an
unpack error from dpkg.

The file /usr/bin/histogram is contained in the packages
 * outguess
   * 1:0.4-2 as present in trixie
   * 1:0.4-2+b1 as present in trixie
 * ruby-histogram/0.2.4.1-2 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation.  Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

Helmut Grohne

--- End Message ---
--- Begin Message ---
Source: ruby-histogram
Source-Version: 0.2.4.1-3
Done: Simon Quigley <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ruby-histogram, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon Quigley <[email protected]> (supplier of updated ruby-histogram 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 [email protected])


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

Format: 1.8
Date: Tue, 23 Jun 2026 10:19:19 -0500
Source: ruby-histogram
Architecture: source
Version: 0.2.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<[email protected]>
Changed-By: Simon Quigley <[email protected]>
Closes: 1140594
Changes:
 ruby-histogram (0.2.4.1-3) unstable; urgency=medium
 .
   * Remove /usr/bin/histogram, leaving the gem copy (Closes: #1140594).
Checksums-Sha1:
 56edf0cf32b19b5b461328b51d1e6828ada3f0ae 2084 ruby-histogram_0.2.4.1-3.dsc
 5bfe70c866f310e7faaaba262500edf0dc4e5bb0 2300 
ruby-histogram_0.2.4.1-3.debian.tar.xz
 ac56a7ccc9e698cf798ca147f72fac0401396c16 7812 
ruby-histogram_0.2.4.1-3_source.buildinfo
Checksums-Sha256:
 7df56b78ea6d33d96c9ebd0586f1a9218cae552d3302a49c21559574c3d47a89 2084 
ruby-histogram_0.2.4.1-3.dsc
 b86434b62c18e5430c3ed347dd39e16aab473601c85b0e761153b06123db0ef6 2300 
ruby-histogram_0.2.4.1-3.debian.tar.xz
 600888effe22fb8f2b4d1664f928d8d024189898df5a337a69f5e5483b3331a8 7812 
ruby-histogram_0.2.4.1-3_source.buildinfo
Files:
 39d6ab052a39c7137f3daebaee3a49cd 2084 ruby optional 
ruby-histogram_0.2.4.1-3.dsc
 71680dcc79702d6a122a6d1b69697f16 2300 ruby optional 
ruby-histogram_0.2.4.1-3.debian.tar.xz
 5c7ab3313253f5c67cb011f4b9bf6356 7812 ruby optional 
ruby-histogram_0.2.4.1-3_source.buildinfo

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

iQIzBAEBCgAdFiEEXHq+og+GMEWcyMi14n8s+EWML6QFAmo6pB0ACgkQ4n8s+EWM
L6RoFRAAgX1AC1QUWUlp7kRfmMMoKjgc1c7/Y/s4t6yQY6amm6cnIUHft3EzsDh5
GRjxCNE0/8QcqgQUG1mQqx55378W/8CrJHCXqnIZBLlMFtKsPtZ4G2Vzwn1bSfAU
BoQKCkR1II0aS+000HKB5U6z2U1Pbi860Ft7WL+tgj2XEZYIUrEOZOyVytk7DiF1
n4tfUNu0kYwwZ6ntwY/g/x3qST9n5xsoSRyDNdKkSb/wJScsuLXAiLyhwmJ1qzE4
vY/PCHoyGZS2jqXK1n0BNJRBwVLIo8XpSuLXBERf7TpcEFI9Wvvyp0iVr6u8J8f1
/zwxWsNQ3Yo7U6Pqeb8irXynZHtbhvFkomKD/e2umhItp8zn8ccVsLAzVl+Tk+8V
mmiYNUB5pXLznht6nNOT4JpQJxO/AFPG1bxbMEDOKAIqXgk8cG2z63D2Rw5cs6AK
EDmNlBJgHv8V2bE4Dstbp+NdrXberGV65eruZjvZFrVTKKt1ByexlYNN13vfgHVP
+51lV9HtZgvEBj2/mBk/NIrWrCclxdTKhbQIIX6UdPxlolVIia/eHHjkX40IgO6m
ekAT8DvlT69d9oQcWaphiK1dM/Qqv5U/ELsnNu3/Fm3Bf1rrqniE7RCfCQeXPjC0
9Ky/BU+IlggC/zEbuFlwXExl1AIT1NZdjMNzruPHBvY5XGfWAUY=
=MXFN
-----END PGP SIGNATURE-----

Attachment: pgpYM3I6kn9Fx.pgp
Description: PGP signature


--- End Message ---

Reply via email to