Bug 368051 - Bittorrent port setting should go all the way to 11
Bittorrent port setting should go all the way to 11
Product: Fedora
Classification: Fedora
Component: Miro (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Thorsten Scherf
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-06 04:37 EST by David Nielsen
Modified: 2009-01-09 00:05 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 00:05:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Nielsen 2007-11-06 04:37:20 EST
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):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Alex Lancaster 2007-11-16 21:56:09 EST
Can you reproduce this bug with the latest Miro in F-7 which is (yum
Comment 2 David Nielsen 2007-11-17 03:49:52 EST
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 04:49:50 EST
I can duplicate this in Miro-1.0.  This is definitely an upstream bug:

Comment 4 Alex Lancaster 2007-11-17 04:51:53 EST
According to this:


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 10:26:15 EDT
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
(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:

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 03:12:46 EST
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: 
Comment 7 Bug Zapper 2009-01-09 00:05:55 EST
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.

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