Your message dated Wed, 29 Jul 2009 18:02:13 +0000
with message-id <e1mwdth-000308...@ries.debian.org>
and subject line Bug#539094: fixed in r-cran-surveillance 1.0.3-2
has caused the Debian Bug report #539094,
regarding r-cran-surveillance: Package FTBFS due to missing build-depends
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.)
--
539094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-surveillance
Version: 1.0.3-1
Severity: serious
Tags: patch
Justification: no longer builds from source
Package needs r-cran-vr and r-cran-colorspace to build from source. I believe
I have svn access to commit the fix and will do so. Ubuntu debdiff attached
(ignore the maintainer changes, the obviously aren't relevant).
-- System Information:
Debian Release: 5.0
APT prefers jaunty-updates
APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500,
'jaunty-backports'), (500, 'jaunty')
Architecture: i386 (i686)
Kernel: Linux 2.6.28-13-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u r-cran-surveillance-1.0.3/debian/changelog r-cran-surveillance-1.0.3/debian/changelog
--- r-cran-surveillance-1.0.3/debian/changelog
+++ r-cran-surveillance-1.0.3/debian/changelog
@@ -1,3 +1,10 @@
+r-cran-surveillance (1.0.3-1ubuntu1) karmic; urgency=low
+
+ * Add r-cran-vr and r-cran-colorspace to build-depends to fix FTBFS due to
+ missing mass and colorspace libraries
+
+ -- Scott Kitterman <sc...@kitterman.com> Tue, 28 Jul 2009 22:28:31 -0400
+
r-cran-surveillance (1.0.3-1) unstable; urgency=low
* Initial release (closes: #515647).
diff -u r-cran-surveillance-1.0.3/debian/control r-cran-surveillance-1.0.3/debian/control
--- r-cran-surveillance-1.0.3/debian/control
+++ r-cran-surveillance-1.0.3/debian/control
@@ -1,11 +1,12 @@
Source: r-cran-surveillance
Section: contrib/science
Priority: optional
-Maintainer: Debian-Med Packaging Team <debian-med-packag...@lists.alioth.debian.org>
+Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
+XSBC-Original-Maintainer: Debian-Med Packaging Team <debian-med-packag...@lists.alioth.debian.org>
Uploaders: Andreas Tille <ti...@debian.org>
DM-Upload-Allowed: yes
Build-Depends: debhelper (>= 7.0), cdbs, r-base-dev, r-cran-xtable, r-cran-spc,
- r-cran-maptools, r-cran-vcd, r-cran-msm
+ r-cran-maptools, r-cran-vcd, r-cran-msm, r-cran-vr, r-cran-colorspace
Standards-Version: 3.8.1
Homepage: http://surveillance.r-forge.r-project.org
Vcs-Browser: http://svn.debian.org/wsvn/debian-med/trunk/packages/R/r-cran-surveillance/trunk/?rev=0&sc=0
--- End Message ---
--- Begin Message ---
Source: r-cran-surveillance
Source-Version: 1.0.3-2
We believe that the bug you reported is fixed in the latest version of
r-cran-surveillance, which is due to be installed in the Debian FTP archive:
r-cran-surveillance_1.0.3-2.diff.gz
to pool/contrib/r/r-cran-surveillance/r-cran-surveillance_1.0.3-2.diff.gz
r-cran-surveillance_1.0.3-2.dsc
to pool/contrib/r/r-cran-surveillance/r-cran-surveillance_1.0.3-2.dsc
r-cran-surveillance_1.0.3-2_i386.deb
to pool/contrib/r/r-cran-surveillance/r-cran-surveillance_1.0.3-2_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 539...@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 r-cran-surveillance
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: Wed, 29 Jul 2009 19:25:11 +0200
Source: r-cran-surveillance
Binary: r-cran-surveillance
Architecture: source i386
Version: 1.0.3-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:
r-cran-surveillance - development and the evaluation of epidemiological
outbreak detect
Closes: 539094
Changes:
r-cran-surveillance (1.0.3-2) unstable; urgency=low
.
* Change section to contrib/gnu-r
* Add r-cran-vr and r-cran-colorspace to build-depends to fix FTBFS due to
missing mass and colorspace libraries (Thanks to Scott Kitterman
<sc...@kitterman.com> for providing the patch)
Closes: #539094
* Standards-Version: 3.8.2 (no changes needed)
Checksums-Sha1:
90ddc6090d51a32713d010a5dfc52a254f7585cd 1508 r-cran-surveillance_1.0.3-2.dsc
07d8ba94c6ee72873e4a6272cf5603207185cc45 1979
r-cran-surveillance_1.0.3-2.diff.gz
75375dcf710e519cbb37922fd2f7854967434a7c 1160400
r-cran-surveillance_1.0.3-2_i386.deb
Checksums-Sha256:
9e1c4de3afaf2daac03a8635895ddd1b102b3c6e3700d9b08aca6bc8ee5fbf16 1508
r-cran-surveillance_1.0.3-2.dsc
2eae3e7feb3880a0f36e168837606f1e30ece9ec255b42513c0dffaa9456cff0 1979
r-cran-surveillance_1.0.3-2.diff.gz
3eacf56c1d0e326f8e9eb537678c000cecfa3c1d401626a0c381650a0e958c5c 1160400
r-cran-surveillance_1.0.3-2_i386.deb
Files:
c5113e89daf7daf0a931c24e2586907a 1508 contrib/gnu-r optional
r-cran-surveillance_1.0.3-2.dsc
c3a6627ed7e0933b79e380f1d79c1846 1979 contrib/gnu-r optional
r-cran-surveillance_1.0.3-2.diff.gz
661ca2d84b177e8279851393c955f735 1160400 contrib/gnu-r optional
r-cran-surveillance_1.0.3-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkpwiesACgkQYDBbMcCf01rrAwCfevKkV82iWnwsfU/iqteVWC+t
67EAnRpENgMtvLA/l5M8C4W6KcPeHFua
=lz8r
-----END PGP SIGNATURE-----
--- End Message ---
