Bug 795

Summary: Missing component in bugzilla xorg-x11-drv-nvidia-173xx and nvidia-173xx-kmod
Product: Infrastructure Reporter: Nicolas Chauvet <kwizart>
Component: BugzillaAssignee: Thorsten Leemhuis <fedora>
Status: RESOLVED FIXED    
Severity: normal CC: lxtnow, matthias, mschwendt
Priority: P5    
Version: NA   
Hardware: All   
OS: GNU/Linux   
namespace:
Attachments: Patch aimed to fix the missing 173xx component

Description Nicolas Chauvet 2009-08-31 20:44:25 CEST
xorg-x11-drv-nvidia-173xx and nvidia-173xx-kmod are missing from our bugzilla.
Comment 1 Michael Schwendt 2009-09-01 09:18:39 CEST
If it's not in the owners.list files, it won't be synced.

[...]

Currently, only the "live555" entry in the free-rawhide owners list causes problems, since it specifies a bad comma-separated list for the primary owner field.
Comment 2 Nicolas Chauvet 2009-09-02 17:27:43 CEST
live555 should be set to me As I'm the current active maintainer.

rathan can be kept on the co-maintainer list.

But indeed, there is no 173xx packages in owner list. It should have been added as the initial rpmfuison import.

I have no right to modify owner list, How can I do to be allowed to modify them ?
Comment 3 Xavier Lamien 2009-09-02 18:02:05 CEST
Fixed.
You have been set as main owner.
Comment 4 Nicolas Chauvet 2009-09-02 18:17:07 CEST
Created attachment 278 [details]
Patch aimed to fix the missing 173xx component

Also with this patch:
- Remove legacy nvidie serie that never existed in rpmfusion.
- Rename 96 kernel module according to the new Summary
Comment 5 Nicolas Chauvet 2009-09-07 21:58:36 CEST
Is it fixed ?
Comment 6 Xavier Lamien 2009-09-08 00:53:29 CEST
yeah,
Looks like i skipped the heads up on that one.

Please check that all packages are fine that way.
Comment 7 Nicolas Chauvet 2009-09-08 12:20:26 CEST
(In reply to comment #6)
> yeah,
> Looks like i skipped the heads up on that one.
> 
> Please check that all packages are fine that way.
> 

173xx are fine, but legacies are still here.( in bugzilla component).
Comment 8 Michael Schwendt 2009-09-09 10:51:54 CEST
Removing components automatically is not implemented. It could be done, but typically a component cannot be removed because there are tickets assigned to it. Then somebody needs to move existing tickets elsewhere before a component could be removed. Or put back the component in the file to sync from if there are too many tickets. Else the sync script would need to decide whether to print a warning or ignore such issues. It's a can of worms.

nvidia-legacy-kmod
| Sorry, there is 1 bug outstanding for this component.
| You must reassign that bug to another component before
| you can delete this one. 
 => moved + deleted

xorg-x11-drv-nvidia-legacy
 => deleted