Package: gpodder
Version: 0.13.1-1
Severity: wishlist
Is there a reason for the hash-like naming of folders and files? There's no
point for it and is very inconvenient for
handling files. Could someone please explain why gpodder handles files this
way, and if there could be a change made to
have logical naming of folders and files.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gpodder depends on:
ii python2.5.2-3An interactive high-level object-o
ii python-feedparser 4.1-12 Universal Feed Parser for Python
di python-glade2 2.12.1-6 GTK+ bindings: Glade support
di python-gtk2 2.12.1-6 Python bindings for the GTK+ widge
ii python-support0.8.7 automated rebuilding support for P
Versions of packages gpodder recommends:
pn python-gpod none (no description available)
pn python-pymtp none (no description available)
Versions of packages gpodder suggests:
pn gnome-bluetooth none (no description available)
di mplayer 1:1.0.rc2svn20080706-0.1 The Ultimate Movie Player For Linu
pn python-bluez | none (no description available)
pn python-eyed3none (no description available)
pn python-pymadnone (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]