Package: glib2.0 Version: 2.53.7-1 sources: https://packages.debian.org/source/sid/glib2.0
Even the workaround "For a short-term work-around: Add the files to debian/not-installed" does not work. On Sun, Sep 10, 2017 at 12:05 PM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > Package: glib2.0 > Version: 2.53.7-1 > sources: https://packages.debian.org/source/sid/glib2.0 > > Your comments don't make sense to me: > - I don't see any error raised by ./configure > - if some packages conflicts with the build, they should appear during > the dpkg-checkbuilddeps process which I always perform before any debian > build; here, it quietly passes > - yet again, I don't see any reason why any build process should try to > install anything on the host outside of the build folder tree: this is a > comment regarding all the "libtool: warning: '../../glib/libglib-2.0.la' > has not been installed in '/usr/lib/x86_64-linux-gnu'" > - the final error messages state that "dh_missing: > usr/share/systemtap/tapset/libglib-2.0.so.0.5307.0.stp exists in > debian/install/udeb but is not installed to anywhere": of course, that's > why we are building this. > > My debhelper is 10.7.2. > > On Sat, Sep 9, 2017 at 10:01 PM, Michael Biebl <bi...@debian.org> wrote: > >> Am 09.09.2017 um 20:25 schrieb jean-christophe manciot: >> > Package: glib2.0 >> > Version: 2.53.6-1 >> > sources: https://packages.debian.org/source/sid/glib2.0 >> > >> > What do you precisely mean by tainted and how can I solve this? >> > >> >> You have additional packages installed which are auto-detected by >> ./configure. Building in a clean chroot should solve this. >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> > > > -- > Jean-Christophe > -- Jean-Christophe
