Package: logjam
Version: 4.5.1-2
Severity: important

I'm using logjam with a custom installation of the LiveJournal software.
However, since logjam 4.5.1-2 publishing a blog entry fails.

When I klick "Save" to publish a blog entry in logjam 4.5.1-2, I get
the following error message:

=== Error =============================
Client error: Unknown metadata: taglist
[ Cancel ]

Clicking on "cancel" is the only choice and aborts posting the blog
entry.

This is a regression from 4.4.1-2. Downgrading to 4.4.1-2 I can
continue to update my blog.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (900, 'stable'), (700, 'unstable'), (100, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.3-swsusp2-2.1.9.9
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages logjam depends on:
ii  libaspell15               0.60.3-5       GNU Aspell spell-checker runtime l
ii  libatk1.0-0               1.10.1-2       The ATK accessibility toolkit
ii  libc6                     2.3.5-6        GNU C Library: Shared libraries an
ii  libglib2.0-0              2.8.0-1        The GLib library of C routines
ii  libgnutls11               1.0.16-13.1    GNU TLS library - runtime library
ii  libgtk2.0-0               2.6.8-1        The GTK+ graphical user interface 
ii  libgtkspell0              2.0.10-3       a spell-checking addon for GTK's T
ii  libpango1.0-0             1.10.0-2       Layout and rendering of internatio
ii  libsoup2.2-7              2.2.3-2        an HTTP library implementation in 
ii  libx11-6                  6.8.2.dfsg.1-6 X Window System protocol client li
ii  libxml2                   2.6.21-1       GNOME XML library
ii  xlibs                     6.8.2.dfsg.1-6 X Window System client libraries m
ii  zlib1g                    1:1.2.2-4      compression library - runtime

logjam recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to