Could it be that there is some config option that is still wreaking havoc after having been disabled.
The initial setup might have had amd64/i386 build architecture all enabled. I then disabled i386 to get something working quickly only to enable it again a couple of months later, this time with the build architecture all disabled for i386. On Thu, 20 Feb 2020 at 14:40, Marc Leeman <marc.lee...@gmail.com> wrote: > > I'm adding the daemon logfile, but other than the a fore mentioned issue, > I am not seeing something out of the ordinary. > > On Thu, 20 Feb 2020 at 14:19, Marc Leeman <marc.lee...@gmail.com> wrote: > >> >> So the good news is that it is not something general, ... >> >> No, I've checked it only for amd64 >> >> I also had exactly the same issue backporting 1.16.2 from sid :-/ >> >> >> >> [image: Screenshot from 2020-02-20 14-14-42.png] >> >> On Thu, 20 Feb 2020 at 14:01, Stephan Sürken <abs...@debian.org> wrote: >> >>> Hi Marc, >>> >>> On Wed, 2020-02-19 at 12:17 +0100, Marc Leeman wrote: >>> >>> (...) >>> >>> > older platforms) and amd64 (current). I've come accross the following >>> > while backporting GStreamer 1.14.4 from buster to stretch. >>> >>> just tried it here with no issues. >>> >>> Ftr, I did a portext to stretch with >>> >>> >>> https://deb.debian.org/debian/pool/main/g/gstreamer1.0/gstreamer1.0_1.14.4-1.dsc >>> >>> Could it be that in your stretch distribution, you have >>> >>> 'BUILD ARCHITECTURE ALL' >>> >>> checked for both, amd64 and i386? >>> >>> Hth! >>> >>> S >>> >>> >> >> -- >> g. Marc >> > > > -- > g. Marc > -- g. Marc
