Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 228821 - Many unowned directories since crazy version up and down
Many unowned directories since crazy version up and down
Product: Fedora
Classification: Fedora
Component: tcl (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Marcela Mašláňová
Depends On:
  Show dependency treegraph
Reported: 2007-02-15 06:41 EST by Robert Scheck
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 8.4.13-10
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-16 09:00:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Unified diff of tcl spec files (840 bytes, patch)
2007-02-15 06:43 EST, Robert Scheck
no flags Details | Diff

  None (edit)
Description Robert Scheck 2007-02-15 06:41:39 EST
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:

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

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 06:43:19 EST
Created attachment 148105 [details]
Unified diff of tcl spec files
Comment 2 Robert Scheck 2007-02-16 09:00:23 EST
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.

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