thinkle / gourmet

Gourmet Recipe Manager
GNU General Public License v2.0
338 stars 138 forks source link

import of MealMaster files with non-ASCII characters hangs #666

Closed ockham closed 11 years ago

ockham commented 11 years ago

Converted from SourceForge issue 2899344, submitted by SourceForge user nobody on 2009-11-17 20:21:06 UTC.

Package: gourmet Version: 0.15.1-1 Severity: important

* Please type your report below this line *

Import of MealMaster files with non-ASCII characters hangs with an error (see attached trace).

-- System Information: Debian Release: lenny/sid (lenny with some packages from squeeze/sid) APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=eo.UTF-8, LC_CTYPE=eo.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash

Versions of packages gourmet depends on: ii python 2.5.2-3 An interactive high-level object-o ii python-central 0.6.11 register and build utility for Pyt ii python-glade2 2.12.1-6 GTK+ bindings: Glade support ii python-gtk2 2.12.1-6 Python bindings for the GTK+ widge ii python-imaging 1.1.6-3 Python Imaging Library ii python-pysqlite2 2.5.5-1 Python interface to SQLite 3 ii python-reportlab 2.1dfsg-2 ReportLab library to create PDF do ii python-sqlalchemy 0.5.6-1 SQL toolkit and Object Relational

Versions of packages gourmet recommends: ii python-gnome2 2.22.0-1 Python bindings for the GNOME desk

Versions of packages gourmet suggests: pn python-metakit (no description available) pn python-pyrtf (no description available)

-- no debconf information

ockham commented 11 years ago

Submitted by SourceForge user sf-robot on 2010-03-21 02:20:19 UTC.

This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker).

ockham commented 11 years ago

Submitted by SourceForge user thomas_hinkle on 2010-03-06 03:36:59 UTC.

We are unable to reproduce this problem and are therefore closing this bug. Thank you for reporting the issue. Feel free to reopen this report or submit a new one with more information if you are still experiencing problems.