Your message dated Tue, 09 Oct 2012 21:49:19 +0200
with message-id <[email protected]>
and subject line Re: Bug#688980: unblock: r-cran-pscl/1.03.10-1.1
has caused the Debian Bug report #688980,
regarding unblock: r-cran-pscl/1.03.10-1.1
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.)
--
688980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688980
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
In order to fix #684823, which solution does the Release Team prefer:
- unblock r-cran-pscl/1.03.10-1.1 which is currently in sid and contains the
fix,
- or me making an upload to t-p-u, with the attached patch?
Thanks,
diff -Nru r-cran-pscl-1.03.5/debian/changelog r-cran-pscl-1.03.5/debian/changelog
--- r-cran-pscl-1.03.5/debian/changelog 2010-04-14 08:28:46.000000000 +0200
+++ r-cran-pscl-1.03.5/debian/changelog 2012-09-27 21:16:15.000000000 +0200
@@ -1,3 +1,10 @@
+r-cran-pscl (1.03.5-1+deb70u1) testing-proposed-updates; urgency=low
+
+ * Non-maintainer upload.
+ * replace-obsolete-pythag.patch: new patch, fixes FTBFS (Closes: #684823)
+
+ -- Sébastien Villemot <[email protected]> Thu, 27 Sep 2012 21:15:23 +0200
+
r-cran-pscl (1.03.5-1) unstable; urgency=low
* New upstream release.
diff -Nru r-cran-pscl-1.03.5/debian/patches/replace-obsolete-pythag.patch r-cran-pscl-1.03.5/debian/patches/replace-obsolete-pythag.patch
--- r-cran-pscl-1.03.5/debian/patches/replace-obsolete-pythag.patch 1970-01-01 01:00:00.000000000 +0100
+++ r-cran-pscl-1.03.5/debian/patches/replace-obsolete-pythag.patch 2012-09-27 21:14:49.000000000 +0200
@@ -0,0 +1,19 @@
+Description: Use hypot instead of pythag
+ The pythag function has been definitely abandoned in favor of hypot in
+ R 2.14.0, see /usr/share/doc/r-base-core/changelog.gz
+Origin: upstream, version 1.03.10
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684823
+Last-Update: 2012-08-27
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/pi.c
++++ b/src/pi.c
+@@ -13,7 +13,7 @@
+ GetRNGstate();
+
+ for(i=0;i<*n;i++){
+- d = pythag(unif_rand(),unif_rand());
++ d = hypot(unif_rand(),unif_rand());
+ if(d<1.0)
+ (*z)++;
+ }
diff -Nru r-cran-pscl-1.03.5/debian/patches/series r-cran-pscl-1.03.5/debian/patches/series
--- r-cran-pscl-1.03.5/debian/patches/series 1970-01-01 01:00:00.000000000 +0100
+++ r-cran-pscl-1.03.5/debian/patches/series 2012-09-27 21:14:49.000000000 +0200
@@ -0,0 +1 @@
+replace-obsolete-pythag.patch
--- End Message ---
--- Begin Message ---
On 09/10/2012 19:37, Sébastien Villemot wrote:
> Mehdi Dogguy <[email protected]> writes:
>
>> On 27/09/2012 21:34, Sébastien Villemot wrote:
>>> Package: release.debian.org Severity: normal User:
>>> [email protected] Usertags: unblock
>>>
>>> In order to fix #684823, which solution does the Release Team
>>> prefer:
>>>
>>> - unblock r-cran-pscl/1.03.10-1.1 which is currently in sid and
>>> contains the fix,
>>>
>>> - or me making an upload to t-p-u, with the attached patch?
>>>
>>
>> I think the best way forwad would be to upload a targeted fix to
>> t-p-u. Please go ahead and thanks for your work!
>
> Thanks, version 1.03.5-1+deb70u1 uploaded to t-p-u.
>
Approved.
Cheers.
--
Mehdi Dogguy مهدي الدڤي
--- End Message ---
