Your message dated Thu, 27 Dec 2018 12:28:13 +0100
with message-id <[email protected]>
and subject line Bug#910438: kopano-server: logrotate exits with error after 
package removal
has caused the Debian Bug report #910438,
regarding kopano-server: logrotate exits with error after package removal
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 [email protected]
immediately.)


-- 
910438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910438
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kopano-server
Version: 8.6.5-1
Severity: important
User: [email protected]
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package's logrotate
configuration causes logrotate to exit with an error after
the package has been removed.

>From the attached log (scroll to the bottom...):

1m24.8s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts/tmp/tmpihm1IJ', '/usr/sbin/logrotate', 
'/etc/logrotate.d/kopano-server']
  error: stat of /var/log/kopano failed: No such file or directory


cheers,

Andreas

Attachment: kopano-server_8.6.5-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Version: 8.6.91-1

Hello Andreas,

Am 06.10.18 um 14:22 schrieb Andreas Beckmann:
> Hi,
> 
> during a test with piuparts I noticed your package's logrotate
> configuration causes logrotate to exit with an error after
> the package has been removed.
> 
> From the attached log (scroll to the bottom...):
> 
> 1m24.8s ERROR: Command failed (status=1): ['chroot', 
> '/srv/piuparts/tmp/tmpihm1IJ', '/usr/sbin/logrotate', 
> '/etc/logrotate.d/kopano-server']
>   error: stat of /var/log/kopano failed: No such file or directory

this issue should be gone by the upload of 8.6.91-1 at least.
We had some overlapping logrotate files between some packages which is
fixed by the named version now. I will close this report now. If I
missed something please feel free to reopen.

Thanks for doing all this QA work!

-- 
Regards
Carsten Schoenert

--- End Message ---

Reply via email to