Colin, that seems like a horrible solution - you now have everybody's
apt claiming they need to get a package that 404s, causing apt-get
upgrade to fail. I understand a buggy package was released, but once
that has been done, you can't just remove the package itself (while
leaving reference to it
Copying a response from the Debian mailing list linked above that
includes an email from James Roskind, the original author. The basic
problem is that the profiler module restricts copying altering the
code to work done in python or for a python module - as such, it is too
restrictive to fit
Wow. Ok, if you read my previous posts from a few weeks ago and today, I
am having the *same* issue as described in the bug. I didn't think it
was necessary to re-state what the bug itself states. And really, how
many people who have a Launchpad account don't do basic things like
check if this is
Ok, so I'm a complete jackass. Had a copy of pidgin installed from
source (I guess from before the Ubuntu repos had the latest version?),
and another copy installed from backports atop that. Finally realized
something was up when I apt-get remove'd everything slightly related to
pidgin and yet I
can anybody confirm the fix has been implemented in Hardy backports? I
filed a separate bug report, and then you marked it as a duplicate of
this one. So which statement of yours should I follow - file a separate
bug report, or just keep quite and pretend there isn't a problem?
Sorry, but I get
strangely, I'm running Hardy and have upgraded (via apt-get I'm
assuming, don't ever recall installing any other version of pidgin) to a
higher version than is currently available on the
http://packages.ubuntu.com/hardy/net/pidgin page. I downloaded the
version from the page (thinking for whatever
ahhh nevermind, i've got the latest version from hardy backports, and it
seems that this fix has not propagated to there? is there any way other
than downgrading pidgin that I can get an updated version of libpurple
that will allow me to connect to icq?
--
Cannot connect to ICQ (The client
thanks for the tip. kept running into this issue trying to ugprade from
dapper hardy - it bombed out the update-manager and kept causing dpkg
--configure -a to eventually fail due to too many errors. simple adding
of a line to /etc/python/debian_config fixed it! now, why it doesn't
automatically
*** This bug is a duplicate of bug 163116 ***
https://bugs.launchpad.net/bugs/163116
Jamie Strandboge wrote 1 hours ago:
Turns out there were more problems with the patch and all releases have
been disabled. Updated packages for Dapper, Edgy, Feisty and Gutsy will
be provided soon.
