Your message dated Sun, 12 Jun 2011 17:59:47 -0400
with message-id <4df536d3.3040...@debian.org>
and subject line Re: Bug#630254: pidgin: Version in stable cannot login anymore
has caused the Debian Bug report #630254,
regarding pidgin: Version in stable cannot login anymore
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
630254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pidgin
Version: 2.7.3-1+squeeze1
Justification: renders package unusable
Severity: grave

Hi,

the version in stable cannot login anymore, whereas the version in
testing can. Is there any way to upload a
changed version to stable? Or os the pidgin version stable simply broken?
Installing pidgin from testing upgrades a huge pile of packages, so I'd
really like to avoid that. Using licq atm,
but it's just not pidgin ;)

Thanks & kind regards,
Benjamin

-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39.1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pidgin depends on:
ii  gconf2             2.28.1-6              GNOME configuration
database syste
ii  libatk1.0-0        1.30.0-1              The ATK accessibility toolkit
ii  libc6              2.11.2-10             Embedded GNU C Library:
Shared lib
ii  libcairo2          1.8.10-6              The Cairo 2D vector
graphics libra
ii  libdbus-1-3        1.2.24-4              simple interprocess
messaging syst
ii  libdbus-glib-1-2   0.88-2.1              simple interprocess
messaging syst
ii  libfontconfig1     2.8.0-2.1             generic font configuration
library
ii  libfreetype6       2.4.2-2.1             FreeType 2 font engine,
shared lib
ii  libglib2.0-0       2.24.2-1              The GLib library of C routines
ii  libgstreamer0.10-0 0.10.30-1             Core GStreamer libraries
and eleme
ii  libgtk2.0-0        2.20.1-2              The GTK+ graphical user
interface
ii  libgtkspell0       2.0.16-1              a spell-checking addon for
GTK's T
ii  libice6            2:1.0.6-2             X11 Inter-Client Exchange
library
ii  libpango1.0-0      1.28.3-1+squeeze2     Layout and rendering of
internatio
ii  libpurple0         2.7.3-1+squeeze1      multi-protocol instant
messaging l
ii  libsm6             2:1.1.1-1             X11 Session Management library
ii  libstartup-notific 0.10-1                library for program launch
feedbac
ii  libx11-6           2:1.3.3-4             X11 client-side library
ii  libxml2            2.7.8.dfsg-2+squeeze1 GNOME XML library
ii  libxss1            1:1.2.0-2             X11 Screen Saver extension
library
ii  perl               5.10.1-17             Larry Wall's Practical
Extraction
ii  perl-base [perlapi 5.10.1-17             minimal Perl system
ii  pidgin-data        2.7.3-1+squeeze1      multi-protocol instant
messaging c

Versions of packages pidgin recommends:
ii  gstreamer0.10-plugins-base    0.10.30-1  GStreamer plugins from the
"base"
ii  gstreamer0.10-plugins-good    0.10.24-1  GStreamer plugins from the
"good"

Versions of packages pidgin suggests:
pn  evolution-data-server         <none>     (no description available)
pn  gnome-panel | kdebase-workspa <none>     (no description available)
ii  libsqlite3-0                  3.7.3-1    SQLite 3 shared library

-- no debconf information




--- End Message ---
--- Begin Message ---
Version: 2.7.5-1

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602541

The workaround seems to be to disable SSL, but then it will use an insecure connection so it might transmit your password/conversation in the clear. You can also try logging in as an AIM account with your ICQ number.


--- End Message ---

Reply via email to