Control: tag -1 + patch On Thu, Apr 02, 2020 at 09:27:29PM +0200, Paul Gevers wrote: > Source: facter > Version: 3.11.0-3 > Severity: serious > Tags: sid bullseye > User: debian...@lists.debian.org > Usertags: needs-update > Control: affects -1 src:ruby-defaults > > [X-Debbugs-CC: debian...@lists.debian.org, > ruby-defau...@packages.debian.org] > > Dear maintainer(s), > > With a recent upload of ruby-defaults the autopkgtest of facter fails in > testing when that autopkgtest is run with the binary packages of > ruby-defaults from unstable. It passes when run with only packages from > testing. In tabular form: > > pass fail > ruby-defaults from testing 1:2.7 > facter from testing 3.11.0-3 > all others from testing from testing > > I copied some of the output at the bottom of this report. I think the > only issue that the autopkgtest is showing is that you're using a > deprecated method. If you can't fix the code on the short term (best) or > run the test suite without emitting warnings (a good thing to do > anyways, autopkgtest isn't meant to catch those), please consider adding > the allow-stderr restriction for the time being. > > Currently this regression is blocking the migration of ruby-defaults to > testing [1]. Of course, ruby-defaults shouldn't just break your > autopkgtest (or even worse, your package), but it seems to me that the > change in ruby-defaults was intended and your package needs to update to > the new situation. > > If this is a real problem in your package (and not only in your > autopkgtest), the right binary package(s) from ruby-defaults should > really add a versioned Breaks on the unfixed version of (one of your) > package(s). Note: the Breaks is nice even if the issue is only in the > autopkgtest as it helps the migration software to figure out the right > versions to combine in the tests. > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=ruby-defaults > > https://ci.debian.net/data/autopkgtest/testing/amd64/f/facter/4775724/log.gz > > autopkgtest [07:14:35]: test puppet: - - - - - - - - - - results - - - > - - - - - - - > puppet FAIL stderr: > /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is > obsolete
Dear maintainer(s), Please apply the attached patch.
From 479d32ff543cf5a1215f214302566740876c663e Mon Sep 17 00:00:00 2001 From: Antonio Terceiro <terce...@debian.org> Date: Fri, 3 Apr 2020 09:42:31 -0300 Subject: [PATCH] autopkgtest: ignore output on stderr This makes the autopkgtest less fragile as otherwise it will fail if e.g. any dependency generates a Ruby warning. This is specially annoying when handling migrations of the Ruby interpreter. Closes: #955582 --- debian/tests/control | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/tests/control b/debian/tests/control index 4bfefb12..5c181550 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -3,7 +3,9 @@ Restrictions: allow-stderr Depends: @ Tests: ruby +Restrictions: allow-stderr Depends: facter, ruby Tests: puppet +Restrictions: allow-stderr Depends: facter, puppet -- 2.26.0
signature.asc
Description: PGP signature
