TEMPORARILY accept test with duplicate output

cabal-testsuite/PackageTests/Backpack/Includes2/setup-internal-fail.cabal.out

@@ -12,5 +12,6 @@ Error:
                            brought into scope by mixins: fail:mysql (Database.MySQL as Database)
                         or 'fail-0.1.0.0-postgresql:Database.PostgreSQL'
                            brought into scope by mixins: fail:postgresql (Database.PostgreSQL as Database)
-      While filling requirements of build-depends: fail:mylib
+      While filling requirements of     build-depends: fail:mylib
+                                    and build-depends: fail:mylib
     In the stanza library

cabal-testsuite/PackageTests/Backpack/Includes2/setup-internal-fail.out

@@ -11,5 +11,6 @@ Error:
                            brought into scope by mixins: fail:mysql (Database.MySQL as Database)
                         or 'fail-0.1.0.0-postgresql:Database.PostgreSQL'
                            brought into scope by mixins: fail:postgresql (Database.PostgreSQL as Database)
-      While filling requirements of build-depends: fail:mylib
+      While filling requirements of     build-depends: fail:mylib
+                                    and build-depends: fail:mylib
     In the stanza library

cabal-testsuite/PackageTests/ReexportedModules/setup-fail-ambiguous.cabal.out

@@ -17,6 +17,10 @@ Error:
         It could refer to either:
              'containers-<VERSION>:Data.Map'
              brought into scope by build-depends: containers
+          or 'containers-<VERSION>:Data.Map'
+             brought into scope by build-depends: containers
+          or 'containers-dupe-0.1.0.0:Data.Map'
+             brought into scope by build-depends: containers-dupe
           or 'containers-dupe-0.1.0.0:Data.Map'
              brought into scope by build-depends: containers-dupe
         The ambiguity can be resolved by qualifying the

cabal-testsuite/PackageTests/ReexportedModules/setup-fail-ambiguous.out

@@ -15,6 +15,10 @@ Error:
         It could refer to either:
              'containers-<VERSION>:Data.Map'
              brought into scope by build-depends: containers
+          or 'containers-<VERSION>:Data.Map'
+             brought into scope by build-depends: containers
+          or 'containers-dupe-0.1.0.0:Data.Map'
+             brought into scope by build-depends: containers-dupe
           or 'containers-dupe-0.1.0.0:Data.Map'
              brought into scope by build-depends: containers-dupe
         The ambiguity can be resolved by qualifying the