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. Rather than dealing with github's idiosyncrasies, I opt for Ccing the upstream author directly: Please always call pkg-config via $PKG_CONFIG to facilitate cross building. The relevant variable is set up by the PKG_PROG_PKG_CONFIG macro. eiciel's configure.ac contains one remaining direct pkg-config call. You can find a patch for fixing the very same issue in the mate-eiciel fork at https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=901164;filename=cross.patch;msg=5. Once eiciel has fixed this, I hope that it trickles down via the mate-eiciel git repository into Debian. Helmut
