Comment 0 for bug 1912792

[impact]

the (trivial) autopkgtest for this package always fails, since some change in upstream autodep8, dctrl-tools, or autopkgtest code that has changed the import module name used.

The problem is the autodep8-generated test used to correctly calculate the module name to import as "oslo_versionedobjects", but now incorrectly calculates it as "oslo.versionedobjects". This is likely due to the autodep8 test generation script changing all '-' chars to '_', but not '.' to '_'. With python2, this package created a (dummy) binary package named python-oslo-versionedobjects, while with python3 it provides only python3-oslo.versionedobjects.

[test case]

check the autopkgtests, e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/p/python-oslo.versionedobjects/20210113_184523_626c0@/log.gz

[regression potential]

any regression would almost certainly be limited to failing to run the autodep8 test, or an incorrect pass or incorrect fail of the autodep8 test.

[scope]

This was detected and fixed starting in cosmic with this version:
http://launchpadlibrarian.net/375048921/python-oslo.versionedobjects_1.33.1-0ubuntu1_1.33.1-0ubuntu2.diff.gz

This fix was not backported to bionic or earlier.

[other info]

as this is a trivial autopkgtest fix, I'll add block-proposed-bionic, and really this bug probably doesn't even need a fix uploaded, as this package's tests haven't been run for bionic in 2 years, so it should be enough to just point to this bug as explanation for why to ignore this package's failing autopkgtests on bionic.