LottaNZB doesn't handle correctly port change

Bug #245787 reported by Stéphane Maniaci
4
Affects Status Importance Assigned to Milestone
LottaNZB
Fix Released
High
Severin H

Bug Description

I got a NZB from Binsearch and loaded it in LottaNZB. Nothing, so I checked preferences and set port to 80 instead of 119, still nothing. Checked back preferences, and saw that port 119 was still set. I tried to change it from the Choose Usage Mode dialog and from Preferences, but both doesn't register the port change.

What I don't understand is why I can download with hellanzb (after setting the server name, port and auth in /etc/hellanzb.conf), and why I can't if I edit the ~/.lottanzb.conf file in the same way.

Revision history for this message
Stéphane Maniaci (stephh) wrote :
Revision history for this message
Stéphane Maniaci (stephh) wrote :
Revision history for this message
Stéphane Maniaci (stephh) wrote :

The debug log

Revision history for this message
VuDu (vudu-curse) wrote :

I'm having the same problem.
I've updated from 0.2, not clean install.
It's useless to change the port, because it'll go back to 119.

Revision history for this message
Severin H (severinh) wrote :

Hi VuDu, hi Stéphane,

I didn't have the time yet to reproduce and confirm this bug but since there are two people experiencing the same problem, I set the bug's status to 'Confirmed'. This is a quite severe problem. We need to fix it urgently and it might also be a reason to release a bug-fix version like 0.3.1.

Thanks for reporting this bug!

Changed in lottanzb:
assignee: nobody → lottanzb
importance: Undecided → High
milestone: none → 0.3
status: New → Confirmed
Revision history for this message
Severin H (severinh) wrote :

The bug should be fixed both in lp:lottanzb and lp:lottanzb/0.3 now.

@Stéphane: I would really appreciate it if you gave it a try before we release 0.3.1.

Changed in lottanzb:
assignee: lottanzb → lantash
status: Confirmed → Fix Committed
Severin H (severinh)
Changed in lottanzb:
milestone: 0.3 → 0.3.1
Revision history for this message
VuDu (vudu-curse) wrote :

Sorry, but I'm not used to launchpad, how can I download lp:lottanzb/0.3 or lp:lottanzb.
bzr branch lp:lottanzb/0.3 doesn't mean much to me... and the answers section seems to be empty. :(

Revision history for this message
Sander Tuit (avirulence) wrote : Re: [Bug 245787] Re: LottaNZB doesn't handle correctly port change

Hi,

If you have bzr (or bazaar) installed, you should be able to:

1) Launch a terminal
2) type: bzr branch lp:lottanzb/0.3
3) cd 0.3
4) sudo python setup.py install

On Tue, Jul 8, 2008 at 7:21 PM, VuDu <email address hidden> wrote:
> Sorry, but I'm not used to launchpad, how can I download lp:lottanzb/0.3 or lp:lottanzb.
> bzr branch lp:lottanzb/0.3 doesn't mean much to me... and the answers section seems to be empty. :(
>
> --
> LottaNZB doesn't handle correctly port change
> https://bugs.launchpad.net/bugs/245787
> You received this bug notification because you are subscribed to
> LottaNZB.
>
> Status in LottaNZB • Automated Usenet Client: Fix Committed
>
> Bug description:
> I got a NZB from Binsearch and loaded it in LottaNZB. Nothing, so I checked preferences and set port to 80 instead of 119, still nothing. Checked back preferences, and saw that port 119 was still set. I tried to change it from the Choose Usage Mode dialog and from Preferences, but both doesn't register the port change.
>
> What I don't understand is why I can download with hellanzb (after setting the server name, port and auth in /etc/hellanzb.conf), and why I can't if I edit the ~/.lottanzb.conf file in the same way.
>

Revision history for this message
Severin H (severinh) wrote :

A second and more convenient way is to wait a few hours until 0.3.1 is available at lottanzb.org. ;-)

Revision history for this message
VuDu (vudu-curse) wrote :

Just installed it from bzr like aVirulence said and the problems seems fixed :)

Thanks ;)

Revision history for this message
Stéphane Maniaci (stephh) wrote :

Just updated, works fine.

Severin H (severinh)
Changed in lottanzb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.