13:04 <sil2100> The only problem I see so far is with the versioning
13:05 <sil2100> Currently the train does not support dual-landing with two different versioning schemes
13:06 <sil2100> And when building for instance dbus-cpp with your script, the package version for both xenial and vivid will be 5.0.0, but the contents inside will have 4.3.0 for vivid and 5.0.0 for xenial
13:06 <sil2100> Meaning that the package version is lying and trying to tell vivid-overlay users that it's shipping a different version
Sadly, I'm not sure if this could be done from override_dh_auto_clean as the rest. For now the only idea I have is to support such cases in the CI Train, but that's just my first guess.
13:04 <sil2100> The only problem I see so far is with the versioning
versioning schemes
version for both xenial and vivid will be 5.0.0, but the contents inside
will have 4.3.0 for vivid and 5.0.0 for xenial
vivid- overlay users that it's shipping a different version
13:05 <sil2100> Currently the train does not support dual-landing with two different
13:06 <sil2100> And when building for instance dbus-cpp with your script, the package
13:06 <sil2100> Meaning that the package version is lying and trying to tell
Sadly, I'm not sure if this could be done from override_ dh_auto_ clean as the rest. For now the only idea I have is to support such cases in the CI Train, but that's just my first guess.