Bug 228821

Summary: Many unowned directories since crazy version up and down
Product: [Fedora] Fedora Reporter: Robert Scheck <redhat-bugzilla>
Component: tclAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 8.4.13-10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-02-16 14:00:23 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:
Attachments:
Description Flags
Unified diff of tcl spec files none

Description Robert Scheck 2007-02-15 11:41:39 UTC
Description of problem:
Marcela, can you please ensure after such crazy version hoppings, that you add 
the lines for owning directories to the tcl package back, immediately? 

Because currently the following directories are unowned:
/usr/share/tcl8.4
/usr/share/tcl8.4/encoding
/usr/share/tcl8.4/http1.0
/usr/share/tcl8.4/http2.5
/usr/share/tcl8.4/msgcat1.3
/usr/share/tcl8.4/opt0.4
/usr/share/tcl8.4/tcltest2.2
/usr/share/tcl8.4

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

Actual results:
Many unowned directories since crazy version up and downgrades.

Expected results:
Fix like at my patch or better - soon, please.

Additional info:
BTW, did you EVER read the Fedora Packaging Guidelines before submitting an 
alpha version of a package with incorrect Version tag into Fedora resulting in 
the use of Epoch for the downgrade? I'm assuming not, otherwise you wouldn't 
have done that absolute nonsense... :-(

Comment 1 Robert Scheck 2007-02-15 11:43:19 UTC
Created attachment 148105 [details]
Unified diff of tcl spec files

Comment 2 Robert Scheck 2007-02-16 14:00:23 UTC
Fixed in tcl-8.4.13-10, but you caused exactly the same problem for the tk 
package today! See bug #226494 comment #1 for more information.