Package: dh-debputy
Followup-For: Bug #1121339

Happy new year.
Thanks for merging.
I have rebased and pushed some work that I was preparing to the
bug-1121339-built-using branch.

> I also added a minor tweak to the migration code such that it
> detects `dh-builtusing` patterns and emits a warning about having to
> migrate the manually. Ideally, that migration would be automated but
> the migration infrastructure does not support patching
> `debian/control` yet, so that was a "better than nothing" fix.

It may be better that way.  Some (mostly deprecated) stuff in
dh-builtusing would be hard to translate automatically anyway.

> I tweaked the logging so it now uses the exact path to the pattern
> in the manifest when logging (such as
> `packages.NAME.built-using[0].sources`)

The hash key is 'sources-for', not 'sources'.  Moreover, I have used
the parent 'packages.NAME.built-using[0]' when the reported issue is
not caused by the glob.

> I tweaked the tests to skip running the metadata detector when the
>  package is not active. I am happy to accept patches or merge
>  requests for additional tests to cover anything you might feel
>  would be lost by this change.

No problem. I have completely removed these tests, which were copied
from dh-sequence-builtusing but make little sense here.

Reply via email to