amule can't handle large files (4GB or more)

[Felipe Figueiredo]

Binary package hint: amule

Files greater than 4 GB don't even appear in the search, and can't be added as links. When you try to add a link of a large file, the message log says

Invalid ed2k link! Error: Invalid file size

I tried several sizes to try to approximate the limit size, with the following bogus links:

ed2k://|file|file3gb.ext|3221225472|030935A4C1D25BC69A7608F9A5807FD7|/
(valid size, adds "file3gb.ext" to the download list, with 0 sources)

ed2k://|file|file4gb.ext|4294967296|030935A4C1D25BC69A7608F9A5807FD7|/
(2008-02-17 20:24:38: Invalid ed2k link! Error: Invalid file size )

I tried reducing the size in each order of magnitude, to the following results:

4294967296 (4GB - invalid)
4284967296 valid size
4293967296 invalid
4290967296 invalid

So, reducing about 10MB from 4GB makes the link valid.

[Emilio Pozuelo Monfort (pochu)]

This is fixed in 2.2.0, and I'll upload it tomorrow.

[Felipe Figueiredo (philsf)]

On Sun 17 Feb 2008 21:12:43 Emilio Pozuelo Monfort wrote:
> This is fixed in 2.2.0, and I'll upload it tomorrow.
>
> ** Changed in: amule (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Emilio Pozuelo Monfort (pochu)
> Status: New => Fix Committed
>
>

Thanks for the quick answer!

Will it make it into -proposed or -backports?

regards
FF

[Emilio Pozuelo Monfort (pochu)]

Felipe Figueiredo wrote:
> On Sun 17 Feb 2008 21:12:43 Emilio Pozuelo Monfort wrote:
>> This is fixed in 2.2.0, and I'll upload it tomorrow.
>>
>> ** Changed in: amule (Ubuntu)
>> Importance: Undecided => Medium
>> Assignee: (unassigned) => Emilio Pozuelo Monfort (pochu)
>> Status: New => Fix Committed
>>
>>
>
> Thanks for the quick answer!
>
> Will it make it into -proposed or -backports?

It will go to hardy for now. I'll see if it's suitable to request a backport to
Gutsy, but that will need backporting libcrypto++ too.

>
> regards
> FF
>

[Launchpad Janitor (janitor)]

This bug was fixed in the package amule - 2.2.0~svn20080218-0ubuntu1

---------------
amule (2.2.0~svn20080218-0ubuntu1) hardy; urgency=low

  * New svn snapshot from 20080218 tarball, renamed debian/ to
    debian-upstream/.
    FeatureFreeze exception: LP: #192156.
    The 2.2.0 isn't released yet because of build failures in MacOS X,
    but is stable enough and recommended by upstream.
    LP: #40238, #112745, #65496, #123695, #192781.

  * debian/patches/cas_configfile.c_good_default_paths.diff:
    - Updated for the new release.
  * debian/patches/wx-2.8.diff,
    debian/patches/configure_proper_libpng_detection.diff,
    debian/patches/for_upstream-manpage_typos.diff
    - Removed, fixed upstream.
  * debian/patches/nodes-url.diff:
    - Removed, as upstream uses now a different server list.
  * debian/patches/series:
    - Updated accordingly.
  * debian/control:
    - Require libcrypto++-dev >= 5.5.2-1, as aMule now checks for crypopp
      instead of crypto++, and 5.5.2-1 added the necessary symlinks.
      Otherwise aMule FTBFS.
    - Build-depend on libgeoip-dev to get geoip support.
    - Require debhelper >= 5.0.51 to have dh_icons.
    - Moved homepage to the Homepage field.
    - Updated Standards-Version to 3.7.3. No changes needed.
  * debian/mans/amulegui.1:
    - Removed, as it's shipped upstream now.
  * debian/amule-utils-gui.manpages:
    - Ship amulegui.*1 manpages from upstream, and stop shipping
      debian/mans/amulegui.1
  * debian/rules:
    - Stop manually installing amulegui.desktop and amulegui.xpm.
      It's now done upstream.
    - No need to symlink debian/amule.xpm to debian/amule-32.xpm and
      remove it in clean. Let's rename amule-32.xpm to amule.xpm instead.
    - Build with geoip support.
    - Call dh_icons and dh_desktop.
    - Explicitly install debian/amule.xpm, as upstream's amule.xpm isn't
      menu-policy compliant (32x32 vs 128x128).
  * debian/amule-32.xpm, debian/amule.xpm:
    - Renamed debian/amule-32.xpm as debian/amule.xpm.
  * debian/amulegui.desktop:
    - Removed, it's included upstream now.

 -- Emilio Pozuelo Monfort <email address hidden> Mon, 18 Feb 2008 19:43:28 +0100