Your message dated Wed, 28 May 2008 17:02:06 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#483316: fixed in jruby0.9 0.9.9-8
has caused the Debian Bug report #483316,
regarding jruby0.9: FTBFS: tar: jruby-bin-7.tar.gz: Cannot open: No such file
or directory
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 [EMAIL PROTECTED]
immediately.)
--
483316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483316
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: jruby0.9
Version: 0.9.9-7
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080527 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on
i386.
Relevant part:
> /usr/bin/fakeroot debian/rules binary
> dh_testdir
> # Add here commands to compile the package.
> /usr/bin/ant compile
> Buildfile: build.xml
>
> init:
>
> prepare:
>
> compile.tasks:
> [copy] Copying 1 file to
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/build/classes/jruby
>
> check-for-optional-java4-packages:
>
> check-for-optional-packages:
>
> compile-jruby:
>
> compile:
>
> BUILD SUCCESSFUL
> Total time: 2 seconds
> touch build-stamp
> dh_testdir
> dh_testroot
> dh_clean -k
> dh_installdirs
> # Add here commands to install the package into debian/jruby0.9.
> /usr/bin/ant dist-bin
> Buildfile: build.xml
>
> init:
>
> prepare:
>
> compile.tasks:
> [copy] Copying 1 file to
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/build/classes/jruby
>
> check-for-optional-java4-packages:
>
> check-for-optional-packages:
>
> compile-jruby:
>
> compile:
>
> serialize:
> [jruby-serialize] Serializing 20 files to
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/build/classes/jruby
>
> generate-method-classes:
> [touch] Creating
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/build/__empty.rb
> [delete] Deleting:
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/build/__empty.rb
>
> jar-jruby:
> [jar] Building jar:
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/lib/jruby.jar
>
> jar:
>
> dist-bin:
> [tar] Building tar:
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/jruby-bin-0.9.9.tar.gz
>
> BUILD SUCCESSFUL
> Total time: 15 seconds
> tar -zxf jruby-bin-7.tar.gz -C
> /build/user-jruby0.9_0.9.9-7-amd64-11XSTA/jruby0.9-0.9.9-7/debian/jruby0.9/usr/lib/
> tar: jruby-bin-7.tar.gz: Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> tar: Child returned status 2
> tar: Error exit delayed from previous errors
> make: *** [install] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/05/27
This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3
is now the default on most architectures (even if it's not the case on
i386 yet). Consequently, many failures are caused by the switch to gcc
4.3.
If you determine that this failure is caused by gcc 4.3, feel free to
downgrade this bug to 'important' if your package is only built on i386,
and this bug is specific to gcc 4.3 (i.e the package builds fine with
gcc 4.2).
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Source: jruby0.9
Source-Version: 0.9.9-8
We believe that the bug you reported is fixed in the latest version of
jruby0.9, which is due to be installed in the Debian FTP archive:
jruby0.9_0.9.9-8.diff.gz
to pool/main/j/jruby0.9/jruby0.9_0.9.9-8.diff.gz
jruby0.9_0.9.9-8.dsc
to pool/main/j/jruby0.9/jruby0.9_0.9.9-8.dsc
jruby0.9_0.9.9-8_all.deb
to pool/main/j/jruby0.9/jruby0.9_0.9.9-8_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.
Sebastien Delafond <[EMAIL PROTECTED]> (supplier of updated jruby0.9 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: Wed, 28 May 2008 09:25:14 -0700
Source: jruby0.9
Binary: jruby0.9
Architecture: source all
Version: 0.9.9-8
Distribution: unstable
Urgency: low
Maintainer: Sebastien Delafond <[EMAIL PROTECTED]>
Changed-By: Sebastien Delafond <[EMAIL PROTECTED]>
Description:
jruby0.9 - 100% pure-Java implementation of Ruby
Closes: 483316
Changes:
jruby0.9 (0.9.9-8) unstable; urgency=low
.
* Extract version number the right way (Closes: #483316).
* Lintian cleanups.
Files:
91363a835a296813968798401d381e33 675 interpreters optional jruby0.9_0.9.9-8.dsc
954118c9a59442208497cbd9bb098229 16567 interpreters optional
jruby0.9_0.9.9-8.diff.gz
874fbbbe0a6b5074bca352d6b773adbb 4045954 interpreters optional
jruby0.9_0.9.9-8_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIPYuhiZgNKcDdyD8RAjfuAJ46bJRRsSieUX3Pd9ErpvLFwELTfgCfaPT8
L766ezdGOhhAzBpGY8FqPQ4=
=UDOk
-----END PGP SIGNATURE-----
--- End Message ---
