Your message dated Thu, 3 Mar 2016 12:54:21 +0900
with message-id 
<CADCYzv6X1Hmn0_1YLEjXFKzc2JGO=A=enqy_3006ai1p-_c...@mail.gmail.com>
and subject line Re: chasen: causes installation failure in naist-jdic
has caused the Debian Bug report #814626,
regarding chasen: causes installation failure in naist-jdic
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.)


-- 
814626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chasen
Version: 2.4.5-23
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package causes naist-jdic to
fail to to install.

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

  Setting up naist-jdic (1:0.4.3-7) ...
  Now generating naist-jdic data. This may take a while...
  /usr/bin/chasen-config: 92: /usr/bin/chasen-config: dpkg-architecture: not 
found
  /var/lib/dpkg/info/naist-jdic.postinst: 24: 
/var/lib/dpkg/info/naist-jdic.postinst: /usr/lib//chasen/makemat: not found
  dpkg: error processing package naist-jdic (--configure):
   subprocess installed post-installation script returned error exit status 127


You shouldn't use dpkg-architecture from maintainer scripts
but resolve the architecture specific bits at package build time.


cheers,

Andreas

Attachment: chasen_2.4.5-23.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
On Sat, 13 Feb 2016 15:37:43 +0100 Andreas Beckmann <a...@debian.org> wrote:
> Package: chasen
> Version: 2.4.5-23
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts

> You shouldn't use dpkg-architecture from maintainer scripts
> but resolve the architecture specific bits at package build time.

Fixed in 2.4.5-24.

--- End Message ---

Reply via email to