Bug 19747 - "hash collision" messages when installing package "locales-en"
Summary: "hash collision" messages when installing package "locales-en"
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-10 13:15 CET by PC LX
Modified: 2016-12-07 12:31 CET (History)
3 users (show)

See Also:
Source RPM: locales-2.22-5.mga6.src.rpm
CVE:
Status comment:


Attachments

Description PC LX 2016-11-10 13:15:55 CET
Description of problem:

When upgrading a Mageia 5 system to cauldron, I see the following messages when the package "locales-en" is updated:

hash collision (4008928995) en_AU.iso88591, ar_BH.utf8M
hash collision (248735460) en_IE.iso88591, eu_ES.utf8M
hash collision (1904037018) en_SG, ar_TN.utf8M
hash collision (1904040618) en_ZW, ta_IN.utf8M
hash collision (1391945444) en_ZW.iso88591, af_ZA.utf8M



Version-Release number of selected component (if applicable):

# rpm -q locales locales-en 
locales-2.22-5.mga6
locales-en-2.22-5.mga6



How reproducible:

Always.



Steps to Reproduce:
1. Start with a up-to-date Mageia 5 system.
2. Remove the Mageia 5 repositories and add the Mageia 6/cauldron repositories.
3. Update the system by running "urpmi --auto-update".
4. See the messages "hash collision" when the package "locales-en" is updated.
David Walser 2016-11-11 16:10:04 CET

CC: (none) => thierry.vignaud, tmb

Comment 1 Marja Van Waes 2016-11-11 20:38:04 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

Comment 2 PC LX 2016-12-07 12:31:01 CET
On a recent upgrade from Mageia 5 system to cauldron, I did not see the above mentioned messages, so I think this issue is resolved and am marking it a such.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.