Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 272101 - net-p2p/amule-2.2.5: amulecmd always shows 000.part.met
Summary: net-p2p/amule-2.2.5: amulecmd always shows 000.part.met
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo net-p2p team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-01 14:56 UTC by Sebastian Koehler
Modified: 2009-07-15 09:51 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Koehler 2009-06-01 14:56:14 UTC
The amulecmd command does not correctly display the *.part.met information in the show dl and show ul output. It will display 000.part.met for all downloads.

$ amulecmd
This is amulecmd 2.2.5

Creating client...
Succeeded! Connection established to aMule 2.2.5

---------------------------------------
|          aMule text client          |
---------------------------------------

Use 'Help' for command list

aMulecmd$ show dl
 > 00000000000000000000000000000000 File_A.download
 >       [1.3%]    0/   0          - Waiting - 000.part.met - Auto [Hi]
 > 00000000000000000000000000000000 File_B.download
 >       [0.0%]    0/   0          - Waiting - 000.part.met - Auto [Hi]

Reproducible: Always

Steps to Reproduce:
1. Add new download
2. invoke amulecmd
3. issue show dl to check *.part.met file name

Actual Results:  
will always display 000.part.met

Expected Results:  
should return the correct temporary file name of the running download
Comment 1 Raúl Porcel (RETIRED) gentoo-dev 2009-06-27 14:36:47 UTC
Did this happen with 2.2.4? Also you should report this upstream
Comment 2 Sebastian Koehler 2009-06-28 14:11:10 UTC
Yes, 2.2.4 had the same cosmetic issue. I've just opend a bug in aMule Mantis.
http://www.amule.org/abugs/view.php?id=1537
Comment 3 Sebastian Koehler 2009-07-15 09:51:57 UTC
The reported bug is only present on big endian systems. It has been resolved in amule SVN 9701.