On 1 June 2018 at 21:43, Graham Inggs wrote:
> r-cran-fastica also seems to be missing r-api-3.4 so doesn't appear on
> the tracker, but needs a rebuild.
Sorry, my mistake, please ignore.
r-cran-fastica also seems to be missing r-api-3.4 so doesn't appear on
the tracker, but needs a rebuild.
On Thu, May 31, 2018 at 10:36:27PM -0700, Jonathan Nieder wrote:
>...
> I don't think most users of testing realize that
> they also need to include stable-backports in sources.list to get
> security fixes.
>...
No, this wouldn't get them all security fixes.
It would only make a difference when
Processing control commands:
> block 896667 by -1
Bug #896667 [release.debian.org] transition: r-base-3.5
896667 was not blocked by any bugs.
896667 was not blocking any bugs.
Added blocking bug(s) of 896667: 900591
--
896667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896667
900591:
On 01/06/2018 17:19, Dirk Eddelbuettel wrote:
This is now taken care of: dbi_1.0.0-2 was just uploaded
Thanks Dirk!
Another weirdness I have come across in Ubuntu today is rebuilds of
r-cran-expm and r-cran-mlmrev fail with the following:
dh_auto_install: warning: can't parse dependency
On 1 June 2018 at 06:32, Dirk Eddelbuettel wrote:
|
| On 1 June 2018 at 12:41, Graham Inggs wrote:
| | A warning: src:dbi has a hard-coded dependency on r-api-3.4 in
| | debian/control, and src:wkward has the same in debian/rules.
|
| That was from when dh-r was borked and could not cope with
On 1 June 2018 at 13:37, Emilio Pozuelo Monfort wrote:
| On 01/06/18 13:32, Dirk Eddelbuettel wrote:
| >
| > On 1 June 2018 at 11:54, Emilio Pozuelo Monfort wrote:
| > | Scheduled for cluster foreign rmpi nlme rmatrix robustbase lmtest
survival lme4
| > | tseries.
| >
| > Why is that needed?
On Fri, Jun 01, 2018 at 11:54:35AM +0200, Emilio Pozuelo Monfort wrote:
> > I don't see anything wrong with these source packages, as simply rebuilding
> > them
> > is enough for the r-api-3.5 dependency to appear.
> >
> > Was there a bug in dh-r at the time these were uploaded?
It smells like
On 01/06/18 13:32, Dirk Eddelbuettel wrote:
>
> On 1 June 2018 at 11:54, Emilio Pozuelo Monfort wrote:
> | Scheduled for cluster foreign rmpi nlme rmatrix robustbase lmtest survival
> lme4
> | tseries.
>
> Why is that needed? Aren't ALL binary packages auto-rebuilt?
Depending on your
On 1 June 2018 at 12:41, Graham Inggs wrote:
| A warning: src:dbi has a hard-coded dependency on r-api-3.4 in
| debian/control, and src:wkward has the same in debian/rules.
That was from when dh-r was borked and could not cope with srcname != pkgname.
I can look into fixing it this morning
On 1 June 2018 at 11:54, Emilio Pozuelo Monfort wrote:
| Scheduled for cluster foreign rmpi nlme rmatrix robustbase lmtest survival
lme4
| tseries.
Why is that needed? Aren't ALL binary packages auto-rebuilt?
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
A warning: src:dbi has a hard-coded dependency on r-api-3.4 in
debian/control, and src:wkward has the same in debian/rules.
I was unable to find any more [1][2] like these codesearch.d.o.
[1] https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+r-api-3.4
[2]
On 01/06/2018 11:54, Emilio Pozuelo Monfort wrote:
Scheduled for cluster foreign rmpi nlme rmatrix robustbase lmtest survival lme4
tseries.
Thanks!
On 01/06/18 11:44, Graham Inggs wrote:
> On 01/06/2018 10:09, Graham Inggs wrote:
>> On 1 June 2018 at 09:24, Graham Inggs wrote:
>>> Does anyone know why some packages, e.g. cluster, foreign, nlme and
>>> rmatrix appear different on the tracker [1]?
>>>
>>> Did they lose their dependency on
On 01/06/2018 10:09, Graham Inggs wrote:
On 1 June 2018 at 09:24, Graham Inggs wrote:
Does anyone know why some packages, e.g. cluster, foreign, nlme and
rmatrix appear different on the tracker [1]?
Did they lose their dependency on r-api-3.4 somewhere along the line?
Was this intentional?
Do
On 1 June 2018 at 09:24, Graham Inggs wrote:
> Does anyone know why some packages, e.g. cluster, foreign, nlme and
> rmatrix appear different on the tracker [1]?
>
> Did they lose their dependency on r-api-3.4 somewhere along the line?
> Was this intentional?
> Do they also need to be rebuilt?
>
Does anyone know why some packages, e.g. cluster, foreign, nlme and
rmatrix appear different on the tracker [1]?
Did they lose their dependency on r-api-3.4 somewhere along the line?
Was this intentional?
Do they also need to be rebuilt?
[1]
Hi Sébastien,
On Fri, Jun 01, 2018 at 08:57:48AM +0200, Sébastien Villemot wrote:
> On Fri, Jun 01, 2018 at 08:20:48AM +0200, Andreas Tille wrote:
>
> > I have uploaded r-cran-pkgconfig at Thu May 31 20:37:04 BST 2018 [1] and it
> > was accepted to unstable at Thu May 31 20:53:21 BST 2018 [2].
On Fri, Jun 01, 2018 at 08:20:48AM +0200, Andreas Tille wrote:
> I have uploaded r-cran-pkgconfig at Thu May 31 20:37:04 BST 2018 [1] and it
> was accepted to unstable at Thu May 31 20:53:21 BST 2018 [2]. However,
> packages.d.o states it has r-api-3.4! :-(
It's because r-cran-pkgconfig
Hi Andreas
On 1 June 2018 at 08:20, Andreas Tille wrote:
> I have uploaded r-cran-pkgconfig at Thu May 31 20:37:04 BST 2018 [1] and it
> was accepted to unstable at Thu May 31 20:53:21 BST 2018 [2]. However,
> packages.d.o states it has r-api-3.4! :-(
Check the build logs [1], it seems it
Hi Emilio,
On Thu, May 31, 2018 at 09:25:50AM +0200, Emilio Pozuelo Monfort wrote:
>
> Cool, it's almost built everywhere now.
I have uploaded r-cran-pkgconfig at Thu May 31 20:37:04 BST 2018 [1] and it
was accepted to unstable at Thu May 31 20:53:21 BST 2018 [2]. However,
packages.d.o states
21 matches
Mail list logo
