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

Bug#364322: marked as done (rscheme: [patch] please properly support amd64)

Your message dated Thu, 27 Apr 2006 16:32:16 -0700
with message-id <E1FZFy4-0005KB-Nl@spohr.debian.org>
and subject line Bug#364322: fixed in rscheme 0.7.3.4.b3-4
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: rscheme
Version: 0.7.3.4.b3-3
Severity: important
Tags: patch
Justification: fails to build from source

I regret to report that "hoping for the best" doesn't quite cut it.
The attached dpatch allows rscheme to build, and AFAICT even work, on
amd64, and also fixes a couple of typos I noticed along the way; could
you please apply it?

Thanks!

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (300, 'unstable'), (300, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.9
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages rscheme depends on:
ii  libc6                         2.3.6-7    GNU C Library: Shared libraries
ii  libgd2-xpm                    2.0.33-3   GD Graphics Library version 2
ii  libgmp3c2                     4.2.dfsg-1 Multiprecision arithmetic library
ii  libx11-6                      2:1.0.0-6  X11 client-side library
ii  zlib1g                        1:1.2.3-11 compression library - runtime

rscheme recommends no packages.

-- no debconf information

Attachment: 99_amd64.dpatch
Description: application/shellscript


--- End Message ---
--- Begin Message --- 
Source: rscheme
Source-Version: 0.7.3.4.b3-4

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

rscheme_0.7.3.4.b3-4.diff.gz
  to pool/main/r/rscheme/rscheme_0.7.3.4.b3-4.diff.gz
rscheme_0.7.3.4.b3-4.dsc
  to pool/main/r/rscheme/rscheme_0.7.3.4.b3-4.dsc
rscheme_0.7.3.4.b3-4_i386.deb
  to pool/main/r/rscheme/rscheme_0.7.3.4.b3-4_i386.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 364322@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lars Bahner <bahner@debian.org> (supplier of updated rscheme 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: Sun, 23 Apr 2006 16:44:19 +0000
Source: rscheme
Binary: rscheme
Architecture: source i386
Version: 0.7.3.4.b3-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Lars Bahner <bahner@debian.org>
Description: 
 rscheme    - Threaded, persistent, OO, scheme interpreter and compiler
Closes: 364322
Changes: 
 rscheme (0.7.3.4.b3-4) unstable; urgency=low
 .
   * Applying amd64 patch from Aaron M. Ucko. (Closes: #364322)
Files: 
 d2483ae6754a348435ccbfca845dcef3 849 devel optional rscheme_0.7.3.4.b3-4.dsc
 ff4897e90aef7425bc702ed3686e6e8e 22158 devel optional rscheme_0.7.3.4.b3-4.diff.gz
 881067378536960a70c266926de5070d 6768544 devel optional rscheme_0.7.3.4.b3-4_i386.deb

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

iD8DBQFEUUNNmXJ8FFTsuK8RAmoGAJ4q6f8RrJnRZCgoEugboZo+H5I/eACfT3jW
oqO0dQHiEuZbNXcUacuTKQE=
=4avt
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: