On 01/23/2012 06:07 PM, Guido Günther wrote: > I can't seem to reproduct this in a clean amd64 sid chroot. Are you > still seeing this?
Hm, this is still reproducible for me in an up-to-date sid i386 system
that i've been keeping updated for several months now.
But i made a fresh chroot on the same machine, and did nothing in it but:
apt-get install build-essential fakeroot
apt-get build-dep gtk-vnc
and then tried to rebuild gtk-vnc 0.5.0-2, and it built cleanly.
So something is amiss in the regularly-upgraded build environment, but
i'm not sure what it is, or how or why it breaks the build for gtk-vnc.
Since i have a reproducible test case, i'm happy to investigate it
further, but i don't know what i should be looking for. I've compared
the files are different between the two in /etc/, but see nothing
relevant there. But there are many more packages installed in the
normal sid system than in the chroot, and i am not sure if any of them
(or the config files they supply) are the cause of the problem. If
that's the root of the problem, i suspect gtk-vnc is missing a
Build-Conflicts: or something.
Any ideas what i should check or look for?
--dkg
signature.asc
Description: OpenPGP digital signature
