Your message dated Wed, 01 Jul 2015 01:19:18 +0200
with message-id <[email protected]>
and subject line closing bugs reported against bzr-gtk/olive-bzr
has caused the Debian Bug report #538922,
regarding /usr/bin/olive-gtk: olive-gtk doesn't say what it is.
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 [email protected]
immediately.)
--
538922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538922
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bzr-gtk
Version: 0.95.0+bzr649-1
Severity: normal
File: /usr/bin/olive-gtk
When you run olive for the first time, it shows you a
picture of an olive. If you don't happen to start
it in a bzr directory, it doesn't give you many clues
as to what the heck it does.
The only clue is the titlebar which says "Olive - Bazaar GUI".
Obviously, if you know that Bazaar is a version control system,
you could guess at what it does. But, though it may be
surprising, quite a number of adults I surveyed
associate the word "bazaar" with a middle-Eastern shopping
experience rather than with programming tools.
The "Help" menu isn't helpful, because it only gives credits.
"Help" should give the user a 1-sentence summary of what the
program does. Explaining thing is, after all, what it's
there for. I'd suggest this:
"Olive is a graphical front end that lets you conveniently
control the Bazaar (bzr) distributed version control system.
This program lets you track changes to a group of files
and collaboratively work on programs or documents."
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages bzr-gtk depends on:
ii bzr 1.16.1-1 easy to use distributed version co
ii python 2.5.4-2 An interactive high-level object-o
ii python-central 0.6.11 register and build utility for Pyt
ii python-glade2 2.14.1-3 GTK+ bindings: Glade support
ii python-gtk2 2.14.1-3 Python bindings for the GTK+ widge
ii python-notify 0.1.1-2+b1 Python bindings for libnotify
Versions of packages bzr-gtk recommends:
ii bzr-dbus 0.1~bzr39-1 D-Bus announcements plugin for Baz
ii python-cairo 1.8.4-3 Python bindings for the Cairo vect
ii python-gnome2-desktop 2.24.1-1 Python bindings for the GNOME desk
ii python-gnomekeyring 2.24.1-1+b2 Python bindings for the GNOME keyr
ii python-gtksourceview2 2.6.0-1 Python bindings for the GtkSourceV
ii python-nautilus 0.5.1-2 Python binding for Nautilus compon
ii seahorse 2.26.1-2 GNOME front end for GnuPG
Versions of packages bzr-gtk suggests:
pn bzr-avahi <none> (no description available)
pn bzr-loom <none> (no description available)
pn bzr-search <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
olive-bzr was upstream split from bzr-gtk, so it was no longer part of
the bzr-gtk Debian package.
olive-bzr which was intended for inclusion never made it into Debian.
bzr-gtk was removed from Debian, see http://bugs.debian.org/719658 for
details. Closing the remaining bug reports now.
Andreas
--- End Message ---
