Please add DEP3 Origin which would help a lot to understand the patch.
I did that a couple of days ago, let me know if I am missing some extra
field:
https://salsa.debian.org/python-team/packages/pythonqt/-/commit/67190c86593ae462e38d9a64d51d6fd9c7749cfe
BTW, you unintentionally commited a change of the upstream source since
you probably forgot `quilt pop -a` before `git commit`. This happens
from time to time to everyone. ;-) Just a hint to verify this for the
future.
Oops, indeed, sorry for the mess and thanks for the revert.
It seems the CI pipeline failed due to a 403 error, is there a way to
restart it?
Another commit I reverted was the probably unintended change of your
email address in d/changelog. Please make sure it is identically to the
address in the Uploaders field of d/control. If you run lintian on your
build result it considers your work a NMU if its not identically. This
is how I spotted the issue.
Ok, understood.
Hmmm, sounds convincing in principle but I'm not observing this in my
build. Can you please check again?
Maybe I misunderstood what the multiarch means. I thought that you meant
that the library should end up in /usr/lib/x86_64-linux-gnu/ rather than
in /usr/lib, which is what changed in my local build when I moved to
dh_auto_configure.
It would be great if I could reproduce the Multiarch install which is
not visible in my pbuilder-build.
Can you tell me what output would you expect? Meaning different folders
for each arch, or different suffixes for each arch but all in same
folder? That way I can understand better what to change on the CMake side.
If it's just different folders, could you try
adding -DCMAKE_INSTALL_LIBDIR=lib/$(DEB_HOST_MULTIARCH) to the
auto_configure postfix flags and see if that changes anything in your
pbuilder-build?
BTW, I'm in contact with Mechtilde from DFSG team about the ctk package.
She told me there is a licensing issue we need to discuss. We'll meet
here at MiniDebConf Winterthur face to face later today.
Great, thanks a lot!
Fernando.
