Bug 1441315 - perl-Test-Assert-0.0504-18.fc27 FTBFS: rm: cannot remove '/tmp/tmp.TSfaP5NJDu/S.gpg-agent.ssh': No such file or directory
Summary: perl-Test-Assert-0.0504-18.fc27 FTBFS: rm: cannot remove '/tmp/tmp.TSfaP5NJDu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Test-Assert
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-11 16:20 UTC by Petr Pisar
Modified: 2017-04-16 14:38 UTC (History)
2 users (show)

Fixed In Version: perl-Test-Assert-0.0504-19.fc26
Clone Of:
Environment:
Last Closed: 2017-04-16 14:38:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2017-04-11 16:20:44 UTC
perl-Test-Assert-0.0504-18.fc27 fails to build in F27 because a failure after running tests:

WARNING: This key is not certified with a trusted signature!
Primary key fingerprint: 56B4 B786 A62D 3EA1 34CF  264C 84C1 C77B C0B1 0A5B
xt/signature.t ................... ok
All tests successful.
Files=9, Tests=43,  6 wallclock secs ( 0.04 usr  0.02 sys +  6.01 cusr  0.18 csys =  6.25 CPU)
Result: PASS
+ rm -r /tmp/tmp.TSfaP5NJDu
rm: cannot remove '/tmp/tmp.TSfaP5NJDu/S.gpg-agent.ssh': No such file or directory
rm: cannot remove '/tmp/tmp.TSfaP5NJDu/S.gpg-agent.browser': No such file or directory

This happens when building the package in a mock environment since Test::Signature moved to gnupg2.

I recommend to remove the test completely because it does not make sense to test a signature of a code by running the code.

Comment 1 Paul Howarth 2017-04-11 16:54:48 UTC
(In reply to Petr Pisar from comment #0)
> perl-Test-Assert-0.0504-18.fc27 fails to build in F27 because a failure
> after running tests:
> 
> WARNING: This key is not certified with a trusted signature!
> Primary key fingerprint: 56B4 B786 A62D 3EA1 34CF  264C 84C1 C77B C0B1 0A5B
> xt/signature.t ................... ok
> All tests successful.
> Files=9, Tests=43,  6 wallclock secs ( 0.04 usr  0.02 sys +  6.01 cusr  0.18
> csys =  6.25 CPU)
> Result: PASS
> + rm -r /tmp/tmp.TSfaP5NJDu
> rm: cannot remove '/tmp/tmp.TSfaP5NJDu/S.gpg-agent.ssh': No such file or
> directory
> rm: cannot remove '/tmp/tmp.TSfaP5NJDu/S.gpg-agent.browser': No such file or
> directory
> 
> This happens when building the package in a mock environment since
> Test::Signature moved to gnupg2.

Do you mean *not* in a mock environment? It builds fine in mock for me, and in koji last week. It looks like GPG agent sockets lingering a little.

I suspect that changing 'rm -r "$GNUPGHOME"' to 'rm -rf "$GNUPGHOME"' would address this more simply than avoiding the test, which is mainly useful as a test of Test::Signature as far as I'm concerned.




> 
> I recommend to remove the test completely because it does not make sense to
> test a signature of a code by running the code.

Comment 2 Petr Pisar 2017-04-12 06:30:48 UTC
I mean in a mock environment. But it's quite possible that gnupg2 behavior in the mock is influenced by the system. For example it can see a running ssh-agent process from the system.

The "rm -rf" works for me.

Comment 3 Fedora Update System 2017-04-12 08:32:45 UTC
perl-Test-Assert-0.0504-19.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b1cc9ffe46

Comment 4 Fedora Update System 2017-04-12 23:23:00 UTC
perl-Test-Assert-0.0504-19.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b1cc9ffe46

Comment 5 Fedora Update System 2017-04-16 14:38:49 UTC
perl-Test-Assert-0.0504-19.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.