New release + doc-base

This never actually made it to archive. Needs experimental to build though.

+------------------------------------------------------------------------------+
| Summary                                                                      |
+------------------------------------------------------------------------------+

Build Architecture: amd64
Build Type: binary
Build-Space: 525616
Build-Time: 208
Distribution: unstable
Host Architecture: amd64
Install-Time: 715
Job: /media/scarlett/Work/debian-new/forks-for-merges/build/qtscxml-everywhere-src_5.12.2-1.dsc
Lintian: info
Machine Architecture: amd64
Package: qtscxml-everywhere-src
Package-Time: 1479
Piuparts: pass
Source-Version: 5.12.2-1
Space: 525616
Status: successful
Version: 5.12.2-1
--------------------------------------------------------------------------------
Finished at 2019-04-12T14:04:41Z
Build needed 00:24:39, 525616k disk space

These are the remaining lintian -

I: qtscxml-everywhere-src source: testsuite-autopkgtest-missing

This seems common with all qt modules I have seen ( tests in rules )

I: qtscxml5-doc-html: file-references-package-build-path usr/share/qt5/doc/qtscxml/qtscxml.index
N: 
N:    The listed file or maintainer script appears to reference the build path
N:    used to build the package as specified in the Build-Path field of the
N:    .buildinfo file.
N:    
N:    This is likely to cause the package to be unreproducible, but it may
N:    also indicate that the package will not work correctly outside of the
N:    maintainer's own system.
N:    
N:    Please note that this tag will not appear unless the .buildinfo file
N:    contains a Build-Path field. That field is optional. You may have to set
N:    DEB_BUILD_OPTIONS=buildinfo=+path or use
N:    --buildinfo-option=--always-include-path with dpkg-buildpackage when
N:    building.
N:    
N:    Refer to https://reproducible-builds.org/,
N:    https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, and the
N:    dpkg-genbuildinfo(1) manual page for details.
N:    
N:    Severity: wishlist, Certainty: possible
N:    
N:    Check: files, Type: binary, udeb

This is important as I see it, when a user trys to use this doc it has wrong paths. I have tried many things and google is failing me on how to resolve this. Any ideas?