Your message dated Sat, 18 Jun 2011 06:47:22 +0000
with message-id <e1qxpjs-0007fw...@franck.debian.org>
and subject line Bug#630852: fixed in ginkgocadx 2.4.1.1-2
has caused the Debian Bug report #630852,
regarding ginkgocadx: FTBFS on non-x86 architectures: hardcodes -msse2
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 ow...@bugs.debian.org
immediately.)
--
630852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ginkgocadx
Version: 2.4.1.1-1
Severity: serious
Justification: fails to build from source
Builds of ginkgocadx on non-x86 Linux architectures are failing
because it passes the x86-specific -msse2 flag, which is a bad idea
even on x86: it's redundant on amd64, and fails to account for the
fact that i386 is supposed to support older processors. Could you
please remove it?
Thanks!
Alas, that still won't be enough to get the package building, as it
also runs afoul of libvtk5-dev bug #630559. :-/ (Moreover, it doesn't
officially support non-Linux architectures at all, though you may be
able to get away with having it treat them in the same manner as Linux.)
--- End Message ---
--- Begin Message ---
Source: ginkgocadx
Source-Version: 2.4.1.1-2
We believe that the bug you reported is fixed in the latest version of
ginkgocadx, which is due to be installed in the Debian FTP archive:
ginkgocadx_2.4.1.1-2.debian.tar.gz
to main/g/ginkgocadx/ginkgocadx_2.4.1.1-2.debian.tar.gz
ginkgocadx_2.4.1.1-2.dsc
to main/g/ginkgocadx/ginkgocadx_2.4.1.1-2.dsc
ginkgocadx_2.4.1.1-2_amd64.deb
to main/g/ginkgocadx/ginkgocadx_2.4.1.1-2_amd64.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 630...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated ginkgocadx 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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 18 Jun 2011 08:10:00 +0200
Source: ginkgocadx
Binary: ginkgocadx
Architecture: source amd64
Version: 2.4.1.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team
<debian-med-packag...@lists.alioth.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Description:
ginkgocadx - Medical Imaging Software and complete DICOM Viewer
Closes: 630852
Changes:
ginkgocadx (2.4.1.1-2) unstable; urgency=low
.
* debian/patches/01_no_msse.patch: Do not build with -msse flag
Closes: #630852
Checksums-Sha1:
f43e6f6d6c476db9aeb39f0b48c84045f1279c11 1667 ginkgocadx_2.4.1.1-2.dsc
0cf69feebaffeaf9eae54a57443af4f1f204e968 8891
ginkgocadx_2.4.1.1-2.debian.tar.gz
de90dbea476695f9924294338d975967d1f20bbe 4305918 ginkgocadx_2.4.1.1-2_amd64.deb
Checksums-Sha256:
62a8a8c82872b4b904b3be973f1c5e7858c75bab1cc794e61489ba24b452ac6d 1667
ginkgocadx_2.4.1.1-2.dsc
786d6a0a0d3a4f0bb5c2d6a18416eea98a796ae8b903139d17c1f88037777ebf 8891
ginkgocadx_2.4.1.1-2.debian.tar.gz
8f4e6b4c43a143dba71a517ac3824c45fa4536df722a6a0ce46d6542aaa92559 4305918
ginkgocadx_2.4.1.1-2_amd64.deb
Files:
21a3a6b077659a1a14d79bb0e07b1f6d 1667 science optional ginkgocadx_2.4.1.1-2.dsc
b68c4ece5af073c40a0b14ad1baf0505 8891 science optional
ginkgocadx_2.4.1.1-2.debian.tar.gz
d1adcb5411697f5435c795620d3875d8 4305918 science optional
ginkgocadx_2.4.1.1-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk38RM8ACgkQYDBbMcCf01qaxgCfb3RVs5vV8jaL61stcl1B3+TL
DoIAn1EZZuH9wXgT9WhWJMuF4qopygU+
=0O37
-----END PGP SIGNATURE-----
--- End Message ---
