Hey all,
I can see all is green but I still get messages about failing builds and on
the website shows build error. Do I still have to do something? Thanks in
advance.
Regards,
Sokratis
On Thu, Aug 10, 2023 at 2:53 PM Martin Grigorov
wrote:
> Hi,
>
> All is green at
> https://bioconductor.org/checkResults/3.18/bioc-LATEST/omada/
>
> Regards,
> Martin
>
> On Thu, Aug 10, 2023 at 9:44 AM Sokratis Kariotis <
> sokratiskario...@gmail.com> wrote:
>
>> Hey all,
>>
>> Is this fixed now? I think I can see all pass, but on the actual website
>> its still on error. Thanks!
>>
>> Cheers,
>> Sokratis
>>
>> On Tue, Aug 1, 2023 at 4:25 PM Sokratis Kariotis <
>> sokratiskario...@gmail.com> wrote:
>>
>>> Hey,
>>>
>>> I believe I have resolved the conflicts and now can run: *git push
>>> upstream main:devel*
>>> with Everything up-to-date as a result. However, *git push origin main*
>>> does not yield
>>> anything and it keeps hanging without a message. I checked
>>> https://bioconductor.org/checkResults/3.18/bioc-LATEST/omada/
>>> and the last commit is April.
>>>
>>>
>>> On Mon, Jul 31, 2023 at 10:01 PM Kern, Lori <
>>> lori.sheph...@roswellpark.org> wrote:
>>>
You'll need to find the merge conflicts and resolve them. Recommit
those files and then it should go.
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
Sokratis Kariotis
*Sent:* Monday, July 31, 2023 7:27 AM
*To:* Martin Grigorov
*Cc:* bioc-devel@r-project.org
*Subject:* Re: [Bioc-devel] Omada package failing due to removed
dependency
Tried but its Already up to date.
On Mon, 31 Jul 2023, 7:22 pm Martin Grigorov, <
martin.grigo...@gmail.com>
wrote:
> Hi Sokratis,
>
> You need to do "git pull --rebase" before trying to push.
> Most probably the version has been bumped upstream.
>
> Regards,
> Martin
>
> On Mon, Jul 31, 2023 at 2:16 PM Sokratis Kariotis <
> sokratiskario...@gmail.com> wrote:
>
>> Hey all,
>>
>> I created a new key and now I can commit etc but there is a conflict
that
>> is not allowing me to go ahead.
>>
>> My commands:
>> git add .
>> git commit -m "Update metrics"
>> git push upstream main:devel
>>
>> *The above results in the following error:*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Enumerating objects: 19, done.Counting objects: 100% (17/17),
done.Delta
>> compression using up to 16 threadsCompressing objects: 100% (11/11),
>> done.Writing objects: 100% (11/11), 4.78 KiB | 4.78 MiB/s,
done.Total 11
>> (delta 7), reused 0 (delta 0), pack-reused 0remote: Error: You
cannot push
>> without resolving merge conflicts.remote:remote: Please check the
files in
>> the commit pushed to the git-serverremote: for merge conflict
markers like
>> '<<<', '', '>>>'.remote:To
>> git.bioconductor.org:packages/omada ! [remote rejected] main ->
devel
>> (pre-receive hook declined)error: failed to push some refs to
>> 'git.bioconductor.org:packages/omada'*
>>
>>
>>
>> On Mon, Jul 31, 2023 at 3:36 PM Mike Smith
wrote:
>>
>> > Hi Sokratis,
>> >
>> > Everything in Bioconductor is built around the central
Bioconductor git
>> > repositories. The only way to get changes out to users is to
commit
>> them
>> > to git.bioconductor.org and then the build system will pick those
up,
>> run
>> > the tests and checks, create new versions of packages, and make
them
>> > available for distribution.
>> >
>> > Perhaps you can include the git command you're running to submit
the
>> > changes and a copy of the exact error you're receiving. That
might help
>> > the team suggest a solution.
>> >
>> > Best regards,
>> > Mike
>> >
>> > On Fri, 28 Jul 2023 at 08:32, Sokratis Kariotis <
>> > sokratiskario...@gmail.com> wrote:
>> >
>> >> Hey both,
>> >>
>> >> I have edited the package code but I'm having some difficulties
>> pushing it
>> >> to trigger another build (github passphrase). Is there another
way to
>> >> trigger the build? Thanks!
>> >>
>> >> Cheers,
>> >> Sokratis
>> >>
>> >> On Wed, Jul 12, 2023 at 1:43 AM Kern, Lori <
>> lori.sheph...@roswellpark.org
>> >> >
>> >> wrote:
>> >>
>> >> > We can give you a little more time (a few weeks) to fix the
package
>> but
>> >> > please fix as soon as possible to avoid
