Re: [Bioc-devel] Not receiving notice after valid push to conductor, how to check status

2022-01-03 Thread Kern, Lori
Once your package is accepted into Bioconductor it is no longer on the Single 
Package Builder for new submissions and therefore you will not get an on-demand 
build report.
Packages accepted to Bioconductor are built once daily and the reports can be 
found at:
http://bioconductor.org/checkResults/





Lori Shepherd - Kern

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263


From: Bioc-devel  on behalf of Jiping Wang 

Sent: Monday, January 3, 2022 11:56 AM
To: bioc-devel@r-project.org 
Subject: [Bioc-devel] Not receiving notice after valid push to conductor, how 
to check status

Hi,

Do we still receive the automatic notice after pushing package updates (with 
version bump) to Bioconductor? I recently submitted updates of RiboDiPA 
package, but I didn�t receive automatic report from bioc-issue-bot? Where 
should I check the status of it? In the past, I remember I receive automatic 
update on it from bioc-issue-bot. Something like following:
�Received a valid push on git.bioconductor.org; starting a build for commit id: 
93b588adba022eaf14549e97a53f45c89d19a8f9� from bioc-issue-...@bioconductor.org
Thanks for help.

Jiping Wang

[[alternative HTML version deleted]]



This email message may contain legally privileged and/or confidential 
information.  If you are not the intended recipient(s), or the employee or 
agent responsible for the delivery of this message to the intended 
recipient(s), you are hereby notified that any disclosure, copying, 
distribution, or use of this email message is prohibited.  If you have received 
this message in error, please notify the sender immediately by e-mail and 
delete this email message from your computer. Thank you.
[[alternative HTML version deleted]]

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


[Bioc-devel] Not receiving notice after valid push to conductor, how to check status

2022-01-03 Thread Jiping Wang
Hi,

Do we still receive the automatic notice after pushing package updates (with 
version bump) to Bioconductor? I recently submitted updates of RiboDiPA 
package, but I didn�t receive automatic report from bioc-issue-bot? Where 
should I check the status of it? In the past, I remember I receive automatic 
update on it from bioc-issue-bot. Something like following:
�Received a valid push on git.bioconductor.org; starting a build for commit id: 
93b588adba022eaf14549e97a53f45c89d19a8f9� from bioc-issue-...@bioconductor.org
Thanks for help.

Jiping Wang

[[alternative HTML version deleted]]

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


Re: [Bioc-devel] Git recognizes me but denies access

2022-01-03 Thread Nitesh Turaga
Is this resolved Philipp? 

‘destiny’ seems to be failing on windows still 
http://bioconductor.org/checkResults/release/bioc-LATEST/destiny/. 

Best,

Nitesh 


Nitesh Turaga
Scientist II, Department of Data Science,
Bioconductor Core Team Member
Dana Farber Cancer Institute

> On Dec 19, 2021, at 7:17 AM, Philipp A.  wrote:
> 
> Seems like I fixed it! Is there anything else I have to do?
> 
> destiny is green now on your build bots (linux and mac, I don’t see windows
> there but there seems to be a build artifact on destiny’s landing page).
> 
> Seems like checking doesn’t use BiocCheck there, is that no longer used? If
> it were used, it would break because it doesn’t consider my .ipynb files to
> be vignettes.
> 
> Best, Phil
> 
> Am Mo., 13. Dez. 2021 um 19:55 Uhr schrieb Philipp A. :
> 
>> Am Mo., 13. Dez. 2021 um 14:24 Uhr schrieb Kern, Lori <
>> lori.sheph...@roswellpark.org>:
>> 
>>> I don't see any changes on the RELEASE_3_14 branch.  Please make sure to
>>> push to the RELEASE_3_14 branch […]
>>> 
>> 
>> Understood! Done, I cherry-picked all the commits over.
>> 
>> Am Mo., 13. Dez. 2021 um 19:39 Uhr schrieb Hervé Pagès <
>> hpages.on.git...@gmail.com>:
>> 
>>> Just in case someone is watching this thread and wondering what we're
>>> doing with the LaTeX environment on the build machines.
>>> […]
>>> All these installations are stock installations.
>> 
>> 
>> That’s extremely weird, as I also use stock TexLive to locally build
>> things, and everything works flawlessly.
>> 
>> Well, I circumvented the problem by building HTML vignettes instead, which
>> is probably more convenient for users anyway.
>> 
> 
>   [[alternative HTML version deleted]]
> 
> ___
> Bioc-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


Re: [Bioc-devel] DeMixT Bioconductor maintainer

2022-01-03 Thread Nitesh Turaga
Hi Peng and Shuai,

Happy new year.

I’ve added Shuai as a maintainer to the package.

Shuai, you need to activate your BiocCredentials account with the email you 
gave. 

https://git.bioconductor.org/BiocCredentials/account_activation. 

Once you activate and add your SSH keys, you’ll have access. Please change the 
maintainer once this happens on the DESCRIPTION file.

Best,

Nitesh 

Nitesh Turaga
Scientist II, Department of Data Science,
Bioconductor Core Team Member
Dana Farber Cancer Institute

> On Dec 28, 2021, at 5:36 PM, Yang,Peng  wrote:
> 
> Hi Bioconductor team,
>  
> I would like to change maintainer for our DeMixT package.
> https://bioconductor.org/packages/release/bioc/html/DeMixT.html
>  
> Below is the contact information.
> maintainer: Shuai Guo
> email: shuai@uth.tmc.edu (cc'd in this email)
>  
> I will update the new maintainer information in DESCRIPTION, and push  
> to the Bioconductor (devel brunch) very soon.
>  
> Thanks,
> Peng

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel