Your message dated Wed, 11 Jan 2017 03:36:28 +0100
with message-id <[email protected]>
and subject line Re: Bug#845478: dpkg postinst script fails to move files in
/etc
has caused the Debian Bug report #845478,
regarding dpkg postinst script fails to move files in /etc
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.)
--
845478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845478
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.18.15
Severity: normal
Dear Maintainer,
since I upgaded to sid the following postinstall script doest work
anymore(https://github.com/sixsixfive/Hedera/blob/master/debian/postinst)
commands that fail:
https://github.com/sixsixfive/Hedera/blob/master/debian/postinst#L45
https://github.com/sixsixfive/Hedera/blob/master/debian/postinst#L73
https://github.com/sixsixfive/Hedera/blob/master/debian/postinst#L95
its also a complete mystery to me that it worked in the past and that it still
works on siduction, ubuntu/KDE neon
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.6-8
ii libc6 2.24-6
ii liblzma5 5.2.2-1.2
ii libselinux1 2.6-3
ii tar 1.29b-1.1
ii zlib1g 1:1.2.8.dfsg-2+b3
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 1.3.1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
On Fri, 2016-12-30 at 06:38:42 +0100, HJ wrote:
> I finally found some free time to look closer, however I really couldn't
> fix it so I reinstalled a fresh testing and surprise it worked fine. Not
> sure what caused this issue on the old system but it works now so I guess
> this bug can be closed ;)
Ok, thanks! Doing so now. If this happens again, please feel free to
reopen or file a new report.
Thanks,
Guillem
--- End Message ---
