Pyramid
Updated 3 Days AgoPublic

This operation is about replacing dh with dhmk and bumping our debhelper compat level to 11 following Debian.

Debian dhmk -> dh move

Debian replaced dhmk with dh, see:

Side effects of this change in Kubuntu

Because of our customized pkg-kde-tools/dhmk we have something like this in each and every of our build logs:

=== Start list-missing
<missing files list here, if any>
=== End list-missing
dpkg-genchanges > ../.pkg-kde-lintian.changes
dpkg-genchanges: info: including full source code in upload
=== Start lintian
<lintian warnings here, if any>
=== End lintian

Our packaging status reports (generated by ppa-build-status and tritemio-build-status) and our CI expect those markers to do their job, therefore if we do the dhmk -> dh move right now we may cause some malfunctioning in our information tools, example:

We could also get other unexpected side effects; for instance baloo is failing its autopkgtests only when built with dh and debhelper compat level 11.

Short term plan

The general idea is moving away from dhmk to not have an excessive delta with other distributions. In order to avoid inminent problems and buy some time to figure out a proper solution, we decided to not move away from dhmk yet, keeping this partcular change out of our Debian merges for now.

We also decided to keep the debhelper compat level to 9 along with dhmk usage and we would switch to 11 once we have ported our rules files to dh. Why? Because, as we can see in the mails linked above, dhmk is no longer properly maintained, therefore switching to compat level 11 might trigger some dhmk malfunctioning.

Possible long term solutions (WIP)

TODO: Explain

Related workboard tasks

Last Author
joselema
Projects
None
Subscribers
None