aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Problem with today cvs  (Read 5155 times)

mithrandir77

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 69
Problem with today cvs
« on: January 19, 2006, 12:56:06 PM »

Configure and install with no problems

But if i run amuled:

> amuled
amuled: OnInit - starting timer
This binary requires you to run amule --run-this-at-my-own-risk-kthx and only if you're very sure of it.



I don't understand...  What's the problem? ?( ?( ?(
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Problem with today cvs
« Reply #1 on: January 19, 2006, 01:08:37 PM »

Lack of english reading? read the message.
Logged

mithrandir77

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 69
Re: Problem with today cvs
« Reply #2 on: January 19, 2006, 01:12:04 PM »

Quote
Originally posted by Kry
Lack of english reading? read the message.

I don't have lack of english reading...

I don't understand the message...

Why 'This binary requires you to run amule --run-this-at-my-own-risk-kthx'?

I can't run amuled instead of amule?
Or i have to run amule with that option???  ?(
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: Problem with today cvs
« Reply #3 on: January 19, 2006, 01:26:46 PM »

You have to add the "--run-this-at-my-own-risk-kthx" option to your command line in order to start any binary built from this Tarball after understanding that it means "Run this at my own risk".

See here: http://forum.amule.org/thread.php?threadid=8893

Kry is implementing large file support at the moment which seems to be a very invasive task, therefore this barrier was added in order to prevent people from using this code without knowing that it's possibly breaking things.

Use an earlier snapshot and wait a few days...
Logged

mithrandir77

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 69
Re: Problem with today cvs
« Reply #4 on: January 19, 2006, 01:29:13 PM »

Ok, thanks a lot.

It's the first time i meet this message.

I have just read that post about some problems, but it is not present any information about this option, so i don't understand.

 :P
Logged

Arichy

  • Full Member
  • ***
  • Karma: 0
  • Offline Offline
  • Posts: 224
Re: Problem with today cvs
« Reply #5 on: January 19, 2006, 01:46:28 PM »

2.1.0 is not usable - it crashes all the time. Bugsquashing is imho more required than implementing new features like large file support. Also it should have been better to name 2.1.0 2.1.0RC1. I use 2.0.3 again now - sorry, but that runs fine stable all the time!
Logged
Gentoo i686

mithrandir77

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 69
Re: Problem with today cvs
« Reply #6 on: January 19, 2006, 01:50:59 PM »

Quote
Originally posted by Arichy
2.1.0 is not usable - it crashes all the time. Bugsquashing is imho more required than implementing new features like large file support. Also it should have been better to name 2.1.0 2.1.0RC1. I use 2.0.3 again now - sorry, but that runs fine stable all the time!

I don't have problem with 2.1.0 and then with cvs-version (which, i suppose, follows 2.1.0 release)

It crashes sometimes with amulegui but it happens also with 2.0.3, and i suppose becausa i have a lot of file shared.

Try to download cvs version (earlie than today version, 01-17-2006 for example)
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: Problem with today cvs
« Reply #7 on: January 19, 2006, 01:55:23 PM »

Quote
Originally posted by Arichy
2.1.0 is not usable - it crashes all the time.
Sorry, this information is worthless. It didn't crash a single time for me.

If it crashes for you, post backtraces.
Quote
Originally posted by Arichy
Bugsquashing is imho more required than implementing new features like large file support.
This is very, very correct and that's why the devs have two branches: One for improving 2.1.0 and one for implementing totally new things.

You are using the one where totally new things are implemented. Don't use it if you don't like it - it's normal that it doesn't work at all sometimes.
Quote
Originally posted by Arichy
Also it should have been better to name 2.1.0 2.1.0RC1.
Again: Nobody benefits from such an information, it could be a local problem on your system just as well and without more details it's impossible to tell.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Problem with today cvs
« Reply #8 on: January 19, 2006, 02:48:39 PM »

Quote
Originally posted by Arichy
2.1.0 is not usable - it crashes all the time. Bugsquashing is imho more required than implementing new features like large file support. Also it should have been better to name 2.1.0 2.1.0RC1. I use 2.0.3 again now - sorry, but that runs fine stable all the time!

Blahblahblah. We do what we feel like and I feel like implementing new features. Other people feels like bugfixing. And 2.1.0 should be stable,a nd it's stable for most people, your info is incomplete and worthless and so, I'll happily ignore it.

And yes, 2.1.1 will NOT be based on current CVS, but fixes backported to 2.1.0 branch, which we have almost ready to release.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Problem with today cvs
« Reply #9 on: January 19, 2006, 02:49:11 PM »

Quote
Originally posted by mithrandir77
Ok, thanks a lot.

It's the first time i meet this message.

I have just read that post about some problems, but it is not present any information about this option, so i don't understand.

 :P

amuled --help :P
Logged