Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Vollstrecker]

Thanks Uwe, this patch is really nice. I'll implement it when I come home today, so this morning there will be the old version again.

[Vollstrecker]

RR4t: Does it work now?

[RRT4]

yes, it is working now

tnx

[1Carlos]

Originally posted by RRT4
yes, it is working now

tnx

No, it doesn't work. Now i can't install the deb on my unstable.
In Sid there isn't libcrypto++5.2c2 (there is only for AMD64), so i have to change the packet by hand.
Anyway, good job.

Please sorry my bad English.

[Kry]

I warn people again that you might fail secure ident with other clients when not using our internal libcrypto.

[Uwe]

could you please tell us what bugs you mean so we can proof whether these bugs are fixed in official cryptolib or even in debian?

@1Carlos: in unstable there is now libcrypto++5.2c2a because of another abi transition... you could rebuild the package for unstable because the packages from vollstrecker.net are for etch (where libcrypto++5.2c2a has not entered yet - and will not for at least a couple of days...)

[Vollstrecker]

I think I've read something about the libcrypto Bug in debians BTS, but I don't know if they just know it, or fixed it.
@Kry have you thought about giving the libcrypto fix in amule to the devs of libcrypto?

[Carcass]

Hi guys at this our in Italy 4.36 AM  :O I have finded the reason  because amule don't installe d on my debian sid............libcrypto.

Now I have downloaded the patch but I don't know how use it............

To the core how I can installed my amule cvs on debian sid.............?

Thanks for the patient.  :O

Good Nigth

[Jacobo221]

> Kry: I warn people again that you might fail secure ident with other clients when not using our internal libcrypto.

well, that's horrible news, since official Debian amule package switched to libcrypto months ago:
http://packages.debian.org/unstable/x11/amule
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323010

are you saying all those ppl may be failing at SUI?

[Xaignar]

The problem is that the optimization flags very easily cause errors when doing various operations with CryptoPP. The included unit-tests catch this in my experience, but I cant say if Debian/Ubuntu are running them (Gentoo luckily started doing it with 5.2.x) ...

[Uwe]

so again the question, are the crypto++ developers aware of this bug, is it fixed already or is there a bug-report or something where we can track the current status?

[Carcass]

I resolve put in the libs download from web  

[Uwe]

for all the sid users I rebuilt the package for current sid... haven't testet it but it should work

Code: [Select]

deb http://uwe.ktv-zone.de/debian/amule-sid/ ./
I will not update these packages as regularly as vollstrecker but at least one or two times a week or when there was an important change in amule or vollstrecker's package...

[Uwe]

I did some more work on the packages

* split i18n-files into seperate packages for each language
* fixed debian/rules to use files in debian/tmp for mv's instead of source-files where possible

When applying the patch you should set the conflics-fields in the i18n-packages to the current version (making << ${Source-Version} shouldn't be necessary), else there might be some upgrade-problems because of file conflicts between amule-i18n-* and old amule packages.

The next points on plan are:
* fully migrate to dh_install
* split of arch-depending and arch-independing packages (amule-i18n-* should better be arch-indep)
* spend some time with the cryptopp-bug and whether it is fixed in debian

[Vollstrecker]

Maybe you should think about email the patches, so its easier it discuss them (maybe in german if I interpret your name correctly).

First: Why do amule and amuled depend on the en_gb pkg, but remote-gui depends on en_us?

Second: On Webservertemplatepkg's you removed the rm.....*Makefile* line, which causes that the Makefiles would jump into them.

Third: I have choosen the << ${Source-Version}  Variant, because so it's not possible to use todays build with some yesterdays files. It could happen that some strings in the po's change. It could work woth the old files, but the translation wouldn't be found and displayed.