[Bioc-devel] Applying changes to existing package

[Martin Morgan]

On 03/19/2018 08:28 AM, Christian Oertlin wrote:
> Thank you for the explanation - I indeed ran build and check but before the merge with the upstream branch. So this error slipped through.
> 
> For the RELEASE_3_6 branch the version should be 1.0.1 then? just to be sure.

Yes, the current release version is 1.0.0, so the next release version 
is 1.0.1.

Martin

> ________________________________________
> From: Martin Morgan [martin.morgan at roswellpark.org]
> Sent: 19 March 2018 13:09
> To: Christian Oertlin; Shepherd, Lori; Sean Davis
> Cc: bioc-devel at r-project.org
> Subject: Re: [Bioc-devel] Applying changes to existing package
> 
> On 03/19/2018 03:20 AM, Christian Oertlin wrote:
>> Hej,
>>
>> I just wanted to check the build report/version number of the anota2seq package, however it is not listed in the build report anymore.
>>
>>
>>
>> http://bioconductor.org/checkResults/ (it cannot be found in this list anymore- which was the case prior to the update)
>>
>> what could have happened?
> 
> Usually this means that the package is fundamentally broken. In this
> case the DESCRIPTION file in git is not formatted correctly
> 
> $ cat DESCRIPTION
> Package: anota2seq
> <<<<<<< HEAD
> Version: 1.0.1
> =======
> Version: 1.1.0
>   >>>>>>> upstream/master
> 
> 
> This the result of a 'merge conflict' and you need to resolve it (edit
> DESCRIPTION file) so that it is correct. Remember that you are
> contributing to the 'devel' branch, where the current version of your
> package is 1.1.0. So the next version should be 1.1.1.
> 
> Remember also that you can build and check your package locally before
> pushing it, so that these errors are easily spotted.
> 
> Martin
> 
>>
>> Christian
>> ________________________________
>> From: Shepherd, Lori [Lori.Shepherd at RoswellPark.org]
>> Sent: 16 March 2018 12:32
>> To: Sean Davis; Christian Oertlin
>> Cc: bioc-devel at r-project.org
>> Subject: Re: [Bioc-devel] Applying changes to existing package
>>
>>
>> you can also check the build and check status on out systems off the daily build reports.  It normally can take up to 24 hours for changes to appear but you should see the version number bump.
>>
>>
>> http://bioconductor.org/checkResults/
>>
>>
>> Lori Shepherd
>>
>> Bioconductor Core Team
>>
>> Roswell Park Cancer Institute
>>
>> Department of Biostatistics & Bioinformatics
>>
>> Elm & Carlton Streets
>>
>> Buffalo, New York 14263
>>
>> ________________________________
>> From: Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of Sean Davis <seandavi at gmail.com>
>> Sent: Friday, March 16, 2018 6:31:04 AM
>> To: Christian Oertlin
>> Cc: bioc-devel at r-project.org
>> Subject: Re: [Bioc-devel] Applying changes to existing package
>>
>> Hi, Christian.
>>
>> There is not yet a browsable version of the Bioconductor git repository.
>> The way to check git.bioconductor.org status is, as you noted, to work with
>> a checkout of the repository locally. If you'd like a more visual view of
>> your local checkout, you might take a look at one of several desktop
>> repository browsers.
>>
>> Sean
>>
>> On Fri, Mar 16, 2018 at 5:53 AM Christian Oertlin <christian.oertlin at ki.se>
>> wrote:
>>
>>> Hello everyone,
>>>
>>> I am the maintainer of the anota2seq package.  The package was accepted
>>> for release 3.6 and is on the bioconductor webpage.
>>>
>>> I had minor updates for the package which I pushed to the github
>>> repositories by following the steps here:
>>> https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
>>>
>>> I can see the changes in my github webpage ChrOertlin/anota2seq/
>>>
>>> This might be a very naive question. When I follow to
>>> https://git.bioconductor.org/ I can find the package as listed. Is there
>>> a way to see the contents of that repository other from changing into the
>>> upstream git branch locally, for example a website like my personal github
>>> account? Just to check if everything is in the right place in a more visual
>>> way...
>>>
>>>
>>> Cheers,
>>> Christian
>>>
>>>           [[alternative HTML version deleted]]
>>>
>>> _______________________________________________
>>> Bioc-devel at r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>>
>> --
>> --
>> Sean Davis, MD, PhD
>> Center for Cancer Research
>> National Cancer Institute
>> National Institutes of Health
>> Bethesda, MD 20892
>> https://seandavi.github.io/
>> https://twitter.com/seandavis12
>>
>>           [[alternative HTML version deleted]]
>>
>> _______________________________________________
>> Bioc-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>
>> 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 at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>
> 
> 
> 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.
> 


This email message may contain legally privileged and/or...{{dropped:2}}