Re: [MoM] PythonQt

Hi Fernando,

Am Mon, Aug 17, 2026 at 12:20:43PM +0200 schrieb Fernando Hueso González:
> Thanks a lot Andreas for the revamp and guidance.

Sorry for my late reply - I'm basically offline + badly connected this
week.

> I also checked the copyright file, and it seems fully up-to-date.

Good!
 
> I just updated the changelog using the gbp dch command you suggested
> earlier.

I migt check tomorrow.
 
> Question about your recent commits:
> https://salsa.debian.org/python-team/packages/pythonqt/-/commit/c2253faca8310c9ede060b46eb61e0ecfb7ff7ac
> Why is the syntax sometimes "-- Name " and sometimes "[Name]" ?

""-- Name " is part of the d/changelog syntax and marks the changelog
owner (= the person who signs responsible for this package version).
"[Name]" is just free text and helps the reader to know who worked on
this package version.  If only the changelog owner worked on the package
you leave it out.
 
> https://salsa.debian.org/python-team/packages/pythonqt/-/commit/e715afffd5a9a18be607a7fa69bb32a2cb09865d
> Why is the repository pointing to sourceforge rather than GitHub ? (first
> and last lines), inbetween is ok

Not checked due to limited bandwidth.  Please assume I might make mistakes.
If Github is the recent one just use this and fix my mistake.
 
> > Please inspect the patches in debian/patches.  I deactivated these all
> > by renaming series to _series.  Please inspect every single one whether
> > it can be removed or should be adapted.  I did not looked at these files
> > at all!
> I just checked, and none of these are need anymore! They were either merged
> to upstream or are no longer needed with Qt6 and Python3.
> > The package now needs adaption from Qt5 to Qt6 (does not build as is).
> 
> I did the proper changes: the CI now builds the package correctly with CMake
> and Qt6.

I'll check later.

> However, it fails at the install step, saying it cannot find libPythonQt.so.
> 
> In a local build on Ubuntu 26, the install step via make install spits out
> the following:
> 
> Install the project...
> -- Install configuration: "Release"
> -- Installing: /usr/local/lib/libPythonQt.so
> -- Installing: /usr/local/include/PythonQt/PythonQtBoolResult.h
> -- Installing: /usr/local/include/PythonQt/PythonQtClassInfo.h

> -- Installing: /usr/local/include/PythonQt/PythonQtUtils.h
> -- Installing: /usr/local/include/PythonQt/PythonQtVariants.h
> -- Installing: /usr/local/include/PythonQt/PythonQtPythonInclude.h
> -- Installing: /usr/local/include/PythonQt/PythonQtConfigure.h
> -- Installing: /usr/local/lib/libPythonQt_QtAll.so
> -- Set non-toolchain portion of runtime path of "/usr/local/lib/libPythonQt_QtAll.so" to ""
> -- Installing: /usr/local/include/PythonQt/PythonQt_QtAll.h
> 
> In the repo, the libpythonqt-dev contains:
> 
> lib/libPythonQt*.so usr/lib/
> 
> Do you think that the problem is that the default install path is /usr/local
> rather than lib? Or maybe the CI is not calling "make install" correctly
> since I don't see it in the build logs of the pipeline?

Sounds like a sensible explanation for the issue - can't check right now.
 
> Looking at CTK, I see though a different structure in debian/rules, that has
> a custom:
> 
> # Runtime Package
> dh_install -p$(pkg_run) usr/lib/*.so.*
> # Development Package
> dh_install -p$(pkg_dev) usr/include
> dh_install -p$(pkg_dev) usr/lib/lib*.so
> 
> that is not present in PythonQt, but I am not sure if this was something
> specific to CTK because of the libctk0.1 suffixes.
> 
> 
> Another question, when running lintian, I got:
> 
> /Cannot find a changes file for pythonqt/4.1.0-1. It would be named like:
>     pythonqt_4.1.0-1_amd64.changes
>     pythonqt_4.1.0-1_multi.changes
>     pythonqt_4.1.0-1_all.changes
>     pythonqt_4.1.0-1_source.changes/
> 
> Here, I do not understand if any action is required.
> 
> Side note: I cannot seem to run lintian-brush or routine-update on my
> Ubuntu26, couldn't figure out what package does that.

Both are commands are in the packages with the same name in Debian
unstable.

> Best regards, Fernando.

Sorry for the short reply - will be more verbosely later.

Kind regards
     Andreas.