Bug#901164: caja-eiciel FTCBFS: configure.ac hard codes build architecture pkg-config

[Alex ARNAUD]

It seems there are confusions. My response below.

Le 03/07/2018 à 16:40, Helmut Grohne a écrit :
> On Tue, Jul 03, 2018 at 11:50:04AM +0200, Alex ARNAUD wrote:
>> If it's an upstream issue, could you report and submit your patch upstream?
>> Upstream is here:https://github.com/darkshram/mate-eiciel
> 
> I think you mean https://github.com/rofirrim/eiciel.

The Github link here is not for Caja but for Nautilus. Here we're 
talking about Caja only. So https://github.com/darkshram/mate-eiciel is 
the right place for us.

On Debian, there are two packages: eiciel and caja-eiciel

What file manager are you using? Caja or Nautilus?

> packaged a fork and thus you should register your code copy. See
> https://wiki.debian.org/EmbeddedCodeCopies for details. By forking
> upstreams, you are copying bugs (like this one). That is why the Debian
> policy discourages forking or packaging forks. I've clone bug -2 for
> dealing with the code copy.

I'm neither the upstream maintainer nor the initial author of the package.

Are you able to use eiciel with Caja? If not, I assume it's why there is 
a fork.

> Once eiciel has fixed this, I hope that it trickles down via the
> mate-eiciel git repository into Debian.

I hope so :).

Best regards,
Alex.