The only rdependency is aMule. I'll take care of it.
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
ACK. Hope I'm not too late for the freeze :)
** Changed in: libcrypto++ (Ubuntu)
Status: In Progress => Confirmed
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Bugs, which
I will take care of this. I'm likely to upload aMule 2.2.0 svn and it's
affected by http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448766
which is fixed in this new package, so I'll do both at the same time.
** Changed in: libcrypto++ (Ubuntu)
Importance: Undecided => Wishlist
Assignee:
Is "taking care of fixing amule" something that I can do? I mean,
someone like me who doesn't have write privileges to ubuntu
repositories?
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of
So, just to be clear: who will take care of fixing amule and other
reverse dependencies once this is synced?
** Changed in: libcrypto++ (Ubuntu)
Status: In Progress => Incomplete
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received thi
Okay, I built amule with --disable-embedded-crypto, against libcryptopp
v5.5.2, and it did not crash on startup for me.
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Here's another one:
https://bugs.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/68792
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
But I should emphasize that there are other known crashes with amule on,
e.g. Gutsy, which have the same last few stack frames:
https://bugs.launchpad.net/ubuntu/+source/amule/+bug/172323
So I really think that amule tends to crash like this sometimes,
regardless of which version of Crypto++ it i
On Feb 7, 2008, at 8:38 AM, Emilio Pozuelo Monfort wrote:
> That's wrong. It's not using the system crypto library in your
> build, but not in
> the Ubuntu package, which is passing --disable-embedded-crypto to ./
> configure.
Okay, thanks.
By the way, how about if we stop passing --disable-e
Zooko O'Whielacronx wrote:
> Okay, I did "apt-get source amule", and then I cd'ed into the
> amule-2.1.3 directory and ran "./configure", and it printed out, among
> other things:
>
> checking whether to use embedded Crypto... yes
>
> This means that amule is not even using the system-wide instal
Okay, I did "apt-get source amule", and then I cd'ed into the
amule-2.1.3 directory and ran "./configure", and it printed out, among
other things:
checking whether to use embedded Crypto... yes
This means that amule is not even using the system-wide installation of
Crypto++, so upgrading that ver
On Feb 7, 2008, at 7:31 AM, Daniel Holbach wrote:
> My misunderstanding the amule crash happens without the upgrade, amule
> will build fine against the new version, so let's sync it.
Daniel:
I'm sorry, I miscommunicated. I *guess* that the amule crash happens
without the upgrade based on the
My misunderstanding the amule crash happens without the upgrade, amule
will build fine against the new version, so let's sync it.
ACKed.
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ub
Unsubscribing Ubuntu Sponsors for universe from this bug for now.
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
So I rather doubt that upgrading the version of libcryptopp is actually
what causes nxvl's crash. nxlv: could you try the same thing linking
against the current libcryptopp in Hardy pre-release?
Could you try it several times in a row and see if it keeps happening?
Thank you,
Regards,
Zooko
-
** Changed in: libcrypto++ (Ubuntu)
Assignee: Nicolas Valcárcel (nxvl) (nvalcarcel) => (unassigned)
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
Hm. See also:
https://bugs.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/68792
https://bugs.launchpad.net/ubuntu/+source/amule/+bug/186636
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member o
On Feb 5, 2008, at 1:28 PM, Nicolas Valcárcel (nxvl) wrote:
> Ok, it builds fine, but it crashes on use, here is the output of the
> error.
Thanks for working on this.
Did you figure out that aMule was not linking to libcryptopp at all,
and it is aMule using its own internal copy of CryptoPP t
Ok, it builds fine, but it crashes on use, here is the output of the
error.
[EMAIL PROTECTED]:~/src/amule$ amule
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/nxvl/.aMule/Temp.
All PartFiles Loaded.
ListenSocke
** Changed in: libcrypto++ (Ubuntu)
Assignee: (unassigned) => Nicolas Valcárcel (nxvl) (nvalcarcel)
Status: New => In Progress
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of U
It doesn't seem that amule has problems with the changes since i don't
find a link to the library hardcoded. I'm testing the build, instalation
and use of amule with this library to see if it works and/or fix it
[EMAIL PROTECTED]:~/src/amule/amule-2.1.3$ grep -R "libcrypto++" *
configure:
I'm sorry, but I don't understand a lot of things about the Ubuntu
package building infrastructure. My first question is: doesn't the
amule package get automatically rebuilt, such as by a BuildBot, when its
dependencies change? That would seem to be sufficient to solve this
problem.
Here are a c
No doesn't look like amule can continue to use the old package:
[EMAIL PROTECTED]:~$ debdiff libcrypto++6_5.5-5_amd64.deb
libcrypto++7_5.5.2-1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in
Are you asking me? I don't know who will take care of that. There are
no source code changes required to upgrade from Crypto++ 5.5 to Crypto++
5.5.2, so I guess this is just a matter of rebuilding amule. Aren't
builds automated?
Also doesn't increasing the SONAME mean that amule can continue usi
This is part of the debian changelog: "Increased SONAME from 6 to 7
because of API changes."
At least amule is going to need to go through a transition. Who will
take care of that?
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug
** Changed in: libcrypto++ (Ubuntu)
Sourcepackagename: None => libcrypto++
** Tags added: sync
--
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
26 matches
Mail list logo
