Bug 368051

Summary: Bittorrent port setting should go all the way to 11
Product: [Fedora] Fedora Reporter: David Nielsen <gnomeuser>
Component: MiroAssignee: Thorsten Scherf <tscherf>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8CC: alex, triage
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: bzcl34nup
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-09 05:05:55 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:

Description David Nielsen 2007-11-06 09:37:20 UTC
Description of problem:
This is likely an upstream bug but upstream is hiding the good stuff somewhere
and it likely also requires me to open yet another bugzilla account.

When setting the bittorrent port you are unable to go beyond port ~37000 however
I need to set it to 50301, if I do that however my setting is rudely resat to
the default 8600 or 8700 setting.

Please fix.

Version-Release number of selected component (if applicable):
Miro-0.9.8.1-7.fc8

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Alex Lancaster 2007-11-17 02:56:09 UTC
Can you reproduce this bug with the latest Miro in F-7 which is 0.9.9.9? (yum
update)

Comment 2 David Nielsen 2007-11-17 08:49:52 UTC
Port number is still limited to 32768, my setup uses 50381 which means we still
need to go all the way to eleven.

Comment 3 Alex Lancaster 2007-11-17 09:49:50 UTC
I can duplicate this in Miro-1.0.  This is definitely an upstream bug:

http://bugzilla.pculture.org/show_bug.cgi?id=5177

Comment 4 Alex Lancaster 2007-11-17 09:51:53 UTC
According to this:

http://bugzilla.pculture.org/show_bug.cgi?id=5177#c6

it's the display of the ports that is wrong, but the ports do get set properly
(haven't tested that myself though).

Comment 5 Bug Zapper 2008-04-04 14:26:15 UTC
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
rawhide.
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 6 Bug Zapper 2008-11-26 08:12:46 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 7 Bug Zapper 2009-01-09 05:05:55 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.