Your message dated Mon, 27 Dec 2021 11:49:04 +0100
with message-id <56aa1561-4e09-6868-b384-a9fe81b01...@debian.org>
and subject line Fixed
has caused the Debian Bug report #985864,
regarding trove-common: fails to install: install: cannot stat
'/usr/share/trove-common/trove-guestagent.conf': No such file or directory
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.)
--
985864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trove-common
Version: 1:15.0.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Setting up trove-common (1:15.0.0~rc1-1) ...
install: cannot stat '/usr/share/trove-common/trove-guestagent.conf': No such
file or directory
dpkg: error processing package trove-common (--configure):
installed trove-common package post-installation script subprocess returned
error exit status 1
Processing triggers for ca-certificates (20210119) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
trove-common
cheers,
Andreas
trove-common_1:15.0.0~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
This was fixed in debian/15.0.0-2
Closing this bug.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
