Debian Bug report logs - #722451
ITP: Compiz -- Compositing "3D" window manager

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Klaus Knopper <bugs@knopper.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: RFP: compiz -- Compositing "3D" window manager

Date: Wed, 11 Sep 2013 09:53:45 +0200

Package: wnpp
Severity: wishlist


* Package name    : compiz
  Version         : 0.9.11
  Upstream Author : Sam Spilsbury <sam.spilsbury@canonical.com> and others
* URL             : https://launchpad.net/compiz
* License         : GPL-2+, LGPL-2.1+, MIT/X11
  Programming Lang: C, C++, Python
  Description     : Compositing "3D" window manager

 From https://launchpad.net/~compiz-team :
 .
 Compiz is an OpenGL compositing manager that use
 GLX_EXT_texture_from_pixmap for binding redirected top-level windows
 to texture objects. It has a flexible plug-in system and it is
 designed to run well on most graphics hardware.
 .
 Okay, this description isn’t really meaningful. In a nutshell, Compiz
 is a compositing manager, which means that it enhances the overall user
 interaction by adding fancy effects to your windows, from drop shadows
 to awesome desktop effects like the Desktop Cube or the Expo view.
 Compiz can also be a window manager, which means that it is the
 software between you and your desktop apps. It enables you to move or
 resize windows, to switch workspaces, to switch windows easily (using
 alt-tab or so), and so on.
 .
 Upstream Compiz Maintainers

Message #14 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: 722451@bugs.debian.org, bugs@knopper.net

Subject: Adoption

Date: Mon, 11 Aug 2014 23:50:38 +0200

Hi,

Do you plan still to package Compiz? Do you have a problem which 
prevents this? Do you need help? Otherwise, can I adopt it so that 
someone and I can package it before freeze? Our work to prepare has now 
good improvement.

Thanks,

Regards,

-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients 
visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #19 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: 722451@bugs.debian.org

Subject: Adoption

Date: Mon, 11 Aug 2014 21:08:42 +0200

Hi,

Do you plan still to package Compiz? Do you have a problem which prevents this? Do you need help? Otherwise, can I adopt it so that someone and I can package it before freeze? Our work to prepare has now good improvement.

Thanks,

Regards,

-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #24 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Carlos Alberto Lopez Perez <clopez@igalia.com>

To: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>, 722451@bugs.debian.org, bugs@knopper.net

Subject: Re: Bug#722451: Adoption

Date: Tue, 26 Aug 2014 23:56:48 +0200

[Message part 1 (text/plain, inline)]

On 11/08/14 23:50, MENGUAL Jean-Philippe wrote:
> 
> Hi,
> 
> Do you plan still to package Compiz? Do you have a problem which
> prevents this? Do you need help? Otherwise, can I adopt it so that
> someone and I can package it before freeze? Our work to prepare has now
> good improvement.
> 
> Thanks,
> 
> Regards,
> 

Hi,

This bug is marked as RFP = Request For Package. This means that the
reporter is asking for someone to package this software, but no one has
still offered to package and maintain it.

If you want to package/maintain it yourself, please retitle the bug to
ITP = Intend To Package, assign the bug to yourself, and start working
on it.

Find here help about packaging for Debian:
https://wiki.debian.org/DebianMentorsFaq#Packaging

And here help about using the BTS (Bug Tracking System):

https://wiki.debian.org/HowtoUseBTS
https://www.debian.org/Bugs/server-control


Thanks!

[signature.asc (application/pgp-signature, attachment)]

Message #31 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

To: Carlos Alberto Lopez Perez <clopez@igalia.com>

Cc: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>, 722451@bugs.debian.org, bugs@knopper.net

Subject: Re: Bug#722451: Adoption

Date: Wed, 27 Aug 2014 06:31:49 +0200

Hello,

On Tue, Aug 26, 2014 at 11:56:48PM +0200, Carlos Alberto Lopez Perez wrote:
> On 11/08/14 23:50, MENGUAL Jean-Philippe wrote:
> > 
> > Hi,
> > 
> > Do you plan still to package Compiz? Do you have a problem which
> > prevents this? Do you need help? Otherwise, can I adopt it so that
> > someone and I can package it before freeze? Our work to prepare has now
> > good improvement.
> > 
> > Thanks,
> > 
> > Regards,
> > 
> 
> Hi,
> 
> This bug is marked as RFP = Request For Package. This means that the
> reporter is asking for someone to package this software, but no one has
> still offered to package and maintain it.
> 
> If you want to package/maintain it yourself, please retitle the bug to
> ITP = Intend To Package, assign the bug to yourself, and start working
> on it.
> 
> Find here help about packaging for Debian:
> https://wiki.debian.org/DebianMentorsFaq#Packaging
> 
> And here help about using the BTS (Bug Tracking System):
> 
> https://wiki.debian.org/HowtoUseBTS
> https://www.debian.org/Bugs/server-control
> 
> Thanks!

Actually, I do package the compiz git from launchpad regularly for using
it in Debian/Knoppix as the main window manager. Please find the source
& binary packaging here:

http://debian-knoppix.alioth.debian.org/packages/compiz/

However, I'm not am official Debian Package Maintainer and thus the
packages won't show up anywhere else than in Knoppix currently.

Regards
-Klaus

Message #36 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Carlos Alberto Lopez Perez <clopez@igalia.com>

To: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

Cc: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>, 722451@bugs.debian.org

Subject: Re: Bug#722451: Adoption

Date: Wed, 27 Aug 2014 11:54:57 +0200

[Message part 1 (text/plain, inline)]

On 27/08/14 06:31, Prof. Dipl.-Ing. Klaus Knopper wrote:
> Hello,
> 
> On Tue, Aug 26, 2014 at 11:56:48PM +0200, Carlos Alberto Lopez Perez wrote:
>> On 11/08/14 23:50, MENGUAL Jean-Philippe wrote:
>>>
>>> Hi,
>>>
>>> Do you plan still to package Compiz? Do you have a problem which
>>> prevents this? Do you need help? Otherwise, can I adopt it so that
>>> someone and I can package it before freeze? Our work to prepare has now
>>> good improvement.
>>>
>>> Thanks,
>>>
>>> Regards,
>>>
>>
>> Hi,
>>
>> This bug is marked as RFP = Request For Package. This means that the
>> reporter is asking for someone to package this software, but no one has
>> still offered to package and maintain it.
>>
>> If you want to package/maintain it yourself, please retitle the bug to
>> ITP = Intend To Package, assign the bug to yourself, and start working
>> on it.
>>
>> Find here help about packaging for Debian:
>> https://wiki.debian.org/DebianMentorsFaq#Packaging
>>
>> And here help about using the BTS (Bug Tracking System):
>>
>> https://wiki.debian.org/HowtoUseBTS
>> https://www.debian.org/Bugs/server-control
>>
>> Thanks!
> 
> Actually, I do package the compiz git from launchpad regularly for using
> it in Debian/Knoppix as the main window manager. Please find the source
> & binary packaging here:
> 
> http://debian-knoppix.alioth.debian.org/packages/compiz/
> 
> However, I'm not am official Debian Package Maintainer and thus the
> packages won't show up anywhere else than in Knoppix currently.
> 

You don't need to be a Debian Maintainer (DM) to maintain packages in
Debian. Anyone can maintain packages in Debian.

The only difference is that DM are allowed to upload directly to the
archive, while not-DM people need that some DD (Debian Developer) review
and sponsor the package.

Once you are maintaining one or more packages in Debian you can apply to
become a DM if you want, so you can upload further updates of your
packages directly to the archive.

We have a clear process defined for this. Once you have your package
ready, you can upload it to mentors.debian.net (or to other site if you
prefer) and you ask on the mailing list debian-mentors@lists.debian.org
(subscribe yourself to the list) for someone to review and upload your
package.

Probably you will have to trim the Changelog for the initial upload to
Debian, and include a line on it closing this bug #722451. But first you
should retitle this bug to ITP and assign it to yourself, to show your
intention of packaging Compiz for Debian. So anyone else that could be
interested in doing the work is aware that you are already working on
this. So we avoid duplicating work.

[signature.asc (application/pgp-signature, attachment)]

Message #41 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Carlos Alberto Lopez Perez <clopez@igalia.com>, 722451@bugs.debian.org

Cc: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>, MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

Subject: Re: Bug#722451: Adoption

Date: Thu, 28 Aug 2014 01:15:32 +0200

Carlos Alberto Lopez Perez, le Wed 27 Aug 2014 11:54:57 +0200, a écrit :
> We have a clear process defined for this. Once you have your package
> ready, you can upload it to mentors.debian.net (or to other site if you
> prefer) and you ask on the mailing list debian-mentors@lists.debian.org
> (subscribe yourself to the list) for someone to review and upload your
> package.

I'm willing to review & upload under the debian-accessibility umbrella.
Best would probably be to maintain the packaging on alioth.debian.org
(so we can both get to commit to it), you just need to get an account
there and ask for joining the pkg-a11y group.

Samuel

Message #50 received at 722451@bugs.debian.org (full text, mbox, reply):

From: José Silva <jsantossilva@hotmail.com>

To: 722451@bugs.debian.org, "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

Cc: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

Subject: Re: Bug#722451: Adoption

Date: Sat, 13 Sep 2014 02:00:32 +0100

Hello,

> Please find the source & binary packaging here:
> http://debian-knoppix.alioth.debian.org/packages/compiz/

There are only packages for knoppix i386.

1. Could you please also package for amd64?

2. My system is debian jessie/sid xfce4 amd64. Once your packages are 
for debian/knoppix, will I be able to install your packages if build to 
amd64?

Regards,
jss

Message #55 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

To: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

Cc: José Silva <jsantossilva@hotmail.com>, 722451@bugs.debian.org, "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

Subject: Re: Bug#722451: Adoption

Date: Tue, 30 Sep 2014 03:46:21 +0200

[Message part 1 (text/plain, inline)]

Hello,

About amd64 packages and Debian: Since Knoppix has a 32bit as well as a
64bit kernel, but userspace is always 32bit in both cases, I personally
only need to build the i386 versions, these I provided at
http://debian-knoppix.alioth.debian.org/packages/compiz together with
the package sources. The source should build on plain Debian testing and
sid, regardless of bitness (i386 or amd64) on your system, I removed the
"Ubuntu specials" in the original debian/control dependencies and
debian/rules which would otherwise fail to build on Debian. Knoppix is
based on Debian testing+unstable.

I just uploaded the 0.9.12.0 compiz version based on
https://launchpad.net/compiz/+milestone/0.9.12.0, which features two
IMHO important accessibility patches (that I also attached here). They
fix the erraneous transparency on first usage of the ezoom and annotate
plugin (mouse curser and writing on screen were almost invisible unless
you activated the "magnify" plugin temporarily). I already suggested the
patches on the compiz bugtracker:
https://bugs.launchpad.net/compiz/+bug/1362005
https://bugs.launchpad.net/compiz/+bug/1362009
They have not been reviewed that, though.

Nevertheless, if you plan to adopt compiz in Debian again, I'd suggest
using the upstream sources on https://launchpad.net/compiz rather than
my modified version on
http://debian-knoppix.alioth.debian.org/packages/compiz and coordinate
with the project maintainers, which is just what Jean-Philippe Mengual
suggested.  Once compiz is officially back in Debian, I will happily use
that version rather than my forked version. I do need at least the ezoom
patch included in Knoppix, though, since ezoom (Super+Mousewheel) is an
important accessibility feature for users with low vision and is also
practival for presentations where the mousepointer should be visible.

Regards
-Klaus Knopper

On Tue, Sep 30, 2014 at 01:36:43AM +0200, MENGUAL Jean-Philippe wrote:
> Hi,
> 
> I'm going to package before freeze, on the top of 0.9.12 from
> Ubuntu. I don't have enough info about Knoppix packages
> (Debian-based, release, where they rely on, etc)..
> 
> I wonder if I should create from scratch in pkg-a11y group, or
> request for forwarding compiz from X to pkg-a11y before "updating"
> the git repo and so on.
> 
> I probably will go from scratch in pkg-a11y, if you have no problems
> with that.
> 
> Regards,
> 
> Le 13/09/2014 03:00, José Silva a écrit :
> >
> >Hello,
> >
> >> Please find the source & binary packaging here:
> >> http://debian-knoppix.alioth.debian.org/packages/compiz/
> >
> >There are only packages for knoppix i386.
> >
> >1. Could you please also package for amd64?
> >
> >2. My system is debian jessie/sid xfce4 amd64. Once your packages
> >are for debian/knoppix, will I be able to install your packages if
> >build to amd64?
> >
> >Regards,
> >jss
> 
> -- 
> Jean-Philippe MENGUAL
> 
> accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels
> 
> Mail: texou@accelibreinfo.eu
> 
> Site Web: http://www.accelibreinfo.eu

[compiz-ezoom.patch (text/x-diff, attachment)]

[compiz-annotate.patch (text/x-diff, attachment)]

Message #60 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: José Silva <jsantossilva@hotmail.com>, 722451@bugs.debian.org, "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

Subject: Re: Bug#722451: Adoption

Date: Tue, 30 Sep 2014 01:36:43 +0200

Hi,

I'm going to package before freeze, on the top of 0.9.12 from Ubuntu. I 
don't have enough info about Knoppix packages (Debian-based, release, 
where they rely on, etc)..

I wonder if I should create from scratch in pkg-a11y group, or request 
for forwarding compiz from X to pkg-a11y before "updating" the git repo 
and so on.

I probably will go from scratch in pkg-a11y, if you have no problems 
with that.

Regards,

Le 13/09/2014 03:00, José Silva a écrit :
>
> Hello,
>
> > Please find the source & binary packaging here:
> > http://debian-knoppix.alioth.debian.org/packages/compiz/
>
> There are only packages for knoppix i386.
>
> 1. Could you please also package for amd64?
>
> 2. My system is debian jessie/sid xfce4 amd64. Once your packages are 
> for debian/knoppix, will I be able to install your packages if build 
> to amd64?
>
> Regards,
> jss
>


-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #65 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

Cc: José Silva <jsantossilva@hotmail.com>, 722451@bugs.debian.org

Subject: Re: Bug#722451: Adoption

Date: Tue, 30 Sep 2014 07:05:42 +0200

Le 30/09/2014 03:46, Prof. Dipl.-Ing. Klaus Knopper a écrit :
> Hello,
> Hi,

> About amd64 packages and Debian: Since Knoppix has a 32bit as well as a
> 64bit kernel, but userspace is always 32bit in both cases, I personally
> only need to build the i386 versions, these I provided at
> http://debian-knoppix.alioth.debian.org/packages/compiz together with
> the package sources. The source should build on plain Debian testing and
> sid, regardless of bitness (i386 or amd64) on your system, I removed the
> "Ubuntu specials" in the original debian/control dependencies and
> debian/rules which would otherwise fail to build on Debian. Knoppix is
> based on Debian testing+unstable.

Ok so you did a major part of the work, and it's excellent given the few 
time before freeze and the complexity of the package. So I think I'll 
put in Debian what you do for Knoppix, it seems relevant.

>
> I just uploaded the 0.9.12.0 compiz version based on
> https://launchpad.net/compiz/+milestone/0.9.12.0, which features two
> IMHO important accessibility patches (that I also attached here). They
> fix the erraneous transparency on first usage of the ezoom and annotate
> plugin (mouse curser and writing on screen were almost invisible unless
> you activated the "magnify" plugin temporarily). I already suggested the
> patches on the compiz bugtracker:
> https://bugs.launchpad.net/compiz/+bug/1362005
> https://bugs.launchpad.net/compiz/+bug/1362009
> They have not been reviewed that, though.

But are these changes packaged in

http://debian-knoppix.alioth.debian.org/packages/compiz

? What's the status of your patch above (in launchpad) in debian-knoppix 
(uploaded? waiting for acceptation on launchpad before shipping in 
debian-knoppix, etc)?

> Nevertheless, if you plan to adopt compiz in Debian again, I'd suggest
> using the upstream sources on https://launchpad.net/compiz rather than
> my modified version on
> http://debian-knoppix.alioth.debian.org/packages/compiz and coordinate
> with the project maintainers, which is just what Jean-Philippe Mengual
> suggested.

But given details you gave, it's useless. It seems much more relevant to 
use your package, put them in Debian, and work you and us in order to 
stay synchronoous with Canonical. I don't think 2 "branches" should 
exist, I would prefer Debian + knoppix merge sfnce the base is similar.



> Once compiz is officially back in Debian, I will happily use
> that version rather than my forked version. I do need at least the ezoom
> patch included in Knoppix, though, since ezoom (Super+Mousewheel) is an
> important accessibility feature for users with low vision and is also
> practival for presentations where the mousepointer should be visible.

Just to be sure: can we take your package, ship the patch, upload in 
Debian? Or do you prefer to wait some Canonical's feedback? I really 
would like to merge Debian and you, so that your maintainance work is 
automatically shipped in Debian. It'll improve Debian+knoppix a11y, and 
will represent less work for me with low dev skills.

Last question: does Compiz magnify know to "follow the focus" now?

Regards,

> Regards
> -Klaus Knopper
>
> On Tue, Sep 30, 2014 at 01:36:43AM +0200, MENGUAL Jean-Philippe wrote:
>> Hi,
>>
>> I'm going to package before freeze, on the top of 0.9.12 from
>> Ubuntu. I don't have enough info about Knoppix packages
>> (Debian-based, release, where they rely on, etc)..
>>
>> I wonder if I should create from scratch in pkg-a11y group, or
>> request for forwarding compiz from X to pkg-a11y before "updating"
>> the git repo and so on.
>>
>> I probably will go from scratch in pkg-a11y, if you have no problems
>> with that.
>>
>> Regards,
>>
>> Le 13/09/2014 03:00, José Silva a écrit :
>>> Hello,
>>>
>>>> Please find the source & binary packaging here:
>>>> http://debian-knoppix.alioth.debian.org/packages/compiz/
>>> There are only packages for knoppix i386.
>>>
>>> 1. Could you please also package for amd64?
>>>
>>> 2. My system is debian jessie/sid xfce4 amd64. Once your packages
>>> are for debian/knoppix, will I be able to install your packages if
>>> build to amd64?
>>>
>>> Regards,
>>> jss
>> -- 
>> Jean-Philippe MENGUAL
>>
>> accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels
>>
>> Mail: texou@accelibreinfo.eu
>>
>> Site Web: http://www.accelibreinfo.eu


-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #70 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

To: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

Cc: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>, José Silva <jsantossilva@hotmail.com>, 722451@bugs.debian.org

Subject: Re: Bug#722451: Adoption

Date: Tue, 30 Sep 2014 13:43:58 +0200

[Message part 1 (text/plain, inline)]

Hello Jean-Philippe,

On Tue, Sep 30, 2014 at 07:05:42AM +0200, MENGUAL Jean-Philippe wrote:
> Le 30/09/2014 03:46, Prof. Dipl.-Ing. Klaus Knopper a écrit :
> >Hello,
> >Hi,
> 
> >About amd64 packages and Debian: Since Knoppix has a 32bit as well as a
> >64bit kernel, but userspace is always 32bit in both cases, I personally
> >only need to build the i386 versions, these I provided at
> >http://debian-knoppix.alioth.debian.org/packages/compiz together with
> >the package sources. The source should build on plain Debian testing and
> >sid, regardless of bitness (i386 or amd64) on your system, I removed the
> >"Ubuntu specials" in the original debian/control dependencies and
> >debian/rules which would otherwise fail to build on Debian. Knoppix is
> >based on Debian testing+unstable.
> 
> Ok so you did a major part of the work,

Well, I just added the changes that I needed in Knoppix. They are small
compared to the frequent upstream work on the Ubuntu launchpad. On the
other hand, my version is probably better tested because of inclusion in
Knoppix (with around 8000-20000 downloads per day), compared to the
upstream compiz version that Ubuntu seems to maintain last but not least
as a testcase for their own unity desktop.

The main development work is done on launchpad, whereas I just pull the
sources once or twice a year when there is a major upgrade, and include
them in Knoppix since compiz is one of the main features there.

Adopting the upstream launchpad version with its frequent changes from
bzr, may cause you more work, but would be closer to the original
authors of the software. It would also in my interest because if you are
maintaining compiz in Debian officially, I can stop creating a fork of
the upstream compiz version. 

If you choose my version, we have a packaging chain like this:

launchpad-based development from upstream authors -> Knoppers testing distribution -> Debians official packaging

Should be OK, too, then I will function as a proxy.

It's your decision, of course. Just tell me the final result, so that I
won't accidentially switch back to the official Debian package while the
official Debian package just uses Knoppix packages as upstream, so we
have a loop which is likely not being synchronized with upstream
development again. ;-)

> and it's excellent given the
> few time before freeze and the complexity of the package. So I think
> I'll put in Debian what you do for Knoppix, it seems relevant.

True, there are time constraints, and once the packages are in Debian
before feature freeze, you can probably still change the upstream source
later, so adopting the packages that work for Debian-based Knoppix right
now is probably the quickest way to do it.

You may want to recheck if my preference for using file-based settings
in $HOME/.config/compiz-1/compizconfig/* instead of using gsettings, is
suitable for Debian. I think a file-based configuration has less hidden
dependencies to gnome, though, while in Ubuntu, they keep everything
inside the gnome configuration scheme by default so it's configurable
with the central configuration GUI instead of needing its own "compiz
configuration settings manager" (ccsm). If not, change the "backend =
ini" parameter in /etc/compizconfig/config back to gsettings
accordingly.

> >I just uploaded the 0.9.12.0 compiz version based on
> >https://launchpad.net/compiz/+milestone/0.9.12.0, which features two
> >IMHO important accessibility patches (that I also attached here). They
> >fix the erraneous transparency on first usage of the ezoom and annotate
> >plugin (mouse curser and writing on screen were almost invisible unless
> >you activated the "magnify" plugin temporarily). I already suggested the
> >patches on the compiz bugtracker:
> >https://bugs.launchpad.net/compiz/+bug/1362005
> >https://bugs.launchpad.net/compiz/+bug/1362009
> >They have not been reviewed that, though.
> 
> But are these changes packaged in
> 
> http://debian-knoppix.alioth.debian.org/packages/compiz

Yes, they are included in my packages and well tested in Knoppix 7.4.1
and 7.4.2. I had sent the patches to upstream, but they have not looked
at them yet.

> ? What's the status of your patch above (in launchpad) in
> debian-knoppix (uploaded? waiting for acceptation on launchpad
> before shipping in debian-knoppix, etc)?

Waiting to be reviewed. But due to the technical context, these changes
should be considered harmless, i.e. compiz wll not crash just because I
changed the color settings before drawing, which is already done in
other stable plugins, too.

> >Nevertheless, if you plan to adopt compiz in Debian again, I'd suggest
> >using the upstream sources on https://launchpad.net/compiz rather than
> >my modified version on
> >http://debian-knoppix.alioth.debian.org/packages/compiz and coordinate
> >with the project maintainers, which is just what Jean-Philippe Mengual
> >suggested.
> 
> But given details you gave, it's useless. It seems much more
> relevant to use your package, put them in Debian, and work you and
> us in order to stay synchronoous with Canonical. I don't think 2
> "branches" should exist, I would prefer Debian + knoppix merge sfnce
> the base is similar.

It was mainly two packages and tools that don't exist in Debian which
caused the original debian/* recipes to fail outside of Ubuntu. If you
have some time now or later, you way want to check comparing a fresh bzr
checkout of compiz 0.9.12.0 from launchpad to my source. Unfortunately,
being lazy, I did not create a patch for all of my changes except the
two plugin fixes I mentioned, but changed the source files directly in
about 4 places. Also time constraints for a quick release. :-/

Running a diff between upstream compiz 0.9.12.0 and my source should not
be very large.

> >Once compiz is officially back in Debian, I will happily use
> >that version rather than my forked version. I do need at least the ezoom
> >patch included in Knoppix, though, since ezoom (Super+Mousewheel) is an
> >important accessibility feature for users with low vision and is also
> >practival for presentations where the mousepointer should be visible.
> 
> Just to be sure: can we take your package, ship the patch, upload in
> Debian?

Yes, of course, it's open source and I know my packages are working in
Debian testing and unstable. :-)

> Or do you prefer to wait some Canonical's feedback?

Waiting for them could take a few weeks, they work in bursts on compiz
and sometimes longer pauses in between, following the Ubuntu release
cycle. I think they would be happy if Debian adopts their work, I
already had a few email conversations with them.

> I really
> would like to merge Debian and you, so that your maintainance work
> is automatically shipped in Debian. It'll improve Debian+knoppix
> a11y, and will represent less work for me with low dev skills.

Sure, no problem. :-)

But we should keep a switch to the main development source in mind for
later, and start an email exchange with upstream so they may find a way
to provide additional build configurations for original Debian
additionally to their current Ubuntu-only builds, and save both of us
some work.

> Last question: does Compiz magnify know to "follow the focus" now?

The "ezoom" plugin has an optional setting to zoom and scale to newly
appearing windows, menus and popups (through their initial focus event).
So, if a dialog appears outside of the currently visible magnified area,
ezoom will reposition the visible range and scale to that new window, so
you don't miss it. In standard operation, it just follows the mouse.  I
attached two screenshots of the corresponding settings in ccsm.

What you probably have in mind and what is often asked for, is the
possibility to follow the "text cursor", for example if typing in
LibreOffice. The problem seems to be getting the coordinates of the
"text cursor" from the X server. This has not been done in compiz or
ezoom yet. Do you know any other magnification software that can follow
the "text cursor", which I could use as a template in order to improve
ezoom?

Regards
-Klaus

[compiz-ccsm-focus-tracking.png (image/png, attachment)]

[compiz-ccsm-mouse-behavior.png (image/png, attachment)]

Message #75 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>, 722451@bugs.debian.org

Cc: José Silva <jsantossilva@hotmail.com>

Subject: Re: Bug#722451: Adoption

Date: Tue, 30 Sep 2014 21:24:55 +0200

Well, I just added the changes that I needed in Knoppix. They are small 
compared to the frequent upstream work on the Ubuntu launchpad. On the 
other hand, my version is probably better tested because of inclusion in 
Knoppix (with around 8000-20000 downloads per day), compared to the 
upstream compiz version that Ubuntu seems to maintain last but not least 
as a testcase for their own unity desktop. The main development work is 
done on launchpad, whereas I just pull the sources once or twice a year 
when there is a major upgrade, and include them in Knoppix since compiz 
is one of the main features there. Adopting the upstream launchpad 
version with its frequent changes from bzr, may cause you more work, but 
would be closer to the original authors of the software. It would also 
in my interest because if you are maintaining compiz in Debian 
officially, I can stop creating a fork of the upstream compiz version. 
If you choose my version, we have a packaging chain like this: 
launchpad-based development from upstream authors -> Knoppers testing 
distribution -> Debians official packaging


But what changes do you do that imply a "Knoppix step" instead of 
maintaining directly in Debian? Why couldn't your work be done directly 
in Debian? I ask because:
1. I think we want in Debian a Compiz more similar as you do than this 
from Ubuntu, given they try to make it work for Unity, not us.
2. Do you do code patches? Important code patches?

Why couldn't the string be: upstream -> Debian (with you as 
co-maintainer and your release). It matches to Debian philosophy: 
stability, safety; it gives a cleaner package without Unity integration, 
etc. Why would we need, between upstream and Debian, a step in Knoppix 
instead of applying directly your work in Debian? Again, due to Unity 
integration and not priority for a11y, I don't think Debian has interest 
to use upstream release if you patch it in the direction we hope.

Should be OK, too, then I will function as a proxy. It's your decision, 
of course. Just tell me the final result, so that I won't accidentially 
switch back to the official Debian package while the official Debian 
package just uses Knoppix packages as upstream, so we have a loop which 
is likely not being synchronized with upstream development again. ;-)

Well I really think we could use directly your work, which is a kind of 
filter with upstream, directly in Debian instead of creating a 
knoppix-"step".

>> and it's excellent given the
>> few time before freeze and the complexity of the package. So I think
>> I'll put in Debian what you do for Knoppix, it seems relevant.
> True, there are time constraints, and once the packages are in Debian
> before feature freeze, you can probably still change the upstream source
> later, so adopting the packages that work for Debian-based Knoppix right
> now is probably the quickest way to do it.
>
> You may want to recheck if my preference for using file-based settings
> in $HOME/.config/compiz-1/compizconfig/* instead of using gsettings, is
> suitable for Debian. I think a file-based configuration has less hidden
> dependencies to gnome, though, while in Ubuntu, they keep everything
> inside the gnome configuration scheme by default so it's configurable
> with the central configuration GUI instead of needing its own "compiz
> configuration settings manager" (ccsm). If not, change the "backend =
> ini" parameter in /etc/compizconfig/config back to gsettings
> accordingly.
Ok I'll check. I hope to use ccsm yes, but shipped typically in 
settings. I'll think of this.

>>> I just uploaded the 0.9.12.0 compiz version based on
>>> https://launchpad.net/compiz/+milestone/0.9.12.0, which features two
>>> IMHO important accessibility patches (that I also attached here). They
>>> fix the erraneous transparency on first usage of the ezoom and annotate
>>> plugin (mouse curser and writing on screen were almost invisible unless
>>> you activated the "magnify" plugin temporarily). I already suggested the
>>> patches on the compiz bugtracker:
>>> https://bugs.launchpad.net/compiz/+bug/1362005
>>> https://bugs.launchpad.net/compiz/+bug/1362009
>>> They have not been reviewed that, though.
>> But are these changes packaged in
>>
>> http://debian-knoppix.alioth.debian.org/packages/compiz
> Yes, they are included in my packages and well tested in Knoppix 7.4.1
> and 7.4.2. I had sent the patches to upstream, but they have not looked
> at them yet.
>
>> ? What's the status of your patch above (in launchpad) in
>> debian-knoppix (uploaded? waiting for acceptation on launchpad
>> before shipping in debian-knoppix, etc)?
> Waiting to be reviewed. But due to the technical context, these changes
> should be considered harmless, i.e. compiz wll not crash just because I
> changed the color settings before drawing, which is already done in
> other stable plugins, too.
>
>>> Nevertheless, if you plan to adopt compiz in Debian again, I'd suggest
>>> using the upstream sources on https://launchpad.net/compiz rather than
>>> my modified version on
>>> http://debian-knoppix.alioth.debian.org/packages/compiz and coordinate
>>> with the project maintainers, which is just what Jean-Philippe Mengual
>>> suggested.
>> But given details you gave, it's useless. It seems much more
>> relevant to use your package, put them in Debian, and work you and
>> us in order to stay synchronoous with Canonical. I don't think 2
>> "branches" should exist, I would prefer Debian + knoppix merge sfnce
>> the base is similar.
> It was mainly two packages and tools that don't exist in Debian which
> caused the original debian/* recipes to fail outside of Ubuntu. If you
> have some time now or later, you way want to check comparing a fresh bzr
> checkout of compiz 0.9.12.0 from launchpad to my source. Unfortunately,
> being lazy, I did not create a patch for all of my changes except the
> two plugin fixes I mentioned, but changed the source files directly in
> about 4 places. Also time constraints for a quick release. :-/
Oh! You mean that all your patches are not applied at each deb package 
generation? They're hardcoded? If yes, after packaging, I think it worth 
to compare both upstream and your files to apply patches more properly.

> Running a diff between upstream compiz 0.9.12.0 and my source should not
> be very large.
So it worth try to make the package clean in changes it brings in the code.

>>> Once compiz is officially back in Debian, I will happily use
>>> that version rather than my forked version. I do need at least the ezoom
>>> patch included in Knoppix, though, since ezoom (Super+Mousewheel) is an
>>> important accessibility feature for users with low vision and is also
>>> practival for presentations where the mousepointer should be visible.
>> Just to be sure: can we take your package, ship the patch, upload in
>> Debian?
> Yes, of course, it's open source and I know my packages are working in
> Debian testing and unstable. :-)
>
>> Or do you prefer to wait some Canonical's feedback?
> Waiting for them could take a few weeks, they work in bursts on compiz
> and sometimes longer pauses in between, following the Ubuntu release
> cycle. I think they would be happy if Debian adopts their work, I
> already had a few email conversations with them.
>
>> I really
>> would like to merge Debian and you, so that your maintainance work
>> is automatically shipped in Debian. It'll improve Debian+knoppix
>> a11y, and will represent less work for me with low dev skills.
> Sure, no problem. :-)
>
> But we should keep a switch to the main development source in mind for
> later, and start an email exchange with upstream so they may find a way
> to provide additional build configurations for original Debian
> additionally to their current Ubuntu-only builds, and save both of us
> some work.
True.

>> Last question: does Compiz magnify know to "follow the focus" now?
> The "ezoom" plugin has an optional setting to zoom and scale to newly
> appearing windows, menus and popups (through their initial focus event).
> So, if a dialog appears outside of the currently visible magnified area,
> ezoom will reposition the visible range and scale to that new window, so
> you don't miss it. In standard operation, it just follows the mouse.  I
> attached two screenshots of the corresponding settings in ccsm.
>
> What you probably have in mind and what is often asked for, is the
> possibility to follow the "text cursor", for example if typing in
> LibreOffice. The problem seems to be getting the coordinates of the
> "text cursor" from the X server. This has not been done in compiz or
> ezoom yet. Do you know any other magnification software that can follow
> the "text cursor", which I could use as a template in order to improve
> ezoom?
I believe gnome-mag with Orca did that in 2.x releases. Ok so it's 
something to do.

Regards,

> Regards
> -Klaus


-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #80 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>, 722451@bugs.debian.org

Cc: José Silva <jsantossilva@hotmail.com>

Subject: Re: Bug#722451: Adoption

Date: Tue, 14 Oct 2014 01:35:38 +0200

Hi,

I think your Compiz packaging will be in Debian before next Sunday or 
20th. I plan to add yourself from possible uploaders, because I really 
hope we'll be able to work together on the package itself. I'm sure your 
work is directly importable in Debian and does what's needed.

I've an usage question (personally I cannot test due to my blindness): I 
was said that Emerald was useful to add icons to minimize, restore, 
close, etc top right of the window. But other users tell me metacity 
does that too, via gtk-window-decorator. So far I uploaded Emerald, so 
that once frozen, we can test Emerald and Metacity and see the results. 
I prefer having a useless package than a useful missing package after 
freeze.
But anyway: do you confirm that Metacity provides what's needed or is 
Emerald useful? My purpose is to make Compiz work with Orca too, so with 
Meta-tab etc. Other point: if Metacity is enough, how do you set it to 
have gtk-window-decorator enabled and how is it shipped in Compiz? 
Finally, 9hat's the Metacity status: maintained upstream? will it be 
linked to gnome3 (it'd justify Emerald to have less useless deps to 
install)?

Thanks for your feedback.

Regards,

Le 30/09/2014 13:43, Prof. Dipl.-Ing. Klaus Knopper a écrit :
> Hello Jean-Philippe,
>
> On Tue, Sep 30, 2014 at 07:05:42AM +0200, MENGUAL Jean-Philippe wrote:
>> Le 30/09/2014 03:46, Prof. Dipl.-Ing. Klaus Knopper a écrit :
>>> Hello,
>>> Hi,
>>> About amd64 packages and Debian: Since Knoppix has a 32bit as well as a
>>> 64bit kernel, but userspace is always 32bit in both cases, I personally
>>> only need to build the i386 versions, these I provided at
>>> http://debian-knoppix.alioth.debian.org/packages/compiz together with
>>> the package sources. The source should build on plain Debian testing and
>>> sid, regardless of bitness (i386 or amd64) on your system, I removed the
>>> "Ubuntu specials" in the original debian/control dependencies and
>>> debian/rules which would otherwise fail to build on Debian. Knoppix is
>>> based on Debian testing+unstable.
>> Ok so you did a major part of the work,
> Well, I just added the changes that I needed in Knoppix. They are small
> compared to the frequent upstream work on the Ubuntu launchpad. On the
> other hand, my version is probably better tested because of inclusion in
> Knoppix (with around 8000-20000 downloads per day), compared to the
> upstream compiz version that Ubuntu seems to maintain last but not least
> as a testcase for their own unity desktop.
>
> The main development work is done on launchpad, whereas I just pull the
> sources once or twice a year when there is a major upgrade, and include
> them in Knoppix since compiz is one of the main features there.
>
> Adopting the upstream launchpad version with its frequent changes from
> bzr, may cause you more work, but would be closer to the original
> authors of the software. It would also in my interest because if you are
> maintaining compiz in Debian officially, I can stop creating a fork of
> the upstream compiz version.
>
> If you choose my version, we have a packaging chain like this:
>
> launchpad-based development from upstream authors -> Knoppers testing distribution -> Debians official packaging
>
> Should be OK, too, then I will function as a proxy.
>
> It's your decision, of course. Just tell me the final result, so that I
> won't accidentially switch back to the official Debian package while the
> official Debian package just uses Knoppix packages as upstream, so we
> have a loop which is likely not being synchronized with upstream
> development again. ;-)
>
>> and it's excellent given the
>> few time before freeze and the complexity of the package. So I think
>> I'll put in Debian what you do for Knoppix, it seems relevant.
> True, there are time constraints, and once the packages are in Debian
> before feature freeze, you can probably still change the upstream source
> later, so adopting the packages that work for Debian-based Knoppix right
> now is probably the quickest way to do it.
>
> You may want to recheck if my preference for using file-based settings
> in $HOME/.config/compiz-1/compizconfig/* instead of using gsettings, is
> suitable for Debian. I think a file-based configuration has less hidden
> dependencies to gnome, though, while in Ubuntu, they keep everything
> inside the gnome configuration scheme by default so it's configurable
> with the central configuration GUI instead of needing its own "compiz
> configuration settings manager" (ccsm). If not, change the "backend =
> ini" parameter in /etc/compizconfig/config back to gsettings
> accordingly.
>
>>> I just uploaded the 0.9.12.0 compiz version based on
>>> https://launchpad.net/compiz/+milestone/0.9.12.0, which features two
>>> IMHO important accessibility patches (that I also attached here). They
>>> fix the erraneous transparency on first usage of the ezoom and annotate
>>> plugin (mouse curser and writing on screen were almost invisible unless
>>> you activated the "magnify" plugin temporarily). I already suggested the
>>> patches on the compiz bugtracker:
>>> https://bugs.launchpad.net/compiz/+bug/1362005
>>> https://bugs.launchpad.net/compiz/+bug/1362009
>>> They have not been reviewed that, though.
>> But are these changes packaged in
>>
>> http://debian-knoppix.alioth.debian.org/packages/compiz
> Yes, they are included in my packages and well tested in Knoppix 7.4.1
> and 7.4.2. I had sent the patches to upstream, but they have not looked
> at them yet.
>
>> ? What's the status of your patch above (in launchpad) in
>> debian-knoppix (uploaded? waiting for acceptation on launchpad
>> before shipping in debian-knoppix, etc)?
> Waiting to be reviewed. But due to the technical context, these changes
> should be considered harmless, i.e. compiz wll not crash just because I
> changed the color settings before drawing, which is already done in
> other stable plugins, too.
>
>>> Nevertheless, if you plan to adopt compiz in Debian again, I'd suggest
>>> using the upstream sources on https://launchpad.net/compiz rather than
>>> my modified version on
>>> http://debian-knoppix.alioth.debian.org/packages/compiz and coordinate
>>> with the project maintainers, which is just what Jean-Philippe Mengual
>>> suggested.
>> But given details you gave, it's useless. It seems much more
>> relevant to use your package, put them in Debian, and work you and
>> us in order to stay synchronoous with Canonical. I don't think 2
>> "branches" should exist, I would prefer Debian + knoppix merge sfnce
>> the base is similar.
> It was mainly two packages and tools that don't exist in Debian which
> caused the original debian/* recipes to fail outside of Ubuntu. If you
> have some time now or later, you way want to check comparing a fresh bzr
> checkout of compiz 0.9.12.0 from launchpad to my source. Unfortunately,
> being lazy, I did not create a patch for all of my changes except the
> two plugin fixes I mentioned, but changed the source files directly in
> about 4 places. Also time constraints for a quick release. :-/
>
> Running a diff between upstream compiz 0.9.12.0 and my source should not
> be very large.
>
>>> Once compiz is officially back in Debian, I will happily use
>>> that version rather than my forked version. I do need at least the ezoom
>>> patch included in Knoppix, though, since ezoom (Super+Mousewheel) is an
>>> important accessibility feature for users with low vision and is also
>>> practival for presentations where the mousepointer should be visible.
>> Just to be sure: can we take your package, ship the patch, upload in
>> Debian?
> Yes, of course, it's open source and I know my packages are working in
> Debian testing and unstable. :-)
>
>> Or do you prefer to wait some Canonical's feedback?
> Waiting for them could take a few weeks, they work in bursts on compiz
> and sometimes longer pauses in between, following the Ubuntu release
> cycle. I think they would be happy if Debian adopts their work, I
> already had a few email conversations with them.
>
>> I really
>> would like to merge Debian and you, so that your maintainance work
>> is automatically shipped in Debian. It'll improve Debian+knoppix
>> a11y, and will represent less work for me with low dev skills.
> Sure, no problem. :-)
>
> But we should keep a switch to the main development source in mind for
> later, and start an email exchange with upstream so they may find a way
> to provide additional build configurations for original Debian
> additionally to their current Ubuntu-only builds, and save both of us
> some work.
>
>> Last question: does Compiz magnify know to "follow the focus" now?
> The "ezoom" plugin has an optional setting to zoom and scale to newly
> appearing windows, menus and popups (through their initial focus event).
> So, if a dialog appears outside of the currently visible magnified area,
> ezoom will reposition the visible range and scale to that new window, so
> you don't miss it. In standard operation, it just follows the mouse.  I
> attached two screenshots of the corresponding settings in ccsm.
>
> What you probably have in mind and what is often asked for, is the
> possibility to follow the "text cursor", for example if typing in
> LibreOffice. The problem seems to be getting the coordinates of the
> "text cursor" from the X server. This has not been done in compiz or
> ezoom yet. Do you know any other magnification software that can follow
> the "text cursor", which I could use as a template in order to improve
> ezoom?
>
> Regards
> -Klaus


-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #85 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Prof. Dipl.-Ing. Klaus Knopper" <bugs@knopper.net>

To: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

Cc: 722451@bugs.debian.org, José Silva <jsantossilva@hotmail.com>

Subject: Re: Bug#722451: Adoption

Date: Tue, 14 Oct 2014 03:17:35 +0200

Hello Jean-Philippe,

On Tue, Oct 14, 2014 at 01:35:38AM +0200, MENGUAL Jean-Philippe wrote:
> Hi,
> 
> I think your Compiz packaging will be in Debian before next Sunday
> or 20th. I plan to add yourself from possible uploaders, because I
> really hope we'll be able to work together on the package itself.
> I'm sure your work is directly importable in Debian and does what's
> needed.
> 
> I've an usage question (personally I cannot test due to my
> blindness):

You did not tell me that detail before, though I should probably have
guessed. Maybe you have heared that my wife is blind, too
(http://en.wikipedia.org/wiki/Knoppix#Adriane_Knoppix), she does not use
the graphical desktop at all even with the usual orca+compiz
combination, but a text-based interface instead with sbl as
screenreader, and is working way faster using this method than any
seeing person I know working on the graphical interface including
myself.

> I was said that Emerald was useful to add icons to
> minimize, restore, close, etc top right of the window.

I should explain what it does. For the effect part like zooming, window
overview by moving mouse top right, moving windows with key
combinations, the plain compiz composite manager as add-on to a desktop
like LXDE, GNOME, KDE, openbox ... is sufficient, but people working
graphically will most likely want to use the mouse for grabbing windows
at a title bar, using minimize and maximize as buttons in the title bar
and so on.  That's where the "window decorator" comes in, it's the part
of the GUI that draws window borders, title bar, buttons and menus
aroung the window.  Since the window management has to closely work
together with compiz, it is not possible to use openbox, metacity etc.
directly for this together with compiz. The window decorator has to work
together with compiz special handling of transparency and effects. On
the other side, a compiz-aware window decorator will ONLY work together
with compiz and will not start without compiz having started prior.  So
the two, effect manager compiz and window decorators, make sense at
least as a "recommends" field in each other package.

The only three window decorators that are compatible with compiz which I
am aware of, are in fact emerald (which is probably the oldest from the
time when compiz was forked as compiz-fusion), gtk-window-decorator and
kde(4)-window-decorator. All three have the same function, by drawing
borders around windows so they can be resized and moved using the mouse,
plus icons for maximize, minimize, close, and a menu button on the left
(which is configurable by either gconf/dconf in GTK or KDE settings in
KDE). The users choice of window decorator can also be called by a
script "compiz-decorator".

I use gtk-window-decorator in Knoppix, which regularly resides inside
the package compiz-gnome built from the compiz source, because it
depends only on compiz and common GTK and metacity libraries, is
relatively lightweight, and shares look&feel with the metacity window
manager which is what I also use for graphics cards that are unable to
run compiz, so the windows will look the same in compiz or without
compiz. It is possible to switch between compiz and a 2D non-effect
desktop by calling

compiz --replace
vs.
metacity --replace

compiz would call the window-decorator that had been set forth in its
configuration plugin "window decoration", where compiz-decorator is the
default alias, which then calls either gtk-window-decorator or
kde-window-decorator.

I hope this clears up the relation between compiz and the window
decorator.

Which one works better with orca, may depend on whether you prefer KDE
or GNOME accessibility. From my experience, orca works well nowadays
with GTK as well as QT based applicatione, provided that the at-spi and
atk packages are installed for both versions. Concerning the decorator,
this plays only a role in reading the window menu from the title bar and
the window title itself, which will most likely not being used by a
blind user who works more with keyboard hotkeys defined in compiz
directly instead of clicking somewhere near the top 10 pixels of a
window.

> But other
> users tell me metacity does that too, via gtk-window-decorator.

Again, metacity itself cannot be used as window decorator in compiz,
since it replaces compiz when being started with --replace. But
gtk-window-decorator, which is built with metacity libraries for
configuration, look&feel, works together with compiz.

> So
> far I uploaded Emerald, so that once frozen, we can test Emerald and
> Metacity and see the results.

The script /usr/bin/compiz-decorator contains these lines:
 73 # start a decorator
 74 if [ -x ${COMPIZ_BIN_PATH}emerald ] && [ "$USE_EMERALD" = "yes" ]; then
 75     DECORATOR=emerald
 76 elif [ -x ${COMPIZ_BIN_PATH}gtk-window-decorator ] && [ -n "$GNOME_DESKTOP_SESSION_ID" ]; then
 77     DECORATOR=gtk-window-decorator
 78 elif [ -x ${COMPIZ_BIN_PATH}kde4-window-decorator ] && [ x$KDE_SESSION_VERSION = x"4" ]; then
 79     DECORATOR=kde4-window-decorator
 80 fi
so it will find the best match on its own.

> I prefer having a useless package than
> a useful missing package after freeze.
> But anyway: do you confirm that Metacity provides what's needed or
> is Emerald useful?

Not metacity, but gtk-window-decorator from compiz-gnome provides a
metacity-lookalike window decorator, same as kde(4)-window-decorator
will provice a window decorator with a KDE4 look&feel.

Emerald can be used, too. You can install all three with no conflicts, I
guess.

> My purpose is to make Compiz work with Orca too,
> so with Meta-tab etc. Other point: if Metacity is enough, how do you
> set it to have gtk-window-decorator enabled and how is it shipped in
> Compiz?

I'm afraid that metacity (which will not work together with compiz) has
lost most of its useful keyboard shurtcuts in Debian/unstable since
moving to GTK3, including Alt-Tab for window cycling.  metacity-based
gtk-window-decorator instead can still do this because compiz is doing
the hotkey handling via the "command" plugin independent of the
decorator.

> Finally, 9hat's the Metacity status: maintained upstream?

metacity seems to be maintained, but has less useful features than
compiz plus metacity-based gtk-window-decorator with the same look/feel.

> will it be linked to gnome3 (it'd justify Emerald to have less
> useless deps to install)?

I'm not sure if emerald has less useless deps to install that the
compiz-gnome package that's included in compiz source, you could try.

Regards
-Klaus

Message #90 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Adam Borowski <kilobyte@angband.pl>

To: 722451@bugs.debian.org

Subject: you need to upload compiz/emerald/emerald-themes NOW

Date: Mon, 20 Oct 2014 01:08:45 +0200

Hi!
I hope you're aware that, to be included in jessie, any new packages must
hit the archive by Oct 26.  And -before- that, it must clear the massively
overloaded NEW queue (to which everyone puts last-moment uploads).  So,
here's a reminder.

Also, if you'd want some testing, are the packages you're preparing same as
those on http://debian-knoppix.alioth.debian.org/packages/compiz/ ?  That
repository lacks emerald, though.  I'm using compiz (0.8.4-5.2) for years,
it wouldn't be nice if jessie lacked it or had it broken.

Also, I wonder why you're building it against metacity (depreciated) rather
than marco (actively developed fork) -- compiz tends to be used with Mate
and XFCE rather than Gnome3.

-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable and Non-Discriminatory prices.

Message #95 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: Adam Borowski <kilobyte@angband.pl>, 722451@bugs.debian.org

Subject: Re: Bug#722451: you need to upload compiz/emerald/emerald-themes NOW

Date: Mon, 20 Oct 2014 02:22:11 +0200

Le 20/10/2014 01:08, Adam Borowski a écrit :
> Hi!

Hi,

> I hope you're aware that, to be included in jessie, any new packages must
> hit the archive by Oct 26.  And -before- that, it must clear the massively
> overloaded NEW queue (to which everyone puts last-moment uploads).  So,
> here's a reminder.
I'm aware and worry, given that my packaging skills are limited and it's 
hard for me to package such complex things. But I hope, I hope, I hope! 
I search help too!

> Also, if you'd want some testing, are the packages you're preparing same as
> those on http://debian-knoppix.alioth.debian.org/packages/compiz/ ?  That
> repository lacks emerald, though.

Yes, I plan to import in Debian Jessie the packaging from knoppix. But 
the trial I did today resulted failures. So I try to get helped from the 
Knoppix's packager. Dunno why pdebuild fails.

For Emerald, it's committed in git.debian.org/pkg-a11y/emerald.git. I'd 
like to have success, but so far the build doesn't find some libs I 
don't know myself, such as libdecoration. I'm not sure I'll be able to 
package it before 26th.

Finally, libwnckmm, one dependency for Emerald, is waiting for 
acceptation in master FTP. It's in the queue.



>    I'm using compiz (0.8.4-5.2) for years,
> it wouldn't be nice if jessie lacked it or had it broken.
It's major for me to have it in Jessie. That's why I'll try to import 
it, although I need discussions with release-manager team. I'll try to 
respect delays, if I can't, I'll try to argue. Otherwise I'll do an 
external repo.

> Also, I wonder why you're building it against metacity (depreciated) rather
> than marco (actively developed fork) -- compiz tends to be used with Mate
> and XFCE rather than Gnome3.
>
I don't build against anything. :) And my purpose would be to build 
against Emerald, Marco and MATE. That's to fix all that I need help and 
support from the Knoppix's packager. One thing is sure, I don't want 
Compiz in Jessie to be built against Metacity. It'll be against Marco or 
Emerald.

Any help would be appreciated, but be sure I'll do all needed efforts to 
get Compiz and Emerald in Jessie. I plan arguing after freeze, because 
it's major!

Sincerely,

-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #100 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Stephen M. Webb" <stephen.webb@canonical.com>

To: 722451@bugs.debian.org

Subject: Packaging Compiz for Debian

Date: Wed, 22 Oct 2014 10:51:22 -0400

I'm very interested in minimizing the delta between Ubuntu packaging
of Compiz and Debian packaging of Compiz.  I think the best approach
is to create a Compiz packaging team at Alioth and host all of the
Debian packaging there:  that way, we (upstream Compiz) as team
members can keep the Debian packages up to date in a more timely
manner, even if that means distro-patching upstream changes between
releases.

Once this bug is closed with the upload (or before that, depending on
timing) could we please move in that direction?

Message #105 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 22 Oct 2014 17:05:34 +0200

Stephen M. Webb, le Wed 22 Oct 2014 10:51:22 -0400, a écrit :
> I think the best approach is to create a Compiz packaging team at
> Alioth and host all of the Debian packaging there:

Well, we can also give you access to the pkg-a11y project.

> that way, we (upstream Compiz) as team members can keep the Debian
> packages up to date in a more timely manner,

That'd be good indeed!

> even if that means distro-patching upstream changes between
> releases.

Sure, we can manage this like we do for brltty, at-spi etc.

> Once this bug is closed with the upload (or before that, depending on
> timing) could we please move in that direction?

I guess compiz won't be ready for Jessie, so I guess you can already
sync with Jean-Philippe.

Samuel

Message #110 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Stephen M. Webb" <stephen.webb@canonical.com>

To: 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 22 Oct 2014 13:49:59 -0400

> Well, we can also give you access to the pkg-a11y project.

It just doesn't make much sense to me that a major window manager
would be a subproject of the a11y team.

A separate team makes it easier for additional upstream Compiz
developers to participate in maintaining the Debian packaging, and
also it's more sensible when it comes time to add additional non-core
Compiz plugins.

Short term, for the purposes of getting Compiz back into the archives,
status quo will do.

Message #115 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: "Stephen M. Webb" <stephen.webb@canonical.com>, 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 22 Oct 2014 19:58:03 +0200

Stephen M. Webb, le Wed 22 Oct 2014 13:49:59 -0400, a écrit :
> > Well, we can also give you access to the pkg-a11y project.
> 
> It just doesn't make much sense to me that a major window manager
> would be a subproject of the a11y team.

Ok, then fine :)

It just happens that a couple of years ago, only a11y people were
interested in packaging compiz, but if that has changed, that's just
even greater :)

Samuel

Message #120 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: Samuel Thibault <sthibault@debian.org>, 722451@bugs.debian.org, "Stephen M. Webb" <stephen.webb@canonical.com>

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 22 Oct 2014 22:25:36 +0200

Is it optimal to create a group for a single packages? Usually, groups 
handle themes or several packages.

Moreover, the Compiz which is about being packaged has important 
changes, intended to make it a good a11y tool. It's at least what I 
understood from Knoppix's release.

That's why personally, especially since we have 3 new devs to help 
packaging, I think you should join pkg-a11y and work on the Debian git 
repo, where you can create branches, tags, etc. Your help is, of course, 
welcome.

Would you agree to maintain in pkg-a11y until Jessie (if we manage to 
upload before freeze), then thinking of this together? 1st because 3 
contrib have just come, and 4 with you; then because the time before 
deadline freeze is short.

Regards,

Le 22/10/2014 19:58, Samuel Thibault a écrit :
> Stephen M. Webb, le Wed 22 Oct 2014 13:49:59 -0400, a écrit :
>>> Well, we can also give you access to the pkg-a11y project.
>> It just doesn't make much sense to me that a major window manager
>> would be a subproject of the a11y team.
> Ok, then fine :)
>
> It just happens that a couple of years ago, only a11y people were
> interested in packaging compiz, but if that has changed, that's just
> even greater :)
>
> Samuel
>


-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #125 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 22 Oct 2014 23:12:31 +0200

MENGUAL Jean-Philippe, le Wed 22 Oct 2014 22:25:36 +0200, a écrit :
> Is it optimal to create a group for a single packages?

It's not a single package, we have to package a few things like
libwnckmm, compiz, emerald, etc.

> Moreover, the Compiz which is about being packaged has important changes,
> intended to make it a good a11y tool. It's at least what I understood from
> Knoppix's release.

Using another group for compiz doesn't really interfere with that.

Samuel

Message #130 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Ksamak <ksamak@riseup.net>

To: 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 5 Nov 2014 14:17:39 +0100

[Message part 1 (text/plain, inline)]

On Wed, 22 Oct 2014 23:12:31 +0200 Samuel Thibault <sthibault@debian.org> wrote:
> 
> > Moreover, the Compiz which is about being packaged has important changes,
> > intended to make it a good a11y tool. It's at least what I understood from
> > Knoppix's release.
> 

It should be noted that the packaging for sid has been done, and that an
upload request has been made.
-- 
ksamak

[signature.asc (application/pgp-signature, inline)]

Message #135 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Stephen M. Webb" <stephen.webb@bregmasoft.ca>

To: 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 17 Dec 2014 11:25:11 -0500

[Message part 1 (text/plain, inline)]

What is the current status of this?  The package has not been uploaded to experimental yet.

Where is the Debianized source? The source at http://anonscm.debian.org/cgit/pkg-a11y/compiz.git/ doesn't look like it
would build on ARM or run on any architecture (because it's missing multiarch changes for plugin search).

-- 
Stephen M. Webb  <stephen.webb@bregmasoft.ca>

[signature.asc (application/pgp-signature, attachment)]

Message #140 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: stephen.webb@bregmasoft.ca, 722451@bugs.debian.org, Ksamak <ksamak@riseup.net>

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 17 Dec 2014 20:57:07 +0100

Hi,

I'll let ksamak to answer when he goes back from holiday, as he 
packaged. In my remember, he submitted the package to a mentor who 
didn't have the time to look at it. I cannot remember if he submitted 
this in our own repo or in alioth. Anyway, I know he did a quite 
important work so that Compiz to be multi-architecture, and then started 
a thought about the decorator and dependencies.

Your feedback about ARM is interesting. Maybe he forgot something. I Cc 
him and will ping him as soon as he is back.

Sincerely,

Le 17/12/2014 17:25, Stephen M. Webb a écrit :
> What is the current status of this?  The package has not been uploaded to experimental yet.
>
> Where is the Debianized source? The source at http://anonscm.debian.org/cgit/pkg-a11y/compiz.git/ doesn't look like it
> would build on ARM or run on any architecture (because it's missing multiarch changes for plugin search).
>


-- 
Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu

Message #145 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Miguel A. Colón Vélez <debian.micove@gmail.com>

To: 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Fri, 19 Dec 2014 18:42:45 -0500

Hello:

I had been working on a compiz package for the Debian X Strike Force
team a few years back but they were never interested. I based it on
their git repository and have been updating it since before compiz was
removed from Debian.

The package is in here
https://github.com/micove/compiz

It builds in amd64 and armel (well it's at 22% and slowwlllly
compiling with qemu) and tries to maintain an upgrade path with
0.8.4-5.2 and 0.9.2.1+git20110224.cb1268cb-1 that were previously in
squeeze/sid/experimental. The package does not play nice with Ubuntu
since it's based in the Debian package therefore the unity stuff is
missing and need a soname bump among other things.

The current source in
http://anonscm.debian.org/cgit/pkg-a11y/compiz.git is a bit broken
since dh-exec code does not work because the file is not executable
and  multiarch in general does not work among other things. Also the
upgrade path for Debian is broken too since the package is clearly
based on the Ubuntu one. Debian had packages like
compiz-fusion-plugins-{main,extra,unsupported} that never were in
Ubuntu while providing transitional packages for packages that were
never in Debian. Basically several packages had different names and
even packages with the same name had different files which needs a
different set of transitional packages and Break/Replaces.

Not sure what the status of this packaging is but I hope this helps,
Miguel

Message #150 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Ksamak <ksamak@riseup.net>

To: 722451@bugs.debian.org

Cc: stephen.webb@bregmasoft.ca

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Fri, 26 Dec 2014 10:30:50 +0100

[Message part 1 (text/plain, inline)]

> Le 17/12/2014 17:25, Stephen M. Webb a écrit :
>What is the current status of this?  The package has not been uploaded to experimental yet.
>
>Where is the Debianized source? The source at http://anonscm.debian.org/cgit/pkg-a11y/compiz.git/ doesn't look like it
>would build on ARM or run on any architecture (because it's missing multiarch changes for plugin search).
>
The packaging has been uploaded to alioth and is awaiting review.
However it doesn't seem to be high prio.
You can find a copy of the repo here for the moment for your convenience:

git -c http.sslVerify=false clone http://git.ksamak.net/accelibreinfo/compiz.git

-- 
ksamak
I am the "ILOVEGNU" signature virus. Just copy me to your signature.
This email was infected under the terms of the GNU General Public License.

[signature.asc (application/pgp-signature, inline)]

Message #155 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Stephen M. Webb" <stephen.webb@bregmasoft.ca>

To: 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Wed, 03 Jun 2015 08:30:58 -0400

[Message part 1 (text/plain, inline)]

Any progress?  It's been 10 months and no upload yet.

As an upstream maintainer I'm perfectly willing to take over this work: we regularly build against sid anyway.

-- 
Stephen M. Webb  <stephen.webb@bregmasoft.ca>

[signature.asc (application/pgp-signature, attachment)]

Message #160 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Ksamak <ksamak@riseup.net>

To: stephen.webb@bregmasoft.ca, 722451@bugs.debian.org

Subject: Re: Bug#722451: Packaging Compiz for Debian

Date: Thu, 4 Jun 2015 11:59:42 +0530

[Message part 1 (text/plain, inline)]

On Wed, Jun 03, 2015 at 08:30:58AM -0400, Stephen M. Webb wrote:
> Any progress?  It's been 10 months and no upload yet.
> 
> As an upstream maintainer I'm perfectly willing to take over this work: we regularly build against sid anyway.
> 
> -- 
> Stephen M. Webb  <stephen.webb@bregmasoft.ca>
> 

We are still actively working on the project, and using compiz on
regular basis. I was under the impression that the program needed
careful tests before being uploaded, but if it's acceptable, we'd be
glad to see it back in debian.
If you can provide help, we would greatly appreciate it, as we already
have users that make daily use of compiz, and some bug reports.  I can
be of any assistance required in maintaining or debugging the software.
If you judge necessary to put yourself as a maintainer in debian, i will
still be as active.
thank you for the interest
-- 
Ksamak
hypra.fr Team

[signature.asc (application/pgp-signature, inline)]

Message #170 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>

To: 722451@bugs.debian.org, Debian Accessibility Team <debian-accessibility@lists.debian.org>

Subject: Creating Compiz group

Date: Thu, 30 Jul 2015 01:28:22 +0200

Hi,

Actually I hoped submitting the package to a11y team could speed up the 
upload, but lack of time prevents this. So as requested by Stephen, 
we've just created a Compiz packaging team, so that:
1. Ubuntu, Knoppix and Debian have a synchronized packaging policy of 
this package
2. Upstream devs and package maintainers can dialog

Don't hesitate to join the group. Were subscribed now ksamak, Stephen, 
Samuel, Luke, and Klaus. And any interested dev is 9elcome.

Once the group formed, I'll see at DebConf how to upload in the 
appropriate dir on alioth, so that we upload and maintain together. 
ksamak and I, from Hypra, had feedbacks for users, we'd like to ship 
them in the regular Debian bug tracking system.

Here's the project URL:
https://alioth.debian.org/projects/compiz/

Thanks very much to Samuel for creating.

We requested for a svn repo, it should be enough. If you prefer git, 
tell us quickly.

Regards,

-- 

Jean-Philippe MENGUAL

HYPRA, progressons ensemble

Tél.: 01 84 73 06 61
Mail:contact@hypra.fr

Site Web:http://hypra.fr

Message #175 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <texou@accelibreinfo.eu>

To: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>, 722451@bugs.debian.org, Debian Accessibility Team <debian-accessibility@lists.debian.org>

Subject: Re: Bug#722451: Creating Compiz group

Date: Thu, 30 Jul 2015 01:49:26 +0200

Oops actually Samuel created a git repo and svn one, that was an 
excellent idea. I think you'll prefer git. Furthermore, if you want a 
mailing list, tell us, we can create it.



Regards,

Le 30/07/2015 01:28, MENGUAL Jean-Philippe a écrit :
> Hi,
>
> Actually I hoped submitting the package to a11y team could speed up 
> the upload, but lack of time prevents this. So as requested by 
> Stephen, we've just created a Compiz packaging team, so that:
> 1. Ubuntu, Knoppix and Debian have a synchronized packaging policy of 
> this package
> 2. Upstream devs and package maintainers can dialog
>
> Don't hesitate to join the group. Were subscribed now ksamak, Stephen, 
> Samuel, Luke, and Klaus. And any interested dev is 9elcome.
>
> Once the group formed, I'll see at DebConf how to upload in the 
> appropriate dir on alioth, so that we upload and maintain together. 
> ksamak and I, from Hypra, had feedbacks for users, we'd like to ship 
> them in the regular Debian bug tracking system.
>
> Here's the project URL:
> https://alioth.debian.org/projects/compiz/
>
> Thanks very much to Samuel for creating.
>
> We requested for a svn repo, it should be enough. If you prefer git, 
> tell us quickly.
>
> Regards,
>


-- 
Jean-Philippe MENGUAL

HYPRA, progressons ensemble

Tél.: 01 84 73 06 61

Mail: contact@hypra.fr

Site Web: http://hypra.fr

Message #180 received at 722451@bugs.debian.org (full text, mbox, reply):

From: "Prof. Dipl.-Ing. Klaus Knopper" <accessibility@knopper.net>

To: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>

Cc: 722451@bugs.debian.org, Debian Accessibility Team <debian-accessibility@lists.debian.org>

Subject: Re: Creating Compiz group

Date: Thu, 30 Jul 2015 09:05:16 +0200

Hello Mengual,

On Thu, Jul 30, 2015 at 01:28:22AM +0200, MENGUAL Jean-Philippe wrote:
> Hi,
> 
> Actually I hoped submitting the package to a11y team could speed up the
> upload, but lack of time prevents this. So as requested by Stephen, we've
> just created a Compiz packaging team, so that:
> 1. Ubuntu, Knoppix and Debian have a synchronized packaging policy of this
> package
> 2. Upstream devs and package maintainers can dialog

While pulling compiz regularly from upstream
http://bazaar.launchpad.net/~compiz-team/compiz/0.9.12/ , I still have a
few lines of local patches concerning the default configuration and
build dependencies for Debian, plus a bugfix for mouse cursor visibility
which hasn't made it into the official repository yet, so I'll likely
continue to build my own packages for Knoppix, but I'm very happy to
know that compiz makes it back into the Debian mainline. :-)

> Don't hesitate to join the group. Were subscribed now ksamak, Stephen,
> Samuel, Luke, and Klaus. And any interested dev is 9elcome.

Thanks, I'm glad I'm in automatically. :-)

> Once the group formed, I'll see at DebConf how to upload in the appropriate
> dir on alioth, so that we upload and maintain together. ksamak and I, from
> Hypra, had feedbacks for users, we'd like to ship them in the regular Debian
> bug tracking system.
> 
> Here's the project URL:
> https://alioth.debian.org/projects/compiz/

At which level is this kept in sync with the launchpad repository?

> Thanks very much to Samuel for creating.
> 
> We requested for a svn repo, it should be enough. If you prefer git, tell us
> quickly.

Svn is OK for me.

Regards
-Klaus

Message #185 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Ksamak <ksamak@riseup.net>

To: "Prof. Dipl.-Ing. Klaus Knopper" <accessibility@knopper.net>, 722451@bugs.debian.org

Cc: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>, Debian Accessibility Team <debian-accessibility@lists.debian.org>

Subject: Re: Bug#722451: Creating Compiz group

Date: Thu, 30 Jul 2015 14:04:45 +0530

[Message part 1 (text/plain, inline)]

On Thu, Jul 30, 2015 at 09:05:16AM +0200, Prof. Dipl.-Ing. Klaus Knopper wrote:
> Hello Mengual,
> 
> On Thu, Jul 30, 2015 at 01:28:22AM +0200, MENGUAL Jean-Philippe wrote:
> While pulling compiz regularly from upstream
> http://bazaar.launchpad.net/~compiz-team/compiz/0.9.12/ , I still have a
> few lines of local patches concerning the default configuration and
> build dependencies for Debian, plus a bugfix for mouse cursor visibility
> which hasn't made it into the official repository yet, so I'll likely
> continue to build my own packages for Knoppix, but I'm very happy to
> know that compiz makes it back into the Debian mainline. :-)
Nice to know there's a little more work to merge, especially on mouse
things, we'll try to work on that too.
> 
> At which level is this kept in sync with the launchpad repository?
We're currently trying to (re)filter out the ubuntu deps from they
modifs on version 0.9.12.1+15.10.20150627.1-0ubuntu1, and make debian
version 0.9.12.1 . Shouldn't be too long now, depending on other prios.
> 
> > Thanks very much to Samuel for creating.
yep, that too, thx.

> Svn is OK for me.
I'd prefer git.

-- 
Ksamak
hypra.fr Team

[signature.asc (application/pgp-signature, inline)]

Message #190 received at 722451@bugs.debian.org (full text, mbox, reply):

From: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>

To: "Prof. Dipl.-Ing. Klaus Knopper" <accessibility@knopper.net>

Cc: 722451@bugs.debian.org, Debian Accessibility Team <debian-accessibility@lists.debian.org>

Subject: Re: Creating Compiz group

Date: Thu, 30 Jul 2015 09:23:11 +0200

Hi,

While pulling compiz regularly from upstream 
http://bazaar.launchpad.net/~compiz-team/compiz/0.9.12/ , I still have a 
few lines of local patches concerning the default configuration and 
build dependencies for Debian, plus a bugfix for mouse cursor visibility 
which hasn't made it into the official repository yet, so I'll likely 
continue to build my own packages for Knoppix, but I'm very happy to 
know that compiz makes it back into the Debian mainline. :-)

ok yo'll do as you prefer. But I'm sure Your package and Ours, i.e.

git+ssh://ksamak-guest@git.debian.org/git/pkg-a11y/compiz.git


have large common points and they should be the Debian paakages. So if 
xou don't want to "upload" your work in Debian repo, the idea with this 
group is:
- Ubuntu has treir package, as well as upstream
- you pull in your branch ubuntu and apply your patches.
- We (Debian+Hypra) sznchronize your branch with HEAD to upload to 
Debian with your satches, our patches, etc. (that Ubuntu and upstream 
can use ii they like).

Of course, it'd be still greater if you would want to upload your 
patches directly in HEAD of the new project, so that we upload directly 
without synchronizing 2 branches HEAD and yours.

But well, it's to respect any policy that this project was created, so 
that any existing project has its branch but sync is easier (as sync 
between branches instead of repo).

Regards,

Message #201 received at 722451@bugs.debian.org (full text, mbox, reply):

From: williamsharry <fernandoorozocrojas@gmail.com>

To: undisclosed-recipients:;

Subject: Dear Friend

Date: Tue, 10 May 2016 14:01:26 +0000

Dear Friend
I have been expecting to hear from you based on my first message to
you, or didn't you receive my first message that I sent to you?
If not reply back to me immediately its urgent
Thanks

Message #241 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Harley Cascante <h.cascante@outlook.com>

To: "722451@bugs.debian.org" <722451@bugs.debian.org>

Subject: Compiz team/package status.

Date: Wed, 2 Nov 2016 08:42:36 +0000

[Message part 1 (text/plain, inline)]

Guys, I'm a compiz "mere mortal" user, but I'd like to know what is the status of this project.
Have your team been actively working on it lately? (late 2016).
Any news on bringing compiz back to Debian's official repos?
Thank you very much for your work and interest.
I'd gladly help testing *basic* things if that helps speed the inclusion of the package or anything (I've got little to no programming skills sorry).

Sent from my Windows Phone

[Message part 2 (text/html, inline)]

Message #246 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Jean-Philippe MENGUAL <jpmengual@hypra.fr>

To: Harley Cascante <h.cascante@outlook.com>, 722451@bugs.debian.org, Cyril Brulebois <cyril@debamax.com>

Subject: Re: Bug#722451: Compiz team/package status.

Date: Wed, 2 Nov 2016 22:05:29 +0100

Hi,

1. Compiz in Debian

Yes, latest Compiz from Canonical will be in Debian 9. Upload is coming
soon, Hypra paid for a Debian dev to do it. We choosed Compiz from
Canonical because it's tested and mainstream. We don't use
Compiz-reloaded (0.8), as so few users, plugins, etc.

So yes, upload comes very soon (this month).

2. Compiz status

1st, be aware that the 1st upload will likely not work with Gnome 3.22.
Usable with MATE and other desktops, but not Gnome. Patches come.

Next, note that Canonical just maintains bugfixes now. It means that
bugs like Gnome compatibility will be fixed, but this package is about
dying for them (about 5 years). However, Hypra uses it with MATE for
low-vision features. Then, Hypra will probably be the next biggest
Compiz contributor through all features we plan. But of course, we'll
love to be helped by community and to see this project a;ive. So far, we
do pull request for Canonical and it's fine.

Best regards,


Le 02/11/2016 à 09:42, Harley Cascante a écrit :
> Guys, I'm a compiz "mere mortal" user, but I'd like to know what is the
> status of this project.
> Have your team been actively working on it lately? (late 2016).
> Any news on bringing compiz back to Debian's official repos?
> Thank you very much for your work and interest.
> I'd gladly help testing *basic* things if that helps speed the inclusion
> of the package or anything (I've got little to no programming skills sorry).
> 
> Sent from my Windows Phone

-- 
Jean-Philippe MENGUAL

HYPRA, progressons ensemble

Tél.: 01 84 73 06 61

Mail: contact@hypra.fr

Site Web: http://hypra.fr

Message #251 received at 722451@bugs.debian.org (full text, mbox, reply):

From: Cyril Brulebois <cyril@debamax.com>

To: Jean-Philippe MENGUAL <jpmengual@hypra.fr>

Cc: Harley Cascante <h.cascante@outlook.com>, 722451@bugs.debian.org

Subject: Re: Bug#722451: Compiz team/package status.

Date: Fri, 4 Nov 2016 02:15:18 +0100

[Message part 1 (text/plain, inline)]

Control: tag -1 pending

Jean-Philippe MENGUAL <jpmengual@hypra.fr> (2016-11-02):
> 1. Compiz in Debian
> 
> Yes, latest Compiz from Canonical will be in Debian 9. Upload is
> coming soon, Hypra paid for a Debian dev to do it. We choosed Compiz
> from Canonical because it's tested and mainstream. We don't use
> Compiz-reloaded (0.8), as so few users, plugins, etc.
> 
> So yes, upload comes very soon (this month).

There we go (see below). Of course it's going to land in NEW, and will
need ftpmasters to review the packaging. Maybe we'll need a few rounds
of uploads, we'll see.

Uploading to ftp-master (via ftp to ftp.upload.debian.org):
  Uploading compiz_0.9.13.0+16.10.20160818.2-1.dsc: done.
  Uploading compiz_0.9.13.0+16.10.20160818.2.orig.tar.gz: done.
  Uploading compiz_0.9.13.0+16.10.20160818.2-1.diff.gz: done.
  Uploading compiz-core-dbgsym_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-core_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-dev_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-gnome-dbgsym_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-gnome_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-mate_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-plugins-dbgsym_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-plugins-default-dbgsym_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-plugins-default_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz-plugins-extra_0.9.13.0+16.10.20160818.2-1_all.deb: done.
  Uploading compiz-plugins-main-default_0.9.13.0+16.10.20160818.2-1_all.deb: done.
  Uploading compiz-plugins-main-dev_0.9.13.0+16.10.20160818.2-1_all.deb: done.
  Uploading compiz-plugins-main_0.9.13.0+16.10.20160818.2-1_all.deb: done.
  Uploading compiz-plugins_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz_0.9.13.0+16.10.20160818.2-1_all.deb: done.
  Uploading compizconfig-settings-manager_0.9.13.0+16.10.20160818.2-1_all.deb: done.
  Uploading libcompizconfig0-dbgsym_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading libcompizconfig0-dev_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading libcompizconfig0_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading libdecoration0-dbgsym_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading libdecoration0-dev_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading libdecoration0_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading python-compizconfig-dbgsym_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading python-compizconfig_0.9.13.0+16.10.20160818.2-1_amd64.deb: done.
  Uploading compiz_0.9.13.0+16.10.20160818.2-1_amd64.changes: done.
Successfully uploaded packages.


A bit more info:
  https://compiz.alioth.debian.org/


Cheers,
Cyril.
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

[signature.asc (application/pgp-signature, inline)]

Message #258 received at 722451-done@bugs.debian.org (full text, mbox, reply):

From: Cyril Brulebois <cyril@debamax.com>

To: Jean-Philippe MENGUAL <jpmengual@hypra.fr>

Cc: Harley Cascante <h.cascante@outlook.com>, 722451-done@bugs.debian.org

Subject: Re: Bug#722451: Compiz team/package status.

Date: Mon, 19 Dec 2016 02:51:18 +0100

[Message part 1 (text/plain, inline)]

Hi,

Cyril Brulebois <cyril@debamax.com> (2016-11-04):
> There we go (see below). Of course it's going to land in NEW, and will
> need ftpmasters to review the packaging. Maybe we'll need a few rounds
> of uploads, we'll see.
> 
> Uploading to ftp-master (via ftp to ftp.upload.debian.org):
[…]
> Successfully uploaded packages.
> 
> 
> A bit more info:
>   https://compiz.alioth.debian.org/

A quick update: this first upload got automatically rejected because of
differences in Debian & Ubuntu multi-arch implementations. A re-upload
as -2, without multi-arch bits, was accepted by ftpmaster:
  https://tracker.debian.org/news/824674

even if an RC bug was filed right away so that the copyright file would
receive an update before the package is allowed in testing:
  https://bugs.debian.org/848545

I think I've addressed most if not all copyright issues with the recent
-3 upload:
  https://tracker.debian.org/news/824918

The package also FTBFS on armel/armhf, which I filed for reference as:
  https://bugs.debian.org/848617


There's still work to be done, but compiz is now back in unstable, which
should be a nice first step for a wider adoption as an accessibility
tool; thanks should go to the Hypra company who funded my work in this
area.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.