Your message dated Wed, 22 Jun 2016 16:51:12 +0000
with message-id <e1bflmu-0002ng...@franck.debian.org>
and subject line Bug#827849: fixed in ppc64-diag 2.7.1-2
has caused the Debian Bug report #827849,
regarding ppc64-diag-doc: fails to install: ppc64-diag-doc.postinst: 
/etc/ppc64-diag/ppc64_diag_setup: not found
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.)


-- 
827849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ppc64-diag-doc
Version: 2.7.1-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 ppc64-diag-doc.
  (Reading database ... 
(Reading database ... 6446 files and directories currently installed.)
  Preparing to unpack .../ppc64-diag-doc_2.7.1-1_all.deb ...
  Unpacking ppc64-diag-doc (2.7.1-1) ...
  Setting up ppc64-diag-doc (2.7.1-1) ...
  /var/lib/dpkg/info/ppc64-diag-doc.postinst: 10: 
/var/lib/dpkg/info/ppc64-diag-doc.postinst: /etc/ppc64-diag/ppc64_diag_setup: 
not found
  dpkg: error processing package ppc64-diag-doc (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   ppc64-diag-doc


cheers,

Andreas

Attachment: ppc64-diag-doc_2.7.1-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: ppc64-diag
Source-Version: 2.7.1-2

We believe that the bug you reported is fixed in the latest version of
ppc64-diag, 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 827...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frederic Bonnard <fre...@linux.vnet.ibm.com> (supplier of updated ppc64-diag 
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: SHA256

Format: 1.8
Date: Wed, 22 Jun 2016 16:32:50 +0200
Source: ppc64-diag
Binary: ppc64-diag-doc ppc64-diag
Architecture: source
Version: 2.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Frederic Bonnard <fre...@linux.vnet.ibm.com>
Changed-By: Frederic Bonnard <fre...@linux.vnet.ibm.com>
Description:
 ppc64-diag - Platform error log analysis tool and rtas_errd daemon
 ppc64-diag-doc - Documentation for ppc64-diag tools
Closes: 827849
Changes:
 ppc64-diag (2.7.1-2) unstable; urgency=medium
 .
   * Assign prerm and postinst to ppc64-diag package only (Closes: #827849)
Checksums-Sha1:
 5f927d0a582f719f7e652019718f12b4a6362654 1992 ppc64-diag_2.7.1-2.dsc
 32126d09f620fb71b836960eb7138d0e560dee02 12484 ppc64-diag_2.7.1-2.debian.tar.xz
Checksums-Sha256:
 8fcaa0168ce276dccbcd14b444d2e21af9f81a5f961b118ac515524f7926bbb1 1992 
ppc64-diag_2.7.1-2.dsc
 76ca140750893671f188e66a20d3d1a1e109fdf315442419889be5512698171d 12484 
ppc64-diag_2.7.1-2.debian.tar.xz
Files:
 3fe90a5fdc32d0ccc373f342c1cd6951 1992 misc extra ppc64-diag_2.7.1-2.dsc
 355341adc4734c53a3e36deae72023a7 12484 misc extra 
ppc64-diag_2.7.1-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXaq1/AAoJEPNPCXROn13ZEWsP/AjM+qFgvT69EcjkAMRpbJ5a
BRUtCuqLl9G2d1L49/s/t+iEJHNbXZmadFKwgkCvK/wyXYkGFX7aGBOA4zBtmDGT
4KRHiZKwpIM6W/pUPnWPMPBtH02aQzGry/uO+hfA/bIi9/bz3LbJHXvv9BCgD/kS
Oui4ypWXgragXDvPkslNGN/XYsjB+GHiTOUDXa1kcIVxl5qz6HPH98TZRv+/GOsm
/0EzkQM9H2FqkaJpH/FoXVzIbxNaFMTNFbMWrspzZVOlW+2w5tLovF9JNPY4Dq3o
vvxBLvzmq8ePHVBNnHofM6JW07ssatr1eUZzDq0EGseDY6E6L6XRWt2P2GUUkf5z
45uwkzYqCvPeyM8SyQp3RWduvYy7ISuVx96qsIQoVmT0YD7nrpQSBfIf3ihlNT6p
CM/dC+L1wbSHMC/iyB39763WhLDM65UAiBPnsaWIqR81xUkmRX/kjCmty42seJ51
38qEt4N24jM6DBhaneS+lQt6uh5P2qZZYdwxnUWvkX8hxFY/JYfuGbxEmjwezS/l
goma/mbW/02Kf252VeWezN63aN9omSwhXPXecGTr30swtl9aEZ8EA9wClSflJPiy
v4X+xNPTrOWffZiHB3sInjsLYftv6fATgsCQxT3NGMHDO57jY91zmtJU2NqQIQWD
ACEjEbkBicKFUCeCo01V
=lEoX
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to