[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#398567: marked as done (cipe-common: postinst fails: /var/lib/dpkg/info/cipe-common.postinst: line 22: update-modules: command not found)

Your message dated Wed, 24 Jan 2007 12:02:02 +0000
with message-id <E1H9gpG-0008FD-MS@ries.debian.org>
and subject line Bug#398567: fixed in cipe 1.5.4free-12
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: cipe-common
Version: 1.5.4free-10
Severity: serious
Usertags: grid5000


During a piuparts run over all the packages in etch, I ran into a
problem with your package:
  Setting up cipe-common (1.5.4free-10) ...
  /var/lib/dpkg/info/cipe-common.postinst: line 22: update-modules:
command not found
  dpkg: error processing cipe-common (--configure):
   subprocess post-installation script returned error exit status 127

The full log is available from 

The piuparts run was done on about 40 AMD64 nodes of the Grid'5000
platform, using a clean chroot containing an etch i386 environment
(not unstable).  Internet was not accessible from the build systems.

About Grid'5000:
Grid'5000 is an highly reconfigurable experimental Grid platform
gathering 9 sites and featuring a total of 5000 CPUs. It serves as a
testbed for research in Grid Computing. See https://www.grid5000.fr/
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

--- End Message ---
--- Begin Message ---
Source: cipe
Source-Version: 1.5.4free-12

We believe that the bug you reported is fixed in the latest version of
cipe, which is due to be installed in the Debian FTP archive:

  to pool/main/c/cipe/cipe-common_1.5.4free-12_all.deb
  to pool/main/c/cipe/cipe-source_1.5.4free-12_all.deb
  to pool/main/c/cipe/cipe_1.5.4free-12.diff.gz
  to pool/main/c/cipe/cipe_1.5.4free-12.dsc
  to pool/main/c/cipe/pkcipe_1.5.4free-12_amd64.deb

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 398567@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Michael Ablassmeier <abi@debian.org> (supplier of updated cipe 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 ftpmaster@debian.org)

Hash: SHA1

Format: 1.7
Date: Wed, 24 Jan 2007 12:46:53 +0100
Source: cipe
Binary: pkcipe cipe-common cipe-source
Architecture: source all amd64
Version: 1.5.4free-12
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Michael Ablassmeier <abi@debian.org>
 cipe-common - common files for the CIPE VPN software
 cipe-source - lightweight encrypted IP tunnels over UDP (source)
 pkcipe     - public key based configuration tool for the CIPE VPN software
Closes: 398567
 cipe (1.5.4free-12) unstable; urgency=medium
   * QA upload.
   * Really add module-init-tools to depends, sight.
     Closes: #398567
 fcfa00c2ca1843e105a27949d360cdca 610 net optional cipe_1.5.4free-12.dsc
 2b689700774fe5366f994f33e719b041 54969 net optional cipe_1.5.4free-12.diff.gz
 41bc797dcc484f9bb46e6e024d917e71 190036 net optional cipe-source_1.5.4free-12_all.deb
 3c1875f2eee914d731ecf7ae60b51a3d 68644 net optional cipe-common_1.5.4free-12_all.deb
 1eab6bc9048f501b12822c64db64ed9c 35770 net optional pkcipe_1.5.4free-12_amd64.deb

Version: GnuPG v1.4.6 (GNU/Linux)


--- End Message ---

Reply to: