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

Bug#415031: marked as done (camas: FTBFS: make: execvp: ./configure: Permission denied)



Your message dated Sat, 17 Mar 2007 20:32:03 +0000
with message-id <E1HSfZL-0005DB-6g@ries.debian.org>
and subject line Bug#415031: fixed in camas 1.2.21-3.1
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-3
Severity: serious
Usertags: grid5000 rebuild

Hi,

During a rebuild of all packages in sid, I discovered that your package
failed to build on i386.

Relevant parts:
 debian/rules build
dh_testdir
if test "no" = "yes"; then \
	    ./autogen.sh; \
	fi
# Add here commands to configure the package.
./configure --prefix=/usr --with-forced-caudium=/usr/lib/caudium --with-pike=/usr/bin/pike7.6
make: execvp: ./configure: Permission denied
make: *** [configure-stamp] Error 127

# ls -l configure
-rw-r--r-- 1 root root 95199 Mar 15 18:12 configure

The full build log is available from 
http://people.debian.org/~lucas/logs/2007/03/13/

About the archive rebuilt: The rebuilt was done on about 40 AMD64 nodes of the
Grid'5000 platform, using a clean chroot containing a sid i386 environment.
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: camas
Source-Version: 1.2.21-3.1

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-3.1.diff.gz
  to pool/main/c/camas/camas_1.2.21-3.1.diff.gz
camas_1.2.21-3.1.dsc
  to pool/main/c/camas/camas_1.2.21-3.1.dsc
camas_1.2.21-3.1_all.deb
  to pool/main/c/camas/camas_1.2.21-3.1_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 415031@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mohammed Sameer <debian@foolab.org> (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 ftpmaster@debian.org)


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

Format: 1.7
Date: Sat, 17 Mar 2007 20:38:17 +0200
Source: camas
Binary: camas
Architecture: source all
Version: 1.2.21-3.1
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Mohammed Sameer <debian@foolab.org>
Description: 
 camas      - A versatile WebMail system for the Caudium WebServer
Closes: 415031
Changes: 
 camas (1.2.21-3.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/rules: make ./configure executable. (Closes: #415031)
Files: 
 212508f7d965a2e9b8b05d9bf774b623 624 web optional camas_1.2.21-3.1.dsc
 18716f353df085e710a6895a8e02f484 72802 web optional camas_1.2.21-3.1.diff.gz
 60c56c3f3e6258db76761e805a52c923 674228 web optional camas_1.2.21-3.1_all.deb

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

iD8DBQFF/DYOy2aOKaP9DfcRAnYMAJ9uD5JcbhLqUMlhpwA2MEKQRC698gCePJUC
N2FKFhW50AMALE4PC/6nJ1c=
=GCFM
-----END PGP SIGNATURE-----


--- End Message ---

Reply to: