On 24 September 2017 at 22:20, Charles Plessy wrote:
| Le Sat, Sep 23, 2017 at 11:58:20AM -0500, Dirk Eddelbuettel a écrit :
| >
| > May I assume that some of you who sp tiredlessly argued for it will now
liase
| > with the release team to get 500+ forcefully rebuilt?
|
| > r-base
Le Sat, Sep 23, 2017 at 11:58:20AM -0500, Dirk Eddelbuettel a écrit :
>
> May I assume that some of you who sp tiredlessly argued for it will now liase
> with the release team to get 500+ forcefully rebuilt?
> r-base (3.4.1.20170921-1) unstable; urgency=medium
>
> * Initial rc build (r73337)
On 24 September 2017 at 13:37, Andreas Tille wrote:
| On Sat, Sep 23, 2017 at 11:58:20AM -0500, Dirk Eddelbuettel wrote:
| >
| > r-base (3.4.1.20170921-1) unstable; urgency=medium
|
| > * Initial rc build (r73337) of R 3.4.2 expected for Sep 28
|
On Sat, Sep 23, 2017 at 11:58:20AM -0500, Dirk Eddelbuettel wrote:
>
> r-base (3.4.1.20170921-1) unstable; urgency=medium
> * Initial rc build (r73337) of R 3.4.2 expected for Sep 28
BTW, shouldn't this rather target to experimental?
On Wed, 2017-09-20 at 11:34 +0200, Sébastien Villemot wrote:
> It consists in bumping the "r-api-3" value to "r-api-3.4", or "r-api-
> 3a" (or basically whatever you want, as long as it is different from
> previous values).
>
> This takes less than 5 minutes of your time, is clean and robust, and
On Wed, Sep 20, 2017 at 08:23:30AM +0200, Andreas Tille wrote:
> On Tue, Sep 19, 2017 at 03:25:56PM +0200, Johannes Ranke wrote:
> > > The whole bug report was, pardon my French, complete and utter nonsense.
> >
> > Wow. Complete and utter. A bug report affecting 100+ packages that was
> >
On Tue, Sep 19, 2017 at 03:25:56PM +0200, Johannes Ranke wrote:
> > The whole bug report was, pardon my French, complete and utter nonsense.
>
> Wow. Complete and utter. A bug report affecting 100+ packages that was merged
> with two independent bug reports (861684, 862969). And that took from
Am Dienstag, 19. September 2017, 07:40:19 CEST schrieb Dirk Eddelbuettel:
> On 19 September 2017 at 14:15, Johannes Ranke wrote:
> | > But you escalated it
> |
> | Mhm. I reported a bug with severity "normal". Maybe the language I used
> | was
> | too dramatic?
>
> The whole bug report was,
On 19 September 2017 at 14:15, Johannes Ranke wrote:
| > But you escalated it
|
| Mhm. I reported a bug with severity "normal". Maybe the language I used was
| too dramatic?
The whole bug report was, pardon my French, complete and utter nonsense. The
folks who needed to know already knew.
But
> But you escalated it
Mhm. I reported a bug with severity "normal". Maybe the language I used was
too dramatic?
> And the net effect is no current R in testing for a year. Really not a good
> outcome.
This could still be overcome by introducing versioned Breaks, that could be
removed then
On 19 September 2017 at 11:07, Johannes Ranke wrote:
| Am Montag, 18. September 2017, 10:39:02 CEST schrieb Dirk Eddelbuettel:
| > Common knowledge. I referenced it half-a-dozen times in the damned thread
| > about the binNMUs.
|
| This (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868558)
Am Montag, 18. September 2017, 10:39:02 CEST schrieb Dirk Eddelbuettel:
> On 18 September 2017 at 22:41, Charles Plessy wrote:
> | Hello everybody,
> |
> | I just wanted to relay the information that some R packages will need a
> | rebuild after the next upgrade of R. (see the email forwarded
On 18 September 2017 at 22:41, Charles Plessy wrote:
| Hello everybody,
|
| I just wanted to relay the information that some R packages will need a
| rebuild after the next upgrade of R. (see the email forwarded below.)
Common knowledge. I referenced it half-a-dozen times in the damned thread
Uff, thanks for letting us know in advance!! I believe this means another
fresh repository in CRAN for the corresponding R release...
Johannes
Am Montag, 18. September 2017, 22:41:04 CEST schrieb Charles Plessy:
> Hello everybody,
>
> I just wanted to relay the information that some R packages
14 matches
Mail list logo
