Bug 679973

Summary: Change top-level folder names in transmission
Product: [Fedora] Fedora Reporter: aznzhang
Component: transmissionAssignee: Rahul Sundaram <metherid>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: charles, jspaleta, metherid, sanjay.ankur
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 14:34:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description aznzhang 2011-02-24 00:56:00 UTC
Description of problem:
"in uTorrent, the top folder name in the torent is merely a suggestion and can be overridden, in transmission, this does not appear to be an option."

How reproducible:
Currently, no transmission client has this functionality enabled without a patch.

Steps to Reproduce:
1. Try to add a torrent file and change the top folder name.


There is a patch for this available on the ticket page for the issue:
https://trac.transmissionbt.com/ticket/1220

Please add the patch to future transmission releases; many users probably want/need this functionality.

Comment 1 Rahul Sundaram 2011-02-24 03:43:07 UTC
Charles,  thoughts?

Comment 2 Charles Kerr 2011-02-24 16:50:12 UTC
I'm not sure I understand this ticket. Why not comment in #1220 rather than here?

It seems like the OP is suggesting that Fedora accept this patch "downstream" at the distro level as sort of a mini-fork and take on responsibility of maintaining that feature.

Fedora certainly has the freedom to do that if they like, but it seems an odd choice. Why not wait for upstream to handle the ticket? What happens to Fedora users if the Transmission developers use a different implementation?

Comment 3 Rahul Sundaram 2011-02-24 17:16:44 UTC
Perhaps, I should have been more clear,  if the upstream patches are something I can use in Fedora now, I am open to doing that.  Otherwise this will have to wait.

Comment 4 Charles Kerr 2011-02-24 17:32:39 UTC
This isn't an upstream patch, it's a contributed patch that hasn't been reviewed/tested/endorsed upstream. Maybe it's great but I can't say.

Also, we're two weeks past feature freeze for F15... my opinion is to wait & revisit this for F16.

Comment 5 Fedora End Of Life 2012-08-16 14:34:43 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping