Bug 13569 - libx11-locale multilib conflicts (rarely)
Summary: libx11-locale multilib conflicts (rarely)
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 3.1
Assignee: Ross Burton
QA Contact:
URL: https://autobuilder.yoctoproject.org/...
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-10-03 12:35 UTC by Ross Burton
Modified: 2019-10-17 15:12 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2019-10-03 12:35:31 UTC 
In a multilib autobuilder build:

Error: Transaction check error:
  file /usr/share/X11/locale/C/Compose conflicts between attempted installs of lib32-libx11-locale-1:1.6.8-r0.x86 and libx11-locale-1:1.6.8-r0.core2_64
  file /usr/share/X11/locale/C/XLC_LOCALE conflicts between attempted installs of lib32-libx11-locale-1:1.6.8-r0.x86 and libx11-locale-1:1.6.8-r0.core2_64
  file /usr/share/X11/locale/am_ET.UTF-8/Compose conflicts between attempted installs of lib32-libx11-locale-1:1.6.8-r0.x86 and libx11-locale-1:1.6.8-r0.core2_64
  file /usr/share/X11/locale/am_ET.UTF-8/XLC_LOCALE conflicts between attempted installs of lib32-libx11-locale-1:1.6.8-r0.x86 and libx11-locale-1:1.6.8-r0.core2_64
  file /usr/share/X11/locale/armscii-8/Compose conflicts between attempted installs of lib32-libx11-locale-1:1.6.8-r0.x86 and libx11-locale-1:1.6.8-r0.core2_64
  file /usr/share/X11/locale/armscii-8/XLC_LOCALE conflicts between attempted installs of lib32-libx11-locale-1:1.6.8-r0.x86 and libx11-locale-1:1.6.8-r0.core2_64
[...]

Those files should have been identical, so we're not sure what happened here. Doesn't happen repeatedly, might be related to hash equiv.
Comment 1 Ross Burton 2019-10-17 15:12:31 UTC 
Hasn't happened since, maybe it was a bug in the old hash equiv code?