Bug#483673: avant-window-navigator requires compiz but doesn't depend on it

2008-06-04 Thread Gerfried Fuchs
* Julien Lavergne <[EMAIL PROTECTED]> [2008-06-03 22:43:44 CEST]:
> Hi,
> 
> >  The package only losely suggests compiz, and even there not as its
> > primary preference:
> > 
> > Suggests: metacity (>= 2.21.5) | xcompmgr | compiz | xfwm4 (>= 4.2)
> > 
> >  Though, trying to start avant-window-navigator gives this message:
> > 
> > #v+
> > Error: Screen isn't composited. Please run compiz (-fusion) or another 
> > compositing manager.
> > #v-
> 
> As Andrew said, to work, avant-window-navigator need a composite
> manager which run with it. So if you install compiz for example,
> avant-window-manager will not work automatically, but only if you run
> compiz. 

 Then please add documentation on how to accomplish that and reference
it in the message that you display when it's run without a composite
enabled manager.

> When I packaged another application which needed composite manager, my
> sponsor told me to set it as a suggest to not create a hard depends on
> compiz (some people want a composite manager but not compiz).

 But the package /does/ have a hard dependency on a compositing manager.
Please note the difference between any compositing manager and compiz
itself - there is no need for the latter, but there is in fact a need
for the former. The way it's done in the suggests doesn't create any
hard depends on compiz but on a compositing manager.

> The order of the suggested packages was made like this :
> - metacity because there is a composite manager, yes not enable by
> default but working quite well. It's also the package which installed
> less depends on the system.

 Please add documentation on how to enable it so people are aware on how
to get it working with it.

> - xcompmgr also because there is not many depends.
> - compiz because you need to set it properly (drivers, launch on
> start...) and you don't need all the effects.

 If you need any special configuration to make it work, pretty please
add documentation on that, too.

> - xfwm4 because it's a composite manager, but you need to install xfce
> depends.

 Are these depends completely fulfilled by installing xfwm4? If not then
the alternative chain doesn't seem to be complete. At least, please also
document it.

> I can also add kwin4 in this list.

 If it would work, it would be a good idea. The list should be as
complete as possible - but my original report still holds:
avant-window-navigator doesn't work without any composite manager but
doesn't depend on any, only suggest them.

> I'm agree that it should be better if I mention that in a
> README.debian. But I'm not convinced that put it as Depends will have
> a better impact, because there is still a manual action for the user.

 But the program /does/ depend on a composite manager. It doesn't work
without any, is useless without any. Yes, that it requires additional
configuration to enable it finally propably should also get addressed -
maybe through some debconf note hinting the users in the correct
direction, or explicitly stating so in the package description. But it
doesn't mean that users should go and install something else once they
found out what's going on and why it's not working, that something else
should already be on the system. That's what Dependencies are there for.

 So long,
Rhonda



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



Bug#483673: avant-window-navigator requires compiz but doesn't depend on it

2008-06-03 Thread Julien Lavergne
Hi,

>  The package only losely suggests compiz, and even there not as its
> primary preference:
> 
> Suggests: metacity (>= 2.21.5) | xcompmgr | compiz | xfwm4 (>= 4.2)
> 
>  Though, trying to start avant-window-navigator gives this message:
> 
> #v+
> Error: Screen isn't composited. Please run compiz (-fusion) or another 
> compositing manager.
> #v-

As Andrew said, to work, avant-window-navigator need a composite manager which 
run with it. So if you install compiz for example, avant-window-manager will 
not work automatically, but only if you run compiz. 
When I packaged another application which needed composite manager, my sponsor 
told me to set it as a suggest to not create a hard depends on compiz (some 
people want a composite manager but not compiz).

The order of the suggested packages was made like this :
- metacity because there is a composite manager, yes not enable by default but 
working quite well. It's also the package which installed less depends on the 
system.
- xcompmgr also because there is not many depends.
- compiz because you need to set it properly (drivers, launch on start...) and 
you don't need all the effects.
- xfwm4 because it's a composite manager, but you need to install xfce depends.
I can also add kwin4 in this list.

I'm agree that it should be better if I mention that in a README.debian. But 
I'm not convinced that put it as Depends will have a better impact, because 
there is still a manual action for the user.

 
Regards,
Julien Lavergne <[EMAIL PROTECTED]>



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



Bug#483673: avant-window-navigator requires compiz but doesn't depend on it

2008-06-02 Thread Gerfried Fuchs
Hi!

 First of all, your reply just made it into the BTS. I'm lucky to bts
cache my bugreports and noticed a change to this bugreport due to that -
otherwise your message wouldn't have reached me. Please notice that
mails to @bugs.debian.org only reaches the BTS and not the
submitters of the bugreports.

* Andrew Starr-Bochicchio <[EMAIL PROTECTED]> [2008-06-01 22:33:15 CEST]:
> AWN require the screen to be composited in order to be shown. Compiz is
> just one of a few options available. The compositor in metacity is still
> experimental and must be turned on through editing a gconf key.
> 
> apps > metacity > compositing_manager

 What kind of key should that become, because it doesn't exist for me?
Can this kindly be documented in some README or similar?

 Furthermore if it's still experimental in metacity, is it a good thing
to list metacity as first alternative in the dependency chain?

 ... it still leaves the question unanswered about if the list in
Suggests has rather to belong in Depends because it doesn't seem to work
at all without a compositing manager?

 Thanks,
Rhonda



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



Bug#483673: avant-window-navigator requires compiz but doesn't depend on it

2008-06-01 Thread Andrew Starr-Bochicchio
AWN require the screen to be composited in order to be shown. Compiz is
just one of a few options available. The compositor in metacity is still
experimental and must be turned on through editing a gconf key.

apps > metacity > compositing_manager



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



Bug#483673: avant-window-navigator requires compiz but doesn't depend on it

2008-05-30 Thread Gerfried Fuchs
Package: avant-window-navigator
Version: 0.2.6-4
Severity: serious
Justification: Policy 7.2

Hi!

 The package only losely suggests compiz, and even there not as its
primary preference:

Suggests: metacity (>= 2.21.5) | xcompmgr | compiz | xfwm4 (>= 4.2)

 Though, trying to start avant-window-navigator gives this message:

#v+
Error: Screen isn't composited. Please run compiz (-fusion) or another 
compositing manager.
#v-

 It seems to be running somehow, but does nothing at all. Opening
awn-manager does show that it should display something. I haven't found
anything in the documentation about what could be meant with "another
compositing manager", but given that metacity is in the Suggests next to
compiz (which is explicitly mentioned) leaves me in the impression that
it should be enough.

 Would be kind to know what I'm doing wrong, if compiz is really
required, and last but least: Why it's only a Suggests and not a Depends
if it is required.

 So long,
Rhonda

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.25-trunk-powerpc
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages avant-window-navigator depends on:
ii  avant-window-navigator-data   0.2.6-4Common files for avant-window-navi
ii  gconf22.22.0-1   GNOME configuration database syste
ii  libawn0   0.2.6-4library for avant-window-navigator
ii  libc6 2.7-10 GNU C Library: Shared libraries
ii  libcairo2 1.6.4-1+b1 The Cairo 2D vector graphics libra
ii  libdbus-glib-1-2  0.74-4 simple interprocess messaging syst
ii  libglib2.0-0  2.16.3-2   The GLib library of C routines
ii  libgtk2.0-0   2.12.9-3   The GTK+ graphical user interface 
ii  libwnck22 2.22.1-1   Window Navigator Construction Kit 
ii  libx11-6  2:1.0.3-7  X11 client-side library

Versions of packages avant-window-navigator recommends:
pn  awn-applets-c-core (no description available)
pn  awn-applets-python-core(no description available)
ii  awn-manager   0.2.6-4A preferences manager for avant-wi
ii  dbus-x11  1.2.1-2simple interprocess messaging syst

-- no debconf information



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