Your message dated Mon, 26 Aug 2019 13:39:26 +0000 with message-id <20190826133926.GC1563@debian> and subject line has caused the Debian Bug report #919815, regarding ruby-sanitize: autopkgtest needs update for new version of ruby-nokogiri to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-sanitize Version: 4.6.6-1 User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-nokogiri [X-Debbugs-CC: debian...@lists.debian.org, ruby-nokog...@packages.debian.org] Dear maintainers, With a recent upload of ruby-nokogiri the autopkgtest of ruby-sanitize fails in testing when that autopkgtest is run with the binary packages of ruby-nokogiri from unstable. It passes when run with only packages from testing. In tabular form: pass fail ruby-nokogiri from testing 1.10.0+dfsg1-1 ruby-sanitize from testing 4.6.6-1 all others from testing from testing I copied some of the output at the bottom of this report. It seems you just need to update your reference. Currently this regression is blocking the migration of ruby-nokogiri to testing [1]. Of course, ruby-nokogiri shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-nokogiri was intended and your package needs to update to the new situation. If needed, please change the bug's severity. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-nokogiri 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 [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from ruby-nokogiri/1.10.0+dfsg1-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=ruby-nokogiri https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-sanitize/1734811/log.gz 1) Failure: Sanitize::Transformers::CleanElement::Basic config#test_0001_should not choke on valueless attributes [/tmp/autopkgtest-lxc.wmo9hlfm/downtmp/build.NYd/src/test/test_clean_element.rb:236]: --- expected +++ actual @@ -1 +1 @@ -"foo <a href rel=\"nofollow\">foo</a> bar" +"foo <a href=\"\" rel=\"nofollow\">foo</a> bar" 217 runs, 1467 assertions, 1 failures, 0 errors, 0 skipssignature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Control: fixed -1 4.6.6-2
--- End Message ---
_______________________________________________ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers