Bug 1788544

Summary:	systemtap-mode.elc conflicts
Product:	Red Hat Enterprise Linux 8	Reporter:	Martin Cermak <mcermak>
Component:	systemtap	Assignee:	Frank Ch. Eigler <fche>
systemtap sub component:	system-version	QA Contact:	Martin Cermak <mcermak>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	low	CC:	lberk, mcermak, mjw
Version:	8.2	Keywords:	Patch, Triaged
Target Milestone:	rc
Target Release:	8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	systemtap-4.1-3.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:54:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Cermak 2020-01-07 13:32:11 UTC

There is a tiny packaging problem in systemtap-devel-4.2-1.el8.i686 and systemtap-devel-4.2-1.el8.x86_64.  When one (or TPS) tries to install all the subrpms we ship via erratum, the transaction fails with:

=======
Error: Transaction check error:
  file /usr/share/emacs/site-lisp/systemtap-mode.elc conflicts between attempted installs of systemtap-devel-4.2-1.el8.i686 and systemtap-devel-4.2-1.el8.x86_64
=======

This is not a serious problem.  But for the sake of smooth installability, I propose to fix this in the future along with some more important update.

Comment 1 Frank Ch. Eigler 2020-01-07 13:58:56 UTC

As systemtap-devel is not intended to be multilib/multi-arch installable (unlike ordinary -devel subrpms), this test seems artificial / unnecessary.

Comment 2 Frank Ch. Eigler 2020-01-10 18:45:29 UTC

Will ditch generating the conflicting .elc file, like subversion does.

Comment 6 errata-xmlrpc 2020-04-28 15:54:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1652