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

[Mike Gabriel]

Hi Helmut,

On Tue, 3 Jul 2018 16:40:35 +0200 Helmut Grohne <helmut at subdivi.de> wrote:
 > Control: clone -1 -2
 > Control: retitle -2 register eiciel fork
 > Control: tags -2 =
 > Control: severity -2 important
 >
 > Hi Alex,
 >
 > 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. It seems you
 > 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.

Please note that caja-* packages are addons for the file browser caja 
(part of the MATE desktop).

The original application is for nautilus. It is not possible to use the 
addons cross-wise.

The projects that people derive from nautilus add-ons for caja are 
technically forks, but they are not two possible options for the same 
use case. They forks target being used in caja, whereas the originals 
are for nautilus.

So, what exactly do you mean by "register eiciel fork"???

Greets,
Mike