gpgv-win32 autopkgtest always fails

i'm marking for disco (as well as b/c where it fails) because i think it would be better to add the test back in and get it working, instead of just removing it

nothing in ubuntu uses gpgv-win32 it's added and used in debian to validate debian cds on windows and we don't care.

This is not a regression in any stable releases, failing tests is not a problem at all. As release and SRU processes only consider regressions (previously passed, now failing). Things that have always failed are treated as such by proposed-updates and the rest of the tooling ("always failed"). This is exactly the same as FTBFS - only regressions count, and we have many packages that have never built on certain arches.

SRU policy, Section 2 "When", has three major categories listing in bullet points cases that are eligible for SRU.

Which one is this SRU submitted under?

https://wiki.ubuntu.com/StableReleaseUpdates#When

An upload of gnupg2 to bionic-proposed has been rejected from the upload queue for the following reason: "fixing tests only does not fit the SRU policy".

An upload of gnupg2 to cosmic-proposed has been rejected from the upload queue for the following reason: "fixing tests only does not fit the SRU policy".

An upload of gnupg to xenial-proposed has been rejected from the upload queue for the following reason: "fixing tests only does not fit the SRU policy".

Hello Dan, or anyone else affected,

Accepted gnupg2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnupg2/2.2.4-1ubuntu1.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted gnupg2 (2.2.4-1ubuntu1.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

libgnupg-interface-perl/0.52-9 (ppc64el, amd64, armhf, i386, arm64, s390x)
paperkey/1.5-3 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#gnupg2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

I can see autopkgtest completing successfully for most archs on http://autopkgtest.ubuntu.com/packages/g/gnupg2 for the new Bionic release, so I'll mark this as verified.

I'm still looking into the regressions for armhf and for libgnupg-interface-perl, but the latter seems to have been broken since 2018.

Autopkgtest failures for gnupg2 on armhf have been fixed with a re-run, so it was likely due to a flaky testbed setup.

Failures for libgnupg-interface-perl are the result of the upstream test suite and very unlikely to be related to this SRU. I've opened bug 1916499 to investigate those separately.

The verification of the Stable Release Update for gnupg2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package gnupg2 - 2.2.4-1ubuntu1.4

---------------
gnupg2 (2.2.4-1ubuntu1.4) bionic; urgency=medium

  * d/p/dirmngr-handle-EAFNOSUPPORT-at-connect_server.patch:
    - Fix IPv6 connectivity for dirmngr (LP: #1910432)
  * Fix autopkgtests (LP: #1825186)
    - add d/t/simple-tests from devel branch
    - remove broken gpgv-win32 test from d/t/control

 -- Heitor Alves de Siqueira <email address hidden> Sat, 16 Jan 2021 14:47:37 +0000