Your message dated Fri, 10 Nov 2006 04:47:15 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396417: fixed in camas 1.2.21-2.2
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: camas
Version: 1.2.21-2.1
Severity: important
Justification: causes camas to FTBFS, but causes unclear so not RC for now
Usertag: grid5000

Hi,

While running a rebuild of the whole archive, I ran into a problem with
camas: its build times out during dependencies resolution, after starting
caudium.

Setting up intltool-debian (0.35.0+20060710.1) ...
Setting up po-debconf (1.0.6) ...
Setting up debhelper (5.0.40) ...
Setting up pike7.6-dev (7.6.93-1) ...
Setting up caudium-modules (1.4.9.1-1) ...
Setting up caudium (1.4.9.1-1) ...
Starting Caudium Webserver: caudium.


After this, nothing else is displayed, but sbuild doesn't return. The
process tree looks like:
 9167 pts/0    S+     0:00  |       \_ /usr/bin/perl /usr/bin/sbuild -d etch32 
-A camas_1.2.21-2.1
 9193 pts/0    S+     0:00  |           \_ /usr/bin/perl /usr/bin/sbuild -d 
etch32 -A camas_1.2.21-2.1
 9194 pts/0    S+     0:00  |           \_ /usr/bin/perl /usr/bin/sbuild -d 
etch32 -A camas_1.2.21-2.1
 9325 pts/0    Z+     0:00  |           \_ [schroot] <defunct>

With an instance of pike7.6 started:
9757 pts/0    S+     0:00 /usr/bin/pike7.6
-M/usr/lib/caudium/etc/modules /usr/lib/caudium/start-caudium
--pid-file=/var/run/caudium/caudium.pid
--config-dir=/etc/caudium/servers

I really don't know how to investigate this further, but prefer to file
this bug to document the issue, since somebody might be better at this
than I am. The bug might be in camas, caudium or even sbuild, I don't
know.

It would be great if somebody could take a look at this.

Thank you,
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: camas
Source-Version: 1.2.21-2.2

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

camas_1.2.21-2.2.diff.gz
  to pool/main/c/camas/camas_1.2.21-2.2.diff.gz
camas_1.2.21-2.2.dsc
  to pool/main/c/camas/camas_1.2.21-2.2.dsc
camas_1.2.21-2.2_all.deb
  to pool/main/c/camas/camas_1.2.21-2.2_all.deb



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steinar H. Gunderson <[EMAIL PROTECTED]> (supplier of updated camas 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 [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 10 Nov 2006 12:55:03 +0100
Source: camas
Binary: camas
Architecture: source all
Version: 1.2.21-2.2
Distribution: unstable
Urgency: medium
Maintainer: Marek Habersack <[EMAIL PROTECTED]>
Changed-By: Steinar H. Gunderson <[EMAIL PROTECTED]>
Description: 
 camas      - A versatile WebMail system for the Caudium WebServer
Closes: 396417
Changes: 
 camas (1.2.21-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depending on a daemon like caudium is bad; we do not normally want
     servers running on buildds. Thus, don't build-depend on caudium anymore;
     all it's used for during build is sanity checking for the Caudium path in
     the configure script. Instead, make a new configure parameter
     --with-forced-caudium= that skips all the sanity checks and just accepts
     the path. Fixes FTBFS in the cases where caudium would have problems
     starting up on the buildd. (Closes: #396417)
Files: 
 7c87498a5414210981e7d1ab23d625d1 738 web optional camas_1.2.21-2.2.dsc
 c324f67777b14ca5a5a91b0d24c96a4c 20443 web optional camas_1.2.21-2.2.diff.gz
 f264f4b2272c025a14f460ce383d8ed5 674394 web optional camas_1.2.21-2.2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iQCVAwUBRVRuG37hqgLJpbVOAQL46gP/XxJSgZygiY6Nd5ljtW1kL0g5BG5kD5so
Fp0BBsXyBEEl77jXOyh33z96vLp6hhajmbNaO7mqgIv2KLIdV7f/suD3R5xu5klo
cVrbH6LKmtUMrZ+SL+TmvldF0u6NTTJrxtBkvepqvFYSJI9/Z8nHYojFwYQTTDj0
m4Jvgv/F/BE=
=JALU
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to