Nothing strange about this. As I said, all packages are built and
checked daily and the build report is updated every day with the new
results. But there is a lag between your changes in svn and what
you see in the build report. More precisely, yesterday's report
didn't reflect your latest changes
Thanks, Hervé. Very strange, when I checked that link earlier today, it
appeared to still have errors. All good now!
On Sun, Apr 23, 2017 at 4:49 PM, Hervé Pagès wrote:
> Hi Maia,
>
> On 04/23/2017 10:09 AM, Maia Smith wrote:
>
>> Just an update - the checked in code is passing R CMD check on my
Hi Maia,
On 04/23/2017 10:09 AM, Maia Smith wrote:
Just an update - the checked in code is passing R CMD check on my computer
(no errors, 1 warning), and has a version bump from 0.99.9 to 0.99.10, but
I still haven't seen a build attempt on bioconductor since I committed the
code a few days ago.
Yes, I know.
I wanted only to mention that this error is hopefully corrected in
today's update.
Christian
On 04/23/17 22:19, Hervé Pagès wrote:
On 04/23/2017 12:15 PM, cstrato wrote:
Dear Herve,
I have just seen that the newest build xps_1.3.3:
https://urldefense.proofpoint.com/v2/url?u=htt
On 04/23/2017 12:15 PM, cstrato wrote:
Dear Herve,
I have just seen that the newest build xps_1.3.3:
https://urldefense.proofpoint.com/v2/url?u=http-3A__bioconductor.org_checkResults_devel_bioc-2DLATEST_xps_veracruz2-2Dbuildsrc.html&d=DwIDaQ&c=eRAMFD45gAfqt84VtBcfhQ&r=BK7q3XeAvimeWdGbWY_wJYbW0WY
Dear Herve,
I have just seen that the newest build xps_1.3.3:
http://bioconductor.org/checkResults/devel/bioc-LATEST/xps/veracruz2-buildsrc.html
still results in an error.
This is probably due to the fact that it still requires $ROOTSYS.
I hope that my current upload xps_1.3.4 has eliminated thi
Just an update - the checked in code is passing R CMD check on my computer
(no errors, 1 warning), and has a version bump from 0.99.9 to 0.99.10, but
I still haven't seen a build attempt on bioconductor since I committed the
code a few days ago. I'm a bit worried because I know the release is
occur
Dear Herve,
Since some users report problems since many years that the libs are
found in '/usr/local/root/lib/root', I agree that it is a good idea
to set LDFLAGS also to
LDFLAGS = ... -rpath $(shell $(ROOTCONFIG) --prefix)/lib/root
I have just uploaded version xps_1.3.4 to BioC devel.
In t
A little more on this.
Martin pointed out the problem is likely the nested quotes in the
textVersion field instead of the double dash in the pages field.
The hint is in the build report output
http://bioconductor.org/checkResults/3.5/bioc-LATEST/pathprint/malbec2-checksrc.html
where it says t
Looking at the build logs we see this error for the data package:
ERROR: extractCitations
tarball:
/home/biocadmin/PACKAGES/3.5/data/experiment/src/contrib/pathprintGEOData_1.0.0.tar.gz
error: /tmp/Rtmpo8k7A4/pathprintGEOData/inst/CITATION:18:181:
unexpected symbol
17: pages ="68--81",
18:
Dear all,
I have updated the CITATION file in my packages pathprint and
pathprintGEOData (to be ready for the release), but in the landing page the
old citation still shows (even the package version in the citation is
different than the one in the details). How can I mend this? Thanks in
advance!
11 matches
Mail list logo
