aMule Forum

English => aMule Help => Topic started by: King84 on April 03, 2012, 02:01:49 PM

Title: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 03, 2012, 02:01:49 PM
Hi everybody,
everytime I open aMule I see these writings in the log:

Code: [Select]


Ciao a tutti,
ogni volta che apro aMule nel Log ci sono queste scritte:

Code: [Select]
[...]
[b]2012-03-29 08:10:58: Stai utilizzando una versione non aggiornata di aMule!
2012-03-29 08:10:58: La tua versione di aMule è la 2.2.6 e l'ultima è la 2.3.1
2012-03-29 08:10:58: L'ultima versione è sempre disponibile su http://www.amule.org[/b]
[...]

Which means "You are using a not updated version of aMule! / Your aMule version is 2.2.6, the last is 2.3.1 / The last version is always disposable on http://www.amulw.org"

I cannot understand what I have to do to update it!
I am using Linux Mint 11 64bit, in the Application AUpdate Manager Program, the most recension version is 2.2.6 (And not 2.3.1)
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: GonoszTopi on April 03, 2012, 08:40:38 PM
I believe noone made packages for Linux Mint. Either you bug your distro's packagers to upgrade, or you compile aMule yourself.
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 05, 2012, 07:25:23 PM
Already bugged 'em, but they didn't answer.

I want to compile it by myself.... HOW?
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: Stu Redman on April 05, 2012, 07:58:01 PM
Mint is derived from Ubuntu -> http://wiki.amule.org/index.php/HowTo_Compile_In_Ubuntu
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 08, 2012, 08:13:49 PM
COuld you please provide me .deb installation files for it?
Please?
64-bit?
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 09, 2012, 12:31:35 PM
Code: [Select]
Ok I wanted to avoid spending my Easter's monday at it but....let's do it....

As written in [url]http://wiki.amule.org/index.php/HowTo_Compile_In_Ubuntu[/url]

[code]ale@beast ~ $ sudo apt-get install g++ binutils-dev libcrypto++-dev libgtk2.0-dev libgd2-xpm-dev libgeoip-dev libupnp3-dev zlib1g-dev autopoint
[sudo] password for ale:
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
autopoint è già alla versione più recente.
g++ è già alla versione più recente.
libgd2-xpm-dev è già alla versione più recente.
libgeoip-dev è già alla versione più recente.
libgtk2.0-dev è già alla versione più recente.
zlib1g-dev è già alla versione più recente.
È stato impostato zlib1g-dev per l'installazione manuale.
libcrypto++-dev è già alla versione più recente.
libupnp3-dev è già alla versione più recente.
binutils-dev è già alla versione più recente.
Il seguente pacchetto è stato installato automaticamente e non è più richiesto:
  libnspr4-0d
Usare "apt-get autoremove" per rimuoverli.
0 aggiornati, 0 installati, 0 da rimuovere e 3 non aggiornati.
ale@beast ~ $

Code: [Select]
ale@beast ~ $ sudo apt-get install libcrypto++-utils
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
libcrypto++-utils è già alla versione più recente.
Il seguente pacchetto è stato installato automaticamente e non è più richiesto:
  libnspr4-0d
Usare "apt-get autoremove" per rimuoverli.
0 aggiornati, 0 installati, 0 da rimuovere e 3 non aggiornati.
ale@beast ~ $

Code: [Select]
ale@beast /usr/share/crypto++ $ cryptest v

[...]

passed    signature and verification
passed    checking invalid signature

All tests passed!

Test ended at Mon Apr  9 12:17:53 2012
Seed used was: 1333966672
ale@beast /usr/share/crypto++ $

Code: [Select]
ale@beast /usr/share/crypto++ $ mkdir /home/ale/.aMule/wx
ale@beast /usr/share/crypto++ $

From the official wx homepage I just downloaded wxGTK-2.8.12.tar.gz in my home, so I write
Code: [Select]
ale@beast ~ $ tar xzf wxGTK-2.8.12.tar.gz
ale@beast ~ $
and it decompresses the archive into the folder named wxGTK-2.8.12

The guide says: "Extract it with tar xzf wxGTK-2.8.12.tar.gz. Make and cd to wx/build and run
../wxGTK-2.8.12/configure --with-gtk --without-libtiff --without-subdirs --enable-unicode --enable-optimise
then make "

[code]ale@beast ~/wxGTK-2.8.12 $ make
make: *** Nessun obiettivo specificato e nessun makefile trovato.  Arresto.
ale@beast ~/wxGTK-2.8.12 $
[/code]
... MAKE what?!? WHere? How??!?

Intuitively I cd to wx/build and run
Code: [Select]
ale@beast ~/wxGTK-2.8.12/build $ ../wxGTK-2.8.12/configure --with-gtk --without-libtiff --without-subdirs --enable-unicode --enable-optimise
bash: ../wxGTK-2.8.12/configure: File o directory non esistente
ale@beast ~/wxGTK-2.8.12/build $
Errors! WHy? What should I do?

I'm stuck!
The guide isn't right!
It is not explained in a good manner.
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: Stu Redman on April 09, 2012, 02:23:00 PM
You are not supposed to use .aMule as the build directory, but it's not a problem.
Quote
The guide says: "Extract it with tar xzf wxGTK-2.8.12.tar.gz. Make and cd to wx/build and run
means simply
Code: [Select]
mkdir /home/ale/.aMule/wx
mkdir /home/ale/.aMule/wx/build
cd /home/ale/.aMule/wx/build
"mkdir" stands for "make directory".
Quote
The guide isn't right!
Yes, it is.
Quote
g++ è già alla versione più recente.
Please switch your system language to English before posting command outputs like this. I can't read that, and won't bother to translate it.
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 10, 2012, 08:09:54 AM
Code: [Select]
ale@beast ~ $ mkdir /home/ale/.aMule/wx
ale@beast ~ $ mkdir /home/ale/.aMule/wx/build
ale@beast ~ $ cd /home/ale/.aMule/wx/build
ale@beast ~/.aMule/wx/build $ ../wxGTK-2.8.12/configure --with-gtk --without-libtiff --without-subdirs --enable-unicode --enable-optimise
bash: ../wxGTK-2.8.12/configure: File o directory non esistente
ale@beast ~/.aMule/wx/build $

o = or
non esistente = not existing
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 10, 2012, 08:16:52 AM
One week and still nobody told me the exact syntax to update this damn program.
Is this possible, in 2012?
No 64-bit packages for Ubuntu?
WTF?
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: Stu Redman on April 10, 2012, 06:51:56 PM
"Updating this damn program" (aka building it from source) is perfectly easy for people with some basic computer skills which you totally lack (along with communication skills, and understanding how to motivate people to spend their free time to help other people).

You are not even able to find the right forum for your rants. We are not responsible for Mint packages. Neither are the Ubuntu people btw.
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 11, 2012, 08:20:31 AM
*thumbs up*
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: King84 on April 12, 2012, 10:11:41 AM
For the record I want to make the point that the updating of aMule from version 2.2.6 to version 2.3.1 on Linux Mint 11 64-bit is now totally completed. I didn't need to contact Linux Mint, nor compiling myself the newer version, but simply asking for help on another forum which, evidently, is more qualified.
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: Stu Redman on April 12, 2012, 02:23:21 PM
I'm afraid we can only send incompetent entitled Italian idiots there (http://www.linuxmind-italia.org/index.php?topic=13377.msg155031#msg155031).

It appears there are aMule packages for Debian Sid (http://packages.debian.org/sid/amule) that work for Mint too, that's all.
Since Ubuntu 12.4 will have aMule 2.3.1 packages as well, the next Mint version should have them too anyway.
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: GonoszTopi on April 13, 2012, 07:15:19 AM
[...] find the right forum [...]
I [...] need to [...] simply asking for help on another forum [...].
That's how things work.
Title: Re: Cannot update from 2.2.6 to 2.3.1 (64-bit)
Post by: Stu Redman on April 13, 2012, 01:34:00 PM
Hey, did you delete Kry's post or what? Without it my last post makes not much sense.