caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Helmut Brandl <helmut.brandl@gmx.net>
Cc: Romain Calascibetta <romain.calascibetta@gmail.com>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Policy to merge pull requests in the opam repository
Date: Wed, 17 May 2017 00:03:40 +0800	[thread overview]
Message-ID: <04466E7A-A016-47DE-A16E-CD4A3110B00C@recoil.org> (raw)
In-Reply-To: <3B072E90-5950-4422-94C1-390A89BB4F11@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 3185 bytes --]

There is a cron job that runs hourly, which rebuilds https://opam.ocaml.org with the latest packages.  It should normally update within the hour, and your PR was merged 20 minutes ago.  If it hasn't shown up within the next 60-90 minutes, then begin a gentle panic, but until then it is a normal delay in the publishing workflow :-)

To get it immediately, you can:
-  `opam init https://github.com/ocaml/opam-repository.git` on a new repository 
- `opam repo set-url default https://github.com/ocaml/opam-repository.git` to an existing installation

which will fetch the packages directly and bypass the OPAM HTTP mirror.

regards,
Anil

> On 17 May 2017, at 00:00, Helmut Brandl <helmut.brandl@gmx.net> wrote:
> 
> I have done the `opam update` already. The merge is visible in the github opam repository. However it is not (yet?) visible via the website “https://opam.ocaml.org/packages/ <https://opam.ocaml.org/packages/>”.
> 
> 
>> On May 16, 2017, at 10:55, Romain Calascibetta <romain.calascibetta@gmail.com <mailto:romain.calascibetta@gmail.com>> wrote:
>> 
>> Hi,
>> 
>> You need to launch `opam update` before :) !
>> 
>> Regards,
>> 
>> Romain Calascibetta
>> 
>> On Tue, May 16, 2017 at 10:53 PM Helmut Brandl <helmut.brandl@gmx.net <mailto:helmut.brandl@gmx.net>> wrote:
>> Sorry for my impatience. I’ve just got the message that my pull request has been merged.
>> 
>> However the package is not yet installable via the command ‘opam install alba’. Does this only take some time as well?
>> 
>> Regards
>> Helmut
>> 
>>> Begin forwarded message:
>>> 
>>> From: Helmut Brandl <helmut.brandl@gmx.net <mailto:helmut.brandl@gmx.net>>
>>> Subject: [Caml-list] Policy to merge pull requests in the opam repository
>>> Date: May 16, 2017 at 10:38:07 CDT
>>> To: caml users <caml-list@inria.fr <mailto:caml-list@inria.fr>>
>>> Reply-To: Helmut Brandl <helmut.brandl@gmx.net <mailto:helmut.brandl@gmx.net>>
>> 
>>> 
>>> Hello list,
>>> 
>>> I have managed to prepare a new version of the Albatross verifier and want to release the new version in the opam repository.
>>> 
>>> I have done all preparations, i.e. written the needed files opam,descr and url, pinned the version locally, forked the opam repository and created a pull request. My pull request has passed all tests which are triggered by the github workflow automatically.
>>> 
>>> What is the policy to get my pull request merged. Do I just have to wait for feedback or are some other actions needed by me to trigger the merge. It is my understanding that the merge can only be done by people who have write access to the opam repository. How is the frequency?
>>> 
>>> I don’t want to urge anything. I just want to understand the policy.
>>> 
>>> Regards
>>> Helmut
>>> 
>>> -- 
>>> Caml-list mailing list.  Subscription management and archives:
>>> https://sympa.inria.fr/sympa/arc/caml-list <https://sympa.inria.fr/sympa/arc/caml-list>
>>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners <http://groups.yahoo.com/group/ocaml_beginners>
>>> Bug reports: http://caml.inria.fr/bin/caml-bugs <http://caml.inria.fr/bin/caml-bugs>


[-- Attachment #2: Type: text/html, Size: 7310 bytes --]

  reply	other threads:[~2017-05-16 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 15:38 Helmut Brandl
2017-05-16 15:52 ` [Caml-list] Fwd: " Helmut Brandl
2017-05-16 15:55   ` Romain Calascibetta
2017-05-16 16:00     ` [Caml-list] " Helmut Brandl
2017-05-16 16:03       ` Anil Madhavapeddy [this message]
2017-05-16 16:11         ` Helmut Brandl
2017-05-16 15:57 ` Anil Madhavapeddy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=04466E7A-A016-47DE-A16E-CD4A3110B00C@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=helmut.brandl@gmx.net \
    --cc=romain.calascibetta@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).