aptly: Capture the output of the publisher’s subprocess

If we just die, the output is not actually captured by the calling
subroutine. We need to explicitly capture and bubble it up.

Use tee_merged instead of capture_merged to ensure the output is
captured in the logs immediately. The downside is that in case of
an error the output is logged twice.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

src/backend/bs_publish

@@ -2736,7 +2736,12 @@ sub publish {
   if ($repotype{'debian'}) {
     my $aptly_config = BSAptly::aptly_repo_get_config($projid, $repoid);
     if ($aptly_config) {
-	BSAptly::aptly_update_repo($projid, $repoid, $aptly_config, $extrep) or die;
+        my ($outerr, $result) = tee_merged {
+            return scalar BSAptly::aptly_update_repo($projid, $repoid, $aptly_config, $extrep);
+        };
+        if (!$result) {
+            die $outerr;
+        }
     } elsif ($BSConfig::reprepository && $BSConfig::reprepository->{$prp}) {
 	updaterepo_reprepro($prp, $extrep, @changed);
     } else {