Your message dated Wed, 21 Apr 2021 21:17:51 +0200
with message-id <99b8ac09-0f26-79b8-a9db-3f4e12c89...@debian.org>
and subject line Re: Bug#987303: neutron-common: fails to install: cp: cannot
stat '/usr/share/neutron-common/plugins/ml2/ml2_conf.ini': No such file or
directory
has caused the Debian Bug report #987303,
regarding neutron-common: fails to install: cp: cannot stat
'/usr/share/neutron-common/plugins/ml2/ml2_conf.ini': 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.)
--
987303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neutron-common
Version: 2:17.1.1-3
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 neutron-common (2:17.1.1-3) ...
cp: cannot stat '/usr/share/neutron-common/plugins/ml2/ml2_conf.ini': No such
file or directory
dpkg: error processing package neutron-common (--configure):
installed neutron-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:
neutron-common
cheers,
Andreas
neutron-common_2:17.1.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 2:17.1.1-4
On 21/04/2021 18.23, Thomas Goirand wrote:
This was fixed in 2:17.1.1-4 that I just uploaded, before I saw your bug
report. I'm not sure how to fix the BTS metadata then... :/
Done with this mail ;-)
Andreas
--- End Message ---
