Your message dated Thu, 15 Dec 2016 05:33:33 +0000
with message-id <e1chofd-000b6b...@fasolo.debian.org>
and subject line Bug#848004: fixed in up-imapproxy 1.2.8~svn20161210-2
has caused the Debian Bug report #848004,
regarding imapproxy must depend on tzdata
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.)
--
848004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imapproxy
Version: 1.2.8~svn20161210-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...):
Selecting previously unselected package imapproxy.
(Reading database ...
(Reading database ... 4717 files and directories currently installed.)
Preparing to unpack .../imapproxy_1.2.8~svn20161210-1_amd64.deb ...
Unpacking imapproxy (1.2.8~svn20161210-1) ...
Setting up imapproxy (1.2.8~svn20161210-1) ...
Creating config file /etc/imapproxy.conf with new version
mkdir: cannot create directory '/etc': File exists
cp: cannot stat '/etc/localtime': No such file or directory
dpkg: error processing package imapproxy (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
imapproxy
There is probably no /etc/localtime in the minimal chroot used by piuparts.
cheers,
Andreas
imapproxy_1.2.8~svn20161210-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: up-imapproxy
Source-Version: 1.2.8~svn20161210-2
We believe that the bug you reported is fixed in the latest version of
up-imapproxy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Richard Laager <rlaa...@wiktel.com> (supplier of updated up-imapproxy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 13 Dec 2016 18:44:17 -0600
Source: up-imapproxy
Binary: imapproxy
Architecture: source amd64
Version: 1.2.8~svn20161210-2
Distribution: unstable
Urgency: medium
Maintainer: Richard Laager <rlaa...@wiktel.com>
Changed-By: Richard Laager <rlaa...@wiktel.com>
Description:
imapproxy - IMAP protocol proxy
Closes: 770364 838071 848004
Changes:
up-imapproxy (1.2.8~svn20161210-2) unstable; urgency=medium
.
[ Jose Luis Tallon ]
* New maintainer (Closes: 838071)
.
[ Adriano Rafael Gomes ]
* Add pt_BR debconf translation (Closes: 770364)
.
[ Richard Laager ]
* Fix fuzzy pt_BR debconf translation
* Cleanup package maintainer scripts
* Suppress errors from rmdir in prerm
* Lookup the chroot_directory for localtime code
* Handle lack of /etc/localtime (Closes: 848004)
* Handle changed /etc/localtime
Checksums-Sha1:
daf8aaf4448afe9c50298c8152e8ca529286ae64 2111
up-imapproxy_1.2.8~svn20161210-2.dsc
ad923da430856b5c8a79fbed953483a7e93549d2 28164
up-imapproxy_1.2.8~svn20161210-2.debian.tar.xz
b01f9e6d0c58b7035160c716c947c1603aa8cb2b 96140
imapproxy-dbgsym_1.2.8~svn20161210-2_amd64.deb
2383a34994e0f17af3208491cd7f1ebe1ae83623 59524
imapproxy_1.2.8~svn20161210-2_amd64.deb
7f39f9f73219d62b9224f97788c6257d95ba0ae5 5122
up-imapproxy_1.2.8~svn20161210-2_amd64.buildinfo
Checksums-Sha256:
0304f92c0048ed06f20c056fce5d0d098bb14757215284b67bdae1ea78a31861 2111
up-imapproxy_1.2.8~svn20161210-2.dsc
53e9ecc6909357f96275ffbb36d67412d253563f486dcddf52965c51535ce511 28164
up-imapproxy_1.2.8~svn20161210-2.debian.tar.xz
1e3984508b217ec4df707490ebc99bfab81ccd2ef47f826178d9678877ddf40c 96140
imapproxy-dbgsym_1.2.8~svn20161210-2_amd64.deb
ffcdf11c8a365f53f28425d4f18869aee4e99620b58915efa61214f73e1d7e34 59524
imapproxy_1.2.8~svn20161210-2_amd64.deb
30d38c235d852a99b678f7688419d6d34efc5fde7f6ccb25ac1cf9fa34872505 5122
up-imapproxy_1.2.8~svn20161210-2_amd64.buildinfo
Files:
c5452f26ee8b890c4205c636286f4e7a 2111 mail optional
up-imapproxy_1.2.8~svn20161210-2.dsc
07f29260128ed4be6575607a0b5a33b1 28164 mail optional
up-imapproxy_1.2.8~svn20161210-2.debian.tar.xz
2c861b2158f2f6eab201902716ae365b 96140 debug extra
imapproxy-dbgsym_1.2.8~svn20161210-2_amd64.deb
3c10116e77fb4faba13a8a3e4e4b6206 59524 mail optional
imapproxy_1.2.8~svn20161210-2_amd64.deb
59e7fc95fed0e30a3d71c569899c8c7c 5122 mail optional
up-imapproxy_1.2.8~svn20161210-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlhSJx4ACgkQIdIFiZdL
PpZcNxAA1GbK5OFzEK1MBH+kR3PfiUPh0PE+DEuHYmep47h5z4VnnkI0wrIEmFHL
whyXBvVO34sE+0cZX4fv6bIJ5K96qcfZCIFRx48968GQpdJ93DYpSB9L+BROKgwE
vo2L9uKJLi5MVAROHkkN+3EcmMMYaYVvwvVHKytI9czKMdxjmUQXPQiVrz8ISjsR
o22N9/+pKes0+2qYF1syF8G3EM2XbIwPS9+7LELkoss9BCLdZktqaIl5x4Sn5Zda
3zVKaOL2HXeY3CQqtDaabf1uV4LrMBgE9FY6Kf132VazkG9DjEp34Dq4/4pArCFt
Kbgf5fVQCKsKodo2rhq/uzg6rk7TrRN3UmyUBdoT8JC5geUx/DvdEoK9aYZmPnC7
pwIJCUANlBy/ejsl5927FTLBwYhuLVtAnIYWPDJZDYxVO1uLGcNYqh7AkRMVpkwZ
9TJgoypUZDMY8yHoqiZ3cUy2pCivML/FfRE9t66oE3u8EkvaE0tkNZ/j7lh9tLfB
i3eeK/9Wzo9WGk7vwaDeKlBOeqlaFBKl78GyYMWU4tpVx/hB6os0Eb0XfzCF7CV2
GwRPAOVdrG6sFtMsl6ZkqAsYcWFljUHjfSLTbuQT51AFxd3EBqqahTkx3mRuSC2y
qbKkZpuYCbGM1dS+3uOOa2AKpb0ijPzQAnZcEZRQJzZHcLmMqq8=
=RUPf
-----END PGP SIGNATURE-----
--- End Message ---
