Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 63371

Summary: RPM mode verify errors for gimp and gimp-devel
Product: [Retired] Red Hat Public Beta Reporter: Vladimir Ivanovic <vladimir>
Component: gimpAssignee: Matt Wilson <msw>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: skipjack-beta2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-04-15 03:26:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 61590    

Description Vladimir Ivanovic 2002-04-13 00:37:03 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020308

Description of problem:
Three files are in two packages:
  /usr/lib/gimp/1.2/modules/libcolorsel_gtk.a
  /usr/lib/gimp/1.2/modules/libcolorsel_triangle.a
  /usr/lib/gimp/1.2/modules/libcolorsel_water.a
and their modes differ in the two packages. This causes rpmv to complain.

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


How reproducible:
Always

Steps to Reproduce:
1. rpm -V gimp gimp-devel
2.
3.
	

Actual Results:  # rpm -V gimp gimp-devel
.......T c /etc/X11/applnk/Graphics/gimp.desktop
.......T c /usr/share/mc/templates/gimp.desktop
.M......   /usr/lib/gimp/1.2/modules/libcolorsel_gtk.a
.M......   /usr/lib/gimp/1.2/modules/libcolorsel_triangle.a
.M......   /usr/lib/gimp/1.2/modules/libcolorsel_water.a


Expected Results:  Bliss and eternal happiness, wealth, power and all the latest
gadgets from ThinkGeek. Oh, and no ".M......" output when I rpmv the gimp packages.

Additional info: Actually, my system is not skipjack-beta2, but skipjack-beta1
plus all the up2dates since you do not offer an upgrade path from beta1 to beta2.
Comment 1 Matt Wilson 2002-04-15 22:24:46 UTC 

*** This bug has been marked as a duplicate of 43317 ***