[Bioc-devel] Synching version numbers went wrong

White, Shana (vandersm) v@nder@m @ending from m@il@uc@edu
Mon Jul 23 21:20:16 CEST 2018


Hi Mike,


My colleague and I have spent a few hours attempting to fix this problem; we can only propogate changes with version numbers 1.5x and cannot do 1.6x or 1.7x on the devel branch - it seems like the  Bioconductor automatic checks are preventing us from updating the files and at this point we believe the version number can only be fixed from within Bioconductor.  Does the Bioconductor team need to manually change the version number or should we try to force push the changes ourselves? Please let me know if you need any additional details.


Best,



Shana White
Ph. D Candidate  - Biostatistics + Bioinformatics<https://med.uc.edu/eh/divisions/bio>
Predoctoral Fellow - MECEH<https://med.uc.edu/eh/divisions/epi/programs/meceh>
Room 318 Kettering Labs
vandersm using mail.uc.edu
937-657-8289


________________________________
From: Mike Smith <grimbough using gmail.com>
Sent: Thursday, July 12, 2018 4:57:55 AM
To: White, Shana (vandersm)
Cc: bioc-devel
Subject: Re: [Bioc-devel] Synching version numbers went wrong

Hi Shana,

It looks like the release version of KEGGlincs is 1.6.x and the devel version should be 1.7.x.    When you're committing to the master branch of git.bioconductor.org<http://git.bioconductor.org> this equates to the devel version and there's a check in place to prevent even version numbers being committed here.  My recommendation is to make sure that your DESCRIPTION file for that commit has a version number of 1.7.x which should put things back on track.

If you also need to add your changes to the release version (I guess the current build error means you do) then you can see the instructions at https://bioconductor.org/developers/how-to/git/bug-fix-in-release-and-devel/ Step 4 details incorporating changes from one branch to another, and then you need to manually make sure the DESCRIPTION file for committing to the RELEASE_3_7 branch contains a 1.6.x version number.

Mike

On Wed, 11 Jul 2018 at 18:19, White, Shana (vandersm) <vandersm using mail.uc.edu<mailto:vandersm using mail.uc.edu>> wrote:
Hello, when attempting to fix a bug [introduced into my package] and propagate the changes I somehow managed to roll back the middle version number on one of my branches and ended up with the following error message when attempting to correct my mistake:



Error message:


shanas-macbook:KEGGlincs shanabanana$ git push upstream master

Counting objects: 3, done.

Delta compression using up to 4 threads.

Compressing objects: 100% (3/3), done.

Writing objects: 100% (3/3), 298 bytes | 0 bytes/s, done.

Total 3 (delta 2), reused 0 (delta 0)

remote: Error: Illegal version bump from '1.5.1' to '1.6.1'. Check

remote: http://bioconductor.org/developers/how-to/version-numbering/

remote: for details


Many thanks,


Shana White
Ph. D Candidate  - Biostatistics + Bioinformatics<https://med.uc.edu/eh/divisions/bio>
Predoctoral Fellow - MECEH<https://med.uc.edu/eh/divisions/epi/programs/meceh>
Room 318 Kettering Labs
vandersm using mail.uc.edu<mailto:vandersm using mail.uc.edu>
937-657-8289


        [[alternative HTML version deleted]]

_______________________________________________
Bioc-devel using r-project.org<mailto:Bioc-devel using r-project.org> mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

	[[alternative HTML version deleted]]



More information about the Bioc-devel mailing list